Install or Upgrade the Agent Using a Silent Installer

Install or Upgrade the Agent Using a Silent Installer
For information about either installing the agent for the first time or upgrading an existing version of the agent to a later version, refer to the following procedures.
Upgrading a 32-Bit Agent
 
Version 11.5.00 of the System Agent no longer supports 32-bit platforms. When you upgrade an older 32-bit agent to an 11.5.00 agent, the upgrade replaces the 32-bit agent with a 64-bit agent in the same location. To upgrade a 32-bit agent to version 11.5.00, verify that the agent is installed on a supported platform before you performing the upgrade. See the Platform Support Matrix for information about supported platforms .
Install the Agent
Use a silent installer to automate the installation of multiple agents. By configuring a properties file for each agent, you can run a silent installer for multiple agents instead of installing each agent one by one by using an interactive program.
Follow these steps:
 
Upgrade the Agent
To upgrade an existing installation of the agent to the latest version, run the following command. Note that the command includes an optional property, UPGRADE_BACKUP_LOCATION, which designates an absolute path to a directory for the backup files. The directory must exist before you run the command.
If you do not specify this property, the installer places the backup files in the following location: <
AGENT_UPGRADE_PATH
>/backup
UNIX
 
To use JVM bundled with the installer (Linux, AIX and HPUX Only): 
./setup.bin -i silent -DACCEPT_EULA=ACCEPT -DAGENT_UPGRADE_PATH=<path to existing agent directory> -DUSE_BUNDLED_JVM=true [-DUPGRADE_BACKUP_LOCATION=<absolute path to backup directory>]
To use JVM already installed in the system:
./setup.bin -i silent -DACCEPT_EULA=ACCEPT -DAGENT_UPGRADE_PATH=<path to existing agent directory> -DJVM_PATH=<absolute path to java executable> -DJVM_DOT=<absolute path to the jre directory> [-DUPGRADE_BACKUP_LOCATION=<absolute path to backup directory>]
Windows
 
