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

Installing the Agent for NSK

This document describes the hotfix installation procedure for the NSK agent.

A three-character code is assigned to each supported NSK Version. It is shown in the file name of the agent and described in the terminology (NS1 for NSK, Version D40 and later).

Requirements

Network protocol TCP/IP is available.
A User ID has been created for the installation.
Entry #set #informat tacl in the TACLCSTM file for each user who executes jobs in AE.
OSS and NetBatch must be installed in order to be used for job executions.
Ensure that the agent runs with the SUPER.SUPER user in order to avoid problems when processes are canceled.

Supplied Files

The files are packed in an archive file and stored in the subdirectory IMAGE:AGENTS\NSK.

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

Procedure

	1.	Transferring the files to the host

Admin computer
Establish a connection to the host via an FTP client and transfer the two supplied files OINSTALL and UC4AR to a common sub-volume.
The file OINSTALL must be transferred in text mode (code 101) and UC4AR in binary mode (code 0).
Automic stronlgy recommends storing these files in an empty sub-volume.
The file UC4AR is a self-extracting archive that contains all the files that the NSK agent requires.

	2.	Starting the installation procedure

Host
Start a terminal emulation program and log on using the user who should be the program owner.
Change to the sub-volume to which the two files have been transferred.
Set the following command in the TACL input line:

O OINSTALL

This unpacks the file INSTINI in the sub-volume. It must remain in the same sub-volume as the other installation files so that the installation can proceed.

	3.	Adjusting the configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. file INSTINI

Host
The file INSTINI contains several parameters that must be adjusted to your system environment.
Lines that begin with the characters %% are comments.
Blanks can be ignored, they are irrelevant.
Specify the parameters in the following format: <parameter name>=<value>.
The parameter name is predefined and cannot be changed. Its corresponding value depends on your system.
The file INSTINI must be stored in the same sub-volume as all other installation files (OINSTALL, INSTALL).
Automic strongly recommends using empty sub-volumes for volume specifications in order to avoid conflicts with other programs.

Parameter	Description
UC4-PROGRAM-SUBVOLUME=	Sub-volume for the executable agent files.
UC4-STATUS-STORE-SUBVOLUME=	Sub-volume for the StatusStore files of file transfers. The agent automatically created StatusStore files. They store the restart information of active file transfers. This mechanism ensures that aborted file transfers can be restarted from a particular file position (= last restart point). Restart points are created in regular intervals (setting FT_RESTART_INTERVAL in the variable UC_HOSTCHAR_DEFAULT). On Nonstop systems, the StatusStore files are the following 4 Enscribe Files with the default names: UC4SST, UC4SSD, UC4SSL, UC4SSH. You can subsequently change these file names in the agent's INI file.
UC4-STATUS-STORE-AUDITED=	Stores StatusStore files of file transfers as Audited Files (TMF protection). Allowed values: "Y" (recommended default value) or "N"
UC4-TCPIP-PROCESS=	Name of the NonStop TCP/IP process name that should be used by the agent. By default, $ZTC0 is specified (system standard). If you specify a different process name, the required ADD DEFINE TACL statement is automatically inserted in the startup obey file.
UC4-SERVER-PORT	Port number of the Automation Engine's communication process to which the agent should connect. Ensure that all affected firewalls are configured for this port.
UC4-AGENT-PORT=	Port number that should be used by the agent in order to contact other agents. This port cannot be used by other programs.
UC4-SERVER-IP-ADDRESS=	IP address or computer name of the Automation Engine.
UC4-AGENT-PROCESS=	Process name of the agent process.
UC4-OC-PROCESS=	Process name of the AE output collector process.
UC4-TSIM-PROCESS=	Process name of the AE terminal simulator process.
UC4-SYSTEM-NAME=	Logical name of the AE system (Automation Engine).
UC4-AGENT-NAME=	Logical name of the agent instance. By default, the system name of the NonStop Server without "\" is used as the agent name: AE-AGENT-NAME=%NODENAME% You can also extend the agent name using pre- or postfixes. For example: AE-AGENT-NAME=UC4%NODENAME%EXE
UC4-TEMP-SUBVOLUME=	All temporary files, such as job reports and job files, are stored in this sub-volume.

The agent's INI file is completed with the data specified here. After the installation, you can change these values at any time.

	4.	Continuing the installation

Host
Set the following command in the TACL input line:

RUN INSTALL
You receive notifications about the installation progress and can terminate it at any time. In this case, a manual cleanup process can be required.
A connection to the Automation Engine is established when the installation is complete.

Admin computer or Server computer
Verify that the agent is logged on.
- Start the UserInterface for client 0000. Information about agents is available in the System Overview. Newly logged-on agents have not been assigned a client, so they can only be viewed in client 0000. The newly installed agent can then be assigned to clients with the required rights via the Agent object.

	5.	Starting and stopping the Agent

Host
Change to the agent's subvolume and set the following command in the TACL input line:

O EXSTART
The following command stops the agent:

O EXSTOP