Configuring User-Defined Message Search

1. Prepare Test Messages

Prepare at least one test message that contains the payload to be indexed. Make sure that this message is processed successfully and, that you see it in the NWA Message Monitor. Open it with the NWA Message Editor and make sure that it has a version that includes the payload you target for indexing. For optimal performance make sure that you configure it as few message staging and logging versions as possible. Mark down the exact header data for the specific message version that you target for indexing as you will need them in the next steps.

2. View Filters

1. Do one of the following to access the user-defined configuration options:

   • Open a browser and go to http://[host]:[port]/pimon to access the Process Integration tools. Then choose  Configuration and Administration  Adapter Engine  User-Defined Search Configuration .

   • Open a browser and go to http://[host]:[port]/nwa to access SAP NetWeaver Administrator. Then choose  SOA  Monitoring  PI Adapter User-Defined Message Search .

2. Use the following options in the List of Filters screen area to display the filters:

   • Use the Show dropdown menu to display the active, inactive, or all filters.

   • Use the controls on the right to refresh the filter list, show, or hide the search or filtering options, and select the size of the table displaying the filters.

3. Create Filters

1. Do one of the following:

   • To create a new filter, choose the New button.

   • To edit existing filters, select them in the table and choose the Edit button.

     You can select many filters by holding the Ctrl or Shift key.

2. Enter or modify the filter details as follows:

   • It is mandatory to enter the interface and namespace. If needed, you can create more than one filter for the same interface.

   • Set the status of the filter.

   • For new filters, it is mandatory to enter the name of the filter.

   • Optionally, enter details about the sender and the receiver.

   Note Message header fields are matched literally, for example empty sender component will match only message versions with empty sender component. Use wildcard * to match any value.
   Note

   The system does not display the input values for messages that are marked sensitive in Enterprise Services Repository as these messages contain confidential information.

3. Choose Add to finish modifying the filter.

   Optionally, you can create new filter, or modify or delete some of the filters displayed in the list of unsaved filters.

4. Choose Save .

4. Define Search Criteria

1. Select the filter for which you want to define search criteria and choose the Search Criteria tab.

2. Choose New to create new search criteria.

   If you want to edit some of the existing search criteria for this filter, select them and choose Edit .

3. For new search criteria, enter a name and optionally a description.

4. Select one of the following options for the type of the search:

   • Choose Dynamic Header if you want to search for additional information written to the message header by sender adapters. Enter the header and its namespace.

   • Choose XPath Expression if you want to search for information in a particular element or attribute inside the message payload.

     Example To find the OrderID in this XML:

     <urn: OrderReqMT xmlns:urn="urn:test"> 
         <Order>
             <ID>1</ID>
             <Name>nuts</Name>
         </Order>
     </urn: OrderReqMT>
     

     You would use XPath: //ns0: OrderReqMT/Order/ID and prefix definition with value: ns0 and namespace: urn:test.

     Enter the XPath expression using the rules of version 1.0 of the XPath language. For more information, see http://www.w3.org/TR/xpath/.

     Note Use only XPath expressions that return a single value. Do not use XPath expressions that return whole subtrees, such as child::* or //Person (where Person is an element in the message payload that contains child elements).

   • Choose Custom Dynamic Header if you want to search for additional information written to the message header by the users through channel modules. Enter the header and its namespace.

5. Choose Add to finish modifying the search criteria.

   Optionally, you can create new criteria, or modify or delete some of those displayed in the list of unsaved search criteria.

6. Choose Save .

5. Define Namespace Prefixes

You can use a namespace prefix instead of a namespace in XPath expressions. You always define a namespace prefix for a given filter. You can then use it for all search criteria of type XPath for this filter. To define a namespace prefix, proceed as follows:

1. In the filter list, select the filter for which you want to define the namespace prefix.

2. Choose the Prefixes tab and then choose New .

3. Enter the namespace and the prefix and choose Add .

   You can optionally define new prefixes or delete some of the unsaved prefixes.

4. Choose Save.

6. Index Messages and Test Search Criteria

1. You can test if a search criterion can locate a particular message as intended. To do this, choose Test Search Criteria , enter the ID of the message, specify the direction of the message, and run the test.
   Note

   • The test result maintains the order of the attributes in the payload.

   • The system does not display the messages that are marked sensitive in Enterprise Services Repository while performing a search.

   • If the message is not stored in the Advanced Adapter Engine either after the receiver determination phase or the mapping phase, the system does not display the message in the test results.

     For more information, see Saving Message Versions in the AAE (Local Message Processing)

2. Choose Indexing Options to create an index of the messages that match the active filters and search criteria.

   Consider that the system indexes automatically messages for a filter from the moment the filter is created. You can use the Indexing Options feature when you want to index older messages processed by the system in a specific period of time before creating the filter.

   Specify the start and end date of the period for which messages should be indexed. After the indexing starts, you can check whether the indexing job has been completed using the Indexing Status button.

   Note The system does not index messages that are marked sensitive in Enterprise Services Repository as these messages contain confidential information.

7. Troubleshooting

• Make sure that your filters and extractors are configured correctly using the Test Search Criteria. It is pointless to start the Index job if your test message could not be indexed correctly.
• For the best performance, define specific filters that target the explicit message version. Limit the wildcards to avoid applying too many extractors.