This section provides task descriptions for the configuration of the agent for multiple instances of Sun Java System Web Proxy Server 4.0 and the configuration of SSL with the agent. Perform these tasks if they apply to your site's deployment.
Only perform a task if a respective condition applies.
To configure Agent for Sun Java System Web Proxy Server 4.0 for multiple proxy server instances on a single Linux computer, use the GUI or the command-line version of the agent installation program to install the first agent. After the first agent is installed, you can then install successive agents using the config_linux script. This script must be run using the command line as described in the next section. The config_linux script and the unconfig_linux script are both located in the following directory:
Perform the following steps if you want to configure additional agent instances on a system after the original instance of Agent for Sun Java System Web Proxy Server 4.0 has been installed.
Run the config_linux script in the bin directory using the following command:
Follow the prompts to install additional instances of Agent for Sun Java System Web Proxy Server 4.0.
For information on each of the prompts, see GUI Installation of Agent for Sun Java System Web Proxy Server 4.0 on Linux Systems
In general, information needs to be entered for both the protected Sun Java System Web Proxy Server 4.0 instance and the instances of Access Manager. The following text serves as an example:
# ./config_linux Enter the Proxy Server Instance Directory:  Enter the Local Hostname:  Enter the Agent Web Server Port:  Select Agent Web Server Protocol:  http  https -->  Enter the Agent Deployment URI [/amagent] Enter the Access Manager Hostname:  Enter the Access Manager Port:  Select Access Manager Protocol:  http  https -->  Enter the Access Manager Deployment URI [/amserver] Enter the Access Manager's Console Deployment URI [/amconsole] Do You Want Failover Server Support:  yes  No -->  Enter the User Name [UrlAccessAgent] Enter Agent-Access Manager shared secret: Re-enter Agent-Access Manager shared secret: Is CDSSO Enabled:  yes  no -->  Configuring proxy server ... Server version: 4.0
Be sure to use the unconfig_linux script to uninstall any agent that was installed using the config_linux script. You cannot use the GUI installation program to uninstall agents that were installed using the command line. The GUI uninstallation program must be executed only after unconfiguring all the existing agents installed using command-line unconfig_linux script.
During installation, if you chose the HTTPS protocol, Agent for Sun Java System Web Proxy Server 4.0 is automatically configured and ready to communicate over SSL. Before proceeding with the following tasks in this section, ensure that Sun Java System Web Proxy Server 4.0 is configured for SSL.
You should have a solid understanding of SSL concepts and the security certificates required to enable communication over the HTTPS protocol. See the documentation for Sun Java System Web Proxy Server 4.0.
Add the Sun Java System Web Proxy Server 4.0 certificate’s root CA certificate to the Access Manager’s certificate database.
Mark the CA root certificate as trusted to enable Access Manager to successfully send notifications to Agent for Sun Java System Web Proxy Server 4.0.
This section only applies when Access Manager itself is running SSL. By default, the agent installed on a remote Sun Java System Web Proxy Server 4.0 instance will trust any server certificate presented over SSL by the Access Manager host. The web agent does not check the root Certificate Authority (CA) certificate. If the Access Manager host is SSL-enabled and you want the agent to perform certificate checking, adhere to the guidelines as described in the following subsections:
The following property in the web agent AMAgent.properties configuration file controls the agent’s trust behavior, which by default it is set to true:
With this property set to true, the web agent does not perform certificate checking. On Linux systems, enabling the agent to perform certificate checking is a one-step process that only involves setting this property to false as illustrated in the following task.
Set the following property in the web agent AMAgent.properties configuration file to false as follows:
com.sun.am.trust_server_certs = false
The root CA certificate you install on the remote instance of Sun Java System Web Proxy Server 4.0 must be the same one that is installed on the Access Manager host.