User defined message search in 7.1 EHP1

Hello!
I'm trying out the user defined message search right now and it's great. However, I got one question about the indexing. In what way and how much will this affect the system?
Any ideas?

Hi Stefan - We have configured UDMS in our landscape and I don't see any big impact in terms of system performance so far.( We are on 7.3 and all our scenarios are ICo's)
On the other side for the PI release that you are currently on(7.11), has some limitation for the productive usage.
Have a look at the below notes from SAP:
PI monitors in NetWeaver Administrator not supported for production scenarios
PI monitors in NetWeaver Administrator not supported for production scenarios. This includes the user defined message search functionality, e. g. the search for payload attribute values; the lean message search is therefore not supported for production scenarios, and this includes the configuration of this functionality as well as the monitoring at runtime. Starting with Support Package 6 for EHP1 for SAP NetWeaver PI 7.1 the user defined search can be configured in & used for the integration server ABAP client. The SAP NetWeaver Administrator for PI is not supported for use in production scenarios. Not all PI monitors from the Runtime Workbench are completely integrated  into the SAP NetWeaver Administrator for PI. SAP recommends that customers use the Runtime Workbench for PI monitoring in production scenarios and would not support the installation, configuration and usage of the SAP NetWeaver Administrator for PI.
Reference : 1247043 - Release Restrictions for EHP 1 for SAP NetWeaver PI 7.1

