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 follow the following instructions:

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

• On windows: Start a "notepad.exe "as administrator", then open Gateway config file - default at C:\Program Files\IT-Conductor\Agent\conf\AGENT.XML

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

• In the file  Add/Replace the following entries:

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

  <entry key="itconductor.output.directory">#dump directory#</entry>

#dump directory# - specify the directory/folder in the OS format:

Windows: Z:\ITC-Logs

Linux: /mnt/storage/...

• Save the file

• Set the debug level of the Gateway object in IT-Conductor (please request from support - we limit the en-user ability to do so due to performance/space overhead complications)

• 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 interaction. There is no guaranteed sequence as most of the interactions are performed in-parallel in different threads.

Analyzing the Data

Communication data dump is not meant to provide contextual data, so the file names bear no relations to a specific monitored application or specific interaction.

There are however ways to analyze the flow for the  particular applications and data types.

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

<wsa:Action env:mustUnderstand="true">http://schemas.xmlsoap.org/ws/2004/09/transfer/Create> - for Create 

<wsa:Action env:mustUnderstand="true">http://schemas.xmlsoap.org/ws/2004/09/transfer/Put> - for Update

The type of objects created (Classes) is defined by the following fragment:

<wsman:ResourceURI env:mustUnderstand="true">object/Instance</wsman:ResourceURI>  - where "Instance" is one of the classes that are created, typically classes are prefixed with application name like "SAP", "Oracle" etc. for full class hierarchy  please request support - it is very big and only administrators have access to it in IT-Conductor, but we will be able to provide the information pre-request basis.

Here is an example of Object Update Envelope:

<env:Envelope

xmlns:env="http://www.w3.org/2003/05/soap-envelope"
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:wsarole="http://schemas.xmlsoap.org/ws/2004/08/addressing/role"
xmlns:wsen="http://schemas.xmlsoap.org/ws/2004/09/enumeration"
xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd"
xmlns:wsmancat="http://schemas.xmlsoap.org/ws/2005/06/wsmancat"
xmlns:wxf="http://schemas.xmlsoap.org/ws/2004/09/transfer"
xmlns:xop="https://www.w3.org/2004/08/xop/include">

<env:Header>

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

<wsa:To env:mustUnderstand="true">https://cloud.itconductor.com/ws/management</wsa:To>
<wsa:ReplyTo>

<wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>

</wsa:ReplyTo>

<wsa:Action env:mustUnderstand="true">http://schemas.xmlsoap.org/ws/2004/09/transfer/Put>

<wsa:MessageID>uuid:9ce7d4fc-f3c6-40b7-8632-82cf5a0e06ca</wsa:MessageID>

<wsman:OperationTimeout>P0Y0M0DT0H1M0.000S</wsman:OperationTimeout>

<wsman:SelectorSet>

<wsman:Selector Name="OBJECT_Id">xxxxxxxxxxxxxxxxxxx</wsman:Selector>

</wsman:SelectorSet>

</env:Header>

<env:Body>

<Instance>

<AGENT.RestartPending><![CDATA[false]]></AGENT.RestartPending>
<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.Build><![CDATA[20170420023536]]></AGENT.Build>
<AGENT.WrapperVersion />
<AGENT.ProxyAddress><![CDATA[DIRECT]]></AGENT.ProxyAddress>
<AGENT.JREVersion><![CDATA[1.8.0_45]]></AGENT.JREVersion>
<AGENT.OS><![CDATA[Windows 8.1]]></AGENT.OS>
<AGENT.Arch><![CDATA[amd64]]></AGENT.Arch>
<AGENT.RemoteIP><![CDATA[xxx.xxx.xxx.xxx]]></AGENT.RemoteIP>

</Instance>

</env:Body>

</env:Envelope>