masvi10

SOA Security Manager Gateway's CA XML Toolkit logging

Discussion created by masvi10 Employee on Nov 29, 2011
Latest reply on Dec 7, 2011 by Chris_Hackett

Tuesday Tip by Sandra Green, Principal Support Engineer, for 11-29-2011

SOA Security Manager Gateway's CA XML Toolkit logging

There are four types of logging in the SOA Security Manager Gateway:

1. Gateway logging
2. Gateway Management Console logging
3. Filter level logging
4. CA XML Toolkit logging

We covered the first three in the previous three weeks. In this, we cover CA XML Toolkit logging.

This is logging of the component that communicates with the SiteMinder policy server when processing XML messages. For example, when you configure and invoke the CA SOA Security Manager Authentication filter or CA SOA Security Manager Authorization filter. It is implemented using Apache’s log4j standard and you configure logging for this component by manually editing the log.config file. This is at the following location for:

Windows: The SOASecurityGateway\conf\plugin\soasecuritymanager\gw_agent\config directory where they Gateway is installed
Unix: The SOASecurityGateway/conf/plugin/soasecuritymanager/gw_agent/config directory where they Gateway is installed

You can specify the log file name and location using the log4j.appender.A2.File parameter. The default value is $(NETE_TXM_ROOT)/tmxmltoolkit.log where $(NETE_TXM_ROOT) resolves to the location of where to write the file and tmxmltoolkit.log will be the name of this file. If you are using the Windows platform you’ll need to escape the back slash (\) by using two back slashes(\\). For example, if you want the log to be called txm.log and written to the c:\logs directory you would use the following configuration: log4j.appender.A2.File=c:\\logs\\txm.log

The XML SDK process is made up of handlers, each of which can be configured to a different level of tracing. There are five levels (from least detail to most detail):

FATAL, ERROR, WARN, INFO, DEBUG.

You will need to refresh the Gateway in order for the changes to the log.config file to take effect.

Outcomes