Displaying/Changing Configuration Data (SAP Library - SAP Exchange Infrastructure (BC-XI))

Displaying/Changing Configuration Data

Use

The configuration data for the Integration Engine consists of:

Global configuration data

You use the global configuration data to define the role of your current business system.

Global configuration data is client-specific. This means that you can configure multiple business systems in different ways in an SAP system (from SAP Web Application Server 6.20).

You can also load the global configuration data from your System Landscape Directory, if it is already maintained there. You can also define a configuration locally, for example for test purposes, which is different to the data of the System Landscape Directory.

Specific configuration data

Use the specific configuration data to define parameters for different categories, with which you can configure your business system. Changes to the parameter settings are saved during transport.

Prerequisites

In the Integration Engine menu you chose Configuration ® Integration Engine Configuration, and are now on the screen Configuration Data of the Integration Engine.

Loading Global Configuration Data

To load your global configuration data from the System Landscape Directory, following the procedure below:

Choose Edit ® Change Global Configuration Data

Choose System Landscape – Load Configuration.

The system displays a message if no data is maintained in the System Landscape Directory.

Save the loaded data.
To undo the loading of global configuration data from the System Landscape Directory, choose Undo Global Changes.

Changing Global Configuration Data

To change the global configuration data displayed, proceed as follows:

Choose Edit ® Change Global Configuration Data

To change the usage type of your business system, in the field Role of Business System, choose an option using the input help.

The following are the different business system usage types:

Integration Server

The Integration Server receives XML messages, determines the receiver, executes mappings, and routes the XML messages on to the corresponding receiver system. This is a centrally configured Integration Engine that is not able to execute application logic.

Note

There can only be one Integration Server in an SAP system. This means that only one client (business system) can be defined as the Integration Server.

Application system with a local Integration Engine that requires the Integration Server to execute the integration logic (that can run in another client of the same SAP system)

The system can respond as a sender or receiver of XML messages, but it does not contain any integration logic. Therefore, neither routing nor mapping can be executed locally. Instead they must be executed by the Integration Server, which is called by the application system.

Note

Although integration logic is only offered in ABAP-based business systems, the sender/receiver role of an Integration Engine can also be made available in other business systems.

If you want to call an Integration Server, but do not want to configure your business system as an Integration Server, in the field Corresponding Integration Server, enter the URL (Uniform Resource Locator) for the particular Integration Server.

There are two ways of specifying a URL:

http://<host>:<port>/sap/xi/engine?type=entry

<host> is the host name of the Integration Server and <port> is the HTTP port.

If you have already maintained this entry in your System Landscape Directory, you can copy the entry by choosing System Landscape – Load Configuration.

The name of the user and the password must be defined with the HTTP service (/sap/xi/engine) in the target system. The user is the person who processes the XML messages on the Integration Server.

dest://<IntegrationServer-Destination>

<IntegrationServer-Destination> is an RFC destination of type HTTP Connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination.

First create a type H RFC destination with the host name and the HTTP port of the Integration Server. Enter the following path prefix:

/sap/xi/engine?type=entry

In this case, the name of the user and the password are saved in the RFC destination in the current system; you do not need to specify them in the HTTP service in the target system.

You must place the prefix dest:// before the name of the RFC destination so that the system knows that this is not a direct specification of the URL, but a logical definition.

Save your changes. The system displays a message to confirm that the configuration was changed.

Changing Specific Configuration Data

To change the specific configuration data, proceed as follows:

Using the input help for the field Category, choose the categories of parameters in which you want to make changes.
Choose Change Specific Configuration Data.

The system displays a screen with a list of already defined configuration parameters for the categories selected. Choose Goto ® Documentation () for more information on the individual parameters.

In this list you can:

Select an entry and copy it into the input fields Configuration Parameter, Subparameter and Value, to change the entry there.

Set a changed entry in the list.

Copy the Default Value of an entry

Create a new entry using the input fields Configuration Parameter, Subparameter and Value, and add it to the list.
Select an entry and delete it from the list.

Transport the existing entries.

Save your changes.

The system displays a dialog box, in which you must specify a workbench request to transport the changes.

Specify or create a workbench request, and choose Continue.

Your changes are transported.