Administration Guide > Installation > Service Pack and Hotfix Installation > Installing the Agent for BS2000

Installing the Agent for BS2000

This document describes the hotfix installation procedure for the 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.

Because each BS2000 version requires its own agent, a one-character code has been assigned to each supported version. This code is used in the agent's file name and is described in the Terminology . In this document, the specific code has been replaced by the character "?."

Close the agent before you start the update installation.

Requirements

Supplied Installation Files

The files are packed in TAR files. The corresponding TAR file for each BS2000 version is found in the subdirectory IMAGE:AGENTS\BS2000. The file names indicate the current Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. version. In the table below, the version has been replaced by the characters "x.xxx."

TAR files that contain "NK4" in their names are for NK4 pubsets and can also be unpacked with 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

 The CallAPI files and CallAPI implementation are described in a separate document.

 


Procedure

1. Transferring the TAR files to the hostComputer, target system.
2. Unpacking the TAR files and setting up the system environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications.

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH