How to collect additional information for troubleshooting WS-Security issues
Article ID: KB0076066
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | 5.x |
Description
This article lists the steps for collecting additional information for troubleshooting WS-Security issues.
Issue/Introduction
Steps for collecting additional information for troubleshooting WS-Security issues
Resolution
1. Take a backup of the file TIBCO_HOME/bw/5.x/lib/log4j.xml.
2. Open the file TIBCO_HOME/bw/5.x/lib/log4j.xml for editing.
3. Add the following loggers. This is for enabling debug logging.
4. Save the file.
5. Restart the BW application from command line redirecting the output to a file.
*nix
cd TIBCO_HOME/tra/domain/<domain_name>/application/<application_name>
./<application_name>.sh > bwapplication.out 2>&1
Windows
cd TIBCO_HOME\tra\domain\<domain_name>\application\<application_name>
<application_name>.cmd > bwapplication.out 2>&1
6. Reproduce the issue.
7. The output file bwapplication.out will have additional information.
2. Open the file TIBCO_HOME/bw/5.x/lib/log4j.xml for editing.
3. Add the following loggers. This is for enabling debug logging.
<logger name="com.tibco.spin">
<level value="DEBUG"/>
<appender-ref ref="tibco_bw_log"/>
</logger>
<logger name="com.tibco.security.tibcryptx.wss">
<level value="DEBUG"/>
<appender-ref ref="tibco_bw_log"/>
</logger>
<logger name="org.apache.ws.security">
<level value="DEBUG"/>
<appender-ref ref="tibco_bw_log"/>
</logger>
<logger name="org.apache.xml.security">
<level value="DEBUG"/>
<appender-ref ref="tibco_bw_log"/>
</logger>
<logger name="org.jcp.xml.dsig">
<level value="DEBUG"/>
<appender-ref ref="tibco_bw_log"/>
</logger>
<logger name="org.apache.jcp">
<level value="DEBUG"/>
<appender-ref ref="tibco_bw_log"/>
</logger>
<level value="DEBUG"/>
<appender-ref ref="tibco_bw_log"/>
</logger>
<logger name="com.tibco.security.tibcryptx.wss">
<level value="DEBUG"/>
<appender-ref ref="tibco_bw_log"/>
</logger>
<logger name="org.apache.ws.security">
<level value="DEBUG"/>
<appender-ref ref="tibco_bw_log"/>
</logger>
<logger name="org.apache.xml.security">
<level value="DEBUG"/>
<appender-ref ref="tibco_bw_log"/>
</logger>
<logger name="org.jcp.xml.dsig">
<level value="DEBUG"/>
<appender-ref ref="tibco_bw_log"/>
</logger>
<logger name="org.apache.jcp">
<level value="DEBUG"/>
<appender-ref ref="tibco_bw_log"/>
</logger>
4. Save the file.
5. Restart the BW application from command line redirecting the output to a file.
*nix
cd TIBCO_HOME/tra/domain/<domain_name>/application/<application_name>
./<application_name>.sh > bwapplication.out 2>&1
Windows
cd TIBCO_HOME\tra\domain\<domain_name>\application\<application_name>
<application_name>.cmd > bwapplication.out 2>&1
6. Reproduce the issue.
7. The output file bwapplication.out will have additional information.
Feedback
Yes
No
Powered by
