AxM / AA - How to enable AxM soap call logging to Adaptive Auth Enabling the logging the soap messages (which are exchanged between the two products) can be difficult due to the fact that the jars containg the log4j properties are signed, therefore cannot be altered easily.
Use the following methodology to enable AA logging: 1) Extract the aa-onpremise-logging-6.1.3.xx.jar to a particular folder. 2) Since the jars are signed, you must remove the Manifest.MF and signature files (*.sf and *.rsa) before making any updates to the log4j.properties 3) Update the log4j.properties in the extracted folder to enable the logging for axis. [See the reference below]. 4) Package the updated log4j.properties as a aa-onpremise-logging-6.1.3.xx.jar file using Jar tool.
If properly setup, as specified in the attachment, then you will be able to view the SOAP calls between AxM and AA server. You may see other axis related logs.
The log file (axis.log) will be placed under the bin (install_dir/bin) directory of AxM. This is also configurable.
# Set root category priority to INFO and its only appender to CONSOLE.
# Set the enterprise logger category to FATAL and its only appender to CONSOLE. log4j.logger.org.apache.axis.enterprise=DEBUG
# CONSOLE is set to be a ConsoleAppender using a PatternLayout. log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender log4j.appender.CONSOLE.Threshold=OFF log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout log4j.appender.CONSOLE.layout.ConversionPattern=- %m%n
# LOGFILE is set to be a File appender using a PatternLayout. log4j.appender.LOGFILE=org.apache.log4j.FileAppender log4j.appender.LOGFILE.File=axis.log log4j.appender.LOGFILE.Append=true #log4j.appender.LOGFILE.Threshold=OFF log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout log4j.appender.LOGFILE.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n
This solution only applies to SP3 of AxM 6.1. A more usable method will be provided in AxM 6.1 sp4, which is slated to be released in Q1 2012.