XML Transformation information and files to collect
Windows only
Tip for troubleshooting:
The timestamp used in the log filename xmlui*.log is used to create the client correlation ID (clientid). It follows the TCP/IP address of the client. The UI logs this client ID in its log files, and gives it to the server. This enables correlation between a requesting client and the server-side services that process this client's requests. The server-side services use this clientid string when logging messages in the session used by the UI client. Also note that the DataStage XML Transformation Flex application log (flashlog.txt) also contains this same clientid.
Collecting XML Stage specific information
DataStage can create logging and tracing information at multiple layers and in different components.
Client-Server tracing for DataStage Hierarchical feature
Increase the detail included in the client and server side log files for DataStage XML Transformation feature. This should only be performed under the direction of IBM Support.
Command
In the DataStage XML Transformation Flex UI, the main window contains an "Options" link in the upper right corner. Click that link to open a dialog and set serviceability options.
Note that further configuration for Flex logging can be performed. That configuration file is at:<USER_HOME>\mm.cfg and is documented at the Adobe site.
Files and Data to collect:
To set server-side trace for the DataStage XML Transformation UI, use the WebSphere admin console to that server:
Files and Data to collect
|
Description
|
Information Server 8.5 and above - Client only
| |
| <USER_HOME>\Application Data\Macromedia\Flash Player\Logs\flashlog.txt | Log file for the DataStage XML Transformation UI Flex application. (Note this file will only exist when using the debug version of the Adobe Flash Player). |
<USER_HOME>\ds_logs\xmlui_*.log.
|
Log file for the DataStage XML Transformation UI .NET application. Note: capture of all log files here already covered for main DS client collection.
A new log file is created every time the user invokes the DataStage XML Transformation connector application. The file name of a log begins with either "xmlui_assembly", or "xmlui_mdi_importer" followed by a time stamp indicating when the log was created (e.g., xmlui_assembly_2010.10.06_11.35.30.093.log). |
The timestamp used in the log filename xmlui*.log is used to create the client correlation ID (clientid). It follows the TCP/IP address of the client. The UI logs this client ID in its log files, and gives it to the server. This enables correlation between a requesting client and the server-side services that process this client's requests. The server-side services use this clientid string when logging messages in the session used by the UI client. Also note that the DataStage XML Transformation Flex application log (flashlog.txt) also contains this same clientid.
Collecting XML Stage specific information
DataStage can create logging and tracing information at multiple layers and in different components.
Client-Server tracing for DataStage Hierarchical feature
Increase the detail included in the client and server side log files for DataStage XML Transformation feature. This should only be performed under the direction of IBM Support.
Command
In the DataStage XML Transformation Flex UI, the main window contains an "Options" link in the upper right corner. Click that link to open a dialog and set serviceability options.
- Change the client logging level in the Logging section of this dialog. For example, change the level from "Info" to "Debug" to set trace. Log and trace messages are placed into the WAS logs on the server used by the UI. Server-side trace* must be set in order for trace messages to be written on the server. (Note, if a debug Adobe Flash Player is used, a local log file flashlog.txt is also written.)
- Change the server-side logging under Log/Trace Settings Server. For example, check the box labeled "Trace Enabled" to perform trace on the server-side.
Note that further configuration for Flex logging can be performed. That configuration file is at:<USER_HOME>\mm.cfg and is documented at the Adobe site.
Files and Data to collect:
- For client-side Flex application log/trace: <USER_HOME>\Application Data\Macromedia\Flash Player\Logs\flashlog.txt. (When using debug Adobe Flash Player only.)
- For client-side connector application log/trace:<USER_HOME>\ds_logs\xmlui_*.log.
- For server-side log/trace: This log information is placed into the WAS logs for both the server and client-side UI. See section 5 titled "WebSphere Application Server information and files to collect".
To set server-side trace for the DataStage XML Transformation UI, use the WebSphere admin console to that server:
- On the left hand side of the WAS admin console, expand Troubleshooting and click on Logs and Trace.
- Click on the server1 server. Click on Diagnostic Trace.
- Click on the Change Log Detail Levels link.
- Go to the Runtime tab and find component "com.ibm.e2.applications.wisd.model.AssemblyDesigner".
- Set its trace level to 'finest'. Then click Apply.