Skip to Content

As all of us know one of the interesting feature enabled with PI 7.1 EHP1 dealt with User-Defined Message Search. But since (as mentioned in Note 1247043) PI monitors in NetWeaver Administrator (NWAPI) is not supported for production scenarios most of us could not use this feature any further. With PI 7.1 EHP1 Support Package 6 the user defined search could only be configured in & used for the integration server ABAP client. As all of must be aware of by now the PI 7.3 comes with a JAVA only installation option (AEX). So does this mean we cannot use user defined message serach with AEX. Well the good news is now the user defined message search can be configured and monitored from an AEX installation. The user defined message search has been integrated with the new configuration and monitoring tool (pimon).

In this blog I will show how to configure and monitor user defined message search for an AEX installation (PI Adapter User-Defined Message Search). This holds true for a dual stack installation as well.

Configuration:

Navigate to PI Adapter User-Defined Message Search either via pimon->Configuration and Administration from the directory start page or via NWA -> SOA ->Monitoring -> PI Adapter User-Defined Message Search Configuration

 

Now click on the new button to create a filter and Provide the values for required fields along with sender and receiver components as shown below. All the values will be available via drop down (search help).

 

Now we need to create the search criteria for this filter (in the details section). This means we need to enter the fields we want to monitor on a given payload. You can monitor more than one field of a payload at once, only thing you need to create separate search criteria for them. You have an option of either monitoring a payload value (XPATH expression) or a field from the SOAP dynamic header. Please note the XPATH expression must yield a single value.

I am using the following test payload for this blog

 

Now we need to provide the namespace for the prefix value we have used in our XPATH expression. The only restriction is the prefix value cannot be longer than 8 characters.

Now if needed we can test our filter configuration by using the Test Search Criteria button.

 

Monitoring:

Now we can process a message which satisfies the filter criteria and navigate to the Message Monitoring section to check for the payload and the filter. In the Message Monitoring->Database we can use the user defined search criteria under Advanced option to provide our filter and corresponding values. Here you can provide more than one search criteria for a payload search which you have defined in the configuration step earlier.

 

You should see all the message that satisfy the filter condition.

 

Note: Now you can see a new tab has been added to the messages that satisfy a given filter with the set attribute and their corresponding values as shown below.

The user-defined search is one of the many ways to find messages in the Advanced Adapter Engine using the message monitor without the use of TREX. Optionally the user-defined search is also available for searching messages in the Integration Engine. You can configure it using transaction SXMS_LMS_CONF in a dual stack installation as well.

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. R-jay Galbizo

    Hi Abinash,

    Assuming you’re using the SFTP adapter to get all xml files setting it as * to. How can you define a filter on it’s filename? Other filters I have are working except for filename (which i want to include as well).

    I have defined it as:

    Nothing was populated. Not sure if this approach is feasible.

    Cheers,

    R-jay

    (0) 

Leave a Reply