To configure the IBM Lotus Domino 7.0 agent for multiple web 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 in 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 agents on a system after the original IBM Lotus Domino 7.0 agent has been installed.
Run the config_linux script in the bin directory using the following command:
Follow the prompts to install additional instances of the IBM Lotus Domino 7.0 agent.
For information about each of the prompts, see Installing the IBM Lotus Domino 7.0 Agent on UNIX and Linux Systems
In general, information needs to be entered for both the protected IBM Lotus Domino 7.0 instance and the instances of Access Manager. The following text serves as an example run:
# ./config_linux 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_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.