To use JVM bundled with the installer: 
setup.exe -i silent -DACCEPT_EULA=ACCEPT -DAGENT_UPGRADE_PATH=<path to existing agent directory> -DUSE_BUNDLED_JVM=true [-DUPGRADE_BACKUP_LOCATION=<absolute path to backup directory>
To use JVM already installed in the system:
setup.exe -i silent -DACCEPT_EULA=ACCEPT -DAGENT_UPGRADE_PATH=<path to existing agent directory> -DJVM_PATH=<absolute path to java executable> -DJVM_DOT=<absolute path to the jre directory> [-DUPGRADE_BACKUP_LOCATION=<absolute path to backup directory>]
To upgrade with feedback from installer, remove "-i silent" from the command line
iSeries and HPE Integrity NonStop
 
java -jar setup.jar -DACCEPT_EULA=ACCEPT -DAGENT_UPGRADE_PATH=<
path to existing agent directory
> [-DUPGRADE_BACKUP_LOCATION=
<absolute path to backup directory>
]
  • Do not include a space at the end of the path. If a space exists, the installer exits with an error.
    Example:
    #./setup-linux-x86-64-11.3.06.0-428.bin -i silent -DACCEPT_EULA=ACCEPT -DAGENT_UPGRADE_PATH=/opt/CA/Agent_D1 -DUPGRADE_BACKUP_LOCATION="/opt/agent/ test "
  • You can include a space within the path (not at the end), but you must format it as shown in the following examples:
    In the command line:
    -DUPGRADE_BACKUP_LOCATION="/opt/agent/my backup"
    In the property file:
    UPGRADE_BACKUP_LOCATION="\"/opt/agent/my backup\""
Handle Warning Messages with the AGENT_UPGRADE_FORCE Property
When you use the silent installation method to perform an upgrade, you can select how the agent responds to warnings that may occur. If you want the agent to proceed with the upgrade, regardless of warnings that are issued, use the AGENT_UPGRADE_FORCE property.
By default, this property is set to false, meaning that the agent treats warning messages as failures and stops the upgrade procedure. To have the agent ignore the warning messages and proceed with the upgrade, set this property to true. 
A silent upgrade of a 32-bit 11.3.x agent to a 64-bit 11.5 agent fails when AGENT_UPGRADE_FORCE is not set to true in the silent installer properties file. There is no informational message given in the logs to indicate that the 32-bit to 64-bit agent requires this flag.
Sample Silent Upgrade Properties File
The agent comes with a sample properties file, upgrade.properties, for upgrades on all platforms. You can tailor this file for your use. Open it in a text editor, make changes to the properties, then save it.
This upgrade properties file is included with the product. You can obtain it from either the product DVD or from the product image, which is available from the CA Support website. See Download the Agent and Agent Plug-ins for more information.
Sample Upgrade Properties
AGENT_UPGRADE_PATH
The directory where the version of the agent to be upgraded exists. This parameter is required.
Example:
 AGENT_UPGRADE_PATH=/opt/CA/WA_Agent
USE_BUNDLED_JVM
 
If true, then use the JVM bundled with the installer. If there is no JVM bundled with the installer, an error will occur. This is valid only on Linux, AIX, HPUX and Windows.
Default:
 false
JVM_DOT
Path to the JRE to use for the upgrade. Required if USE_BUNDLED_JVM = false. This property is ignored on iSeries.
Example:
 JVM_DOT=/etc/alternatives/jre_1.8.0
JVM_PATH
 
Path to the Java executable to use for the upgrade. Required if USE_BUNDLED_JVM = false. This property is ignored on iSeries.
Example:
 JVM_PATH=/etc/alternatives/jre_1.8.0/bin/java
AGENT_UPGRADE_FORCE
 If true, the upgrade will not fail due to warnings. If false, the upgrade will fail for warnings as well as errors.
Default:
 false
UPGRADE_BACKUP_LOCATION
 
Identifies a directory to keep the backup file for the agent being upgraded.  The backup data is stored in a timestamped tar file.  This can be used to provide a centralized location for all agent backup files. The default value is a directory named backup located within the upgraded agent's directory.
Example:
 UPGRADE_BACKUP_LOCATION=/opt/agent_backups 
Configure the Installer Properties File
You configure the installer properties file as the first step in performing a silent installation for one or more agents. We recommend that you keep a copy of this file to use as a template.
Follow these steps:
 
  1. Open the installer properties file:
    • On UNIX: unix_installer.properties 
    • On Windows: win_installer.properties 
    • On iSeries: i5_installer.properties 
    • On HPE Integrity NonStop: nonstop_installer.properties
    The installer properties file is included with the product. You can obtain it from either the product DVD or from the product image, which is available from the CA Support website. See Download the Agent and Agent Plug-ins for more information. 
  2. Edit the properties for the agent. To uncomment a property line, remove the # sign.
  3. Save the file.
    The properties are set in the installer properties file. See the following example for a UNIX host installer properties file; note the comments in the example, which point out important aspects of the settings that are sometimes overlooked.
Example: UNIX Host Installer Properties File
 
ACCEPT_EULA=ACCEPT #Make sure ACCEPT_EULA is set to ACCEPT USER_INSTALL_DIR=/opt/CA/WA_Agent AGENTPARM_CONVERT_2=No AGENT_NAME=AGENT AGENT_PORT=7520 # JVM_DOT=<Absolute path to a pre-installed JRE location> # JVM_PATH=<Absolute path to the JRE's JAVA VM executable> #JVM_DOT= #JVM_PATH= NUM_MANAGER_1=1 # Specify the agent property to set the agent service to start # automatically at system startup. #SERVICE_AUTO_START= MANAGER_1_INFO_1=AE MANAGER_1_INFO_2=de.example.com MANAGER_1_INFO_3=7507 #Add more managers #MANAGER_2_INFO_1=DSERIES_QA #MANAGER_2_INFO_2=qa.example.com #MANAGER_2_INFO_3=7507 #Should the spool files be cleaned up on a regular schedule #SPOOL_CLEAN_ENABLE=false #SPOOL_EXPIRE=10D #SPOOL_SLEEP=1D STRONG_ENCRYPTION_CIPHER=AES STRONG_ENCRYPTION_KEYGEN=0x62B9FAD75C91526D4D5BEC1A87CA34 STRONG_ENCRYPTION_FILE=$USER_INSTALL_DIR$$/$cryptkey.txt # If LOCK_STRONG_ENCRYPTION_FILE = true then the encryption # key generated is locked to the Agent instance #LOCK_STRONG_ENCRYPTION_FILE=false #Define ENCRYPTION FILE when defining any encryption algorithm LOCAL_SECURITY=off SNMP_MGMT_CONN=0 JMX_PLUGIN=0 FTP_PLUGIN=1 FTP_NO_SERVER=true SNMP_PLUGIN=0 CA_SOCKET=0 NUM_MANAGER_VARS_2=0 NUM_USER_VARS_2=0 LOOKUPCMD=true JOBLOG=false # Specify the owner and group accounts that will be assigned to # the installed files/directories. #SET_OWNER_ACCOUNT=autosys #SET_GROUP_ACCOUNT=autosys #CREATE_OWNER_AND_GROUP_ACCOUNTS=true #Add more settings as raw data to agentparm.txt RAW_DATA=/opt/CA/additional_parameters.txt # Specify the agent start property to start the agent # automatically after installation is complete #START_AGENT_AFTER_INSTALL=false
You might decide not to define a scheduling manager in the properties file, because the scheduling manager can register itself once the agent is running. To allow agent to start without a manager, add this setting:
communication.nomanagers.abort.disable=true
The silent installer allows entry for any additional settings that are not included by default. Use the RAW_DATA parameter to add instance-specific parameters and settings.
Example of a RAW_DATA file
 
runnerplugin.spool.clean.enable=true runnerplugin.spool.expire=10D runnerplugin.spool.sleep=24H communication.nomanagers.abort.disable=true
The contents of the file that are read as raw data are added to the end of the agentparm.txt file. Because the installer does not validate any of the parameters or settings from the file, it is important to review all the settings before adding them as part of a raw data file.
Silent Installer Properties
The installer properties file contains the following properties for the agent:
  • ACCEPT_EULA
    Indicates whether to accept or reject the license agreement.
    • ACCEPT
      Accepts the license agreement.
    • REJECT
      Rejects the license agreement. The installation is aborted.
    Default:
     REJECT
    The license agreement is not shown during the silent installation. Before you run the silent installer, review the license agreement (license.txt) included with the installation package. Then set ACCEPT_EULA to ACCEPT in the installer properties file.
  • USER_INSTALL_DIR
    Specifies the path to the location where you want to install the agent program files. The specified location must be empty.
    For Windows, use two backward slashes to separate directories in the path.
  • AUTOSYS_MODE
    Indicates whether to configure the agent to behave similar to the CA Workload Automation AE legacy Remote Agent (auto_remote).
    • true
      Configures the agent to behave similar to the CA Workload Automation AE legacy Remote Agent.
      This option is not supported on iSeries and z/Linux systems.
    • false
      Configures the agent for a standard installation. Choose this option unless you use CA Workload Automation AE and want to preserve the legacy Remote Agent functionality.
    Default:
     false
  • ENABLE_AE_FIPS_140_2_COMPLIANCE
    Applies only when AUTOSYS_MODE is set to true. In FIPS mode, CA Workload Automation AE complies with the standards in FIPS 140-2: Security Requirements for Cryptographic Modules established by the U.S. government.
    When using FIPS mode for CA Workload Automation AE, set this property to true to ensure that the jobs run by the System Agent also use FIPS when communicating with CA Workload Automation AE. 
  • AUTOROOT_PATH
    Applies only when AUTOSYS_MODE is set to true. This property specifies the directory where CA Workload Automation AE is installed. 
  • USER_INSTALL_LIBRARY
    (iSeries only) Specifies the library on the system to store the native iSeries objects. The specified library must be empty.
    Default: 
    CAWAAGENT
  • JVM_DOT
    (z/Linux only) Specifies the full path to the JRE directory.
  • JVM_PATH
    Absolute path to the Java executable in the JRE to be used for running the System Agent. For Windows, Linux, HP UX, and AIX, if this property is blank, the bundled JVM will be used. For all other systems, (except iSeries and NonStop) leaving the field blank will cause the installation to fail.
    Example:
     JVM_PATH=C:\\Program Files\\java\\jdk1.8.0\\jre\\bin\\java.exe
  • 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 alphanumeric characters and the special characters @, $, and underscore (_); the first character must be a letter.
    • 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_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
  • 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)
    • You can specify a DNS name instead of the IP address for the scheduling manager. However, your agent computer must always be able to resolve the DNS name. 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 ensures 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
  • SPOOL_CLEAN_ENABLE
     Indicates whether to turn on periodic spool file clean up. This helps prevent the spool files from using up all available disk space.
    Default:
     If AUTOSYS_MODE = true, then true. Otherwise, false.
    • true - Enable spool file clean up
    • false - Disable spool file cleanup
  • SPOOL_EXPIRE
     The length of time to keep spool files on disk before they are cleaned up. The value is a number with one of M for Minutes, H for Hours, or D for Days appended.
    Default:
     If AUTOSYS_MODE=true then 7D, otherwise 10D.
  • SPOOL_SLEEP
     The length of time for the spool clean up daemon to wait between attempts to clean up the spool files. The value is a number with one of M for Minutes, H for Hours, or D for Days appended.
    Default:
     1D
  • STRONG_ENCRYPTION_CIPHER
    Specifies the type of cipher algorithm the agent uses to encrypt and decrypt messages that are sent to the scheduling manager. The agent supports the following types:
    Default:
     DES
    CA Workload Automation AE and CA Workload Automation CA 7 Edition support only AES encryption. To determine which encryption types are supported, consult the documentation for your scheduling manager.
    • AES -- Advanced Encryption Standard that uses a 32-character encryption key. AES is the algorithm that U.S. Government organizations require 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.
  • 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 that are required for the chosen cipher algorithm:
    • CA Workload Automation AE and CA Workload Automation CA 7 Edition support only AES encryption. To determine which encryption types are supported, consult the documentation for your scheduling manager.
    • 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 fewer than 16 characters, the keygen utility appends the passphrase with spaces for the missing number of characters. Internally, the keygen utility encodes the 16-character passphrase into a 32-character hexadecimal character AES encryption key.
    • AES -- 32-character hexadecimal character encryption key.
    • Blowfish -- 32 to 64 even-numbered character hexadecimal encryption key.
    • DES -- 16-character hexadecimal encryption key.
    • DESEDE -- 48-character hexadecimal encryption key
  • STRONG_ENCRYPTION_FILE
    Specifies the path to the text file that stores the encryption key for the agent.
  • 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.
    • on
      Enables local security.
    • off
      Disables 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
