Gateway Communication Dump Debug Mode

IT-Conductor provides a facility to dump all communication with the cloud servers into local files.

Capturing The Data

To turn on the communication debug mode, please perform the following:

1. Open an SSH or RDP session to the machine where the Gateway is installed.

2. On Windows: Start a "notepad.exe" as administrator. Open Gateway config file, default at C:\Program Files\IT-Conductor\Agent\conf\AGENT.XML.

On Linux: vi <install directory>/cont/AGENT.XML

3. In the file, add/replace the following entries:

<entry key="itconductor.debug.level">4</entry>
<entry key="">#dump directory#</entry>

"#dump directory#" specifies the directory/folder in the OS format.

  • Windows: Z:\ITC-Logs

  • Linux: /mnt/storage/...

4. Save the file.

5. Set the debug level of the Gateway object in the IT-Conductor.

Note: Please request support. We limit the end user's ability to do so due to performance/space overhead complications.

6. Restart the Gateway.

From now on, all communication messages (soap envelopes) will be stored in the specified directory:

04/20/2017 11:14 AM <DIR> .
04/20/2017 11:14 AM <DIR> ..
04/20/2017 11:34 AM 1,348 soap-0-input.xml
04/20/2017 11:34 AM 4,228 soap-0-output.xml
04/20/2017 11:57 AM 8,970 soap-100-input.xml
04/20/2017 11:57 AM 4,228 soap-100-output.xml
04/20/2017 11:57 AM 1,324 soap-101-input.xml
04/20/2017 11:57 AM 4,228 soap-101-output.xml
04/20/2017 11:57 AM 8,970 soap-102-input.xml
04/20/2017 11:57 AM 4,228 soap-102-output.xml
04/20/2017 11:57 AM 1,324 soap-103-input.xml
04/20/2017 11:57 AM 4,228 soap-103-output.xml
04/20/2017 11:57 AM 8,970 soap-104-input.xml
04/20/2017 11:57 AM 4,228 soap-104-output.xml
04/20/2017 11:57 AM 1,324 soap-105-input.xml
04/20/2017 11:57 AM 4,228 soap-105-output.xml
04/20/2017 11:57 AM 8,970 soap-106-input.xml
04/20/2017 11:57 AM 4,228 soap-106-output.xml
04/20/2017 11:57 AM 1,324 soap-107-input.xml
04/20/2017 11:57 AM 4,228 soap-107-output.xml
04/20/2017 11:57 AM 8,970 soap-108-input.xml
04/20/2017 11:57 AM 4,228 soap-108-output.xml
04/20/2017 11:57 AM 1,324 soap-109-input.xml
04/20/2017 11:57 AM 4,228 soap-109-output.xml
  • soap-<n>-input.xml stores the SOAP sent to IT-Conductor cloud servers from the Gateway.

  • soap-<n>-output.xml stores the SOAP received as a reply from IT-Conductor cloud servers on the Gateway.

  • <n> represents the sequential number of interactions. There is no guaranteed sequence as most of the interactions are performed in parallel in different threads.

Analyzing the Data

The communication data dump does not mean providing contextual data, so the file names are unrelated to a specific monitored application or interaction.

However, there are ways to analyze the flow for particular applications and data types.

All objects creation/updates are performed but two types of soap envelopes (containing):

For Create:

<wsa:Action env:mustUnderstand="true">> 

For Update:

<wsa:Action env:mustUnderstand="true">>

The following fragment defines the type of objects created (Classes):

<wsman:ResourceURI env:mustUnderstand="true">object/Instance</wsman:ResourceURI>

Where Instance is one of the classes created, typically, classes are prefixed with application names like "SAP," "Oracle," etc.

Note: For a full class hierarchy, please request support. Only administrators have access to it in IT-Conductor. We will provide the information on a pre-request basis.

Here is an example of an Object Update Envelope:

        <wsman:ResourceURI env:mustUnderstand="true">object/Instance</wsman:ResourceURI>
        <wsa:To env:mustUnderstand="true"></wsa:To>

        <wsa:Action env:mustUnderstand="true">>
        <wsman:Selector Name="OBJECT_Id">xxxxxxxxxxxxxxxxxxx</wsman:Selector>
                <AGENT.StartTime><![CDATA[2017-04-20 17:13:54.383]]></AGENT.StartTime>
                <DAEMON.StartTime><![CDATA[2017-04-20 17:13:54.383]]></DAEMON.StartTime>
                <AGENT.WrapperVersion />
                <AGENT.OS><![CDATA[Windows 8.1]]></AGENT.OS>

Last updated