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. Note 1418263 – Transaction SXMS_LMS_CONF: Test functionīefore to proceed with User-defined message search test I want to remark an important point related to PI message monitoring application. Don’t forget to Synchronize Cache for any change done on filters and extractors.Īfter creating extractors, flag filter as active and then you can test it with test extractor function. The picture shows a filter with two extractors searching for name and surname fields of a Service Interface using XPath expression. For each filter, it’s possible to maintain more than one extractor. In the samples I created two different filters to check messages executed on both IS and local AAE. Main transaction to define, maintain and synchronize filters and extractors is SXMS_LMS_CONF. Keep in mind that page contains information on how to configure filters and extractors as well. Since it’s a web service published in central Service Registry, you can also think to define filters and extractors with a different application.īeside this, just access transaction SOAMANAGER and follow instructions contained on Synchronizing the Cache section of SAP help pageĬonfiguring the User-Defined Message Search 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. A correct configuration shows PI Overview and common tasks list. ![]() Try to access :/nwapi and check if it’s properly configured, in case of issue please follow instructions contained into wiki Let’s start with needed configuration steps and some useful remarks to quickly enable this feature. 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. It also reduces TCO since separate TREX installation is not required. ![]() It’s very interesting since it allows searching asynchronous message by business-relevant information criteria contained in the message payload. , deals with User-Defined Message Search. New Features & Benefits for Enhancement Package 1 for SAP NetWeaver Process Integration 7.1 ![]() An interesting feature enabled with PI 7.1 EHP1, mentioned into SAP document
0 Comments
Leave a Reply. |