Services (SAP Library - SAP Exchange Infrastructure (BC-XI))

Services

Use

This menu option contains the services of the Adapter Engine that contain configurable parameters. You configure these parameters using the same screen as for the adapters. This menu option is only available for users with the Adapter Engine Administrator role.

Any changes made to the configuration of the services are only activated when the Adapter Engine is restarted. It is not sufficient to simply restart the services (unlike with configuration changes to adapters).

Prerequisites

You have installed the Adapter Engine and the adapter you require, started the Adapter Engine and called it using your web browser. On the configuration screen, you have chosen the menu option Services and the system now displays the menu with the same name.

Features

You have the following choice of services:

GUIBrowserEngine

The GUI browser engine represents a separate HTTP server with a configurable port:

port=<portNo>

This is the HTTP port that the browser can log on to. The default value is 8200 and must not be changed unless it has already been reserved.

The following settings must not be changed under any circumstances:

zones=root

rootDirectory=Administration

If the browser connection to the Adapter Engine uses HTTPS, a corresponding certificate needs to be added to the configuration of the GUIBrowserEngine. You require the following entries:

SSLcertificate=<p12-certificate name>

SSLcertificatePassword=<p12-certificate password>

SSLcertificate specifies the complete file name of a password-protected certificate and SSLcertificatePassword specifies the corresponding password (the password can be protected by using the token concept, described above).

To make the installation HTTPS-enabled you must install additional Java libraries that are available from the SAP Service Marketplace (http://service.sap.com). These IAIK libraries must be located in the Java CLASSPATH.

HttpServer

The HTTP server is used by the outbound adapters. You have the option of making the following settings during the configuration of the HTTP server:

http.authentication=none|basic

Define whether user-authentication is performed. In the basic setting, the HTTP client of the Integration Server must log on to the Adapter Engine with a valid user that has been assigned the role HTTP Server User. In the setting none, no authentication takes place.

The default is none.

HTTP.transmission=plain|SSL

Defines whether the Integration Server and the HTTP server of the Adapter Engine are to communicate using HTTP (plain) or HTTPS (SSL). The following additional specifications are required for SSL:

HTTP.SSLcertificate=<p12-certificate name>

HTTP.SSLcertificatePassword=<p12-certificate password>

PWtokens

This is the service for replacing the password tokens in the adapter configurations. If required, you can change the beginning and end characters of the tokens centrally here.

PWD.beginSeparator=<beginSign>

PWD.beginSeparator=<endSign>

beginSign and endSign can be any character string. Existing replacements of tokens in the adapter configurations must then be adjusted correspondingly.

SLDaccessor

This service enables you to log on to the System Landscape Directory and supports the following functions:

Write access: When the Adapter Engine is started, its current configuration is transferred to the System Landscape Directory. The Runtime Workbench can then access this information, to establish a connection to the monitoring and configuration functions of the Adapter Engine, for example.

Read access: Configuration data can be accessed centrally for each adapter instance at runtime. This service can be activated by the inbound adapter to access the parameter XMB.TargetURL (which describes the address of the Integration Server) dynamically using the parameter XMB.SenderBusinessSystem.

To do so, the corresponding association must be maintained in the System Landscape Directory and the latter must be accessible. You configure the HTTP connection required to access the System Landscape Directory by using the following parameters:

SLD.host=<SLDhostname>

Name of the server on which the System Landscape Directory is running.

SLD.port=

Port number under which the System Landscape Directory can be reached.

SLD.user=

SLD.password=

Valid logon data for the System Landscape Directory installation (the password can be protected by using tokens, as described above).

The user must have the authorizations of group SAP_XI_APPL_SERV_USER on the Integration Server.

Read access to the System Landscape Directory can be activated in the inbound adapters by adding the following entry to the configuration:

XMB.SLDConfiguration=SLDaccessor

In this case, for the system specified with XMB.SenderBusinessSystem, the URL of the corresponding Integration Server in the SLD is exported and the value specified under XMB.TargetURL is used instead. You also need to specify the following:

XMB.TargetURL=<fromSLD>

If the System Landscape Directory logon data is not maintained correctly, corresponding error messages can occur in the Adapter Engine console output when the service is initialized (for example, when the Adapter Engine is started). These error messages do not affect the other functions and can be ignored if access to the System Landscape Directory is not required.