Add an Agent or Advanced Integration to the Topology

You can add an agent to the Topology to work with the server.
cwad121
HID_add_agent
You can add an agent to the Topology to work with the server.
Similar to agents, you can also add advanced integrations such as Advanced Integration for Hadoop to the Topology.
Follow these steps:
 
  1. Connect to the server as an administrator using CA WA Desktop Client.
  2. Open the Admin perspective.
  3. Right-click Topology in the Admin view, and select Open from the pop-up menu.
    The Topology view opens.
  4. Right-click the Agents/Advanced Integrations node in the Topology view, and select New Agent/Advanced Integration from the pop-up menu.
    The Agent/Advanced Integration Definition view opens.
    The number in parentheses beside the Agents/Advanced Integrations node displays the number of agents that have been added to the Topology.
  5. Select the type of agent you want to add in the Select the agent/advanced integration type to define drop-down list.
    The Properties tab opens.
  6. Complete the following fields as appropriate:
    • Name
      Identifies the name of the agent or advanced integration.
      Limits
      : Up to 16 characters
      • The name must match the agentname parameter in the agentparm.txt file. If you are adding an agent plug-in that has an alias, the name must match the communication.alias_
        n
         parameter, where 
        n
         represents the sequential number of the agent plug-in.
      • The name is forced to uppercase. Verify that the name in the agentparm.txt file is in uppercase; otherwise, the server and the agent cannot communicate.
      • An agent cannot have the same name as a user that is defined in the Security view.
    • Description of this agent/advanced integration
      (Optional) Specifies a description for the agent or advanced integration.
    • Address
      Specifies the IP address or DNS name of the computer where the agent or advanced integration is installed.
    • Port number
      Specifies the IP port number that the agent or advanced integration uses to listen for traffic.
      Default:
       7520
      Limits:
       1024-65534
      This port number must match the communication.inputport parameter in the agentparm.txt file.
    • Character code
      Indicates whether the character code is ASCII or EBCDIC.
    • Release number
      Identifies the release number of the agent or advanced integration.
    • Encryption key used from server to agent/advanced integration
      Specifies the encryption key the agent or advanced integration uses to communicate with CA Workload Automation DE.
      • CA Workload Automation DE and the agent or advanced integration must have the same encryption key to communicate. The encryption key of the agent or advanced integration is stored in a text file (encrypted).The security.cryptkey parameter in the agentparm.txt file sets the path of that file. If the keys are different, CA Workload Automation DE and the agent or advanced integration cannot communicate and an AGENTDOWN state occurs when you try to run workload. In the agent or advanced integration definition, you specify the encryption key (unencrypted) without the Ox prefix.
      • If you select NONE in the Encryption Method field, set this value to NOENCRYPTION.
    • Encryption key used from agent to server
      (z/OS Agents only) Specifies the encryption key used from agent to server. Use the same value as specified in the Encryption key used from server to agent field.
    • Name that the agent uses to communicate with the server
      (z/OS Agents only) Specifies the name the agent uses to communicate with the server. The value must match the values specified in the COMMCHAN and EXTSCHED initialization parameters defined in the AGENTDEF data set. The value must be unique for each z/OS Agent that is defined in the Topology.
      Limits:
       Up to 16 characters
    • SNMP Enabled
      Indicates whether SNMP is enabled.
      Default:
       false
      If you select True, you need to update the SNMP information in the agentparm.txt file.
    • Heartbeat Frequency (in minutes)
      Specifies the frequency with which you want the server to send the heartbeat signal in minutes.
      Default: 
      5
      Limits:
       0 and above
      If you want individual agents or advanced integration to have their own heartbeat frequencies, you can set the shared configuration parameter Global Agent heartbeat frequency to 0 (zero).
    • Heartbeat attempts before sending an SNMP notification
       
      Specifies the number of heartbeat signals the server attempts before it sends an SNMP message indicating agent or advanced integration inactivity.
      Default:
       1
      Limits:
       1 and above
    • Remember Manager address changes between restarts
      Indicates whether changes to server properties that affect agent or advanced integration communication are permanently changed on the agent. If you change the ID, address, or port of the server in the Topology, the server sends the agent or advanced integration the updated server connection information at the next heartbeat signal, allowing the server and agent or advanced integration to communicate. Options are as follows:
      • true
        Updates the communication parameters in the agentparm.txt file with changes made to the corresponding properties in the server Topology. For example, if you change the server address and port in the Topology, the communication.manageraddress_
        n
         and communication.managerport_
        n
         parameters in the agentparm.txt file are updated with the new server address and port.
      • false
        Updates the server connection information every time the agent or advanced integration is restarted, allowing the server and agent or advanced integration to communicate for that session only. The communication changes are not saved in the agentparm.txt file.
      Default:
       true
    • Encryption Method
      Specifies one of the following encryption methods CA Workload Automation DE uses to encrypt messages:
      • DES—Specifies Data Encryption Standard encryption. DES uses a 56-bit key. Encryption key length: 56 bits (16 hexadecimal characters). This key length is the default.
      • DESEDE—Specifies 3DES encryption. DESEDE uses the DES algorithm in EDE (encrypt-decrypt-encrypt) mode. Encryption key length: 192 bits (48 hexadecimal characters).
      • AES—Specifies Advanced Encryption Standard encryption. AES uses a 128-bit key. Encryption key length: 32 hexadecimal characters.
      • BLOWFISH—Specifies Blowfish encryption. BLOWFISH uses a 64-bit block and a variable key length. Encryption key length: 32 to 64 even number of hexadecimal characters.
      • NONE—Specifies no encryption.
      • CA Workload Automation DE supports the U.S. Government encryption standard FIPS 140-2 and can be configured to run in a FIPS-compliant mode. Your CA Workload Automation DE environment can be considered FIPS-compliant only if all the components use FIPS-compliant algorithms for encryption and decryption. Currently, only AES and DESEDE algorithms are FIPS-certified. If any of your CA Workload Automation DE components use DES or BLOWFISH, your system is not FIPS-compliant.
      • If you specify NONE as the encryption method, the security.cryptkey parameter in the agentparm.txt file must be set to no value.
  7. (Optional) Do the following to add a virtual agent to a Tandem or OpenVMS parent agent, if necessary:
    1. Select the Virtual Agent tab.
    2. Enter the parameter values for the virtual agent.
       You can enter the port number of the virtual agent in the Address field using the format 
      address:port
      , for example, myVirtualHost:45678.
      The virtual agent is defined.
  8. (Optional) Do the following to define agent users if an agent user specified in a job definition requires a password:
    1. Select the Users tab.
      For a Tandem or OpenVMS parent agent, you need to select Virtual Agent, Users tab.
    2. Click Add User.
      The Add Agent User dialog opens.
    3. Complete the following required fields:
      • User ID—Specifies the agent user ID. This value is case sensitive.
      • Password—Specifies the password for the agent user.
      • Confirm password—Specifies the password for the agent user.
    4. Click OK.
      The agent user is defined.
  9. Click Save at the top right corner of the view.
    The agent is added to the Topology.