Installing the Agent for OS/400

This page guides you through the installation of an OS/400 Agent in an Automation Engine 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 Agent Authentication.

A three-figure abbreviation is provided for each supported OS/400 version. It is part of the agent's file name.

This page includes the following:

Requirements

  • TCP/IP

For information about CallAPI files and their implementation, see CallAPI for OS/400.

Connecting to the Automation Engine

Important! The Automation Engine uses TLS/SSL to communicate only with the Windows, UNIX, and Java Agents. This particular Agent is not a TLS/SSL Agent and therefore connects to a communication process (CP) and uses non-TLS/SSL encryption. The communication between a TLS/SSL and a non-TLS/SSL Agent can be established using the TLS Gateway.

More information:

Non-TLS/SSL Agents, when used for the Automic Automation Kubernetes Edition, establish a connection to a TCP load balancer, which must be reachable for the Agent. The address of the load balancer must be defined on both sides: the Automation Engine and the Agent.

Important! When you install or upgrade Agents manually for an Automic Automation Kubernetes Edition system, you have to make sure that you configure your Agents and/or TLS Gateway to reach the TCP or HTTPS load balancer and not the CP or JCP directly. Also, make sure that your HTTPS load balancer has the required certificates in place. For more information, see Connecting to the AAKE Cluster.

Installing the Agent for OS/400

There are two different methods.

Method 1

  1. Transfer the file to the host, and adjust the library and INI file.

    Start the installation with the supplied file installer.jar:

    java -jar installer.jar /LIB UC4 /SAVF ucxjo41.bin

    If you do not provide the parameters for system, user and password here, a dialog will open where you can enter these credentials.

    The installer automatically transfers the binaries and adjusts the initial library path of the INI files to the specified library.

    Alternatively, you transfer the file to the host computer manually:

    1. Create a library for restoring the Save File:

      CRTLIB LIB(UC4TMP) TYPE(*PROD) TEXT('UC4 Agent')

    2. Create an empty Save File.

      CRTSAVF FILE(UC4TMP/UC4)

    3. On the admin computer, log on to the AS/400 via FTP and transfer UCXJO41.bin to the Save File UC4, library UC4TMP. Example for FTP via the Windows command prompt:

      ftp <MY.AS400>
      <USER>
      <PASSWORD>
      cd UC4TMP
      bin
      put UCXJO41.bin UC4
      quit

  2. On the host, create the library.

    1. Create a library for restoring the Save File:

      CRTLIB LIB(UC4) TYPE(*PROD) TEXT('Automic Agent')

    2. Restore the objects into the UC4 library. If this library contains objects, they will be replaced.

      RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF) SAVF(UC4TMP/UC4) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(UC4)

    3. Remove temporary library and Save File:

      DLTLIB LIB(UC4TMP)

  3. Set up the system environment.

    1. On the server computer, make sure that the AE system is running on the server computer. For more information, see Multi-Server Operations.

    2. On the host, adjust the INI file (UC4/INI - UCXJO41) of the OS/400 agent. For more information, see Agent OS/400.

    3. On the admin or user computer, adjust the HEADER.OS400, TRAILER.OS400 and RESTART.OS400 if necessary. For more information, see Executing Jobs.

    There are two different methods that can be used to start the agent:

    • Method 1 requires a CL routine per agent that should start (more complex)

    • Method 2 starts or ends the agent via separate programs

  4. On the host, create the start and end programs.

    The CL example programs that start and end the agent are provided in the supplied file member CLLE. They must be adjusted to the installation and the OS before you can compile them.

    Start the agent: UC4/CLLE(UCEX_RUN)

    End the agent: UC4/CLLE(UCEX_END)

  5. Start or end the agent.

    1. On the host, you can use the UCEX_RUN program to start the agent.

      An Agent object is automatically created in the system client 0 and stored in the HOST folder.

      The UCEX_END program ends the agent.

      2. In AWI, client 0, verify that the Agent is logged on to the Automation Engine.

      Newly logged on Agents are not assigned to a client automatically and can only be viewed in Client 0. Once you have logged in to Client 0, access the Administration perspective and select Agents & Groups.

      Assign the new Agent to clients with the required rights using the Agent object definition. For more information, see Authorizations Page.

Method 2

  1. Transfer the file to the host, and adjust the library and INI file.

    Start the installation with the supplied file installer.jar:

    java -jar installer.jar /LIB UC4 /SAVF ucxjo41.bin

    If you do not provide the parameters for system, user and password here, a dialog will open where you can enter these credentials.

    The installer automatically transfers the binaries and adjusts the initial library path of the INI files to the specified library.

    Alternatively, you transfer the file to the host computer manually:

    1. Create a library for restoring the Save File:

      CRTLIB LIB(UC4TMP) TYPE(*PROD) TEXT('UC4 Agent')

    2. Create an empty Save File.

      CRTSAVF FILE(UC4TMP/UC4)

    3. On the admin computer, log on to the AS/400 via FTP and transfer UCXJO41.bin to the Save File UC4, library UC4TMP. Example for FTP via the Windows command prompt:

      ftp <MY.AS400>
      <USER>
      <PASSWORD>
      cd UC4TMP
      bin
      put UCXJO41.bin UC4
      quit

  2. On the host, create the library.

    1. Create a library for restoring the Save File:

      CRTLIB LIB(UC4) TYPE(*PROD) TEXT('Automic Agent')

    2. Restore the objects into the UC4 library. If this library contains objects, they will be replaced.

      RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF) SAVF(UC4TMP/UC4) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(UC4)

    3. Remove temporary library and Save File:

      DLTLIB LIB(UC4TMP)

  3. Set up the system environment.

    1. On the server computer, make sure that the AE system is running on the server computer. For more information, see Multi-Server Operations.

    2. On the host, adjust the INI file (UC4/INI - UCXJO41) of the OS/400 agent. For more information, see Agent OS/400.

    3. On the admin or user computer, adjust the HEADER.OS400, TRAILER.OS400 and RESTART.OS400 if necessary. For more information, see Executing Jobs.

  4. On the host, include the library in the library list.

    The library (UC4) that includes the programs (such as the agent or CallAPI) must be included in the library list. You can use the following commands for this purpose:

    • Add the library to the library list: ADDLIBLE UC4

    • Change the current library for the particular job to UC4: CHGCURLIB UC4

  5. On the host, start or end the agent.

    • Start the agent by using the STRUCAGENT command.

      Examples

      The following examples explain the agent's starting procedure:

      STRUCAGENT LIB(UC4) FILE(UC4/INI) MBR(UCXJO41)

      Starts the agent from the library by using the INI file UC4/INI(UCXJO41).

      STRUCAGENT LIB(UC4) PATH('/user/uc4/ucxjo41.ini')

      Starts the agent from the library by using an INI file that is stored in the IFS file system.

    • The ENDUCAGENT command ends the agent.

      Examples

      ENDUCAGENT LIB(UC4) OPTION(*CNTRLD)

      Ends the agent that has been started from the library in a controlled manner. This is the same as the ENDJOB command issued on the agent process.

      ENDUCAGENT LIB(UC4) OPTION(*IMMED)

      Aborts the agent that has been started from the library with ENDJOB OPTION(*IMMED).

    For more information, see OS/400 Agent - Commands.

See also: