Show TOC

Function documentationRuntime Configuration Locate this document in the navigation structure

 

Before messages can be exchanged at runtime, you must define whether you want to use the Web service runtime or the XI runtime.

Integration

The ABAP proxy runtime supports the following approaches:

  • You can use the XI runtime to define the receiver or receivers of a message centrally in the Integration Directory. You can then use the integration logic of the Integration Server (routing, mapping, and Business Process Management).

  • You can use the Web service runtime to call Web services using the Internet. You must then configure the receiver locally in the client system. Furthermore, provider proxies must be encapsulated as Web services (refer also to: Creating a Service Definition). 

If you require a special Protocol that the other runtime does not provide, it is also possible to support both runtimes in your application program.

Features

Local Runtime Configuration

  • You must create a logical port for consumer proxies that use the Web Service Runtime (transaction LPCONFIG).

  • Consumer proxies that use the XI runtime do not need a logical port.

Evaluating at Runtime

You can specify a logical port by using the constructor of a consumer proxy. The ABAP proxy runtime determines which runtime must be active as follows:

  • If no port is specified and there is no default port, the system assumes that the message is to be sent using XI.

  • If a port is specified, but it is not available, the system raises an exception. In all other cases, the port settings described above determine the runtime that the system will use to send the message.