Installing the Agent for BS2000

This document guides you through the new installation of a BS2000 agent.

Various BS2000 versions require their own agent; a one-character code is assigned to each supported version. This code is part of the agent's file name. In this document, the specific code is replaced by the character "?."

The following guide describes how to install an agent in an AE 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 Advanced Security.

Requirements

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 table shown below, the version is represented by the characters "x.xxx."

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

File name Description
x.xxx.UCX2?.LIB 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? Utility for RFC task
x.xxx.UCXJB2?.INI INI file for BS2000 agent

x.xxx.UCXEB2?U.INI

INI file for the utility

x.xxx.UCYEBXXZ

Utility for recalling commands through a console (only for console events)

x.xxx.E.UCXJB2?

Sample - Enter file for BS2000 agent

x.xxx.E.UCXEB2?U Sample - Enter file for the utility

x.xxx.UCX.MSL

Message Library

CalAPI files and their implementation are described in a separate document.

Potential Problems

Procedure

1. Transferring TAR files to the host
2. Unpacking the TAR files and setting up the system environment

The UCYBRFC? file must be shareable if the RFC mechanism is activated.

3. Starting the Agent
4. Shutting down the Agent