Installing the Agent for BS2000

This page guides you through the installation of a BS2000 Agent in an Automation Engine system in which authentication is not used. Additional installation steps are required before the Agent can be started and used if you intend to use one of the available authentication methods. For more information, see Agent Authentication.

Various BS2000 versions require their own Agent. A one-character code is assigned to each supported version. This code is part of the file name of the Agent. In this page, the specific code is replaced by the character "?."

Important! The Automation Engine uses TLS/SSL to communicate only with the Windows, UNIX, and Java Agents. This particular Agent is not a TLS/SSL Agent and therefore connects to a communication process (CP) and uses non-TLS/SSL encryption. The communication between a TLS/SSL and a non-TLS/SSL Agent can be established using the TLS Gateway.

More information:

Non-TLS/SSL Agents, when used for the Automic Automation Kubernetes Edition, establish a connection to a TCP load balancer, which must be reachable for the Agent. The address of the load balancer must be defined on both sides: the Automation Engine and the Agent.

Important! When you install or upgrade Agents manually for an Automic Automation Kubernetes Edition system, you have to make sure that you configure your Agents and/or TLS Gateway to reach the TCP or HTTPS load balancer and not the CP or JCP directly. Also, make sure that your HTTPS load balancer has the required certificates in place. For more information, see Connecting to the AAKE Cluster.

This page includes the following:

Requirements

Set the User ID $UC4 in BS2000 with approximately 10.000 PAM pages.
Install the BS2 TAR program in BS2000. Unpack the TAR file from the supplied installation CD. For more information, see Program BS2-TAR and BS2000 Text Archive (TAR file).

This might not be required when using BS2 TOOLS version 2.00W and later. BS2 TOOLS is used to receive files in a text archive and to unpack text archives.

Supplied Installation Files

The files are packed in TAR files. Each respective TAR file is stored in a subdirectory of IMAGE:AGENTS\BS2000, depending on the BS2000 variant. The file name indicates the current Automation Engine version. In the list below, the version is represented by the characters xx.

TAR files that contain NK4 in their names are for NK4 pubsets and can also be unpacked using the BS2-TAR program.

File name: xx.UCX2?.LIB

Description: Program Library

Library Elements:
- UCXBB2?C: CallAPI Utility
- UCXEB2?U: Utility for the console event (UCON connection)
- UCXJB2?: Agent
- UCXJB2?M: Message program for BS2000 Agent
- UCYBRFC?: Service program for RFC task
  
  For more information, see Service Program for Remote Function Call (RFC) Tasks.
File name: xx.UCXJB2?.INI

Description: INI file for BS2000 Agent
File name: xx.UCXEB2?U.INI

Description: INI file for the utility
File name: xx.UCYEBXXZ

Description: Utility for recalling commands through a console (only for console events)
File name: xx.E.UCXJB2?

Description: Sample - Enter file for BS2000 Agent
File name: xx.E.UCXEB2?U

Description: Sample - Enter file for the utility
File name: xx.UCX.MSL

Description: Message Library

For information about CallAPI files and their implementation, see CallAPI for BS2000.

Installing the Agent for BS2000

In the admin computer, transfer the TAR files to the host.

To do so, transfer the TAR file UCXJB2?.TAR or UCXJB2?NK4.TAR via FTP in text mode. As an alternative, you can transfer the TAR file with FTBS2000 or the EDT file transfer (also in text mode) to BS2000.
In the host, unpack the TAR files and set up the system environment:
1. You can unpack the TAR file with BS2 TAR or with BS2 TOOLS:
  - Unpacking with BS2 TAR:
    
    /FILE UCXJB2?.TAR,LINK=TAR or /FILE UCXJB2?NK4.TAR,LINK=TAR
    /EXEC BS2-TAR
  - Unpacking with BS2 TOOLS:
    
    Show $UC4. Enter the command TAR into the command field next to the TAR file.
  The actual installation files are created and the TAR file can be deleted.
2. Remove the prefix from the installation files.
3. Adjust the INI file of the BS2000 Agent and enter job, see Agent BS2000.
4. Adjust HEADER.BS2000, TRAILER.BS2000 and RESTART.BS2000 if necessary, see Executing Jobs.
  
  The file UCXJB2?M must be shareable, and the user ID and file name must correspond to the INI file entry UC_EX_JOB_MD.
  
  The UCYBRFC? file must be shareable if the RFC mechanism is activated, see Service Program for Remote Function Call (RFC) Tasks.
  
  The program library UCX2?.LIB must be shareable for both, the UCXJB2?M and the UCYBRFC? files.
Start the Agent.
1. The AE system must be running (server computer), see Multi-Server Operations.
2. Start the Agent under $TSOS (host) and set priority and category.
  
  An Agent object is automatically created in system client 0000 and stored in the folder HOST
3. On the admin or server computer, verify that the Agent is logged on to the Automation Engine.
  
  Newly logged on Agents are not assigned to a client automatically and can only be viewed in Client 0. Once you have logged in to Client 0, access the Administration perspective and select Agents & Groups.
  
  Assign the new Agent to clients with the required rights using the Agent object definition. For more information, see Authorizations Page.
In the host, shut down the Agent. To do so, quit the Agent using the command /INTR Tsn, END or using the Task Manager of BS2 TOOLS.