We continuously thrive to improve simulating and troubleshooting message processing in Cloud Integration. With version 2.38, 2.39 and 2.42, we had worked on improving this feature to enhance the usability and increase the available information. This blog describes the new improved addition in the form of tracing of exchange properties which is available with version 2.44. I will provide some details on this addition in this blog.
The affected areas are :
The cases where properties were defined and instantiated in flow steps like content modifier, scripts
were hard to troubleshoot with the existing tracing feature since these properties and its corresponding values were not shown in the message content of tracing feature.
With the version 2.44, this is now integral part of the tracing feature and it has been extended for the flow steps in the first increment where not only user defined exchange properties can be traced, but even the predefined properties coming from the incoming exchange shall be recorded.
The exchange Properties tracing can be extended for the adapters as well, if there are specific properties provided by adapters. We will keep you posted on any further updates on this front.
If you navigate to the MPL and open the step details of a step carrying trace data, the Message Content tab is available. Exchange properties for the incoming exchange is shown in the tabular format containing properties name value pairs like headers.
Just keep in mind, certain properties which are sensitive and confidential in nature from security standpoint will be removed, obfuscated or hashed.
In general with this 2.44 version, trace data shall look comprehensive containing following information in this order
The following example depicts a step recorded for a Groovy script capturing the initially received headers, properties and payload together propagated from the previous flow step which is content modifier in this case.
We have as well enhanced the download feature of trace data where along with headers and payload, properties file can also be available in the one zip file. This can be helpful, if you want to provide this information to others for troubleshooting, for instance when opening a ticket with SAP.
Clicking this button triggers the download of a zip file, which will contain a file with the traced exchange properties as name value pairs, headers file as name value pairs along with the file containing the traced message body for this step.
On download, one zip will contain three files.
On opening the properties file, you will find the value of the properties.
I hope, you can benefit from the enhancements presented in this blog post. In case of questions or feedback, please feel free to comment on this blog.
The affected areas are :
- Record and display the exchange properties in the message content for flow steps
- Download of trace data including exchange properties
Record and display the exchange properties in the message content for flow steps
The cases where properties were defined and instantiated in flow steps like content modifier, scripts
were hard to troubleshoot with the existing tracing feature since these properties and its corresponding values were not shown in the message content of tracing feature.
With the version 2.44, this is now integral part of the tracing feature and it has been extended for the flow steps in the first increment where not only user defined exchange properties can be traced, but even the predefined properties coming from the incoming exchange shall be recorded.
The exchange Properties tracing can be extended for the adapters as well, if there are specific properties provided by adapters. We will keep you posted on any further updates on this front.
If you navigate to the MPL and open the step details of a step carrying trace data, the Message Content tab is available. Exchange properties for the incoming exchange is shown in the tabular format containing properties name value pairs like headers.
Just keep in mind, certain properties which are sensitive and confidential in nature from security standpoint will be removed, obfuscated or hashed.
In general with this 2.44 version, trace data shall look comprehensive containing following information in this order
- Header
- Exchange Properties
- Payload
The following example depicts a step recorded for a Groovy script capturing the initially received headers, properties and payload together propagated from the previous flow step which is content modifier in this case.
Download of trace data including exchange properties
We have as well enhanced the download feature of trace data where along with headers and payload, properties file can also be available in the one zip file. This can be helpful, if you want to provide this information to others for troubleshooting, for instance when opening a ticket with SAP.
Clicking this button triggers the download of a zip file, which will contain a file with the traced exchange properties as name value pairs, headers file as name value pairs along with the file containing the traced message body for this step.
On download, one zip will contain three files.
On opening the properties file, you will find the value of the properties.
I hope, you can benefit from the enhancements presented in this blog post. In case of questions or feedback, please feel free to comment on this blog.
- SAP Managed Tags:
1 Comment
