Sun Java System Access Manager Policy Agent 2.2 Guide for IBM Lotus Domino 6.5.4

Previous: Chapter 2 About Policy Agent 2.2 for IBM Lotus Domino 6.5.4
Next: Chapter 4 The Relationship Between the Agent Profile and Web Agents in Policy Agent 2.2

Chapter 3 Installing Policy Agent 2.2 for IBM Lotus Domino 6.5.4

Policy Agent 2.2 works in tandem with Access Manager to control user access to deployment containers (such as web servers) in an enterprise.

This chapter explains how to install Policy Agent 2.2 for IBM Lotus Domino 6.5.4 on the supported platform. For more information on the supported platforms, see Supported Platforms and Compatibility of Agent for IBM Lotus Domino 6.5.4.

For this chapter, each platform-related section leads you through the pre-installation and installation steps. First, perform the pre-installation (preparation) steps. Then, perform the installation, itself.

Next, complete the applicable post-installation tasks described in Chapter 5, Post-Installation Configuration: Policy Agent 2.2 for IBM Lotus Domino 6.5.4. Note that certain post-installation tasks are required for the agent to work, such as configuring the IBM Lotus Domino 6.5.4 DSAPI filter. After you configure the DSAPI filter, verify that the installation was successful, as described in All Systems: Verifying a Successful Installation on Policy Agent 2.2.

Each section of this chapter focuses on installing IBM Lotus Domino 6.5.4 on a specific platform as follows:

Solaris Systems: Agent Installation for IBM Lotus Domino 6.5.4

This section describes the installation process on Solaris systems.

Preparing to Install Agent for IBM Lotus Domino 6.5.4 on Solaris Systems

Follow the specific steps outlined in this section before you install the web agent to reduce the chance of complications occurring during and after the installation.

To Prepare to Install Policy Agent 2.2 for IBM Lotus Domino 6.5.4 on Solaris Systems

Note –

You must have Java Runtime Environment (JRE) 1.3.1 or higher installed or available on a shared file system in order to run the graphical user interface (GUI) of the web agent installation program. Currently, JRE 1.3.1 or any version higher is certified for use with the web agent installation program.

Perform the following pre-installation tasks:

Ensure that Policy Agent 2.2 for IBM Lotus Domino 6.5.4 is supported on the desired platform as listed in Supported Platforms and Compatibility of Agent for IBM Lotus Domino 6.5.4.

Install IBM Lotus Domino 6.5.4 if not already installed.

Refer to the IBM Lotus Domino 6.5.4 documentation for details on how best to install and configure this server for your platform.

Ensure that IBM Lotus Domino 6.5.4 has the latest patches available.

Set your JAVAHOME environment variable to a JDK version 1.3.1_04 or higher.

The installation requires that you set up your JAVAHOME variable correctly. However, if you have incorrectly set the JAVAHOME variable, the setup script will prompt you for supplying the correct JAVAHOME value:

Please enter JAVAHOME path to pick up java:

Installing Agent for IBM Lotus Domino 6.5.4 on Solaris Systems

The web agent installation program has two interfaces: the graphical user interface (GUI) and the command-line interface. The following sections present instructions to install the web agent using both of these interfaces:

GUI Installation of Agent for IBM Lotus Domino 6.5.4 on Solaris Systems

Use the following instructions to install Agent for IBM Lotus Domino 6.5.4 using the GUI on Solaris systems.

To Install Agent for IBM Lotus Domino 6.5.4 on Solaris Systems Using the GUI

You must have root permissions when you run the web agent installation program.

Unpack the product binary in the directory of your choice using the following command:

# gunzip -dc binaryname.tar.gz| tar -xvof -

In the directory in which you unpack the binaries, issue the following command:

# ./setup

The Welcome page appears.

In the Welcome page, click Next.

Read the License Agreement. Click Yes to agree to the license terms.

In the Select Installation Directory panel, specify the directory where you would like to install the web agent.

Install the web agent in this directory: Enter the full path to the directory where you want to install the web agent. The default installation directory is /opt.

The directory you choose in which to install the web agent is referred to as the Policy Agent base directory, or PolicyAgent-base.

Click Next and provide the following information about the IBM Lotus Domino 6.5.4 instance the agent will protect:

Host Name: Enter the fully qualified domain name (FQDN) of the machine where the IBM Lotus Domino 6.5.4 instance is installed.

For example, if the host is host1, the subdomain is eng, and the domain is example.com, then the Host Name in this case is host1.eng.example.com.

