Start of Content Area

Procedure documentation Combining Different Development Approaches  Locate the document in its SAP Library structure

Use

The separation of outbound and inbound interfaces separates the calling and the called application from one another. In this way, you can in theory have any number interface types communicating with each other in communication involving the Integration Server. Some typical examples are described below, which illustrate the necessary steps in interface development.

Assigning Interfaces

The case examples focus on interface objects. The generate rule is that outbound interfaces are not assigned to the corresponding inbound interfaces until configuration time. In scenarios which involve a service interface, which configuration tool you use depends on the target language.

In the case examples it is irrelevant whether an interface is on the outbound or the inbound side (for example, whether a proxy is used on the inbound or outbound side of the communication). They apply to both cases.

When communicating with external systems, it is possible that there are no interfaces, that is, interfaces cannot be imported to the Enterprise Services Repository (ES Repository). The Communication with Interfaces That Cannot Be Imported section below outlines how to proceed in such cases.

Message Formats

The respective adapter converts the interface call to an XML format supported by the interface. For example, if an RFC is called, the adapter generates RFC XML, which is supported by the Integration Engine. Proxies can process both proxy XML and RFC or IDoc XML: Proxy XML if message types were assigned to the operation of the service interface; RFC or IDoc if an imported RFC message or IDoc message was assigned to the operation of the service interface.

Prerequisites

The prerequisites for a particular scenario depend on the adapter types used on the inbound and outbound sides.

Procedure

K

       1.      Check which existing interfaces are to be used.

       2.      Develop the required interface objects based on the communication parties given:

       Combining Service Interfaces with Imported RFCs or IDocs

       Procedure for Interfaces That Cannot Be Imported

 

 

 

 

 

End of Content Area