Similar Messages

  • User-Defined Message Search - PI 7.1 - EHP1 - SP06 - Not working

    Hi Friends,
    Recently, we have imported SP06 in our PI system (PI 7.1 EHP1). The SXMB_MONI has now new tab "User-Defined Selection Criteria".
    To implement user-defined search, I have created filer, extractor, namespace prefix for one outbound interface through transaction SXMS_LMS_CONF. (As it is explained in SAP EHP1 features PDF and the link "http://help.sap.com/saphelp_nwpi711/helpdata/en/48/c85598f63335bfe10000000a42189d/frameset.htm".
    Also we have created logical port through transaction SOAMANAGER. (followed the steps as mentioned in PDF)
    After filters, extractor, namespace prefix created and activated, I have checked the extractor through Test Extractor, it is working fine. (All are green, given below is the output)
    Type
    Message text
    Processing message 4DDFE95BAEC67152E10000009958A8AB
    Analyzing payload of message version 000
    No filter found
    Analyzing payload of message version 004
    Filter found for interface name PROACT.PROACT01
    Name MATERIAL_ID value RPM312AZ/11522R1 extracted
    Analyzing payload of message version 005
    No filter found
    Analyzing payload of message version 008
    No filter found
    Now, when I do search the same through SXMB_MONI, by giving inputs in the new tab "User-Defined Selection Criteria", Option button "Search for all" , selected the filter name "MATERIAL_ID" in the input field:Name and put material name in the  in the input field:value. (same material I put), it shows the message "No message is available for selection".
    Friends, could you kindly clarify why I am unable to search through SXMB_MONI? Am I missed any of the steps?
    Kindly reply.
    Kind regards,
    Jegathees P.

    Were you able to resolve the issue ?
    If not, You need to execute program SXMS_EXTRACT_MESSAGES to build index for the user defined search from the old messages.
    The job bulids index from the already processed messages.
    Choose the relevant Method when creating the extractor
    Method
    You can choose between two methods:
    Extract During Message Processing
    Select this method if you want the attributes to be extracted from the selected messages while these messages are processed.
    Extract with External Job
    Select this method if you want to extract attributes from messages that were already processed, or if you want to change the extraction of attributes from messages, from which attributes were already extracted.
    For this method you need to set up and use the job SXMS_EXTRACT_MESSAGES.
    thanks
    VJ

  • User defined message search in PI 7.1 EHP1

    Helly,
    I heard about the new feature in EHP1: "Search asynchronous messages by business-relevant information criteria contained in the message payload (SalesOrder Number, customerID, etc)."
    Has anybody tried it yet? Is that realy as simple as it sounds? Can I just search for any free-text information in the SXMB moni? What steps are necessary to use this feature?
    Thanks,
    Christoph

    Hi Christoph,
    User defined message search enables you to search for messages using the XML payload attributes or using the adapter specific message attributes.
    Implementation:1) Execute the transaction SXMS_LMS_CONF.
                               2) Define the filter to select the message you want to search. Filter is selected on Service Interaface level(bot outbound and inbound side).
                               3) On that filter define a extractor.Extractor uses an XPath expression to search for attributes in the payload of a message or you can also selcet select dynamic header for adapter-specific message attributes
                               4) And at last define the namespace prefix (optional step). 
    Thanks
    Amit

  • Performance restrictions using User-Defined Message Search in PI 7.1 EhP1

    Hi Gurus,
    We want to apply the User-Defined Message Search in our productive system.
    We also want to set the extractors to run during Message Processing .
    Do you have any inputs on how this might affect the system performance?
    Any best practices, previous experiences or thoughts on that?
    Some of my questions:
    How many Filters/Extractors would be a limit to not affect too much the messaging processing performance?
    Running the extractors during message processing would greatly affect the performance? When to run the extractors in a batch job instead of runtime?
    Any input is greatly appreciated.
    Regards,
    José Omar

    Hi José ,
    We are also planning to use User-Defined Search feature in our PI system. Could you please let me know whether or not were you able to use this in your PI productive environment?
    Additionally , if you were able to use it can you please let me know the performance?
    Thanks in advance
    Edited by: Ravindra Hegde on Jun 3, 2011 11:26 AM

  • Error in SXMS_LMS_CONF-User Defined Message Search

    Hi Experts,
    I  am trying to implement the user defined message search feature in PI 7.1 EHP1.
    I have done the require configuration as mentioned in the help document
    http://help.sap.com/saphelp_nwpi711/helpdata/en/48/c85598f63335bfe10000000a42189d/frameset.htm
    and also i checked all the screenshots mentioned in the EHP1 new features  article
    FEATURED EVENTS
    I am getting the error in  test extractor SXMS_LMS_CONF and the error text is
    "Error reading message CENTRAL F99654D7FD61463C345CA35621680000"
    I have checked in NWAPI by running the test , it shows "No messages available for selected filter criteria"
    Any pointer to additional/missing config required  will be of great help.
    Regards,
    Srinivas

    Hi All,
    I doubt if i have mentioned the port number and client correctly in the Logical port configuration step in soamanager.
    In the screenshot in the guide i can see.
    Port number : 50000
    ESR  Target client : 800. (page 34)of guide mentioned above
    and the Url access for nwapi  shows  http://<host>:50080/nwapi (page 21)
    for my system
    http://<host>:50700/nwapi ,
    PI client is 001.
    System ID is 07
    I am confused what to mention for ESR clinet and Port.
    Regards
    Srinivas

  • User defined message search on Archived messages in PI 7.31

    Hello Experts,
    We are using XMLDAS to archive the messages of the adapter engine into a file system.
    User defined search is working fine for the messages in the database, based on the UDMS criteria, in database tab of message monitoring. And as per SAP, "Extracted attributes are archived together with the message and could be used for searching".
    But for us,once the messages are archived into a file system, the UDMS criteria is not working from the archive tab in message monitor.We are able to retrieve the messages in the archive tab based on the message id and also the payload content from it but not using UDMS.
    Please let us know if we need to do any specific configuration for the UDMS criteria to work on archived messages as well.
    Regards,
    Ram

    Hello Michael,
    Please check following links for configuration and re-check.
    PI 7.3 – Adapter User-Defined Message Search without TREX
    Configuring User-Defined Message Search - Advanced Adapter Engine - SAP Library
    Also I believe you are searching for new / fresh messages after you configured UDMS. I believe it will not show up old message list prior to UDMS config.
    Hope it helps
    Regards,
    Azhar

  • PI 7.3 Dual Stack User-Defined Message Search

    Hi All,
    I have implemented an Integrated configuration scenario SOAP-> PI – ABAP Proxy the scenario is sync the. The scenario has no mapping so
    no operation mapping exist in the configuration scenario.
    I tried setting up UDMS on the java stack without any success.
    My questions are: is it possible to use UDMS if there is no mapping steps? And also does UDMS work for sync messages?

    Hi Jannus
    Check this document
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/803b22cf-ad75-2f10-0790-da055f2e8c0e?overridelayout=t…
    On the very fast line it is written
    "User Defined Message Search enables to search for asynchronous messages using the information available in payload or adapter-specific message attributes."
    Last time we tried to configure UDMS for sync messages, but we were not able do that.
    Thanks,
    Indrajit

  • Problem with the user-defined message search in PI 7.3.1

    Hi, all
    I having been trying out the new user-defined message search in PI 7.3.1(with TREX). I am stuck on creating the search critera section and could not move forward. Here is how I define the filter:
    Here is a sample payload:
      <?xml version="1.0" encoding="utf-8" ?>
      <ns:JOB_MT xmlns:ns="urn:peoplesoft:batch:job_r:message">
        <MsgData>
          <JOB>
             <ACTION_FLAG>NewPerson</ACTION_FLAG>
             <EMPLID>XXXXX</EMPLID>
             <REG_NO />
             <LAST_NAME>XXXX</LAST_NAME>
             <FIRST_NAME>XXXX</FIRST_NAME>
          </JOB>
        </MsgData>
      </ns:JOB_MT>
    I have tried the xpatch search criteria as the following:
    /ns:JOB_MT/MsgData/JOB/EMPLID
    /ns:JOB_MT xmlns:ns="urn:peoplesoft:batch:job_r:message"/MsgData/JOB/EMPLID
    Both failed to return the emplid field when I clicked on the "test search criteria" against a PI message. Can you advise what I did wrong?
    Thanks,
    Jonathan.

    Hi.
    Did you put the prefix?
    Regards

  • Reg: Configuring the User-Defined Message Search

    Hi Experts !
    I am getting an error while configuring the user defined message search.
    Followed all the step mentioned in the sap help documentation.
    http://help.sap.com/saphelp_nwpi711/helpdata/en/48/c85598f63335bfe10000000a42189d/frameset.htm
    The last step, where we need to enter  URL for WSDL Access i am getting the following error:
    Error in WSDL access: Exception occurred in communication framework:
    Error in HTTP Framework:404Not Found
    http://<Host>/<Port>/MessageSearch/MessageSearchImplBean
    You should enter the host name and the HTTP port for the Advanced Adapter Engine
    i didnt get the meaning of above sentence : Is it different from what we use in the URL to access ESR and ID.
    Is there any other steps to make   MessageSearch/MessageSearchImplBean available
    Regards,
    Srinivas
    Edited by: Srinivas on Oct 1, 2010 7:48 PM

    Hi José Omar,
    thanks for the reply...
    I tried manual configuration but with no luck..opened a similar forum thread
    I have applied the sap note suggested  ,thinking that the error is due
    to any source code.
    The data synchronization is happening properly , but when i use test extractor button it throws the above mentioned error.
    In the system details  in have given the port number as 50700(which is visible in the link when we open integration builder page) and ESR client as 001.
    could you please let me know if the exact values to be filled in transport setting.i just entered the port and client , other things
    as default.
    Regards,
    Srinivas

  • Indexing Failed - User-Defined message search

    Hi
    I am trying to set-up a user-defined message search in our PI 7.3 system. After having created a filter and defined a search criteria, SAP says to "create an index of the messages that match the active filters and search criteria"  [Link|http://help.sap.com/saphelp_nw73/helpdata/en/48/b2e0186b156ff4e10000000a42189b/content.htm]
    Every time I try to run indexing it fails. I don't know why as there is no help-button available and I haven't found anyone experiencing the same issue. Anyone else experienced the same issue?
    Also - using XPath - do I have to consider any particular namespace prefix etc for PI messsages? I have tested my XPath on payload XML in XMLSpy, but the search functionality seem to expect a different format on the XPath syntax...
    Thank you!
    regards Ole

    Hello,
    I have set this up for an interface now. I am not sure how important the index job is because
    the indexing job worked in the dev system, never stopped in QA and failed in prod. Anyway the message search works in all three systems.
    The following blog made me understand the namespace prefix:
    http://scn.sap.com/people/abinash.nanda/blog/2011/08/17/pi-73--adapter-user-defined-message-search
    Regards,
    Per Rune

  • User-Defined Message Search

    Hi experts,
    I've configured the User-Defined Message Search on my PI 7.11.
    Do u need to configure Jobs that will delete the entries that the extractor collects ? what is the impact on the DB ?

    With regard to the necessary configuration on the system for the user defined message search you can check the following
    Configuring the User-Defined Message Search:
    http://help.sap.com/saphelp_nwpi711/helpdata/en/48/c85598f63335bfe10000000a42189d/frameset.htm

  • User defined message search criteria on ECC

    Hi Experts,
    I have configured UDMS-user defined message search under ECC (for message search in MONI) using T-code: SXMS_LMS_CONF and while defining extractors, I have selected both check boxes.
    1. Extract during message processing
    2. Extract with external Job
    As per my knowledge, 1st option indexes all messages which are processed after we activate filters.
    2nd option is used to index previous messages which are processed before defining filter.
    For me 2nd option is working fine (I can search old messages which are indexed using a program:  SXMS_EXTRACT_MESSAGES).
    But 1st option is not working. I have created filters yesterday and activated also, but couldn't able to trace today messages using user defined search.
    Please help in this regard.
    SP.

    Hi.
    From SAP Note.  1600078
    Solution
    Most problems occur because you use the communication components or partners as the filter criteria in the filter even though you want the system to index only certain interfaces. In this situation, you must always set the components or partners to "*".
    If you specify components or partners, you must consider how indexing of messages runs technically. If indexing is called at runtime, the system executes it at the start of the Integration Engine and at the end of the Integration Engine; this means that the value that the components or partners have at this point is definitive. For example, if you have defined a receiving component, this is not set at the start of the Integration Engine (except in special cases) and this is why the filter does not select the message. It also has no effect at the end because the message contains the receiving interface after the mapping. If you call the test function of transaction SXMS_LMS_CONF, the filter is used on each individual persistent version of the message (the same process as when indexing via a job). If the message is made persistent directly before the mapping, the sender interface exists there and the receiving component or partner is set. Therefore, the filter described above would be active here. As a result, this function is better defined to check the XPath than the filter criteria.
    Check if you put  * in the receiver component.
    Regards
    Lucho.

  • User Defined message search on archived messags

    hi all,
    Am not able to retrieve search result in archived messages when using user defined message search. any idea ?
    tx
    mike

    Hello Michael,
    Please check following links for configuration and re-check.
    PI 7.3 – Adapter User-Defined Message Search without TREX
    Configuring User-Defined Message Search - Advanced Adapter Engine - SAP Library
    Also I believe you are searching for new / fresh messages after you configured UDMS. I believe it will not show up old message list prior to UDMS config.
    Hope it helps
    Regards,
    Azhar

  • Enhanced End to End Monitoring u2013 User Defined Message Search?

    Hi Guys,
    I need to search asynchronous messages by business-relevant information criteria contained in the
    message payload (SalesOrder Number, customerID, etc).
    This is possible from EHP1, can somebody explain how to define the filters and i have found in the EHP1 new feauters document that this can be done through ABAP transactions.
    I want to find the message based on the PO number or Sales Order Number
    Configuration via ABAP transaction
    Filters and Extractors
    Fields are extracted by XPath expressions
    any help would be appreciated
    Thanks,
    Srini

    Hi Guys,
    I have followed the oss note 1143645 and run the wizard to configure the NWA and i am getting the errors as below. I have skipped these 2 steps but i need to fix these errors.
    1.Adding server certificate to central System
       Exception in step "addCertificate"
      Exception details : java.lang.Exception: An exception occured while adding Certificate in
      importServerCertificate(): SYSTEM_DOES_NOT_CREATE_TICKETS
      Step was skipped
    2. Get CCMSPING Destinations
        Exception in step "RFCConfig"
        Exception details : com.sap.tc.lm.ctc.metamodel.exception.ActionExecuteException: Execution of
        Function SCSM_GET_CCMSPING_DESTINATIONS ends with an error
        (cause:NO_DESTINATIONS_FOUND:, error code:000).
        Step was skipped.
    I have followed the below link but could not figure out How to register CCMS agents keeping PI as CEN.
    Re: Getting error while Configuring NWA for PI 7.1
    How to register the CCMC ping agents in PI ?  Any hep would be appreciated
    Thanks,
    Srini
    Edited by: Srinivas Reddy on Aug 26, 2009 8:56 PM

  • Sizing Impact for Trex and user defined Message search

    Hi All,
        In PI 7.1 we have content base search in nwapi and also we have trex based earch. Do any one have any idea about the sizing impact for the both...?
    Regards
    Pradeep P N

    Hi.
    From SAP Note.  1600078
    Solution
    Most problems occur because you use the communication components or partners as the filter criteria in the filter even though you want the system to index only certain interfaces. In this situation, you must always set the components or partners to "*".
    If you specify components or partners, you must consider how indexing of messages runs technically. If indexing is called at runtime, the system executes it at the start of the Integration Engine and at the end of the Integration Engine; this means that the value that the components or partners have at this point is definitive. For example, if you have defined a receiving component, this is not set at the start of the Integration Engine (except in special cases) and this is why the filter does not select the message. It also has no effect at the end because the message contains the receiving interface after the mapping. If you call the test function of transaction SXMS_LMS_CONF, the filter is used on each individual persistent version of the message (the same process as when indexing via a job). If the message is made persistent directly before the mapping, the sender interface exists there and the receiving component or partner is set. Therefore, the filter described above would be active here. As a result, this function is better defined to check the XPath than the filter criteria.
    Check if you put  * in the receiver component.
    Regards
    Lucho.

Maybe you are looking for