For troubleshooting web services in the field, here are the instructions for adding logging of the SOAP XML to our application log.
Create the file, services.logging.xml, from the pasted xml in notes:
1) Stop the application server.
2) Install the services.logging.xml in META-INF/xfire
3) In the web.xml file, change to XFire config file to point to services.logging.xml.
Change:
<param-value>META-INF/xfire/services.xml</param-value>
to:
<param-value>META-INF/xfire/services.logging.xml</param-value>
4) Make sure logging is at ERROR level in log4j.properties, such as so if using a console:
log4j.rootCategory= ERROR, CONSOLE, LOGFILE
or if no console is used:
log4j.rootCategory= ERROR, LOGFILE
5) Restart the application and initialize xfire objects by signing in a user.
6) When needing to log SOAP, open the logManager, http://<server name>:<server port>/pmws_server/logManager, and set class org.codehaus.xfire.util.LoggingHandler to debug level
a. In the text box enter ?org.codehaus.xfire.util.LoggingHandler?
b. In the new level field, set the level to INFO
c. Click on the Alter button
7) Once you are finished with logging the SOAP, set the level of org.codehaus.xfire.util.LoggingHandler to ERROR.
Note: The application will need to be primed by accessing the xfire objects, such as by signing in a user, before the xfire object will be visible in the logManager.
- <beans xmlns="http://xfire.codehaus.org/config/1.0">
- <xfire>
- <inHandlers>
<handler handlerClass="org.codehaus.xfire.util.dom.DOMInHandler" />
<handler handlerClass="org.codehaus.xfire.util.LoggingHandler" />
</inHandlers>
- <outHandlers>
<handler handlerClass="org.codehaus.xfire.util.dom.DOMOutHandler" />
<handler handlerClass="org.codehaus.xfire.util.LoggingHandler" />
</outHandlers>
</xfire>
- <service>
<name>AuthService</name>
<namespace>http://auth.api.ws.passmarksecurity.com</namespace>
<serviceClass>com.passmarksecurity.ws.api.auth.AuthService</serviceClass>
<implementationClass>com.passmarksecurity.ws.impl.AuthServiceImpl</implementationClass>
<style>wrapped</style>
</service>
- <service>
<name>AdminService</name>
<namespace>http://admin.api.ws.passmarksecurity.com</namespace>
<serviceClass>com.passmarksecurity.ws.api.admin.AdminService</serviceClass>
<implementationClass>com.passmarksecurity.ws.impl.AdminServiceImpl</implementationClass>
<style>wrapped</style>
</service>
</beans>
Related Articles
A customer requests that a BIN in TEST environment be moved into PRODUCTION environment This procedure explains and provid… 15Number of Views Another Mapping already exists for the target account attribute warning in RSA Identity Governance & Lifecycle when settin… 69Number of Views Set Up Your Trial Environment 35Number of Views Documentation error on setting up autovetting on RSA RM6.6 7Number of Views Replica will not Authenticate Multiple Authentications 26Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to Detect and Resolve Stalled Workflows and Workpoint Issues in RSA Identity Governance & Lifecycle How to change the default Oracle Statistics History Retention period for RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Installation Guide How to Export Root Certificates via Web Browser — RSA Authentication Manager, Identity Router, or Cloud Authentication Ser…