Sun Java System Access Manager 7.1 Developer's Guide

Implementing a Remote Logging Application in a Container

If your remote logging application is running in a container such as Sun Java System Application Server or Web Server, at the command line, set the following properties:

-Ds1is.java.util.logging.config.class=
			com.sun.identity.log.s1is.LogConfigReader

-DLOG_COMPATMODE=Off

-Djava.util.logging.manager=
			com.iplanet.ias.server.logging.ServerLogManager

The -Djava.util.logging.manager property occurs in the Java System Web Server server.xml file. JVM options are typically added to the server.xml file in Java System Web Server, or to the domain.xml file in Java System Application Server.

Setting Environment Variables

You must set the following shared library environment variables in the executable for an application that is using the Logging Service. You can determine how to set the variables depending upon three things:

Whether the application can execute in the local Access Manager server, or executes only a in remote server
Whether or not you want the Access Manager LogManager class to override the native LogManager class
Whether or not SSL is enabled in your deployment

If Client Can Execute in the Local Access Manager Server

When the client application can execute in either the local Access Manager server JVM or 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 set the following variables:
```
-D"java.util.logging.manager=com.sun.identity.log.LogManager"
-D"java.util.logging.config.class=com.sun.identity.log.
			s1is.LogConfigReader"
```
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 set the following variables:
```
-DLOG_COMPATMODE=Off
-Ds1is.java.util.logging.config.class=com.sun.identity.log.
			s1is.LogConfigReader
```

If Client Executes Only in a Remote Server

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:
1. Set the following variables:
  
  -Djava.util.logging.manager=com.sun.identity.log.LogManager
```
-Djava.util.logging.config.file=/AccessManager_base/SUNwam/
		lib/LogConfig.properties
```
2. 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:
1. Set the following variables:
  
  -DLOG_COMPATMODE=Off
  
  -Ds1is.java.util.logging.config.file=/AccessManager-base/SUNwam/lib/LogConfig.properties
2. 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.

If SSL is Enabled

If SSL is enable and uses JSS for Access Manager, set the following parameter:

-D"java.protocol.handler.pkgs=com.iplanet.services.comm"