An XML file ( ConnTrans_Log.xml ) generated by ConnTrans that captures runtime information pertaining to the execution ConnTrans.
The runtime information associated with ConnTrans is logged in a structured manner in the ConnTrans_Log.xmlfile. This ensures the following:
· If you encounter an error during the execution of ConnTrans, you can immediately access and provide the runtime information to the SAP support team, as the information is logged in an XML file.
· External applications or utilities can use the logged runtime information, as the information is available in the standard format (XML).
· The log file provides method level logging and tracing information. The SAP support team can use this information to identify the function that caused the error.
The structure of the ConnTrans_Log.xml file is explained in the following table:
Node |
Description |
||
<CONNTRANS_LOG> |
Forms the root node of the log file. All the information in this file is logged under this node. |
||
<SESSION_ITEM> |
Contains information pertaining to a specific instance of ConnTrans. If you set the mode of logging to append, you can view multiple occurrences of this node under the root node. This node is further classified into the following sections: |
||
Section |
Description |
||
<SESSION_INFO> |
Provides information about the events that occur only once per instance of ConnTrans. Normally, this section contains information associated with the initialization of ConnTrans.
This section must appear only once under a particular <SESSION_ITEM> node. |
||
<CLIENT_INFO> |
Provides information about the mobile client on which you execute ConnTrans, such as: · The name of the machine. · The Internet Protocol (IP) address of the machine. · The site ID assigned to the mobile client. |
||
<STARTUP_OPTIONS> |
Provides information about the different logging and user interface (UI) options specified for a particular instance of ConnTrans. |
||
<EXECUTION_INFO> |
Provides information associated with each execution of ConnTrans that is represented by the <EXECUTION_ITEM> section.
ConnTrans creates an <EXECUTION_ITEM> every time you choose Synchronize. Each <EXECUTION_ITEM> contains a dump of the different UI options that are specified for a particular execution of ConnTrans. This information is further classified into the following sections: · <EXEC_UI_OPTIONS> · <EXECUTION_SUMMARY> · <LOG_ENTRIES> The <LOG_ENTRIES> section contains multiple <LOG ENTRY> sections. Each <LOG ENTRY> contains a <LOG TYPE> item that is assigned one of the following values: |
||
Value |
Indicates |
||
I |
An information message. |
||
W |
A warning message. |
||
E |
An Error message. |
||
Q |
An unprocessed message on the mobile client. |
The ConnTrans_Log.xml file is generated only when you execute ConnTrans. In addition, the information logged in this file depends on the logging options specified in the ConnTrans_Startup.xml file. For more information, see The ConnTrans Startup File.
A sample of the ConnTrans_Log.xml file is displayed below:
- <CONNTRANS_LOG>
- <SESSION_ITEM>
- <STARTUP_OPTIONS>
- <LOGGING_OPTIONS>
<LOG_TO_FILE>-1</LOG_TO_FILE>
<LOG_FILE_PATH>C:\Temp\ConnTrans_Log.xml</LOG_FILE_PATH>
<LOG_APPEND>-1</LOG_APPEND>
<LOG_AUDIT_LEVEL>2</LOG_AUDIT_LEVEL>
<LOG_MAX_SIZE>50</LOG_MAX_SIZE>
</LOGGING_OPTIONS>
- <UI_OPTIONS>
- <SEND_RECEIVE_OPTIONS>
- <TS_INFO>
<TS_PROG_ID>TRANSACTIONLAYERTS.TRANSACTIONLAYERTS
</TS_PROG_ID>
<TS_SEND>1</TS_SEND>
<TS_RECEIVE>0</TS_RECEIVE>
</TS_INFO>
- <TS_INFO>
<TS_PROG_ID>MAPITRANSFERSERVICE.MAPITRANSFERSERVICE
</TS_PROG_ID>
<TS_SEND>0</TS_SEND>
<TS_RECEIVE>1</TS_RECEIVE>
</TS_INFO>
- <TS_INFO>
</SEND_RECEIVE_OPTIONS>
<CLOSE_ON_FINISH>1</CLOSE_ON_FINISH>
<CONNECTION_OPTIONS>1</CONNECTION_OPTIONS>
<AUTO_REDIAL>1</AUTO_REDIAL>
<AUTO_SYNC />
</UI_OPTIONS>
</STARTUP_OPTIONS>
- <CLIENT_INFO>
<ASSIGNED_SITEID>3CA0A10CA4332747E10000000A1145B6
</ASSIGNED_SITEID>
<CLIENT_MACH_NAME>INBLR441</CLIENT_MACH_NAME>
<CLIENT_MACH_IP>10. 55.148.111</CLIENT_MACH_IP>
</CLIENT_INFO>
+ <EXECUTION_INFO>
+ <SESSION_INFO>
</SESSION_ITEM>
</CONNTRANS_LOG>