The following documentation describes an integration scenario in which the business system, which is connected to the Integration Server by means of Java proxies, takes on the role of either a sender system (using client proxies) or a receiver system, or both.
Use
SAP systems based on Web AS 6.40 and higher are able to exchange data by using messages and HTTP. These systems can use Java proxies to connect to the Integration Server.
SAP systems up to and including Release 4.6 are not able to exchange data by using messages and http. Such systems can only connect to the Integration Server by means of the IDoc adapter or the RFC adapter.
To connect the platform-independent message interfaces, which are stored in the Integration Repository, to the Integration Server, use the Java proxy interface (based on the adapter framework).
Description
You can use executable Java proxies to exchange messages between a business system and the Integration Server. Executable Java proxies are shipped by SAP with all platform-independent message interfaces. However, you have to generate these proxies first before you can use them for your own message interfaces.
An application in a business system calls a client proxy to send a message. Proxy runtime receives the message from a business sender system and the Integration Server processes the message further.
To forward messages to a receiver business system, the proxy runtime receives the message in the receiver system, and then calls the Java class that implements the relevant server proxy.
Example
A SAP Web AS 6.40 system uses a client proxy to send a message to the Integration Engine. The message is then processed by the Integration Server. Two receivers are determined:
· Another Web AS 6.40 system
· A system that cannot receive messages directly (for example, an SAP 4.0B system)
On the receiver side, the SAP Web AS 6.40-based system receives a message, which is used by a server proxy to call the Java class. The other receiver system must be connected by means of the IDoc adapter or the RFC adapter.
No comments:
Post a Comment