Show TOC

Procedure documentationConnecting Back-End Systems Locate this document in the navigation structure

 

To import metadata from a back-end system, you must first specify the connectivity data or logical ports required to set up the connection to the back-end system.

Note Note

This step is necessary only if you have not yet entered the connection data for the corresponding back-end system. In the case of systems for which you have already created a search object connector or a model, the connectivity data has already been entered in the system.

End of the note.

Procedure

To create a connection between SAP NetWeaver Enterprise Search and a back-end system, proceed as follows:

  1. Launch the administration cockpit and choose   System Settings   Connect Back-End Systems  .

  2. Select the required type.

    The following types are available in SAP NetWeaver Enterprise Search:

    • Data Provider Service

      To connect customer-specific systems and systems from third-party providers that support Data Provider Services (DPS).

    • SAP BI Search

      To connect an SAP BI/BW system, release 7.0 SPS 14 or higher.

    • SAP BO Legacy Search

      To connect a back-end system of release SAP R/3 4.6C or SAP R/3 4.7.

    • SAP BO Search

      To connect a back-end system of release SAP Business Suite 7.

    • SAP BO Search Service

      To connect a back-end system of release SAP ERP 6.0.

    • SAP KM Search

      To connect SAP Portal with SAP Knowledge Management of release SAP NetWeaver 7.0 (2004s) SPS 12 or later

  3. Create a new system with the parameters that are required to connect to the back-end system. To do this, choose Add.

    The system inserts a new row at the end of the list; enter here the System ID and Client and choose Enter to confirm them.

    Enter the following parameters for the types SAP BI Search, SAP BO Legacy Search, SAP BO Search, and SAP BO Search Service:

    Parameter

    Description

    System Number

    Specify the system number of the back-end system.

    For example 71

    Application Server

    Enter the address of the application server.

    For example server100.company.corp

    User

    Specify the user that you want to use to access the system to be connected.

    Note Note

    For SAP ERP 6.0, this user must have the SAP_BC_SES_ADMIN role.

    On SAP R/3 4.6C and R/3 Enterprise (4.7) systems, this user must have the following authorizations:

    • Profile S_BI-WX_RFC

    • Authorization to run transactions SU01 and PFCG

    • Authorization for the S_USER_GRP authorization object with:

      • Authorization field ACTVT * (all)

      • Authorization field CLASS * (all authorization groups)

    • Authorization for the S_USER_PRO authorization object with:

      • Authorization field ACTVT * (all)

      • Authorization field PROFILE with the value SI_BI-WX_RFC

    End of the note.

    Password

    Enter the password that the user accesses the system with.

    Specify the following parameters for the Data Provider Service type:

    Note Note

    Note that you can create logical ports for search template services and search data services.

    End of the note.

    Parameter

    Description

    Host

    Specify the host.

    Example: www.domain.com

    Port

    Specify the port.

    Example: 8080

    Protocol

    Specify the protocol used (HTTP or HTTPS).

    Logical Port Name

    Specify the name of the logical port that is used for the search template service or search data service.

    Web Service Type

    Choose the Web service type.

    If you want to import templates, choose the search template service type.

    If you have already created logical ports for the search template service, you can also create logical ports of type Search Data Service. When you subsequently create a DPS search object connector, you can select these from a list.

    Service Endpoint

    Specify the service endpoint for the search template service or search data service; you receive this information from the DPS service provider.

    Examples: /myapplication/es/dps/templateservice

    /myapplication/es/dps/dataservice

    Authentication Settings

    Specify the authentication type to be used.

    • No Authentication: No authentication takes place.

    • SAP Authentication Assertion Ticket: The logged-on user is used for authentication via SSO.

    • User/Password: A statically configured serrvice user is used for authentication.

    For more information about creating a connector of type Data Provider Service, see Connecting To Data Provider Services.

    Specify the following parameters for the SAP KM Search type:

    Parameter

    Description

    Host

    Specify the address of the portal server on which Knowledge Management is installed.

    For example portal.company.corp

    Port

    Enter the port of the portal server.

    For example 50000

    Protocol

    Specify the protocol used (HTTP or HTTPS).

    Select the authentication type that is to be used for the connection to the KM system.

    No Authentication: No authentication takes place.

    SAP Authentication Assertion Ticket: The respective logged-on user is used for authentication in the KM system via SSO.

    User ID/Password: A static configured service user is used for authentication in the KM system. This user must have the UME action ESConfiguration assigned to the role.

    For more information about creating a connector of type SAP KM Search, see Connecting SAP KM.

  4. Choose Maintain Connectivity to adopt the connectivity data entered. The connection to the back-end system has now been set up.

  5. To close the window, choose [X] in the title bar.

More Functions for Back-End Systems of Type SAP BO Search

If you have selected a back-end system with the SAP BO Search type, the following functions are available:

Action

Description

Move Search

This function allows you to move an Embedded Search system with its indexes and configuration data to the SAP NetWeaver Enterprise Search system. For more information, see Connecting To an Embedded Search System.

Check for Updates

if you have moved the search from an Embedded Search system to the SAP NetWeaver Enterprise Search system:

You must check the model data regularly for updates to ensure that the current model data from the Embedded Search system is available in the SAP NetWeaver Enterprise Search system.

For more information, see Updating Model Data in the Hub System.

Updating Models

if you have moved the search from an Embedded Search system to the SAP NetWeaver Enterprise Search system:

This function allows you to transfer current model data from the Embedded Search system to the central SAP NetWeaver Enterprise Search system.

For more information, see Updating Model Data in the Hub System.

Updating Runtime Data

This function allows you to manually transfer to current environment information (information about all SAP NetWeaver Enterprise Search connectors) to the back-end systems that are connected. For example, this may be necessary if the connection to a back-end system was terminated and caused the automatic update to fail.