There are two logging options: one is for the framework hosting EWPS, which is called AXIS2. This wraps around EWPS, and you can log the SOAP requests and responses that flow in and out of AXIS2; here’s how:
 
1. Add the following Java options to your JVM:
 
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog 
-Dorg.apache.commons.logging.simplelog.showdatetime=true 
-Dorg.apache.commons.logging.simplelog.log.httpclient.wire=debug 
-Dorg.apache.commons.logging.simplelog.log.org.apache.commons.httpclient=debug
 
You can add these as an environment variable called JAVA_OPTS in a startup script (e.g. for WebLogic or Tomcat – note that if you’re running Tomcat as a Windows service you have to manipulate the service properties to set this instead of using a .bat/.cmd file).
 
2. Configure AXIS2 for debug log output by modifying the ewps-axis2.war/ewps-axis2/WEB-INF/classes/log4j.properties file. The line in bold needs to be modified..
 
# Set root category log4j.rootCategory=DEBUG, CONSOLE, LOGFILE # Set the enterprise logger priority to FATAL log4j.logger.org.apache.axis2.enterprise=FATAL log4j.logger.de.hunsicker.jalopy.io=FATAL log4j.logger.httpclient.wire.header=FATAL log4j.logger.org.apache.commons.httpclient=FATAL # CONSOLE is set to be a ConsoleAppender using a PatternLayout. log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout log4j.appender.CONSOLE.layout.ConversionPattern=[%p] %m%n # LOGFILE is set to be a File appender using a PatternLayout. log4j.appender.LOGFILE=org.apache.log4j.FileAppender log4j.appender.LOGFILE.File=axis2.log log4j.appender.LOGFILE.Append=true log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout log4j.appender.LOGFILE.layout.ConversionPattern= %d [%t] %-5p %c %x – %m%n
 
That’s it. You can also turn on some logging for EWPS itself. In the same directory of the WAR file, modify ewps-axis2.war/ewps-axis2/WEB-INF/classes/log4j.xml. You’ll see it has a section that defines where the log file is located:
 
 
<appender name="fileroll" class="org.apache.log4j.RollingFileAppender">   
       <param name="Append" value="true"/>
       <param name=“File" value="${catalina.home}/logs/EWPSDocumentService.log" />
       <layout class="org.apache.log4j.PatternLayout">
          <param name="ConversionPattern" value="%d{ISO8601}-[%t]-%m\n"/>
       </layout>
    </appender>
 
And, you’ll see the many <category> nodes where you can set the <priority> to debug. In the example below, I have changed ERROR to DEBUG. All of these nodes are set to ERROR by default, so you can turn on the ones needed. I would turn on debug for the node that matches their queuing method for IDS.
 
 
 <category name="http.debug" additivity="false">
       <priority value="DEBUG" />
       <appender-ref ref="stdout" />
       <appender-ref ref="fileroll" />
    </category>
 
Make the changes, save the file, rebuild the WAR if needed, and redeploy.

 

Patch Installation Instructions:
    Notes: 
        a) It is recommended to patch EWPS in a test/development environment first to 
           validate.
        b) This version of EWPS requires minimum of recent Java 1.8 releases. 

    Steps: 
        1. Backup existing EWPS WAR file (default file name ewps-axis2.war).

        2. Modify the new ewps-axis2.war file from this patch to update any necessary 
           configuration changes for your environment. 
           Normally such configuration changes are found in the WAR's 
           WEB-INF/xml/ewps.config.xml file. 

        3. Update the existing EWPS war deployment in the Java Application Server with 
           any environment specifics necessary (such as alternative context-root). 

        4. Test to validate. 

    Revert Patch:
        Restore orignal file(s) backed up in step 1. above if there is a problem. 

Link to patch on MOS:

p34829139_127000_Generic.zip