Displaying/Changing Configuration Data 

Use

The configuration data for the Integration Engine is client-specific. This means that you can configure multiple business systems in different ways in one SAP system. There are two types of configuration data:

·        Global configuration data

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

You can load the global configuration data from the System Landscape Directory, if it is already maintained there. You can also define a configuration locally, for example for test purposes, using configuration data that differs from that in the System Landscape Directory (SLD). You can test this data at any time and then compare it with the data in the SLD.

·        Specific configuration data

You use the specific configuration data to define parameters, which you use to configure your business system.

Prerequisites

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

Loading Global Configuration Data

To load your global configuration data from the System Landscape Directory, proceed as follows:

...

       1.      Choose Edit ® Change Global Configuration Data ® System Landscape – Load Configuration.

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

       2.      Save the loaded data.

       3.      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:

...

       1.      Choose Edit ® Change Global Configuration Data.

       2.      To change the usage type of your business system, in the Role of Business System field, select the required option.

A business system can have one of the following roles:

¡        Integration Server

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

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 (the Integration Server can run in another client of the same SAP system)

The system can act 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.

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.

       3.      If you want to call an Integration Server, but do not want to configure your business system as an Integration Server, enter the address for the Integration Server you want to use in the Corresponding Integration Server field.

There are two ways of specifying an address:

¡        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 centrally in your System Landscape Directory, you can use 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) for the Integration Server in the current system. In this case, the RFC destination contains the host name, port, and path prefix.

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 stored 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 address, but a logical definition.

       4.      Save your changes.

Changing Specific Configuration Data

To change the specific configuration data, proceed as follows:

...

...

       1.      In the Category field, choose the parameter category in which you want to make changes.

       2.      Choose Change Specific Configuration Data.

The system navigates to the view Configuration of the Integration Engine. This provides the same function for displaying a view as the transaction Maintain Table Views: Initial Screen (SM30).

The view displayed contains a table with configuration parameters that have already been defined for the selected category. For more information about the individual parameters, choose the information icon () in the corresponding line.

If you did not select a parameter category in the Category field in step 1, then the table contains all configuration parameters that have already been defined.

In change mode you can do the following:

¡        Change the current value of an entry

The current value overrides the default value.

¡        Create a new entry

Use the input help in each case. You can either accept the default value or specify a current value, which then overrides the default value at runtime.

Select the Prefix column to define the corresponding subparameter as a prefix. This enables you to predefine a configuration value generically for a set of subparameters.

¡        Select an entry and delete it from the table

Modified or new entries are not automatically transported since the parameters are mostly local.

If you do want to transport your entries, choose Utilities ® Comparison and proceed as described in Comparison of Customizing Objects.

You can also transport the entries manually by calling transaction SE09 and including the transport object R3TR TABU SXMSCONFVL with the corresponding table keys (configuration parameters) in your transport request.