Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Authorizing access to resources > Authorizing access to Java EE resources using Tivoli Access Manager > Enable an external JACC provider

Log Tivoli Access Manager security

Use this topic to enable the trace specification to indicate tracing at the required level. The JACC for Tivoli Access Manager provider messages are logged to the configured trace output location, and messages are written to standard out SystemOut.log file. When trace is enabled, all logging, both trace and messaging, is sent to the trace.log file.

With WAS v8 you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using $PROFILE/bin/LogViewer.sh. See the information about using HPEL to troubleshoot applications for more information on using HPEL.New feature:

Procedure

1. The amwas.node_server.pdjlog.properties file must be updated and the isLogging attribute set to true for the required component. For example, to enable tracing for the JACC provider for Tivoli Access Manager, set the following line to true: amwas.node_server.pdjlog.properties:baseGroup.AMWASWebTraceLogger.isLogging=true
2. Enable tracing for the JACC provider of Tivoli Access Manager components in the console...

   1. Click Troubleshoot > Logs and Trace > server_name

   2. Under Logs and Trace tasks, click Diagnostic trace.

   3. Select the Enable Log option.

   4. Click Apply.

   5. Click Troubleshoot > Logs and Trace > server_name

   6. Click Change Log Detail Levels.

   7. Click Components. Tracing for all components can be enabled using the com.tivoli.pd.as.* command. Tracing for separate components can be enabled using the following commands:
      • com.tivoli.pd.as.rbpf.* for role-based policy framework tracing
      • com.tivoli.pd.as.jacc.* for JACC provider tracing
      • com.tivoli.pd.as.pdwas.* for the authorization table
      • com.tivoli.pd.as.cfg.* for configuration
      • com.tivoli.pd.as.cache.* for caching

      See Log level settings.

   8. Click Apply.

What to do next

The trace specification now indicates that tracing is enabled at the required level. Save the configuration and restart the server for the changes to take effect.

Related

Tivoli Access Manager loggers
Enable an external JACC provider

Related

Diagnostic trace service settings

+

Search Tips   |   Advanced Search