In addition to a standard installation and uninstallation of J2EE agents, you can perform a silent installation or uninstallation as described in this appendix.
A silent installation or uninstallation refers to installing or uninstalling a program by implementing a script. The script is part of a state file. The script provides all the answers that you would normally supply to the installation or uninstallation program interactively. Running the script saves time and is useful when you want to install or uninstall multiple instances of Policy Agent using the same parameters in each instance.
Silent installation is a simple two-step process of generating a state file and then using that state file. To generate a state file, you record the installation or uninstallation process, entering all the required information that you would enter during a standard installation or uninstallation. Then you run the installation or uninstallation program with the state file as the input source.
This section describes how to generate a state file for installing a J2EE agent. This task requires you to issue a command that records the information you will enter as you follow the agent installation steps. Enter all the necessary installation information in order to create a complete state file.
To generate a state file for a J2EE agent installation , perform the following:
Change to the following directory:
PolicyAgent-base/bin |
This directory contains the agentadmin program, which is used for installing a J2EE agent and for performing other tasks. For more information on the agentadmin program, see Key Features and Tasks Performed With the J2EE agentadmin Program.
Issue the following command:
./agentadmin --install --saveResponse filename |
An option that saves all of your responses to installation prompts in a state file.
Represents the name that you choose for the state file.
Perform the installation as described in Chapter 3, Installing Policy Agent 2.2 for BEA WebLogic Server/Portal 9.2
Your answers to the prompts are recorded in the state file. When the installation is complete, the state file is created in the same directory where the installation program is located.
When generated, a state file will have read permissions for all users. However, because the state file contains clear text passwords, it is recommended that you change the file permissions to restrict read and write access to the user root.
The installation program does not validate inputs or the state in the silent installation. Ensure that the proper environment exists before performing a silent installation.
To perform a silent installation of a J2EE agent using a state file, perform the following:
Change to the following directory:
PolicyAgent-base/bin |
At this point, this bin directory should contain the agentadmin program and the J2EE agent installation state file.
Issue the following command:
./agentadmin --install --useResponse filename |
An option that directs the installer to run in non-interactive mode as it obtains all responses to prompts from the named state file.
Represents the name of the state file from which the installer obtains all responses.
The installation takes place hidden from view. After completion, the program exits automatically and displays the prompt.
This section describes how to generate a state file for uninstalling a J2EE agent. This task requires you to issue a command that records the information you will enter as you follow the agent uninstallation steps. Enter all the necessary uninstallation information in order to create a complete state file.
To generate a state file for uninstallation of a J2EE agent, perform the following:
Change to the following directory:
PolicyAgent-base/bin |
This directory contains the agentadmin program, which is used for uninstalling a J2EE agent and for performing other tasks. For more information on the agentadmin program, see Key Features and Tasks Performed With the J2EE agentadmin Program.
Issue the following command:
./agentadmin --uninstall --saveResponse filename |
An option that saves all of your responses to uninstallation prompts in a state file.
Represents the name that you choose for the state file.
Perform the uninstallation as explained in Chapter 7, Uninstalling Policy Agent 2.2 for BEA WebLogic Server/Portal 9.2.
Your answers to the prompts are recorded in the state file. When uninstallation is complete, the state file is created in the same directory where the uninstallation program is located.
When generated, a state file will have read permissions for all users. However, because the state file contains clear text passwords, it is recommended that you change the file permissions to restrict read and writeaccess to the user root.
The uninstallation program does not validate inputs or the state in the silent installation. Ensure that the proper environment exists before performing a silent uninstallation.
To perform a silent uninstallation of a J2EE agent using a state file, perform the following:
Change to the following directory:
PolicyAgent-base/bin |
At this point, this bin directory should contain the agentadmin program and the J2EE uninstallation state file.
Issue the following command:
./agentadmin --uninstall --useResponse filename |
An option that runs the uninstallation process in non-interactive mode as all responses to prompts are obtained from the named state file.
Represents the name of the state file from which the installer obtains all responses.
The uninstallation takes place hidden from view. After completion, the program exits automatically and displays the prompt.