When the client application can execute only in a remote server JVM, choose one of the following two configurations:
If it is acceptable for the native LogManager class to be overridden by the Access Manager LogManager class in the JDK1.4 environment, then follow these steps:
Set the following variables:
-Djava.util.logging.manager=com.sun.identity.log.LogManager
-Djava.util.logging.config.file=/AccessManager_base/SUNwam/ lib/LogConfig.properties
In LogConfig.properties, or in the logging.properties file supplied by JDK, set the following properties:
iplanet-am-logging-remote-handler=com.sun.identity.log.handlers. RemoteHandler
iplanet-am-logging-remote-formatter=com.sun.identity.log. handlers.RemoteFormatter
iplanet-am-logging-remote-buffer-size=1
iplanet-am-logging-buffer-time-in-seconds=3600
iplanet-am-logging-time-buffering-status=OFF
If it is not acceptable for the native LogManager class to be overridden by the Access Manager LogManager class in the JDK1.4 environment, then follow these steps:
Set the following variables:
-DLOG_COMPATMODE=Off
-Ds1is.java.util.logging.config.file=/AccessManager-base/SUNwam/lib/LogConfig.properties
In LogConfig.properties, or in the logging.properties file supplied by JDK, set the following properties:
iplanet-am-logging-remote-handler=com.sun.identity.log. handlers.RemoteHandler iplanet-am-logging-remote-formatter=com.sun.identity.log. handlers.RemoteFormatter
iplanet-am-logging-remote-buffer-size=1
iplanet-am-logging-buffer-time-in-seconds=3600
iplanet-am-logging-time-buffering-status=OFF
The Client APIs use this logging configuration by default. In this case, the Logging API will configure a remote handler for all logs. Access to the Directory Server is not required in this case.