Skip to Content

Payload Searching without TREX

An interesting feature enabled with PI 7.1 EHP1, mentioned into SAP document

New Features & Benefits for Enhancement Package 1 for SAP NetWeaver Process Integration 7.1

, deals with User-Defined Message Search. It’s very interesting since it allows searching asynchronous message by business-relevant information criteria contained in the message payload. It also reduces TCO since separate TREX installation is not required. After defining filters and extractors, you just  need the access to Message Monitor java application to search payload of messages executed on both Integration Server and local Advanced Adapter Engine.

Let’s start with needed configuration steps and some useful remarks to quickly enable this feature.

System Configuration

Try to access http://<host>:<port>/nwapi and check if it’s properly configured, in case of issue please follow instructions contained into wiki


. A correct configuration shows PI Overview and common tasks list.

XI Component

To enable cache synchronization for defined filters and extractors, there is the need to create a logical port for Consumer proxy named MessageSearch with implemented operation SetMessageFilters. Since it’s a web service published in central Service Registry, you can also think to define filters and extractors with a different application.

Ws navigator

Beside this, just access transaction SOAMANAGER and follow instructions contained on Synchronizing the Cache section of SAP help page

Configuring the User-Defined Message Search

. Keep in mind that page contains information on how to configure filters and extractors as well.

Soa management

COnsumer Proxy


Web service navigator

Filters and Extractors definition

Main transaction to define, maintain and synchronize filters and extractors is SXMS_LMS_CONF. In the samples I created two different filters to check messages executed on both IS and local AAE. For each filter, it’s possible to maintain more than one extractor. The picture shows a filter with two extractors searching for name and surname fields of a Service Interface using XPath expression. Don’t forget to Synchronize Cache for any change done on filters and extractors.

Filter definition

After creating extractors, flag filter as active and then you can test it with test extractor function. In case of issue apply SAP

Note 1418263 – Transaction SXMS_LMS_CONF: Test function


Test extractor


Test Scenario

Before to proceed with User-defined message search test I want to remark an important point related to PI message monitoring application. If you access Sap Netweaver Administrator and follow the links SOA Management->Monitoring->PI Message Monitoring, you are accessing Message monitor application for ONLY local web services and local AAE processed messages and not the ones processed on Integration Server. A detailed description with more information is also available into SAP help page Monitoring Messages  (

Message Monitor

Finally, the scenarios I tested adopted following technology:

•    Soap->PI->File (AAE)

•    IDoc->PI->Proxy (IS)

After running a test over PI, access Message monitor application and select Database label of Integration Engine component, then choose Advanced, then Select User-Defined Attributes to add attributes defined with transaction SXMS_LMS_CONF.

Pi overview

Soap->PI->File scenario search results

AAE search

IDoc->PI->Proxy scenario search results

!|height=400|alt=IS search|width=599|src=!</body>

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