TDV SAPBW Adapter Tracing and Debug Procedures
Article ID: KB0081309
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | 7.0.0 and later |
Description
Tracing and debugs are two of the different tools that are used in order to troubleshoot issues that involve SAPBW.
The debug process is completed with the log4j.properties file (<BASE_Install> > conf > server) in order to enable this line:
#log4j.logger.com.compositesw.cdms.ds.sapbw=DEBUG
This line obtains the overall information about the API calls that TDV submits to the SAPBW datasource.
Tracing is used in order to capture the raw data that is received from the external SAPBW source so that you can better understand issues. When tracing is active, the data is recorded as it comes out of the SAPBW. Each call to the BW results in a pair of files in the file system (one HTML, and one XML) that contain the data. Since every SAP system can vary in terms of configuration, metadata, or behavior, you need this information in order to diagnose the problems for environments to which you do not have direct access.
Tracing Instructions
Complete these steps in order to enable tracing:
trace_RZX2_OPEN_OBJECTS_GET_03-QU_1330402958951.html
rwx-----+ 1 Administrators None 2597673 Feb 27 20:22
trace_RZX2_OPEN_OBJECTS_GET_03-QU_1330402958951.xml
rwx-----+ 1 Administrators None 66063 Feb 27 20:22
trace_RZX2_OPEN_OBJECTS_GET_06-IC_1330402937782.html
rwx-----+ 1 Administrators None 1065220 Feb 27 20:22
trace_RZX2_OPEN_OBJECTS_GET_06-IC_1330402937782.xml
Note: For Microsoft Windows installations, tracing files are not created if your TDV installation is within a path that contains spaces in the name, such as C: > Program Files > Composite Software. The SAP libraries do not tolerate spaces and tracing does not produce any output files. If your instance is on such a path, Tibco recommends that you install a temporary TDV instance that contains no spaces in the installation path, for the purpose of collecting the debug trace files. Then you can uninstall it afterwards.
The debug process is completed with the log4j.properties file (<BASE_Install> > conf > server) in order to enable this line:
#log4j.logger.com.compositesw.cdms.ds.sapbw=DEBUG
This line obtains the overall information about the API calls that TDV submits to the SAPBW datasource.
Tracing is used in order to capture the raw data that is received from the external SAPBW source so that you can better understand issues. When tracing is active, the data is recorded as it comes out of the SAPBW. Each call to the BW results in a pair of files in the file system (one HTML, and one XML) that contain the data. Since every SAP system can vary in terms of configuration, metadata, or behavior, you need this information in order to diagnose the problems for environments to which you do not have direct access.
Tracing Instructions
Complete these steps in order to enable tracing:
- Verify that the TDV server is shutdown.
- Navigate to apps > dlm > app_ds_sapbw > conf > product.properties and edit the file in order to set the sapbw.trace= value to true.
It does not matter if your server log4j.properties file has the debug logging for the SAPBW adapter enabled also. The setting does not impact this type of tracing. You can optionally add this line in order to specify another directory for the trace files:
- Start the TDV service.
- Perform the minimal steps that are needed in order to reproduce the issue. There are four new trace files in the file system (apps > dlm > app_ds_sapbw). Here is an example directory listing:
trace_RZX2_OPEN_OBJECTS_GET_03-QU_1330402958951.html
rwx-----+ 1 Administrators None 2597673 Feb 27 20:22
trace_RZX2_OPEN_OBJECTS_GET_03-QU_1330402958951.xml
rwx-----+ 1 Administrators None 66063 Feb 27 20:22
trace_RZX2_OPEN_OBJECTS_GET_06-IC_1330402937782.html
rwx-----+ 1 Administrators None 1065220 Feb 27 20:22
trace_RZX2_OPEN_OBJECTS_GET_06-IC_1330402937782.xml
- Zip all four of these files into a single zip file (or equivalent archive) and email them to Tibco support. With the use of these files, the support team can review the session with the BW system in order to determine what occurs during the reproduction.
- Repeat the first three steps, and set the sapbw.trace=false in Step 2 in order to reset the server to the previous state and stop the additional logging.
Note: For Microsoft Windows installations, tracing files are not created if your TDV installation is within a path that contains spaces in the name, such as C: > Program Files > Composite Software. The SAP libraries do not tolerate spaces and tracing does not produce any output files. If your instance is on such a path, Tibco recommends that you install a temporary TDV instance that contains no spaces in the installation path, for the purpose of collecting the debug trace files. Then you can uninstall it afterwards.
Issue/Introduction
This document describes the troubleshooting tools that are specific to the TDV SAP Business Warehouse (SAPBW) adapter.
Feedback
Yes
No
Powered by
