Show TOC

Optional: Establishing Connection to Back-End SystemsLocate this document in the navigation structure

You can use Embedded Search not only to browse your local Business Suite system running on SAP NetWeaver AS for ABAP, you can also connect to and browse other Business Suite or ABAP systems in which Embedded Search is used.

Context

There are two different cases for the local Embedded Search system:

  • Case A: The local Embedded Search system is configured as a proxy. You can connect and browse other, remote Embedded Search systems.
  • Case B: The local Embedded Search system is configured as a back end. You can browse it from a remote Embedded Search system.
Note

The Embedded Search systems that you want to connect to act as a back end must be release SAP NetWeaver 7.4 SPS05 or higher.

You can define local categories in an Embedded Search system that is acting a a proxy, but these can only be used locally. Categories and connector authorizations that are already used in the back-end systems are not available in the proxy system.

Procedure

  1. Select usage type in Customizing

    To configure your system for one of the two cases, call Customizing using transaction SPRO.

    Navigate to Start of the navigation path Search and Operational Analytics Next navigation step Embedded Search Next navigation step Search Configuration Next navigation step Configure Remote Search End of the navigation path and select the use as proxy or back-end system.

  2. Register back-end system

    To manage the connectors of a back-end system in the administration cockpit, you first have to register the back-end system. In the administration cockpit, choose Start of the navigation path System Settings Next navigation step Connect Back-End Systems End of the navigation path.

    You can define new back-end systems or edit or check existing connections.

    To add a new system, choose Add. In the table, enter a system ID and the client, and a description if necessary. Specify the connection information for the system. Depending on whether the back-end system supports SAP HANA or TREX, select the appropriate connection (if already configured) from the proposal list for the TREX Connection or Database Connection field. The proposal list contains existing connections of the back-end system to TREX/BWA or SAP HANA.

    Note

    If the required back-end system (SAP HANA or TREX/BWA) is not listed, you must create it first.

    • Back-end system uses SAP HANA: Use transaction DBCO to create a connection to the SAP HANA of the back-end system in the proxy system. In the database connection, enter an existing SAP HANA user with the required authorizations (sys.trexviadbsl and sys.trexviadbslwithparameter) for use in the search scenario.
    • Back-end system uses TREX/BWA: Create a new RFC connection between the ABAP system of the proxy system and the TREX/BWA of the back-end system. Note the link below.
    In the User and Password fields, enter the data of a user of the remote ABAP system that has the role SAP_ESH_LOCAL_ADMIN.

    Choose Manage Connection Data.

    Once the connection is established, the connectors of the back-end system are displayed in the overview list.

    If the database connection does not have the required authorizations or these have been changed, it may be necessary to delete the database connection in the administration cockpit and create it again. If you delete the connection, the linked RFC connections are also deleted.

    Note The user starting a search in the proxy system must have the appropriate search authorizations in each of the back-end systems. If not, the user will not see any hits from these back-end systems in the search result.
Related Information