Note: Process monitoring within the iPaaS workflow is in your responsibility. System monitoring is the responsibility of SEEBURGER. |
If you are assigned the user role "Message Tracking user", you can find the app Message Tracking in the BIS Portal. The app is ready to use.
Find more information on assigning user rights here:
Message Tracking is an app for monitoring the processing of messages within the iPaaS workflow. You can use it to check the processing status of your messages. This is especially useful for the specialist departments of your company, when they want to know if a message has been sent, etc.
You can use Message Tracking also to identify issues like conversion errors (e.g. invalid EDIFACT format) and communication errors with your trading partners or your backend systems. You can check logfiles for specific processes and filter the data on a high level perspective, like business process, partner, status, etc.
Typical error sources that need to be corrected (such as simple syntax errors, message contents/master data errors) can thus be identified. SEEBURGER can support your IT department during the analysis of the source of an error and suggest solutions.
Message Tracking is meant for monitoring and checking the BIS processes in a general overview, checking the issues in detail can be done in the BIS Front End where you will find logfiles as well. You can use the track ID from Message Tracking to find a specific process in the BIS Front End Process monitor or Solution monitor.
> Process monitoring via BIS Front End
Information: Information stored in the Message Tracking is stored for 60 days per default and is automatically deleted thereafter. An individual storage period can be specified in the service schedule. |
Message Tracking is operated separately for the staging and the production environment. That means, you can track your messages exactly for each of these systems.
You can find a user manual for Message Tracking in the app Documentation in your BIS Portal.