The following FTP properties apply if you want to configure the agent to run FTP workload.
  • 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:
     false
  • 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.
The following SNMP properties apply if you want to configure the agent as an SNMP Manager.
  • 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
  • CA_SOCKET
    Enables a connection to CA Workload Automation AE using the CA Secure Socket Adapter (SSA).
    • 0
      Disables the CA Secure Socket Adapter.
    • 1
      Enables the CA Secure Socket Adapter.
    Default:
     0 (disabled)
  • SSA_COMPONENT_PATH
    Specifies the path to the *.so file (UNIX) or *.dll file (Windows) for communication with CA Workload Automation AE using the CA Secure Socket Adapter.
    Default:
    • For UNIX:
      /opt/CA/SharedComponents/Csam/SockAdapter/lib
    • For Windows:
      C:\Program Files\CA\SharedComponents\Csam\SockAdapter\bin
    For UNIX systems, also specify the EWA_SHARED_DIR property.
  • EWA_SHARED_DIR
    Specifies the path to the shared components directory for CA Workload Automation AE.
    Default:
     /opt/CA/SharedComponents
    This property is required for UNIX systems.
  • 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.
    Examples:
     C:\\MANAGER_1\\FILE1.TXT, ~/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.
    Examples:
     C:\\USER1\\FILE1.TXT, ~/USER_1_FILE.TXT
  • LOOKUPCMD
    Determines how to specify the script or command name (UNIX) or command file (Windows) to run in a job definition.
    • true
      Indicates that the script, command name, or command file can be specified without the full path in a job definition. On UNIX, the agent looks up the path to the script or command name for the specified user ID. On Windows, the agent looks up the path to the command file in the following directories, in the order listed:
      • agent installation directory
      • WINDOWS\system32 directory on 32-bit versions of Windows (or WINDOWS\SysWow64 directory on 64-bit versions of Windows)
      • WINDOWS\system directory
      • WINDOWS directory
      • system path
      • user path
    • false
      Indicates that the full path to the script, command name, or command file must be specified in the job definition.
    Default:
     true
    • On CA Workload Automation AE, set this parameter to true for backward compatibility with legacy agents.
    • If set to true, verify that the agent on UNIX is running under the root account.
    • The agent does not resolve environment variables that are specified in the command file path for Windows jobs.
  • JOBLOG
    Sets whether the agent creates a job log for each job that runs.
    • true
      Enables job logs.
    • false
      Disables job logs.
    Default:
     true
    On iSeries, these job logs are different than the job logs the iSeries system creates.
  • WIN_SERVICE_
    n
    Specifies the name of the Windows service for the agent, where 
    n
     is an integer that corresponds to the scheduling manager being configured. You can control the agent on Windows as a service.
    Default:
     CA Workload Automation Agent 11.3
  • RAW_DATA
    Specifies the path to and name of a text file that contains more agent parameters. In the text file, list each parameter on a separate line. During a silent installation, these parameters are inserted at the end of the agentparm.txt file without any validation or modification.
    Example:
     /usr/home/joe/additional_agentparm.txt
  • CUSTOM_AGENTPARM
    Specifies the path to a custom agentparm.txt file that you provide. The default agentparm.txt file is replaced with the file you specify.
  • START_AGENT_AFTER_INSTALL
     
    If true, tells the installer to automatically start the agent after it has been installed.
    Default:
     false 
  • SERVICE_AUTO_START
    If set to true then the agent service is set to start automatically at System Startup.
    Default(s):
     true for AUTOSYS_MODE = true false for AUTOSYS_MODE = false 
