Logging network requests

Network requests and responses — typically those from SOAP — can be captured for further analysis. Each call is logged in an individual file.

Note: This type of logging is meant to be used temporarily for detailed analysis because the required storage space will grow significantly.

File: WWSettings.xml file

Name of option: LogFile

Location: anywhere between the <Settings> </Settings> tags

Values:

RequestBuffer: the path to where the log files should be stored.

ResponseBuffer: the path to where the log files should be stored.

SOAPResponse: the path to where the log files should be stored.

SOAPRequest: the path to where the log files should be stored.

Advnaced: set to true when a sub folder needs to be created per session, in which all calls are called sequentially. When not set or set to false, per type of call only the last one will be saved (overwriting any previous one). Required storage space will stay about the same, but now only the last call of each type can be traced and there is no way to determine the call sequence.

In order to prevent these files from growing to enormous file sizes, Smart Connection creates a new file at the start of each session and stores the old file in a separate folder, using the date as the folder name.

Areas that can be logged

Specific areas have been identified which can be included or excluded from logging:

SCPro-MCV: Smart Connection panel related logging

SCEnt-Workspace: Workflow actions related logging

SCEnt-Logon: Logon/logoff related logging

SCEnt-DIME: Logging about handling DIME attachments

SCEnt-SOAP: Logging about handling SOAP requests

SCEnt-HTTP: Logging on http requests

SCEnt-HTTPTimer: Timing of http requests

Enabling Generic logging

File: WWSettings.xml file

Name of option: Logging

Location: anywhere between the <Settings> </Settings> tags

Values:

level: Defines the type of information that should be logged:

0 = All. Everything is logged. The logs contains general information about the process.