This section includes various problems you might encounter with this agent on Solaris systems. The symptom of the problem is followed by possible causes and solutions.
Symptom: Cannot install the web agent after a previous installation has been removed.
The following is an example message that is displayed when you run the web agent installation program:
Launching installer... Sun Java(tm) System; Access Manager Policy Agent for IBM Lotus Domino 6.5.4 is installed. Please refer to installation manual to configure this agent for another web server instance or uninstall it before installing another agent.
You might have an existing installation of the web agent.
You might have a previously-installed web agent and did not use the web agent’s uninstallation program to uninstall the agent.
The installation program’s productregistry file might be corrupted.
Possible Solutions: Performing the following troubleshooting activities might resolve the issue:
Check that you have uninstalled any existing installation of the web agent.
The productregistry file may be corrupted if there is no existing installation of the web agent. This file is used by the installation program to track installed products. It is found in /var/sadm/install directory.
Make a backup copy of productregistry file before you make changes.
Remove the web agent entry in this file. This entry starts with the following lines:
<compid>SUNWamdmn <compversion>2.2 <uniquename>SUNWamdmn</uniquename> <vendor></vendor> <compinstance>1 <parent>Agent for Lotus Domino HTTP Server <instance>1 <version>2.2</version> </instance> </parent> <comptype>COMPONENT</comptype> <location>/opt/dm22</location> <dependent> <compref>Agent for Lotus Domino HTTP Server <instance>1 <version>2.2</version> </instance> </compref> </dependent> <data> <key>pkgs <value>SUNWamdmn</value> </key> </data> </compinstance> </compversion> </compid> <compid>Agent for Lotus Domino HTTP Server <compversion>2.2 <uniquename>Agent for Lotus Domino HTTP Server</uniquename> <vendor></vendor> <compinstance>1 <parent>Sun Java(tm) System Access Manager Policy Agent <instance>4 <version>2.2</version> </instance> </parent> <children> <compref>SUNWamdmn <instance>1 <version>2.2</version> </instance> </compref> </children> <comptype>FEATURE</comptype> <location>/opt/dm22</location> <dependent> <compref>Sun Java(tm) System Access Manager Policy Agent <instance>4 version>2.2</version> </instance> </compref> </dependent> <required> <compref>SUNWamdmn <instance>1 <version>2.2</version> </instance> </compref> </required> </compinstance> </compversion> </compid>
Symptom: The uninstallation program does not remove entries from the agent’s web container.
Possible Cause: Another instance of the web agent exists that was configured using the configuration script.
Possible Solution: Remove all the instances of the web agent using the unconfig script before running the uninstallation program.
Symptom: The browser goes into a loop for approximately a minute before displaying an access-denied page.
Possible Cause: The user tries to access a resource for which a policy with a time condition has been set and the time on the web agent host and the Access Manager host are not in sync.
Possible Solution: Login as root and run the command rdate hostname to synchronize the time on both hosts.
Symptom: IBM Lotus Domino 6.5.4 server starts with the following error message:
Unable to load filter
Possible Cause: The DSAPI filter is configured incorrectly. Generally, if any path issue or associated library issue occurs while the DSAPI filter is being added, this error is generated.
Possible Solution: Ensure that the DSAPI filter has been configured with the correct information. For example, verify that the following path has been specified:
Symptom: The DSAPI filter is not functioning properly on a server instance.
When the DSAPI filter was configured, the database selected was not correct.
The DSAPI filter change may not be updated in the database
Ensure that the correct database was selected during configuration.
Replicate the database from the IBM Lotus Domino 6.5.4 administration server.
Symptom: The agent goes into an infinite loop.
Possible Cause: The value for the following property in the web agent AMAgent.properites configuration file is a resource to which users are assigned:
The users assigned to this resource, do not have allow in the policy definition.
Possible Solution: For the get method, specify allow in the policy definition.
Symptom:When a user attempts to access a resource using Internet Explorer as the browser, access is denied.
Possible Cause: Internet Explorer overrides the port number of the web agent with the Access Manager port number. In such cases, the agent log file lists the URL that is being evaluated. The port number for that URL is incorrect.
Possible Solution: You can ensure this problem does not occur by setting the following property in the web agent AMAgent.properties configuration file to true as shown:
com.sun.am.policy.agents.config.override_port = true