Besides message monitoring in SAP as described in Data Extractor paragraph above, it is also possible to track the communication on the Message Broker level. Message Broker produces log files that contain runtime information related to the message processing. The messages are generated with the following log levels:
DEBUG – the most verbose level, containing detailed information of message processing, including content and metadata of XML messages being sent between SAP and Cloud
INFO – contains entries for messages transferred, so that it is possible to track message exchange, but no detailed information (i.e. no message content)
WARN – entries generated for non-critical problems
ERROR – entries generated for problems that prevent message exchange (problem to connect to SAP or Cloud, application misconfiguration, etc.)
It is recommended, that the logging is configured at least at a WARN level, so that all unusual situations are visible in the logs. In a starting phase of using FSM Cloud Connector it may be desirable to set logging level to DEBUG, even if causes big files to be generated and brings some performance overhead. The logging parameters (e.g. path to the log files, logging level, etc.) can be set in Message Broker configuration file. By default, logging is set to a DEBUG level and files are generated in c:\tmp\e4c.log\ directory.