Lotus Domino Data directory: Specify the IBM Lotus Domino 6.5.4 instance that this agent will protect. The following is the default Lotus Domino Data directory:
```
/local/notesdata
```
Web Server Port: Enter the port number for the IBM Lotus Domino 6.5.4 instance that will be protected by the web agent.

Web Server Protocol: If the IBM Lotus Domino 6.5.4 instance has been configured for SSL, choose HTTPS; otherwise choose HTTP.

Agent Deployment URI: Enter a Universal Resource Identifier (URI) that will be used to access Agent for IBM Lotus Domino 6.5.4. The default value is /amagent.

Note –
The web agent uses the value of the com.sun.am.policy.agents.config.agenturi.prefix property in the web agent AMAgent.properties configuration file to support some essential functions such as notification. Agent URI prefix is a configurable subset of Agent Deployment URI. It is important to set a valid URL for this property. Its value should be http://host.domain:port/agent-deployment-uri where host, domain and port are FQDN and port number of the IBM Lotus Domino 6.5.4 instance where the agent is installed and agent-deployment-uri is the URI where the IBM Lotus Domino 6.5.4 instance will look for web-agent related HTML pages. Its default value is amagent.

The following is an example of an Agent Deployment URI:
```
http://host1.example.com:80/amagent
```

When you have entered all the information correctly, click Next.

Enter information about the Access Manager host.

The web agent will connect to this server.

Primary Server Host: Enter the FQDN of the primary Access Manager host.

For example, if the host is host3, the subdomain is eng, and the domain is example.com, then the Host Name in this case is host3.eng.example.com.

Primary Server Port: Enter the port number for the primary Access Manager host.

Primary Server Protocol: If the primary Access Manager host is SSL-enabled, select HTTPS. Otherwise select HTTP.

Primary Server Deployment URI: Enter the location that was specified when Access Manager was installed. The default URI for Access Manager is /amserver.

Primary Console Deployment URI: Enter the location that was specified when Access Manager Console was installed. The default URI for Access Manager is /amconsole.

Failover Server Host: Enter the FQDN of the secondary Access Manager host if the primary Access Manager host becomes unavailable. If no failover server host exists, then leave this field blank.

Failover Server Port: Enter the port number of the secondary Access Manager host. If no failover server host exists, then leave this field blank.

Failover Server Protocol: If the failover Access Manager host is SSL-enabled, select HTTPS. Otherwise select HTTP. If no failover server host exists, then leave this field blank.

Failover Server Deployment URI: Enter the location that was specified when Access Manager was installed. The default URI for Access Manager is /amserver. If no failover server host exists, then leave this field blank.

Failover Console Deployment URI: Enter the location that was specified when Access Manager Console was installed. The default URI for Access Manager is /amconsole. If no failover server host exists, then leave this field blank.

Agent Access Manager Shared Secret: Enter the password for the Access Manager internal LDAP authentication user. This user is also referred to as amldapuser.

For more information about the shared secret and its relationship with the Access Manager agent profile, see Chapter 4, The Relationship Between the Agent Profile and Web Agents in Policy Agent 2.2.

Re-enter Shared Secret: Re-enter the password for the Access Manager internal LDAP authentication user (amldapuser).

CDSSO Enabled: Do not check this box. Cross domain single sign-on is not supported on Agent for IBM Lotus Domino 6.5.4. For more information see Information Specific to Agent for IBM Lotus Domino 6.5.4.

After entering all the information, click Next.

Review the installation summary to ensure that the information you have entered is correct.

If you want to make changes, click Back. If all the information is correct, click Next.

In the Ready to Install panel, click Install Now.

When the installation is complete, you can click Details to view details about the installation, or click Exit to end the installation program.

Restart the IBM Lotus Domino 6.5.4 instance on which you just installed the agent.

Next Steps

After you have installed Agent for IBM Lotus Domino 6.5.4, perform the applicable post-configuration tasks. Ensure that after you perform the required task of configuring the DSAPI filter, you verify that the installation was successful as described in Chapter 5, Post-Installation Configuration: Policy Agent 2.2 for IBM Lotus Domino 6.5.4.

Command-Line Installation of Agent for IBM Lotus Domino 6.5.4 on Solaris Systems

The following instructions describe how to use the command-line interface of the installation program to install Agent for IBM Lotus Domino 6.5.4 on Solaris Systems.

To Install Agent for IBM Lotus Domino 6.5.4 on Solaris Systems Using the Command Line

Installing a web agent on a deployment container using the command line requires you to perform the following steps:

