Index Administration 

Purpose

You use the index administration to control and monitor the indexing for the index-based message search.

Prerequisites

The following prerequisites must be fulfilled before you can use the index administration:

●      You have set up the communication between your components (Integration Engines and Adapter Engines) and the TREX server.

●      You have started the Runtime Workbench and have chosen Index Administration on the initial screen.

●      You have the authorizations of role SAP_XI_ADMINISTRATOR.

Process Flow

To manage your indexes, you proceed as follows:

●      You administer the indexing for all components that can communicate with the TREX server.

●      You specify global parameters that are valid for all components and that are passed to the components when indexing is active.

●      You manage filters, which you use to restrict the indexing of messages according to the defined selection criteria.

Administration of Indexing

To work with indexing administration, choose the Index Administrationtab page (default setting). The system displays a table listing all the Integration Engines and Adapter Engines maintained in the System Landscape Directory (SLD).

You can index all components that are based on SAP NetWeaver '04 Support Package Stack 15 or higher, or SAP NetWeaver 7.0 Support Package Stack 06 or higher, or SAP NetWeaver 7.1.

The table also provides the following information:

●      Status of indexing:

○       Green (): Indexing is active and has no errors

○       Yellow (): Indexing is active; warnings exist

○       Red (): Indexing is active; errors exist

○       Grey (): Indexing is not active

○       Red with lightening (): Status is not known; communication with component is not possible

●      Component name

●      Type of indexing

The type of indexing selected (standard or fast) is displayed.

●      Date and time of the last indexing

●      Number of messages available in index

●      Date, time, and initiator of last change

Depending on the status of the selected component, you can perform the following activities:

●      Choose Refresh to refresh the data displayed.

●      Select a component and then select:

○       Log, to display the log file for the indexing of the selected component.

The log is displayed beneath the table and contains detailed information that may be useful if errors occur.

■       A return value of -1 indicates that an exception was raised. The exception text is displayed.

■       A return value of 0 indicates that no errors have occurred.

■       A return value greater than 0 is an error code from TREX. For more information, see SAP Note 898404.

○       Details, to display more information about the errors that have occurred for components with a red error status ().

○       Type of indexing

If you select fast instead of standard indexing, certain analysis steps are skipped, which speeds up indexing considerably.

The fast indexing method does not support texts in non-segmented languages (Japanese, for example). If you use the fast method for these languages, this can cause unforeseen problems.

○       Activate, to activate the set indexing and create an index for the selected component.

○       Deactivate, to deactivate the set indexing and delete the index for the selected component.

○       A date in the Delta Indexing From field; a delta indexing is to be performed for the selected component for the time period starting from this date up to the current date.

○       Start, to start the delta indexing from the selected date.

Global Settings

The global settings are on the Global Settings tab page. Global parameters are parameters that are valid for all components. They are passed to the relevant components when indexing is activated, and control the indexing of messages on these components. Each parameter has a default setting, which you should only change if required; you can restore the default settings for parameters at any time. The following parameters are available:

●      Maximum number of messages per package to be transferred to the TREX server

When you activate indexing, an indexing service is scheduled, which uses a background job to periodically transfer any new or changed messages in packages to the TREX server for indexing.

●      Maximum size in KB of message packages transferred to the TREX server

●      Time interval in minutes for the periodic transfer of message packages to the TREX server for indexing

●      Time interval in hours for the periodic reorganization of the index of a component on the TREX server

A reorganization service is scheduled after the messages are transferred to the TREX server; this reorganization service deletes messages from the index after a specific, preconfigured retention period.

●      Time period in days for the retention period of messages in the index

●      Time interval in minutes for the periodic processing of the TREX queue

When the TREX server receives the data, it stores it in a queue. A TREX queue is an index, which is periodically processed and which triggers the indexing of messages.

●      Maximum number of entries for processing in the TREX queue

Selection Filters

You can create (and delete) filters to restrict the indexing of messages according to the specified selection criteria. If the filter is left empty, all messages on a component are indexed.

You can specify the following sender and receiver attributes as selection criteria:

●      Party

●      Component

●      Interface name

●      Interface namespace

All fields permit generic entries with an asterisk (*): Input help is available.

The values of the Interface Name and Interface Namespace attributes are combined with OR and applied to both interfaces (sender and receiver interfaces).

If you create multiple filters, these are combined with OR and identify the messages to be indexed.

When you save a filter, it is applied to all components on which message indexing is active.