Procedure documentationConfiguring Communication Using the Integration Server Locate this document in the navigation structure

 

You can configure scenarios in such a way that communication between sender and receiver system is brokered by an Integration Server.

The following show the typical steps that you have to execute to configure local message processing on the Integration Server.

The figure below is a schematic illustration of a scenario in which the Integration Server is between two business systems.

This graphic is explained in the accompanying text.

Caution Caution

The information in this section merely gives an overview of the most important configuration steps. The individual details depend on the specific business process.

For examples of detailed configuration instructions for a specific business process, see the configuration instructions for the demo examples.

For more information, see: Demo Examples

End of the caution.

You can find an overview of the relevant configuration objects under Configuration Objects (Integration Server Communication).

Prerequisites

The design objects relevant for the process are defined in the Enterprise Services Repository.

For more information, see: Enterprise Services Repository

Ideally, you have created a process model in the Enterprise Services Repository for the process to be configured.

In this case, you can use the model configurator to make the configuration settings in the Integration Directory. The configurator guides you through the configuration step-by-step and, where possible, creates the objects for you automatically.

For more information, see: Using the Process Model as a Configuration Template

Procedure

1. Describe System Landscape

Define the technical systems and business systems that are relevant for the process in the System Landscape Directory.

For more information, see: Tasks in the System Landscape Directory

2. Define Collaboration Profile

In the collaboration profile, define the potential senders and receivers of messages and their technical communication options.

  1. To address the potential senders and receivers of messages, define communication components.

    1. For the business systems that you defined in the System Landscape Directory in 1, define communication components in the Integration Directory.

    2. If you use integration processes from the Enterprises Services Repository as sender or receiver of messages, define integration process components for them.

      For more information, see: Defining an Integration Process Component

  2. Define communication channels for the involved sender and receiver communication components. In the communication channel, specify the configuration of the involved sender and receiver adapters.

For more information, see: Define Collaboration Profile

3. Defining Routing

When configuring the routing you specify how the receiver of the messages that arrive at the Integration Server is to be determined.

The routing configuration is made up of the definition of receiver determinations and interface determinations. In receiver determinations you specify the receiver components of the message. In interface determinations you specify the receiver interfaces and, in some cases, mappings.

  1. Define the required receiver determinations.

    For more information, see: Defining Receiver Determinations

  2. Define the necessary interface determinations.

    For more information, see: Defining an Interface Determination

4. Define Collaboration Agreements

In a collaboration agreement, you define which communication channel is to be used for a particular sender-receiver pair.

For the sender and receiver pairs, define receiver agreements and, if necessary, sender agreements.

You must always define receiver agreements (for each technical receiver of a message). You only have to define sender agreements when using special sender adapters that are configured explicitly at the inbound channel of the Integration Server (for example, sender file/FTP adapters).

For more information, see:

Defining Receiver Agreements

Defining Sender Agreements

You can make it easier for a business partner (sender) to call the Integration Server by publishing the sender agreement in the Services Registry. The business partner can then access the sender agreement in the form of a WSDL file in the Services Registry, before the firewall. The WSDL description contains all the relevant configuration data from the sender agreement as well as the assigned communication channel, which are required to call the Integration Server.

For more information, see: Publishing Sender Agreements in the Services Registry

5. Activate Configuration Objects

Activate the configuration objects so that your configuration settings become runtime-relevant.

For more information, see: Change Lists

Note Note

If you execute the configuration with the model configurator, you can execute tasks 3 and 4 automatically.

For more information, see: Using the Process Model as a Configuration Template

End of the note.