Show TOC

Configuring Components for Index-Based Message SearchingLocate this document in the navigation structure

Use

For each component of an integration landscape that creates and persists messages (Integration Server, Adapter Engines and Integration Engines), a unique index can be created that contains all the messages of this component. The SAP NetWeaver search and classification engine TREX is required for this purpose.

To configure a component for index-based message searching, you have to:

  • Ensure that the component is based on one of the following SAP NetWeaver versions:

    • SAP NetWeaver Process Integration 7.1

    • SAP NetWeaver 7.0 Support Package Stack 06 or above

    • SAP NetWeaver '04 Support Package Stack 15 or above

    This is also valid for the AS Java, on which your Runtime Workbench is running.

  • Establish a communication between the component and the TREX server.

  • Set up and maintain the indexing of messages on this component.

More information: Index Administration .

Prerequisites

To enable an index-based message search in an integration landscape by using TREX, you require a TREX installation of the most current support package stack on a separate server. For more information, refer to the installation guide of the SAP NetWeaver standalone engine TREX on SAP Service Marketplace at service.sap.com/instguides nw .

More information about TREX: Technical Operations in Detail

Note

Using TREX for index-based message searching may have an impact on the sizing of your TREX server.

Configuring the Communication with the TREX Server

You have to set up the communication with the TREX server separately for ABAP components (Integration Engines) and for Java components (Adapter Engines and Runtime Workbench).

Integration Engines (ABAP):

ABAP components communicate with the TREX server by using a separate TREX RFC connection. More information: Configuring the RFC Connection in the TREX Admin Tool .

  1. Call transaction SXMB_ADM.

  2. Choose Integration Engine Configuration .

  3. Choose Change Specific Configuration Data .

  4. Add the parameter TREX_RFC_DESTINATION to the category MONITOR.

  5. In the column Current Value , specify the TREX RFC connection and save your entries.

Adapter Engines and Runtime Workbench (Java):

For Adapter Engines and for the Runtime Workbench, the data required for communicating with the TREX server is maintained on the corresponding AS Java. To configure the TREX service for each cluster server node, perform the following steps:

  1. Start the SAP NetWeaver Administrator.

  2. Choose Start of the navigation path Configuration Management  Next navigation step  Infrastructure Management  Next navigation step  Java System Properties  Next navigation step  Details  Next navigation step  Services End of the navigation path.

  3. Select the service TREX Service .

  4. Enter the TCP/IP connection data for the property nameserver.address .

  5. Save your changes and choose Start & Stop: Java EE Services to restart the TREX service on each cluster server node.

Maintaining the Indexing of Messages

Use the Index Administration function of the Runtime Workbench to set up and maintain the indexing of messages on your integration landscape components.