Agent Installation Options

Installing the Agent › Agent Installation Options

Agent Installation Options

The interactive agent installation program prompts you for the following information:

Installation Path

Specifies the path to the location where you want to install the agent program files. The specified location must be empty.

Default: ~/CA/ CA_WA_Agent_R11_3 where ~ is the user home directory that is installing the agent

Library

Defines the name of the library that contains the objects the agent requires.

Default: CAWAGNT113

Notes:

The library can exist, but the library must be empty.
This library cannot be the same library used for another agent installed on the same i5/OS system.

AgentParm File Conversion

Indicates whether or not the installation program preserves settings for a r7.0 agent by converting the existing agentparm.txt file.

Yes—Preserves the parameter settings from the previous release of the agent
No—Does not preserve the parameter settings from the previous release of the agent

Default: No

Path to agentparm.txt file

Specifies the path to an existing agent installation directory for a r7.0 agent. When you specify this path, the installation program converts the agentparm.txt file in this directory to an R11.3 version.

Default: /home/Cybermation/ESP_System_Agent_R7

Agent Name

Defines the agent name. You need the agent name when you configure the scheduling manager to work with the agent.

Default: AGENT

Limits: Up to 16 characters; the first character must be a letter

Notes:

Agent names must begin with an alphabetic character and can contain any alphanumeric characters and the special characters @, $, and underscore (_). Because the scheduling manager uses agent names as file names, use standard file-naming conventions for your operating system.
For CA Workload Automation DE, the agent name must be in uppercase.

Input Port

Specifies the main port number the agent uses to listen for incoming messages from the scheduling manager. You need this port when you configure the scheduling manager to work with the agent.

Default: 7520

Limits: 1024-65534

Note: On UNIX, ports 1–1023 are reserved ports and require root access.

Number of Managers

Specifies the number of scheduling managers you want to configure to work with the agent.

Default: 1

Manager n ID

Specifies the name of the scheduling manager instance that the agent works with, where n is an integer that corresponds to the scheduling manager being configured.

Default: CENTRAL_MANAGER

Example: MYSERVER

Note: You can configure the agent to work with multiple scheduling managers by adding additional scheduling manager definitions in the agentparm.txt file.

Manager n Address

Specifies the address of the scheduling manager that the agent works with, where n is an integer that corresponds to the scheduling manager being configured. This value corresponds to the IP address in the connection details for the scheduling manager. You can specify a list of addresses for the scheduling manager.

Example: 172.24.36.107 (IPv4) or 0:0:0:0:0:FFFF:192.168.00.00 (IPv6)

Notes:

You can specify a DNS name instead of the IP address for the scheduling manager. However, your agent computer must be able to resolve the DNS name at all times. If there is a DNS outage and your agent computer cannot resolve DNS names, the agent cannot communicate with the scheduling manager.
If the scheduling manager address never changes, enter the DNS name for the scheduling manager in the hosts file for your agent computer. This entry helps ensure that the IP address can be resolved after DNS disruptions.

Manager n Port

Specifies the port that the scheduling manager listens on for communication from agents, where n is an integer that corresponds to the scheduling manager being configured. This value corresponds to the port number in the connection details for the scheduling manager.

Default: 7507

Limits: 1024-65534

Cipher Algorithm

Specifies the type of cipher algorithm the agent uses to encrypt and decrypt messages sent to the scheduling manager. The agent supports the following types:

AES—Advanced Encryption Standard that uses a 32-character encryption key. AES is the algorithm required by U.S. Government organizations to protect sensitive (unclassified) information (FIPS-140-2 compliance).
BLOWFISH—A license-free encryption algorithm that uses an encryption key of 32 to 64 even-numbered characters.
DES—Data Encryption Standard that uses a 16-character encryption key.
DESEDE—Triple Data Encryption Algorithm that applies the DES algorithm three times to each data block.

Default: DES

Encryption Key

Defines the encryption key the agent uses to communicate with the scheduling manager. The encryption key must be prefixed with 0x and followed by the number of characters required for the chosen cipher algorithm:

AES—32 hexadecimal character encryption key.
Note: If you omit the 0x prefix, the keygen utility interprets the inputted value as a 16-character passphrase and not as a hexadecimal number. If you enter less than 16 characters, the keygen utility appends the passphrase with spaces for the missing number of characters. The keygen utility will internally encode the 16 character passphrase into a 32 hexadecimal character AES encryption key.
Blowfish—32-64 even-numbered hexadecimal character encryption key
DES—16 hexadecimal character encryption key
DESEDE—48 hexadecimal character encryption key

Local Security Option

Specifies whether local security on the agent is enabled or disabled. Local security on the agent controls which scheduling manager user IDs can perform certain actions, for example, which user IDs can issue CONTROL messages to the agent. If you enable local security, define security rules in a security.txt file.

Default: disabled

Management Connector Option

Enables the following management connectors:

SNMP Connector

Lets you use an SNMP Manager to monitor and control the agent.You can connect the agent to any SNMP Manager that supports SNMP v1, v2, and v3. This option requires the SNMP Manager address and User Datagram Protocol (UDP) port.

Default: disabled

JMX Connector

Lets you use a JMX console to monitor and control the agent. You can use any JMX console that implements JSR-160. This option requires the input port number for the JMX console.

Default: disabled

Remote SNMP Manager Trap Listener Host

Specifies the SNMP trap receiver host name.

Default: localhost

Note: This value applies to the SNMP management connector option.

SNMP Agent Port

Specifies the SNMP GET/SET listening port.

Default: 161

Limits: 1-65535

Note: This value applies to the SNMP management connector option.

JMX Communication Port

Specifies the input port number for the JMX console.

Default: 1099

Note: This value applies to the JMX management connector option.

Enable FTP Plug-in

Enables the FTP plug-in on the agent, which lets you configure FTP client and FTP server options.

Default: disabled (unselected)

FTP Client Information

Specifies whether the agent can act as an FTP client using Regular or Secure Sockets Layer (SSL) encryption for FTP transfers.

Default: Regular Client Transfer

FTP Server Information

Specifies whether the agent can act as an FTP server using regular or Secure Sockets Layer (SSL) encryption for FTP transfers.

Default: Disable FTP Server

FTP Server Port

Specifies the port number for the agent to act as an FTP server.

Default: 21

Limits: 1-65534

FTP User ID

Specifies the FTP user ID required to access the FTP server.

FTP Password

Specifies the password corresponding to the FTP user ID.

Limits: case-sensitive

Verify FTP Password

Confirms the FTP password.

SNMP Job Type Support Configuration

Enables the agent to act as an SNMP Manager to emit and listen for SNMP traps. This option lets users define and run SNMP job types. The agent supports SNMP v1, v2, and v3.

Default: disabled (unselected)

SNMP Trap Listener Port

Specifies the agent port listening for trap information.

Default: 162

Limits: 1-65535