Administration Guide > Installation > Service Pack and Hotfix Installation > Installing the Agent for OS/400

Installing the Agent for OS/400

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

A three-figure abbreviation is provided for each supported OS/400 version. It is part of the agent's file name and is described in the Terminology (O41 for OS/400 version V4R1M0 and later).

Terminate the agent before you start the update installation.

Requirements

Supplied Files

The OS/400 agent is supplied as a binary SavFile. This file is found in the subdirectory IMAGE:AGENTS\AS400.

File name AE CD

Description

ucxjo41.bin

OS/400 agent (binary SavFile)

Content:

IRSTRJOB

Utility program for generating jobs

UCXBO41C

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.

UCXJO41

Agent

UCXJO41M

Messenger program for the OS/400 agent

CLLE

CL source files for starting and ending the agent

INI

INI file

MSL

Message library

TMP

Empty text file

STRUCAGENT Program that starts the agent
ENDUCAGENT Program that ends the agent
MAKEMSL Program that generates the message library
COMPRESS, GSS, LIBCPPRNT Service programs (libraries) for the agent, the CallAPI and the MAKEMSL program

 

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


Procedure

1. Transferring the file to the hostComputer, target system.
2. Creating the library
3. 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.

There are two different methods that can be used to start the agent. Variant 1 requires a CL routine per agent that should start (more complex). Variant 2 starts or ends the agent via separate programs. 

Method 1

4. Creating the start and end programs
5. Starting or ending the Agent

Method 2

4. Including the library in the library listShows entities in a grid view
5. Starting or ending the Agent

 


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

Copyright © 2016 Automic Software GmbH