Procedure for Interfaces That Cannot Be Imported 

Use

The Integration Server supports the connection to external systems where interfaces cannot be imported to the ES Repository. There are two variants:

●      The message schema is contained in a WSDL, XSD, or DTD document and can be processed by proxy generation functions. In this case, you use service interfaces as the counterpart to the interface that cannot be imported.

●      The message schema cannot be imported or processed by proxy generation. In this case, you use adapters on the sender and receiver side to enable communication.

Procedure

Communication Between Proxies and Interfaces That Cannot Be Imported

If your system supports proxy generation and the proxy generation functions can process message schema, proceed as follows:

...

       1.      Import the WSDL, XSD, or DTD document to the ES Repository as an external definition.

       2.      Create a service interface with the interface pattern Stateless or Stateless (XI 3.0-Compatible) and reference from an operation to the message(s) of the external definition. For external systems, you can use an abstract service interface since no proxies have to be generated in this case.

You can only reference messages of one object type from an operation. For example, it is not possible to enter a message type for the request message of a synchronous operation and an external message for the response message of the same operation.

       3.      Generate a proxy for your service interface. The interface that cannot be imported is already available in the application system and can exchange messages with the Integration Server by using the respective adapter.

Communication Between Components That Do Not Support Proxies

The Enterprise Services Builder and the Integration Builder allow manual entry of interface names, which enables you to connect systems from which interfaces cannot be imported or whose message schema is not supported by proxy generation:

●      For technical reasons, it is only possible to import RFCs and IDocs for SAP systems Release 4.0 or higher. However, the RFC and IDoc adapters can be implemented with SAP systems Release 3.1l and higher. In this case you must enter the interface names manually.

●      The Adapter Engine supports the connection of external systems that are not necessarily connected by means of an interface (for example, the file adapter). When configuring the sender adapter, specify instead the ID of the logical sender and receiver by using the respective business system, a namespace, and an interface name of your choice. If a mapping is required, you need an interface to be able to specify your mapping program later in the configuration using an operation mapping../../KW/IWB_EXTHLP~4FEF761A5ECFB1418B79896E10FE4C57/. For external systems, you can use an abstract message interface since no proxies are to be generated in this case.

Even if the proxy generation functions cannot process the message schema of an external definition, it is still useful to import a used message schema to the ES Repository for the following reasons:

●      The message schema is centrally available.

●      You can use the message schema to define a message mapping.

In the case of interfaces that have not been imported, if you have entered the Repository namespace and the interface name correctly during mapping and routing, the Integration Server recognizes the corresponding communication parties (the namespace does not necessarily have to be available in the ES Repository).