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

Installing the Agent for VMS

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

Each supported VMS version is assigned a two-character code. This code appears in all file names of the agent and is described in the Terminology. Throughout this document the specific code will be represented by "??."

In VMS, text strings that are used to enter commands and call files, for example, are case-insensitive. Any combination of uppercase or lowercase letters is acceptable. In this document, uppercase letters are used, except when describing commands of the program FTP.EXE, which can only be entered in lower case.

Close the agent before you start the update installation.

Requirements

Supplied Installation Files

The files that match each VMS version are found in the respective subdirectory of IMAGE:AGENTS\VMS .

File name

Description

Destination directory

File type

uc$crdir.com

Command file that creates directories and determines authorizations

CMD

Text

uc$start.com

Command file for starting the agent

CMD

Text

uc$stop.com

Command file for deactivating the agent

CMD

Text

uc_start.com

Help command file for starting the agents

CMD

Text

uc4$startup.com

Command file (1) for automatically starting the agent

SYS$STARTUP

Text

uc4$startup_bat.com

Command file (2) for automatically starting the agent

SYS$STARTUP

Text

ucx.msl

Message library

BIN

Text

ucxe???f.exe

For file eventAction that is triggered if particular conditions apply. It can be an Automation Engine object type or an entry in a Policy Orchestrator EventBase.

BIN

Binary

ucxjv??.exe

VMS agent

BIN

Binary

ucxjv??m.exe

Messenger program

BIN

Binary

UCXJV??.INI

INI file

BIN

Text

The CallAPI files and 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. implementation are described in a separate document.

 


Procedure

1. Transferring the command file to the hostComputer, target system.
2. Setting up the directories and authorizations
Directory Authorization
BIN SYSTEM: RE, OWNER: RWED, GROUP: E, WORLD: E
CMD SYSTEM: RWE, OWNER: RWED, GROUP: R, WORLD: -
TEMP SYSTEM: RE, OWNER: RWED, GROUP: WE, WORLD: WE
OUT SYSTEM: RW, OWNER: RWD, GROUP: RW, WORLD: RWE
3. Transferring other files to the host
4. 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.

You can also modify both files on the Admin computer before you transfer them.

 


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

Copyright © 2016 Automic Software GmbH