Displaying/Changing Configuration Data

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.

You use the selected configuration data to define the role of your current business system. You can load this data from the System Landscape Directory (SLD) if it is maintained there. You can also define a configuration, for example for test purposes, which is different to the data in the SLD. You can check this configuration at any point and compare it with the data in the SLD.

You define all the remaining configuration data by using parameters with which you can set up your business system.

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

If you do want to transport your entries, choose Utilities → Compare and proceed as described in Comparing Customizing Objects .

You can also transport your 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.

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

To load your configuration data from the SLD, follow the procedure below:

1. Choose Edit → Change Selected Configuration Data → System Landscape - Load Configuration.

   The system displays a message if no data is maintained in the SLD.

2. Save the loaded data.
3. To undo the loading of configuration data from the SLD, choose Undo Changes.

To change the displayed configuration data, proceed as follows:

1. Choose Edit → Change Selected Configuration Data.
2. To change the usage type of your business system, in the field Role of Business System, select an 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 system. It is a centrally configured Integration Engine and 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

     Application system with a local Integration Engine that requires the Integration Server to execute the integration logic (that can be 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.

     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.

3. 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 address for the particular Integration Server.

   You can specify an address in the following way:

   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.

dest://

1. Save your changes.

To change the configuration data, proceed as follows:

1. In the Category field, choose the categories of parameters in which you want to make changes.
2. Choose Change Configuration.

   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.

   Note

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

   In change mode, you can do the following in this table:

   • 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 column Prefix 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

   To display a list of all the parameters together with their default values that you can specify in the selected category, choose Default Values.