Unpack the product binary in the directory of your choice using the following command:

# gunzip -dc binaryname.tar.gz| tar -xvof -

In the directory in which you unpack the binaries, issue the following command:

# ./setup -nodisplay

When prompted, provide the following information:

Have you read, and do you accept, all of the terms of the preceding Software License Agreement? Enter yes.

Install the web agent in this directory: Enter the full path to the directory in which you want to install the web agent.

The directory you choose in which to install the web agent is referred to as the Policy Agent base directory, or PolicyAgent-base.

Provide the following information about the IBM Lotus Domino 6.5.4 instance this agent will protect:
- Host Name
- Lotus Domino Data directory
- Web Server Port
- Web Server Protocol
- Agent Deployment URI
  
  For a description of the information to enter for these prompts, see GUI Installation of Agent for IBM Lotus Domino 6.5.4 on Solaris Systems.

Provide the following information about the Access Manager host:
- Primary Server Host
- Primary Server Port
- Primary Server Protocol
- Primary Server Deployment URI
- Primary Console Deployment URI
- Failover Server Host
- Failover Server Port
- Failover Server Protocol
- Failover Server Deployment URI
- Failover Console Deployment URI
- Agent-Access Manager Shared Secret
- Re-enter Shared Secret
- CDSSO Enabled
  
  For a description of the information to enter for these prompts, see GUI Installation of Agent for IBM Lotus Domino 6.5.4 on Solaris Systems.
  
  The following text is displayed:
  Ready to Install 1. Install Now 2. Start Over 3. Exit Installation

When prompted, What would you like to do?, enter 1 to start the installation.

The following text is displayed:

Product                                             Result      More Information
1.  Sun Java(tm) System Access Manager Policy Agent Installed   Available
2.  Done

To see log information, enter 1. To exit the installation program, enter 2.

Restart the IBM Lotus Domino 6.5.4 instance on which you just installed the agent.

Next Steps

Windows Systems: Agent Installation for IBM Lotus Domino 6.5.4

This section describes the installation process on Windows systems.

Preparing to Install Agent for IBM Lotus Domino 6.5.4 on Windows Systems

Follow the specific steps outlined in this section before you install the web agent to reduce the chance of complications occurring during and after the installation.

To Prepare to Install Agent for IBM Lotus Domino 6.5.4 on Windows Systems

Note –

Perform the following pre-installation tasks:

Ensure that Policy Agent 2.2 for IBM Lotus Domino 6.5.4 is supported on the desired platform as listed in Supported Platforms and Compatibility of Agent for IBM Lotus Domino 6.5.4.

Install IBM Lotus Domino 6.5.4 if not already installed.

Refer to the IBM Lotus Domino 6.5.4 documentation for details on how best to install and configure this server for your platform.

Ensure that IBM Lotus Domino 6.5.4 has the latest patches available.

Set your JAVAHOME environment variable to a JDK version 1.3.1_04 or higher.

The installation requires that you set up your JAVAHOME variable correctly. However, if you have incorrectly set the JAVAHOME variable, the setup script will prompt you for supplying the correct JAVAHOME value:

Please enter JAVAHOME path to pick up java:

Ensure that required libraries are available on the IBM Lotus Domino 6.5.4 instance.

Depending on the Windows system you are using, the following libraries, msvcp70.dll and msvcr70.dll, might not be available. If these libraries are not available to the IBM Lotus Domino 6.5.4 instance upon which you are installing the agent, you must make them available as described in the following substeps.
1. Obtain these Windows libraries: msvcp70.dll and msvcr70.dll.
  
  These libraries come with certain Windows applications. You can also obtain them by contacting Sun technical support.
2. Place the libraries in the system32 subdirectory.
  
  The following path is an example of a conceivable path to this directory:
```
c:\WINDOWS\system32
```

Installing Agent for IBM Lotus Domino 6.5.4 on Windows Systems

The web agent installation program has one interface, the graphical user interface (GUI), for Windows systems. Use the following instructions to install a web agent using the GUI on Windows systems.

GUI Installation of Agent for IBM Lotus Domino 6.5.4 on Windows Systems

Use the following instructions to install a web agent using the GUI on Windows systems.

You must have administrator privileges to run the installation program.

To Install Agent for IBM Lotus Domino 6.5.4 on Windows Systems Using the GUI

Unpack the product binaries.
unzip binaryname.zip
Note –
On Microsoft Windows 2003, the zip file is not automatically unpacked. Therefore, after you download the agents zip file, be sure to extract the zip file to a directory first and then execute setup.exe. To extract the zip file, right click on the zip file in the File Manager and select Extract. After extracting to a directory, double click setup.exe to execute it.

