This section includes various problems you might encounter with this agent on AIX systems. The symptom of the problem is followed by possible causes and solutions.
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 7.0 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 Solutions:
Ensure that the DSAPI filter has been configured with the correct information. For example, verify that the following path has been specified:
Ensure that LIBPATH is set properly as explained in AIX Systems: Setting LIBPATH to Include Libraries Specific to the IBM Lotus Domino 7.0 Agent.
PolicyAgent-base/agents/domino6/lib/libamdomino6.a
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 DSAPI filter change may not be updated in the database
Possible Solutions:
Ensure that the correct database was selected during configuration.
Replicate the database from the IBM Lotus Domino 7.0 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:
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.
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