Previous Topic: Configure Additional OptionsNext Topic: Configuration Files


Configure Communications

After agent installation, you can add communication to additional CA Workload Automation ESP Edition scheduling managers or correct errors in your original communication configuration.

To configure communications

  1. Ping the scheduling manager node.

    Attempt to PING the scheduling manager node. If you cannot, modify the TCP/IP setup on the HP Integrity NonStop computer and on the scheduling manager computer.

    This requires a DNS entry or an entry in the HP Integrity NonStop computer's $SYSTEM.ZTCPIP.HOSTS file for the server where the scheduling manager is installed.

  2. (Optional) Update the CAHOSTS file as necessary.

    A CAHOSTS file is created depending on which scheduling manager is selected. This file is updated automatically for CA Workload Automation AE and a separate file is created for CA Workload Automation ESP Edition and CA Workload Automation CA 7 Edition.

    CAHOSTS is an EDIT File that stores the manager ID, manager address, and manager port. The HOST-FILE-LOCATION parameter in the agent configuration file CAOPTS indicates the present location of the created file. If this parameter is not present in the configuration file, the file is created in the location of CAOPTS – Options configuration file.

    This file has the following format:

    mgr_id=manager_id
    mgr_addr=manager_address
    mgr_port=manager_port 
    
  3. Determine the status of the remote server.

    The remote server must be running. To determine whether it is running, issue the unifstat command.

    A series of messages appears indicating the status of servers. If the remote server is running, the following message appears:

    CCI Remote Server nnn running

    nnn

    Specifies the process ID of the Remote Server process.

  4. Start the HP Integrity NonStop agent.

    If you modify the agent options or determine that not all of the agent is running when the unifstat command is issued, you must stop and restart the agent.

    To stop and restart the agent, log in as SUPER.SUPER and run the following command:

    unicycle all