Run the installation program by double-clicking setup.exe.

The Welcome page appears.

In the Welcome page, click Next.

Read the License Agreement. Click Yes to accept the license agreement.

Select the directory where you want to install the agent.

The directory you choose in which to install the web agent is referred to as the Policy Agent base directory, or PolicyAgent-base.

Enter the applicable information about the IBM Lotus Domino 6.5.4 instance where this agent will be installed in the dialog box.

The dialog box provides fields for entering the required information. You are prompted for information in the order shown as follows:

Host Name: Enter the fully qualified domain name (FQDN) of the system where the IBM Lotus Domino 6.5.4 instance is installed.

For example, if the host is host1, the subdomain is eng, and the domain is example.com, then the Host Name in this case is host1.eng.example.com.

Lotus Domino Data directory: Specify the IBM Lotus Domino 6.5.4 instance that this agent will protect. The following is the default Lotus Domino Data directory:
```
c:\Lotus\Domino\Data
```
Web Server Port: Enter the port number for the IBM Lotus Domino 6.5.4 instance that will be protected by the agent.

Web Server Protocol: If your IBM Lotus Domino 6.5.4 instance has been configured for SSL, then select HTTPS; otherwise select HTTP.

Agent Deployment URI: Enter a Universal Resource Identifier (URI) that will be used to access Agent for IBM Lotus Domino 6.5.4. The default value is /amagent.

Note –
The web agent uses the value of the com.sun.am.policy.agents.config.agenturi.prefix property in the web agent AMAgent.properties configuration file to support some essential functions such as notification. Agent URI prefix is a configurable subset of Agent Deployment URI. It is important to set a valid URL for this property. Its value should be http://host.domain:port/agent-deployment-uri where host, domain and port are FQDN and port number of the IBM Lotus Domino 6.5.4 instance where the agent is installed and agent-deployment-uri is the URI where the IBM Lotus Domino 6.5.4 instance will look for web-agent related HTML pages. Its default value is amagent.

The following is an example of an Agent Deployment URI:
```
http://host1.example.com:80/amagent
```

When you have entered all the information, click Next.

Provide the following information about the Access Manager host:

The deployment container will connect to this server.

Primary Server Host: Enter the FQDN of the primary Access Manager host.

For example, if the host is host3, the subdomain is eng, and the domain is example.com, then the Host Name in this case is host3.eng.example.com.

Primary Server Port: Enter the port number for the primary Access Manager host.

Primary Server Protocol: If the primary Access Manager host is SSL-enabled, select HTTPS. Otherwise select HTTP.

Primary Server Deployment URI: Enter the location that was specified when Access Manager was installed. The default URI for Access Manager is /amserver.

Primary Console Deployment URI: Enter the location that was specified when Access Manager console was installed. The default URI for Access Manager is /amconsole.

Failover Server Host: Enter the FQDN of the secondary Access Manager host if the primary Access Manager host becomes unavailable. If no failover server host exists, then leave this field blank.

Failover Server Port: Enter the port number of the secondary Access Manager host. If no failover server host exists, then leave this field blank.

Failover Server Protocol: If the failover Access Manager host is SSL-enabled, select HTTPS. Otherwise select HTTP. If no failover server host exists, then leave this field blank.

Failover Server Deployment URI: Enter the location that was specified when Access Manager was installed. The default URI for Access Manager is /amserver. If no failover server host exists, then leave this field blank.

Failover Console Deployment URI: Enter the location that was specified when Access Manager Console was installed. The default URI for Access Manager is /amconsole. If no failover server host exists, then leave this field blank.

Agent Access Manager Shared Secret: Enter the password for the Access Manager internal LDAP authentication user. This user is also referred to as amldapuser.

For more information about the shared secret and its relationship with the Access Manager agent profile, see Chapter 4, The Relationship Between the Agent Profile and Web Agents in Policy Agent 2.2.

Re-enter Shared Secret: Re-enter the password for the Access Manager internal LDAP authentication user (amldapuser).

CDSSO Enabled: Do not check this box. Cross domain single sign-on is not supported on Agent for IBM Lotus Domino 6.5.4. For more information see Information Specific to Agent for IBM Lotus Domino 6.5.4.

After entering all the information, click Next.

Review the installation summary to ensure that the information you have entered is correct.

If you want to make changes, click Back. If all the information is correct, click Next.

