Show TOC Start of Content Area

Function documentation Java Proxies as Receiver  Locate the document in its SAP Library structure

Use

You want to make a service available on the AS Java server. The service is to be provided by means of the Integration Server.

Integration

You must deploy the proxy beans and proxy classes generated by Java proxy generation together with the application program.

More information: Generate Java Proxies for XI 3.0 Compatible Service Interfaces

To do so, include them in the same EAR file that contains the classes of your application. The generated classes are dependent on the classes of the Java proxy runtime, which must be installed on the AS Java server. To declare this dependency for EJB applications, include the following packages in the descriptor file application-j2ee-engine.xml:

com.sap.aii.proxy.svc
com.sap.aii.af.sdk.lib
com.sap.xi.util.misc
com.sap.guid

All dependencies are of type weak and have the provider name sap.com.

Note

For SAP NetWeaver Process Integration 7.1, the AS Java library com.sap.aii.proxy.runtime is replaced by the service com.sap.aii.proxy.svc.

Prerequisites

You have created an inbound service interface for your service with interface pattern stateless (XI 3.0 compatible) in the Enterprise Services Repository. Using Java proxy generation, you have created provider proxy beans and provider proxy classes, which you include in your application.

Caution

If you generated Java provider proxies before SAP XI 3.0 FP, see SAP Note 738625.

Features

On the receiver side, the JPR proxy server listens for inbound messages from the messaging system. The JPR proxy server forwards the message to the corresponding server bean using the Java proxy runtime. This bean must be registered in the JPR registry. It calls the implementing class on the AS Java server using the generated provider proxy interface (the generated classes are shown in light gray).

This graphic is explained in the accompanying text

Note the following for the implementing class:

      It must implement the generated provider proxy interface.

      The name of the implementing class is fixed. It comprises the name of the provider proxy interface and Impl.

      The class must be derived from the class AbstractProxy.

If the service interface has the name MyInbound, then the Java interface MyInbound_PortType is generated from it that you must implement using the class MyInbound_PortTypeImpl:

public class MyInbound_PortTypeImpl
                  extends AbstractProxy
                  implements MyInbound_PortType {...}

To use further services of the Java proxy runtime, use the MessageSpecifier interface. For example, this interface enables you to send attachments together with the message.

More information: MessageSpecifier Interface

Activities

...

       1.      Implement the provider proxy interface.

       2.      Register the provider proxy interface with the proxy server.

 

 

 

 

End of Content Area