How do I enable message level debugging for the Java SDK in OpenAM 13.x?
The purpose of this article is to provide information on enabling message level debugging for the Java® SDK in OpenAM. The Java SDK is also referred to as the Client SDK. The Java SDK was deprecated in AM 5 and removed in AM 5.5.
Archived
This article has been archived and is no longer maintained by ForgeRock.
Archived
This article has been archived and is no longer maintained by ForgeRock.
Enabling message level debugging
You can enable message level debugging for the Java SDK by setting the following property in the AMConfig.properties file (located in the /path/to/tomcat/webapps/openam/WEB-INF/classes directory):
com.iplanet.services.debug.level=messageYou should also check the setting for the com.iplanet.services.debug.directory property in this file as this is where the Java SDK logs, including the amRemotePolicy log, are kept.
Once you have reproduced the problem and captured the debug logs, you should revert the debug level to error to avoid filling up the disks where the debug logs are stored.
See Also
Related Training
N/A
Related Issue Tracker IDs
N/A