This section demonstrates the format and use of the agentadmin command with the --custom-install option. The --custom-install option is very similar to the --install option. However, when you install an agent using the agentadmin --custom-install command, the installer provides you with a greater number of prompts, and therefore allows you to select a greater number of settings. The --install option, on the other hand, selects default values for many options. For example, with the --custom-install option, you can create the agent profile during agent installation. You do not have this option with the --install option.
The arguments available with the --custom-install option, as listed in the next section, are the same as for the --install option.
The following example illustrates the format of the agentadmin command with the --custom-install option:
./agentadmin --custom-install [--useResponse] [--saveResponse] filename
The following arguments are supported with the agentadmin command when using the --custom-install option:
Use this argument to save all supplied responses to a state file, or response file, represented as filename in command examples. The response file, or state file, can then be used for silent installations.
Use this argument to install an agent in silent mode as all installer prompts are answered with responses previously saved to a response file, represented as filename in command examples. When this argument is used, the installer runs in non-interactive mode. At which time, user interaction is not required.
Use this argument to specify the name of a file that will be created as part of the processing of this command. This file stores your responses when this argument is used in conjunction with the --saveResponse argument and provides your responses when this argument is used in conjunction with the --useResponse argument.
When you issue the agentadmin command, you can choose the --custom-install option. With the --custom-install option, you can choose the --saveResponse argument, which requires a file name be provided. The following example illustrates this command when the file name is myfile:
./agentadmin --custom-install --saveResponse myfile
Once the installer has executed the preceding command successfully, the responses are stored in a state file that can be used for later runs of the installer.
If desired, you can modify the state file and configure the second installation with a different set of configuration parameters.
Then you can issue another command that uses the ./agentadmin --custom-install command and the name of the file that you just created with the --saveResponse argument. The difference between the previous command and this command is that this command uses the --useResponse argument instead of the --saveResponse argument. The following example illustrates this command:
./agentadmin --custom-install --useResponse myfile
With this command, the installation prompts run the installer in silent mode, registering all debug messages in the install logs directory.