Communication Destinations 
The figures and tables below provide an overview of the internal and external communication destinations used in SAP NetWeaver Enterprise Search.
Note
This documentation shows simplified figures; you can find the technical block diagrams as an attachment to SAP Note 1367252.
Internal Communication Destinations in SAP NetWeaver Enterprise Search 7.2
Number in Figure |
Sender |
Protocol and Authentication Mechanism |
Comment |
|---|---|---|---|
1 |
User interface or REST Web service |
HTTP; SSO |
|
2 |
TREX server registered in SLD |
RFC; user SLDDSUSER |
|
3 |
AS Java registered in SLD |
HTTP destination SLD_DataSupplier; user SLDDSUSER and HTTP destination SLD_Client; user SLDCLIENT |
|
4 |
AS ABAP registered in SLD |
JcoRFCProvider SAPSLDAAPI; user SLDDSUSER and RFC SAPSLDAPI with program ID |
|
5 |
UME that connects to the ABAP User Store |
RFC; user SAPJSF |
|
6 |
TREX server |
RFC; user DDIC |
Required to create the RFC destination on the ABAP side and for connection tests. |
7 |
AS ABAP |
RFC FASTSEARCH with program ID |
|
8 |
User of ICF services |
/sap/es/getdoucment ; user Search_Conn and /sap/bc/webdynpro/sap/esh_adm_smoketest_files; user Search_Conn |
For access through data provider services (DPS) and for testing services required for the basic configuration. |
9 |
Back-end system |
See the figure and table below. |
External Communication Destinations for SAP NetWeaver Enterprise Search 7.2
Number in Figure |
Sender |
Protocol and Authentication Mechanism |
Comment |
|---|---|---|---|
1 |
SAP NetWeaver Enterprise Search |
RFC; with technical user |
Enables number 2 in the figure. |
2 |
SAP BO Legacy Search |
RFC; with generated user |
Is used for data extraction. |
3 |
SAP NetWeaver Enterprise Search |
Netbios or HTTP: With back-end system user |
|
4 |
SAP NetWeaver Enterprise Search |
SOAP Web service; SSO |
The HTTP destinations for all KM connectors are entered in the ESH_ADM_GEN_CONN table. Launch transaction SE16 and enter ESH_ADM_GEN_CONN. In the TEMPLATE_TYPE field, enter the value KM and choose Execute (F8). The list contains the KM_LPORT parameter, the name of the HTTP destination generated by the system (CONNECTION_GUID), and the name of the KM connector. |
5 |
SAP NetWeaver Enterprise Search |
RFC; SSO |
|
6 |
SAP NetWeaver Enterprise Search |
SOAP or REST Web service; with administration user from the back-end system |
|
7 |
SAP NetWeaver Enterprise Search |
HTTP REST Web service |
SAP NetWeaver Enterprise Search consumes OpenSearch. HTTP destination is required. OpenSearch provider is located on the Internet or in the intranet. |
8 |
OpenSearch consumer |
HTTP REST Web service; with ICF user |
SAP NetWeaver Enterprise Search as a provider of OpenSearch services that are made available through an ICF service. The administrator role SAP_ESH_ADMIN is required to launch the Description Document List. The standard user role SAP_ESH_SEARCH is required for searching. |
More information: Connecting Search Providers to SAP NetWeaver Enterprise Search in the SAP NetWeaver Enterprise Search configuration guide.