In the Ready to Install page, click Install Now.

When the installation is complete, you can click Details to view details about the installation, or click Close to end the installation program.

Restart the IBM Lotus Domino 6.5.4 instance on which you just installed the agent.

Restarting your computer is necessary for the agent to work properly. The installation modifies the system path by appending to it the location of the agent libraries. This change takes effect only after your computer is restarted.

Next Steps

Linux Systems: Agent Installation for IBM Lotus Domino 6.5.4

This section describes the installation process on Linux systems.

Preparing to Install Agent for IBM Lotus Domino 6.5.4 on Linux Systems

Follow the specific steps outlined in this section before you install the web agent to reduce the chance of complications occurring during and after the installation.

To Prepare to Install Agent for IBM Lotus Domino 6.5.4 on Linux Systems

Note –

Perform the following pre-installation tasks:

Ensure that Policy Agent 2.2 for IBM Lotus Domino 6.5.4 is supported on the desired platform as listed in Supported Platforms and Compatibility of Agent for IBM Lotus Domino 6.5.4.

Install IBM Lotus Domino 6.5.4 if not already installed.

Refer to the IBM Lotus Domino 6.5.4 documentation for details on how best to install and configure this server for your platform.

Ensure that IBM Lotus Domino 6.5.4 has the latest patches available.

Set your JAVAHOME environment variable to a JDK version 1.3.1_04 or higher.

The installation requires that you set up your JAVAHOME variable correctly. However, if you have incorrectly set the JAVAHOME variable, the setup script will prompt you for supplying the correct JAVAHOME value:

Please enter JAVAHOME path to pick up java:

Installing Agent for IBM Lotus Domino 6.5.4 on Linux Systems

The web agent installation program has two interfaces: the graphical user interface (GUI) and the command-line Interface. The following sections present instructions to install the web agent using both of these interfaces:

GUI Installation of Agent for IBM Lotus Domino 6.5.4 on Linux Systems

Use the following instructions to install the web agent using the GUI on Linux systems.

To Install Agent for IBM Lotus Domino 6.5.4 on Linux Systems Using the GUI

You must have root permissions when you run the agent installation program.

Unpack the product binaries.

Unpack the product binary in the directory of your choice using the following command:

# gunzip -dc binaryname.tar.gz| tar -xvof -

In the directory in which you unpack the binaries, issue the following command:

# ./setup

The Welcome page appears.

In the Welcome page, click Next.

Read the License Agreement. Click Yes to agree to the license terms.

To search for the directory where you would like to install the web agent, click Browse. To accept the default, click Next.

When prompted, provide the following information about the IBM Lotus Domino 6.5.4 instance this agent will protect:

Install Sun Java System Access Manager Policy Agent in this directory: Enter the full path to the directory where you want this agent to be installed, and then click Next.

The directory you choose in which to install the web agent is referred to as the Policy Agent base directory, or PolicyAgent-base.

Host Name: Enter the FQDN of the machine where the IBM Lotus Domino 6.5.4 instance is installed. For example, if the host is host1, the subdomain is eng, and the domain is example.com, then the Host Name in this case is host1.eng.example.com.

Lotus Domino Data directory: Specify the IBM Lotus Domino 6.5.4 instance that this agent will protect. The following is the default Lotus Domino Data directory:
```
/local/notesdata
```
Web Server Port: Enter the port number for the IBM Lotus Domino 6.5.4 instance that will be protected by the agent.

Web Server Protocol: If the IBM Lotus Domino 6.5.4 instance has been configured for SSL, choose HTTPS; otherwise choose HTTP.

Agent Deployment URI: Enter a Universal Resource Identifier (URI) that will be used to access Agent for IBM Lotus Domino 6.5.4. The default value is /amagent.

Note –
The web agent uses the value of the com.sun.am.policy.agents.config.agenturi.prefix property in the web agent AMAgent.properties configuration file to support some essential functions such as notification. Agent URI prefix is a configurable subset of Agent Deployment URI. It is important to set a valid URL for this property. Its value should be http://host.domain:port/agent-deployment-uri where host, domain and port are FQDN and port number of the IBM Lotus Domino 6.5.4 instance where the agent is installed and agent-deployment-uri is the URI where the IBM Lotus Domino 6.5.4 instance will look for web-agent related HTML pages. Its default value is amagent.

The following is an example of an Agent Deployment URI:
```
http://host1.example.com:80/amagent
```

When you have entered all the information, click Next.

Enter information about the Access Manager host.

The web agent will connect to this server.

