To configure Agent for IBM Lotus Domino 6.5.4 for multiple web server instances on a single computer, use the GUI or command-line version of the agent installation program to install the first agent. After the first agent is installed, you can then configure the agent for multiple instances of IBM Lotus Domino 6.5.4 using the config script that is copied into the system during the agent installation. This script must be run in the command line as described in the next section. The config script and the unconfig script are both located in the following directory:
To configure the agent for additional IBM Lotus Domino 6.5.4 instances on a system, run the config script in the bin directory using the following command:
Follow the prompts to install additional instances of Agent for IBM Lotus Domino 6.5.4.
For information on each of the prompts, see Command-Line Installation of Agent for IBM Lotus Domino 6.5.4 on Solaris Systems.
In general, information needs to be entered for both the protected IBM Lotus Domino 6.5.4 instance and the instances of Access Manager. The following text serves as example.
# ./config Enter the Lotus Domino Data 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 webserver ... Done.
Be sure to use the unconfig script to uninstall any web agent that was installed using the config script. You cannot use the GUI installation program to uninstall web agents that were installed using the command line. The GUI uninstallation program must be executed only after unconfiguring all the existing web agents using the command-line unconfig script.