224 Certification Study Guide: IBM Tivoli Access Manager for e-business 6.0
򐂰 NOTICE
򐂰 NOTICE_VERBOSE
You can specify an asterisk (*) to log messages regardless of severity.
6.3.2 Java properties files
Java properties files are ASCII files that are used to customize event logging for
Java-based Tivoli Access Manager servers, daemons, and other Java-language
programs and applications.
Beyond customizing logging, these properties files are used to configure other
aspects of the application. The content of the properties file enables the user to
control the following aspects of message logging:
򐂰 Whether event logging is enabled
򐂰 Where the output should be directed
򐂰 If the output is to a file, the number of files to use and the size of each file
The default locations for the Java properties files for Tivoli Access Manager
components are shown in Table 6-1.
Table 6-1 Location of Java properties files
To summarize, PDJLog.properties is used to define message and trace logging
properties in the following cases:
򐂰 For non application-related Java commands, such as pdjrtecfg and
com.tivoli.pd.jcfg.SvrSslCfg.
Component Default file name
Java application configured using the
com.tivoli.pd.jcfg.SvrSslCfg class.
The output application configuration file as
specified in the com.tivoli.pd.jcfg.SvrSslCfg class.
Java-based Tivoli Access Manager commands, such
as the pdjrtecfg command and
com.tivoli.pd.jcfg.SvrSslCfg or applications not
explicitly configured.
$JAVA_HOME/PolicyDirector/
PDJLog.properties
a
a. pdjrtecfg command creates PD.properties file that stores the result of a successful configuration.
PDJlog.properties file is used just for logging purposes.
Web Portal Manager <TAM install root>\java\export\
pdwpm\pdwpm.properties
Tivoli Access Manager for WebLogic Server $JAVA_HOME/amwls/wls_domain_name/
wls_realm_name/amwlsjlog.properties
Chapter 6. Auditing and troubleshooting 225
򐂰 If a Java application was not explicitly configured with the
com.tivoli.pd.jcfg.SvrSslCfg command.
򐂰 If the application-specific properties file is inaccessible or does not exist.
򐂰 If a required property in the application-specific properties file is not found.
Format of trace events with the Java properties file
To capture trace events for Java applications, you need to configure the Java
properties file defining trace loggers and file handlers.
Trace loggers
Each properties file contains properties for one or more trace loggers. The
isLogging property specifies whether trace logging is enabled.
To turn tracing on for a specific trace logger, use:
baseGroup.trace_logger_name.isLogging=true
To disable logging for a specific trace logger, use:
baseGroup.PDJapp_nameTraceLogger.isLogging=false
File handlers
Associated with each trace logger is at least one file handler. A file handler
specifies the destination for a specific class, or severity, of messages. After trace
logging is enabled by the trace logger, the file handler properties are examined to
determine if traces should be logged and, if so, how and where.
The properties for a file handler are:
baseGroup.PDJapp_nameTraceFileHandler.fileName=
baseGroup.PDJapp_nameTraceFileHandler.maxFileSize=
baseGroup.PDJapp_nameTraceFileHandler.maxFiles=
The meanings of the handlers are the following:
fileName Specifies the fully qualified file name to be used as the
base name for trace log files. The file can be in any
location accessible by the Java application.
maxFileSize Specifies the maximum size, in KB, of each trace log file.
Default is 512.
maxFiles Specifies the maximum number of files to be used for
trace logging. Default is 3.

Get Certification Study Guide: IBM Tivoli Access Manager for e-business 6.0 now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.