The following properties apply if specific owner and group needs to be assigned to the installed files/directories.
  • SET_OWNER_ACCOUNT  (on-Windows systems only)
    The name of the user who will own the installed files and directories.
    Default:
     The user running the installer 
  • SET_GROUP_ACCOUNT
     The name of the group that will own the installed files and directories.  This parameter does not apply on iSeries or Windows
    Default:
     The group assigned to the user running the installation 
  • CREATE_OWNER_AND_GROUP_ACCOUNTS
     If true, then create the assigned owner and group if they do not exist.  This parameter does not apply on Windows, iSeries, or NonStop.
    Default:
     false 
Silent Installer Example
The following example shows the property settings for installing an agent using the silent installer.
Example: Configuring the Installer Properties File
 
The installer properties file in this example installs an agent that is named AGENT2 on a UNIX system in the agent_solaris_aes directory. The agent uses port 34520 for communication with the scheduling manager named manager1 that has an IP address ::FFFF:192.168.00.00 and uses port 8507. Local security for AGENT2 is enabled. The agent uses the AES cipher algorithm. The FILE1.txt file contains the environment variables that the agent and scheduling manager use. More spool-related parameters are appended at the end of the agentparm.txt file as listed in the additional_agentparm.txt file.
The license agreement is not shown during the silent installation. To accept the license agreement, set ACCEPT_EULA to ACCEPT. By default, the installation is aborted. A copy of the license agreement is included at the end of the installer properties file.
ACCEPT_EULA=ACCEPT USER_INSTALL_DIR=/u1/build/CA/agent_solaris_aes AGENT_NAME=AGENT2 AGENT_PORT=34520 NUM_MANAGER_1=1 MANAGER_1_INFO_1=manager1 MANAGER_1_INFO_2=::FFFF:192.168.00.00 MANAGER_1_INFO_3=8507 STRONG_ENCRYPTION_CIPHER=AES STRONG_ENCRYPTION_KEYGEN=0x01020304050607080102030405060708 LOCAL_SECURITY=on NUM_MANAGER_VARS_2=1 MANAGER_VARS_1_INFO_1=MANAGER1_VAR MANAGER_VARS_1_INFO_2=C:\\MANAGER_1\\FILE1.TXT NUM_USER_VARS_2=1 USER_VARS_1_INFO_1=USER1 USER_VARS_1_INFO_2=C:\\USER1\\FILE1.TXT JOBLOG=true RAW_DATA=/usr/home/joe/additional_agentparm.txt
The additional_agentparm.txt file that is specified in the RAW_DATA property contains the following parameters:
runnerplugin.spool.clean.enable=true runnerplugin.spool.expire=50000 runnerplugin.spool.sleep=20000
Run the Silent Installer on UNIX
You can run the silent installer to perform the agent installation.
To run the silent installer on UNIX, type the following command at the command prompt:
./setup.bin -f
path
/unix_installer.properties
  • path
    Specifies the full path to the installer properties file.
