PI/XI: Selecting messages using the content of the message in SAP PI 7.3 – teaser
The content based message search on the java engine was known in SAP PI 7.1 but as SAP decided to sunset /nwapi tool (which was not supported on production landscapes) there had to be an alternative for that. As of PI 7.3 we have a new way to configure and use content based message search on the java engine and this article will explain the steps involved.
Step 1
At first you need to create a new filter which will contain your XPATH expressions which can be indexed once your messages will start flowing. Inside this filter you need to fill in the details like the name of the filter, interface and namespace name and some other like sender or receiver component/party.
Step 2
Next you to add your search criteria which will be your XPATH expression.
Step 3
If you have a message inside your PI monitor already which can be used for testing there is a way to test your xpath expression directly from the configuration screen, you just need to supply the message ID.
Step 4
Once you save your filters and your message will start running you can go to the message monitor and check if the content based message search works. You need to select user defined message search and add a predefined criteria.
Step 5
Next you need to select your filter and put the value you’re looking for in the Value and once you run the monitor your message should be selected.
Note
Please remember that content based message search by default works only after you define and save it in the configuration so if you’d like to use it for messages which you received before creating the filter you need to go to the filter configuration and run the indexing program yourself (starting with the data on which the message reached PI).
I hope this gives you a better overview of the new content based message search with SAP PI 7.3.
I have an aditional question: as you said, /nwapi tool for PI 7.1 EHP1 is not supported in production landscapes, so how can we achieve this functionality in PI 7.1 EHP1?
In pi 7.1 EHP1 this funcionality is working, only to the IE.
you have to configure the filters in the ABAP transaction SXMS_LMS_CONF
y monitorear en la transaccion ABAP SXMB_ADM
but you must upgrage to the stack 06 to monitor, or you can build a report
Regards,
Ariel Mena
Hi Michal,
Does the note below mean that for searching through messages that you received after you created the filter it's no necessary to index? i.e. the search will index them automatically after they are received in PI?
Thanks,
Roberto
Hi,
>>>i.e. the search will index them automatically after they are received in PI?
no, they will be indexed automatically - but messages from the past you need to index manually,
Regards,
Michal Krawczyk
I have no issues with indexing but when executing step 3, I am getting an error
However there is nothing in NWA log.
my expath is: /<namespace>:MT_EMP/Record/Employee/Name
is this correct format?
Kindly revert
Regards
Anand
Hi Michal,
I am using version 7.3. I am receiving message from 3rd party in single string format. I reckon I won't be able to create filter in this case. is that right?
Can you please let me know how to handle such situation?
Regards,
Pratibha
Hi Michal,
I'm using version 7.31 java stack only.
I defined some user defined searches.
Everything is working fine when searching for messages in database in the message monitor.
But once the message is getting archived I can't use the user defined search in the archive tab of the message monitor to find messages.
It's always returning 0 messages. The messages are there and I can access their payload.
I used XML DAS to archive the messages.
I read your blog on how to access the tables of the user defined attributes (XI_AF_LMS_DATA).
Through this table I would be able to find message ID's corresponding to my search criteria's but it's just not what we need.
We would like to be able to use the user defined search via the message monitor archiving tab.
Any idea what could be the problem?
Kr,
Sebastien
Hi Michal
I am trying to configure User defined search in AE of SAP PI 7.4
But for some of the interfaces i am facing the issue. I get error stating that Service Interface or Namespace doesnot exist in the set of allowed list.
This issue is only happening when i am trying to configure UDMS for Business Systems like ECC, CRM...etc. for other components it is working fine.
Please suggest
Hi,
I just came upon this entry and would like to ask some questions re: indexing
I understand that the indexing is automatic once you set the the filters and activate. Will the indexing stop if you set the filter status to 'Inactive'?
Our concern is on the impact of indexing to the system's performance especially for high volume traffic. Is there a way to see the database for the indexing and monitor how it grows for a period?
Cheers,
Kes