Naming Conventions and Terminology 
Throughout the SAP NetWeaver Enterprise Search documentation, the following naming conventions apply:
AS ABAP refers to SAP NetWeaver Application Server ABAP.
AS Java refers to SAP NetWeaver Application Server Java.
Term |
Definition |
|---|---|
SAP NetWeaver Enterprise Search |
The SAP NetWeaver Enterprise Search software installed on a blade system or single-server system. |
Central SAP NetWeaver Enterprise Search system, hub system |
The system or server that SAP NetWeaver Enterprise Search is installed on and that the various search providers are connected to. |
Federated search |
The search principle used by SAP NetWeaver Enterprise Search. Users can use the user interface of the central SAP NetWeaver Enterprise Search system to submit a search request that is forwarded to all connected search providers. The responses from all search providers are displayed together in a single search result. |
Embedded Search system |
An SAP NetWeaver system on which Embedded Search has been set up. |
Delegated search |
The search principle of an Embedded Search system that is connected to the central SAP NetWeaver Enterprise Search system. Users can use the user interface of the Embedded Search system to submit a search request. Search requests are forwarded to the central SAP NetWeaver Enterprise Search system and performed there. The result is sent to the Embedded Search system on which the user submitted the search request. |
Search provider |
Back-end system or service that is connected to SAP NetWeaver Enterprise Search to integrate the search objects that it contains or provides in searches conducted with SAP NetWeaver Enterprise Search. |
Search service provider |
Search provider that uses its own search technology, for example, Search Engine Service (SES) as available in SAP ERP 2005. |
Search data provider |
Search provider that uses the internal search technology of SAP NetWeaver Enterprise Search. |
Search object connector |
Used to connect search providers to SAP NetWeaver Enterprise Search to make objects of a specific type that are stored on these search providers available for searching. |
Extraction layer |
The extraction layer extracts data from search data providers, such as R/3 4.6C systems or file servers, which do not use their own search technology. The extraction layer is implemented by the ABAP component for SAP NetWeaver Enterprise Search. |
Indexing layer |
The indexing layer indexes the data provided by the extraction layer in the Search and Classification (TREX) engine integrated in SAP NetWeaver Enterprise Search. |
Search category |
Logical group of search object connectors used to filter search results. Examples: Sales Order, Product, Files |
Keyword |
Keywords are predefined terms that help you specify your search. You can modify your search query by adding supported keywords to your basic search term. |
Search user interface |
The SAP NetWeaver Enterprise Search User Interface that allows the user to enter search requests and receive results. |
Cruiser |
TREX component that crawls file shares and Web sites for documents to be indexed by TREX. |
The following variables are used in parts of the documentation:
Variables |
Description |
|---|---|
<SAPSID> |
SAP system ID in uppercase letters.
The SAP system ID consists of three characters and must begin with a capital letter, after that it can contain numbers. End of the note. |
<sapsid> |
SAP system ID in lowercase letters |
<host_name> |
Name of the corresponding host |
<port_number> |
Port number within an HTTP address |
<INSTANCE> |
Instance identifier, consisting of uppercase letters identifying the instance type, for example, TRX, JC, and the instance number. |
<instance_no> |
Instance number only, the digit(s) identifying an instance of an Enterprise Search component type.
JD02 identifies the second dialog instance in an SAP NetWeaver Enterprise Search installation. <instance_no> refers here to the digits 02. End of the example. |
<abapci>, <trexci>, <webdisp> |
These variables are used throughout this documentation to indicate the names of the hosts on which the ABAP central instance, TREX central instance, and the SAP Web dispatcher (network components (NC) host), respectively, are installed. Replace them with the host names you have chosen for these hosts. |
The following example shows how the variables are used:
Example
Log on as user <sapsid>adm at the operating system level and switch to the /usr/sap/<SAPSID> directory.
If your SAP system ID is C11, log on as user c11adm and change to the directory /usr/sap/C11.