After the installation completes, the prompt returns. The installation command can be a part of a script and can run as a cron job.
Run the Silent Installer on Windows
You can run the silent installer to perform the agent installation.
To run the silent installer on Windows, type the following command at the command prompt:
setup.exe -f "
path
\win_installer.properties"
  • path
    Specifies the full path to the installer properties file.
After the installation completes, the prompt returns. The installation command can be a part of a script and can run as a cron job.
Run the Silent Installer on iSeries
You can run the silent installer to perform the agent installation.
To run the silent installer on iSeries, type the following command at the command prompt:
java -jar Setup.jar -f
installer.properties
  • response_file
    Specifies the full path to the file where the installation responses are written.
After the installation completes, the prompt returns. The installation command can be a part of a script and can run as a cron job.
Run the Silent Installer on HPE Integrity NonStop
You install the agent in silent mode by using a response file. A response file, nonstop_installer.properties, is provided with the installation media. Edit this file to enter all the required installation options the same way you would through the interactive mode. 
Follow these steps:
 
  1. Log in as a valid user.
  2. Download and unpack the compressed file from the CA Support Online website at casupport.broadcom.com. Follow the instructions for unpacking the files before proceeding with the installation.
  3. Copy (or FTP) the setup file and response file to the target system and directory.
  4. Start the silent installation by entering the following command:
    java -jar setup.jar –f ./nonstop_installer.properties
  • When transferring the nonstop_installer.properties file between hosts, ensure that the end-of-line (EOL) characters are correct. Windows and UNIX use different EOL characters.
  • When the agent installer begins the installation process, it displays a series of Java-related installer messages. These messages are for informational purposes only. You can ignore them.
Review the Log File
The agent installation program creates a log file, which you can review for installation errors. The log file is located in the agent installation directory. Log file names include a date/time stamp of the installation as shown below.
CA_WA_Agent_11.5.00.00_Install_02_14_2018_15_35_31.log
When an installation is terminated prematurely, the installation log file is written to the default installation directory.