Installing the Agent › How to Install the Agent Using a Silent Installer › Silent Installer Properties

Silent Installer Properties

The installer.properties file contains the following properties for the agent:

USER_INSTALL_DIR

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

USER_INSTALL_LIBRARY

Specifies the library on the system where the native i5/OS objects will be stored. The specified library must be empty.

AGENT_INFO_1

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.

AGENT_INFO_2

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

NUM_MANAGER_N=N

Specifies the number of scheduling managers (N) the agent works with.

Default: NUM_MANAGER_1=1

MANAGER_n_INFO_1

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

MANAGER_n_INFO_2

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_INFO_3

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

STRONG_ENCRYPTION_CIPHER

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

STRONG_ENCRYPTION_KEYGEN

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

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.

• off—Disables local security
• on—Enables local security

Default: off

The following properties apply if you want to connect the agent to an SNMP manager.

SNMP_MGMT_CONN

Enables an SNMP connector that lets you use an SNMP Manager to monitor and control the agent. The agent supports SNMP v1, v2, and v3. This option requires the SNMP Manager address and UDP port.

• 0—Disables the SNMP connector
• 1—Enables the SNMP connector

MGMT_SNMP_HOST

Identifies the SNMP Manager IP address or DNS name. Your SNMP administrator can provide the host name.

Default: localhost

Example: 172.24.36.107

MGMT_CONN_AGENT_PORT

Specifies the SNMP GET/SET listening port.

Default: 161

Limits: 1-65535

JMX_PLUGIN

Enables a JMX connector that lets you use a JMX console to monitor and control the agent. You can use any JMX console that implements JSR-160.

• 0—Disables the JMX connector
• 1—Enables the JMX connector

JMX_CONNECTOR_PORT

Specifies the port where the JMX connector listens.

Default: 1099

Limits: 1-65534

FTP_PLUGIN

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

• 0—Disables the FTP plug-in
• 1—Enables the FTP plug-in

Default: 0 (disabled)

FTP_SSL_CLIENT_ENABLED

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

• true—Enables SSL encryption
• false—Enables regular encryption

Default: false

FTP_NO_SERVER

Sets whether the agent can act as an FTP server.

• true—Disables FTP server
• false—Enables FTP server

Default: true

FTP_SSL_SVR_ENABLED

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

• true—Enables SSL encryption
• false—Enables regular encryption

Default: false

FTP_SVR_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

FTP_PASSWORD_V

Confirms the FTP password.

SNMP_PLUGIN

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.

• 0—Disables the SNMP plug-in
• 1—Enables the SNMP plug-in

Default: 0 (disabled)

SNMP_P_TRAP_PORT

Specifies the agent port listening for trap information.

Default: 162

Limits: 1-65535

NUM_MANAGER_VARS_2

Specifies the number of manager environment variables for the scheduling manager.

Limits: 0-3

MANAGER_VARS_n_INFO_1

Specifies the name of the specific scheduling manager the environment variables apply to, where n is an integer that corresponds to the scheduling manager being configured.

Example: MANAGER1_VAR

MANAGER_VARS_n_INFO_2

Specifies the path to the file that stores the environment variables, where n is an integer that corresponds to the scheduling manager being configured.

Example: ~/MANAGER_1_FILE.TXT

NUM_USER_VARS_2

Specifies the number of user environment variables for the scheduling manager.

Limits: 0-3

USER_VARS_n_INFO_1

Specifies the name of the user the environment variables apply to, where n is an integer that corresponds to the scheduling manager being configured.

Example: USER1

USER_VARS_n_INFO_2

Specifies the path to the file that defines user-specific variables.

Example: ~/USER_1_FILE.TXT

LOOKUPCMD

Determines how to specify the script or command name to run in a job definition.

• true—The script or command name can be specified without the full path in a job definition.The agent looks up the path to the script or command name for the specified user ID.
• false—The full path to the script or command name must be specified in the job definition.

Default: true

JOBLOG

Sets whether the agent creates a job log for each UNIX job that runs on the i5/OS system.

• true—Enables job logs
• false—Disables job logs

Default: false

Note: These job logs are different than the job logs the i5/OS system creates.