Thanks to the new improvements of PI 7.3 Advanced Adapter Engine, we are now able to make massive shifts of interfaces from Integration Engine to Adapter Engine using the Integrated Configurations objects. Thanks to the adapters type IDOC_AAE and http_AAE, it is now possible to go for a full Java PI project without any sacrifice considering monitoring functionalities.
Well, this is the customer or end user point of view. On my own developer opinion, my first steps with Java stack only shifts were quite different. My main issue was not really related to development itself. Mapping tools remains the same; I can keep testing mappings directly in the Enterprise Service Builder, no drawbacks here. Main issue is when I started testing End to End scenarios… How can I replace my SXMB_MONI?
Basically, this is the question I have faced a few months ago. I will here answer to simple cases scenarios were SXMB_MONI was my reference tool.
In order to fulfill these requirements, SAP provides PI with a new monitoring set of tools: The PIMON. You can access it using the directory just like other tools or directly with the following URL: http://<host>:<port>/pimon
The screen is divided into 3 main tabs: Monitoring, Configuration and Administration and Testing. We will focus on the first one. This tab is also divided into several parts. We will focus on the Adapter Engine tab.
Among all the functionalities, the most important to deal with if you search for an alternative to SXMB_MONI is the Message Monitor.
Message Monitor quick Start:
We will only talk about the 2 first tabs. The first one, Message Status Overview will allow you to get a quick overview of the entire message flows sorted by interfaces and status. Then, selecting a line and a status type, you will be directed to the Database tab. Each message is here listed in the bottom table. You can also access directly to this Database tab by clicking on it.
Note that in addition to the level detail difference, both screens also have a quite different level of selection. Indeed, Overview tab can only offer predefined time periods, while Database tab will allow you to define your own time periods but also to search by Interface/Partner type or by Message ID.
1…Get the error type?
One of the basic things you expect to find in monitoring. Assuming that you already have selected the message in Database tab, you can select Message Log tab at the bottom of the screen. If an error has occurred, you will find at least one line with status “Error”. The improvement here is that you do not have to check content of 2 different monitoring tools, the entire log is displayed here. No need of communication channel monitoring then.
2… Get the Header Content?
As per before, you must have selected the relevant message in the Database tab. Go to the Message Details tab. If you parse it, you will find most of the data you are looking for.
3… Get the dynamic Configuration objects?
In the same Database tab now switch to Message Content tab. You can view a similar tree as the one displayed in SXMB_MONI. Double-clicking on DynamicConfiguration section allows you to display the Dynamic Configuration Objects.
4…Get the different steps from message processing?
First, you have to select a message in the Message List table of the Database tab. When it is done, just click on the Open Message button.
This will open a new window. From there, you can have access to all the processing steps (if you have activated monitoring for all the steps). You can see the Payloads, Message Headers and Message Attributes.
5…Restart/Edit a message?
From there, you can use the Edit and Resend buttons to modify the message (header, attributes and/or payload) and restart its process. Please note two important things. As per before, messages in success cannot be reprocessed and you can choose from which step you want to restart. Just select the desired step line before clicking the Edit button.
Do not forget to save your modifications before clicking on the Resend button.