Primary Server Host: Enter the fully qualified domain name (FQDN) of the primary Access Manager host.

For example, if the host is host3, the subdomain is eng, and the domain is example.com, then the Host Name in this case is host3.eng.example.com.

Primary Server Port: Enter the port number for the primary Access Manager host.

Primary Server Protocol: If the primary Access Manager host is SSL-enabled, select HTTPS; otherwise select HTTP.

Primary Server Deployment URI: Enter the location that was specified when Access Manager was installed. The default URI for Access Manager is /amserver.

Primary Console Deployment URI: Enter the location that was specified when Access Manager Console was installed. The default URI for Access Manager is /amconsole.

Failover Server Host: Enter the FQDN of the secondary Access Manager host if the primary Access Manager host becomes unavailable. If no failover host exists, then leave this field blank.

Failover Server Port: Enter the port number of the secondary Access Manager host. If no failover host exists, then leave this field blank.

Failover Server Protocol: If the failover Access Manager host is SSL-enabled, select HTTPS. Otherwise select HTTP. If no failover server host exists, then leave this field blank.

Failover Server Deployment URI: Enter the location that was specified when Access Manager was installed. The default URI for Access Manager is /amserver. If no failover host exists, then leave this field blank.

Failover Console Deployment URI: Enter the location that was specified when console was installed. The default URI for Access Manager is /amconsole. If no failover host exists, then leave this field blank.

Agent Access Manager Shared Secret: Enter the password for the Access Manager internal LDAP authentication user. This user is also referred to as amldapuser.

For more information about the shared secret and its relationship with the Access Manager agent profile, see Chapter 4, The Relationship Between the Agent Profile and Web Agents in Policy Agent 2.2.

Re-enter Shared Secret: Re-enter the password for the Access Manager internal LDAP authentication user (amldapuser).

CDSSO Enabled: Do not check this box. Cross domain single sign-on is not supported on Agent for IBM Lotus Domino 6.5.4. For more information see Information Specific to Agent for IBM Lotus Domino 6.5.4.

After entering all the information, click Next.

Review the installation summary to ensure that the information you’ve entered is correct.

If you want to make changes, click Back. If all the information is correct, click Next.

In the Ready to Install page, click Install Now.

When the installation is complete, you can click Details to view details about the installation, or click Close to close the installation program.

Restart the IBM Lotus Domino 6.5.4 instance on which you just installed the agent.

Next Steps

Command Line Installation of Agent for IBM Lotus Domino 6.5.4 on Linux Systems

Use the following instructions to install the web agent using the command line on Linux systems.

To Install Agent for IBM Lotus Domino 6.5.4 on Linux Systems Using the Command Line

You must have root permissions when you run the agent installation program.

Unpack the product binary in the directory of your choice using the following command:

# gunzip -dc binaryname.tar.gz| tar -xvof -

In the directory in which you unpack the binaries, issue the following command:
# ./setup -nodisplay

When prompted, provide the following information:

Have you read, and do you accept, all of the terms of the preceding Software License Agreement? Enter yes.

Install the agent in this directory: Enter the full path to the directory in which you want to install the agent.

The directory you choose in which to install the web agent is referred to as the Policy Agent base directory, or PolicyAgent-base.

Provide the following information about the IBM Lotus Domino 6.5.4 instance this agent will protect:
- Host Name
- Lotus Domino Data directory
- Web Server Port
- Web Server Protocol
- Agent Deployment URI
  
  For a description of the information to enter for these prompts, see GUI Installation of Agent for IBM Lotus Domino 6.5.4 on Linux Systems.

Provide the following information about the Access Manager host:
- Primary Server Host
- Primary Server Port
- Primary Server Protocol
- Primary Server Deployment URI
- Primary Console Deployment URI
- Failover Server Host
- Failover Server Port
- Failover Server Protocol
- Failover Server Deployment URI
- Failover Console Deployment URI
- Agent-Access Manager Shared Secret
- Re-enter Shared Secret
- CDSSO Enabled
  
  For a description of the information to enter for these prompts, see GUI Installation of Agent for IBM Lotus Domino 6.5.4 on Linux Systems.
  
  The following text is displayed:
  Ready to Install 1. Install Now 2. Start Over 3. Exit Installation

When prompted, What would you like to do?, enter 1 to start the installation.

The following text is displayed:

Product                                             Result      More Information
1.  Sun Java(tm) System Access Manager Policy Agent Installed   Available
2.  Done

To see log information, enter 1. To exit the Installation program, enter 2.