Show TOC

Background documentationComponents and Architecture Locate this document in the navigation structure

 

SAP NetWeaver Enterprise Search: Technical Structure

SAP NetWeaver Enterprise Search is delivered as a software that contains several components on one operating system, but appears to the outside world as a single application. All components are handled together as one system.

SAP NetWeaver Enterprise Search comprises the following components:

  • SAP NetWeaver AS ABAP

    The SAP NetWeaver Enterprise Search ABAP system implements the extraction layer. It allows extraction of data from SAP R/3 systems (4.6C and 4.7) and from file servers for indexing by TREX.

    Equally, the Application Server ABAP provides the administration tools and the user interface.

  • SAP NetWeaver AS Java

    The Java component is required only for performing administrative life-cycle management tasks, such as for live update functions. With regard to runtime, performance, and scaling for SAP NetWeaver Enterprise Search, only the Application Server ABAP is important.

  • Search and Classification Engine (TREX)

    Search and Classification (TREX) makes available the search engine and the cruiser component to activate the files search on file servers and Web servers. TREX is also responsible for indexing the data provided by search data providers.

  • SAP Central Services (SCS)

    The SCS component groups together various services necessary to run AS ABAP and AS Java, such as SAP Message Server, SAP Gateway, SAP Web Dispatcher, and SAProuter.

    The SAP Web dispatcher distributes inbound HTTP/HTTPS requests. The SAProuter manages inbound RFC connections.

Note Note

The use of the SAP NetWeaver Enterprise Search hardware is restricted to this software only. You are not allowed to install and run any other software on this hardware.

End of the note.

This graphic is explained in the accompanying text.

SAP NetWeaver Enterprise Search and Connected Systems

Possible Installation Types

You can run SAP NetWeaver Enterprise Search as a single-server system on a single host or run a larger system, for which the TREX instances and application server instances are distributed among several blade servers, depending on your requirements.

This graphic is explained in the accompanying text.

In a multiple-blade system, you always have at least the following basic components:

  • On the master blade, the SAP central services are installed and the required network components are configured.

  • A second blade, on which the dual-stack instance with ABAP and Java and the MaxDB database are installed.

  • Another blade with a TREX instance, which is configued as the TREX master name server.

If required, the basic system can be extended by further instances of the following types:

  • Application Server ABAP (additional dual-stack instance with deactivated AS Java)

  • Search and Classification TREX

In the shared storage for the blades, the database volumes, TREX indexes, and SAP binaries are stored.

This graphic is explained in the accompanying text.

Installation of SAP NetWeaver Enterprise Search as a Multiblade System