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

Linux Systems: Troubleshooting Symptoms in Agent for IBM Lotus Domino 6.5.4

This section includes a problem you might to encounter with this agent on Linux systems. The symptom of the problem is followed by possible causes and solutions.

Linux Systems: Troubleshooting Symptom 1

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:

PolicyAgent-base/agents/domino6/lib/libamdomino6.so

Linux Systems: Troubleshooting Symptom 2

Symptom: The DSAPI filter is not functioning properly on a server instance.

Possible Causes:

When the DSAPI filter was configured, the database selected was not correct.
The partitioned database was not updated.

Possible Solutions:

Ensure that the correct database was selected during configuration.
Replicate the database from the IBM Lotus Domino 6.5.4 administration server.

Linux Systems: Troubleshooting Symptom 3

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:

com.sun.am.policy.agents.config.accessdenied.url

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.

Linux Systems: Troubleshooting Symptom 4

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