Installing the Agent for Siebel (Windows)

This document guides you through the installation of a Siebel agent.

Notes:

  • The following guide describes how to install an agent in an AE 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.

  • It is best to install the agent in a separate directory (such as C:\AUTOMIC\Agent\SIEBEL).

This page includes the following:

Supplied Installation Files

The files are found in the directory IMAGE:AGENTS\SIEBEL\WINDOWS.

  • File name: UCXJSLX.EXE
    Description: Siebel agent

  • File name: UCXJSLX.INI
    Description: INI file for Siebel agent

  • File name: UC.MSL
    Description: Message library

  • File name: ZU00132.DLL
    Description: Runtime library for shared functions

  • File name: ZUSYNCHK.DLL
    Description: Runtime library for syntax checks

  • File name: SETUP.EXE
    Description: Installation program.

Additional files in this sub-directory are components of the installation program and the AE runtime system.

Connecting to the Automation Engine

The Automation Engine and the Windows, UNIX, and Java Agents communicate using TLS/SSL. These agents establish a connection with the Java communication process (JCP), which uses trusted certificates to prove their identity to other communication partners.

Note: The TLS/SSL implementation does not apply to the HP-UX Agent, as it is no longer supported in this version.

You can use the trustedCertFolder=, agentSecurityFolder=, and keyPassword= parameters in the respective INI file to point to the relevant certificates. If the trustedCertFolder= parameter is not set, the certificates should be installed in the respective store; that is the Java trust store for Java Agents, the Windows OS store for Windows Agents, or the TLS/SSL store for UNIX Agents. For more information, see Securing Connections to the AE (TLS/SSL).

For more information about the different certificate types and for detailed instructions on how to create and use them, see What Kind of Certificates Should I Use for Automic Automation v21.

TLS/SSL Agents (in containers or on-premises) and the TLS Gateway, when used for the Automic Automation Kubernetes Edition, establish a connection to an ingress / HTTPS load balancer and not the JCP directly. The ingress / HTTPS load balancer must be reachable and requires a certificate for authentication. The address of the load balancer must be defined on both sides: the Automation Engine and the Agent / TLS Gateway.

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 Siebel (Windows)

  1. On the host computer, install the Microsoft Visual C++ 2017 redistributable package from the IMAGE:CRTS directory.

    This installation step can be ignored if the required version of the package is already installed.

  2. On the host computer, install the agent and set up the system environment.

    1. Start the program SETUP.EXE in the directory IMAGE:AGENTS\SIEBEL\WINDOWS.
      You can change the drive if necessary. For the installation target, you must use the directory C:\AUTOMIC\AGENTS\SIEBEL. Start installation by clicking the big button (computer, packaging and diskette).

      The AE program group is automatically created and the agent is entered.

    2. Adjust the INI file (UCXJSLX.INI) of the Siebel agent to your system environment. For more information, see Agent Siebel.

      Use the trustedCertFolder=, agentSecurityFolder=, and keyPassword= parameters in the respective INI file to point to the relevant certificates. If the trustedCertFolder= parameter is not set, the certificates should be installed in the respective store; that is the Java trust store for Java Agents, the Windows OS store for Windows Agents, or the TLS/SSL store for UNIX Agents. For more information, see Securing Connections to the AE (TLS/SSL).

      For more information about the different certificate types and for detailed instructions on how to create and use them, see What Kind of Certificates Should I Use for Automic Automation v21.

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

  3. On the server computer, start the agent.

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

    2. On the host, start the Agent from the AE program group.

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

    3. On the admin or server computer, 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.

  4. On the host computer, shut down the agent. To do so, right-click the agent in the task bar and select Exit.

You can use the ServiceManager to start and end the agent as a service. For more information, see ServiceManager.

See also: