|Applies To||Jakarta Tomcat 5.5|
RSA Key Manager Server 2.0
Microsoft Windows Server 2003 R2
BEA WebLogic 9.0
|Issue||Debugging key manager server 2.0|
How to enable Key Manager Server tracing?
How to enable debug in Key Manager Server?
|Cause||RSA Key Manager uses Log4J to generate log data. By default, no logs are generated. This can be configured using standard Log4J parameters.|
Extensive Log4J documentation is available at http://logging.apache.org/log4j/docs/index.html. As an initial default configuration do the following:
Create a file called log4j.properties with the following content:
Note that in this example the log file is created in c:\, ensure that any file path used exists. If you are running KMS on Unix, change the path accordingly.
If Key Manager Server is deployed in your own WebLogic domain, enable logging as follows (assume that Key Manager Server configuration files are located in the directory /opt/kms/conf/):
|Notes||The above logfile will only log RKM data. It avoids logging sensitive information, such as passwords. The key to this setting is the rootLogger=OFF line. Changing this could result in passwords being logged in cleartext by the application server, and not by an RKM component. Be very careful before changing the rootLogger setting.|
|Legacy Article ID||a32096|