This document guides you through the new installation of a BS2000 agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host.
Various BS2000 versionsAn application version holds zero or more deployment packages and may have dependencies to zero or more application versions of the same (or to different) applications require their own agent; a one-character code is assigned to each supported version. This code is part of the agent's file name and is described in the terminology. 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.
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.
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 EngineThis component drives an Automation Engine system and consists of different types of server processes. 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 | CallAPIA programming interface that processes a script in the Automation Engine system. It can be called directly from within the program itself or from a different program. Utility | |
UCXEB2?U |
Utility for the console eventAction that is triggered if particular conditions apply. It can be an Automation Engine object type or an entry in a Policy Orchestrator EventBase. (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.
![]() |
1. | Transferring TAR files to the hostComputer, target system. |
---|
/FILE UCXJB2?.TAR,LINK=TAR
or /FILE UCXJB2?NK4.TAR,LINK=TAR
/EXEC BS2-TAR
Show $UC4. Enter the command TAR into the command field next to the TAR file.
The file UCXJB2?M must be shareable, and the userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. 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.
![]() |
3. | Starting the Agent |
---|
Set priority and category.
An agent objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task is automatically created in system clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients.
A particular Automation Engine object type. 0000 and
stored in the folderTop level entities such as Environment, Deployment Target, Activity, … are stored in folders. The permissions a user has on an entity depend on the permissions that are set on the folder for the entities. HOST.
![]() |
4. | Shutting down the Agent |
---|
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |