|Applies To||RSA Hosted Adaptive Authentication|
Direct SOAP implementation with eProxy client in customer environment
|Issue||Raising log level of proxy client to capture request and response SOAP messages|
If the client is of a Java version, then please update log4j.properties file to raise the log level to DEBUG mode. The content of the file is as follows.
Raising the log level to Debug Mode :
Please make the changes in red to the log4j.properties on the client proxy. Before making changes ask the client to store the original settings. The Debug mode should *NOT* be used for an indefinite period of time because the log files become huge. The Debug mode is useful for capturing SOAP requests. Once done capturing requests, ask client to move back to the saved original settings
#NOTICE: please use unix like "/" for path and NOT window "\"
If the client is of Dot Net version, the please update eProxy.dll.xml
Formula to calcuate number of connections per proxy
(2 X Peak Transactions per second X Desired Response time in milliseconds) / (Number of Proxy Clients * 1000)
Required for proxy troubleshooting ?
? Proxy version
? Proxy client log for relevant issue. No need to send entire log, just relevant excerpt.
? properties files(Please refer below)
? Health check report
? Utilization report
? Statistics report for Proxy 2.0 (called SLA report in 1.0)
? Number of errors, frequency and time of errors
Proxy Report URL?s -
Location of Properties files ?
Registry Configurations for .NET ?
|Legacy Article ID||a40569|