Integration Using the Java Proxy Runtime 

Use

The Java Proxy Runtime (JPR) handles the connectivity between Java proxies and the Integration Server. It converts data contained in Java proxy objects to XML messages and the other way round at runtime. For this purpose it requires information from both the exchange profile and the System Landscape Directory (SLD). For more information about JPR, see Java Proxy Runtime.

The JPR is installed with and integrated into the Adapter Engine. The Adapter Engine guarantees the quality of service Exactly Once (In Order) required for asynchronous messages and provides services for queuing, persistence, and monitoring of XI messages (as well as other message formats).

As of SAP NetWeaver ’04, JPR can no longer be used with J2SE, that is, with standalone Java applications.

The JPR is integrated into the J2EE Engine as follows:

●      In the outbound case, an application uses proxy beans to send request messages and possibly receive response messages. The proxies in turn call the JPR to connect to the Adapter Engine which sends the messages to the Integration Server.

●      In the inbound case, a proxy server application is provided, which consists of an EJB bean handling the processing of incoming XI messages. This bean acts as a listener to the Adapter Engine, which receives the messages from the Integration Server, and in turn calls the application bean registered for the particular inbound interface.

Currently, the J2EE Engine is the only J2EE server supported by JPR.

Settings in the Exchange Profile

The JPR uses the values of certain parameters from the exchange profile to determine system-wide settings. These values should have been set during installation of the Adapter Engine.

You access the maintenance screen at: http://<host:port>/webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp

The variables host and port are the hostname and connection port of the J2EE Engine of your business system. Under Connection, the connection parameters of your Integration Server should appear. From there, all necessary profile data is copied to the Secure store of the J2EE Engine.

Entries in the System Landscape Directory

In addition to the deployment of your client proxy classes on the J2EE Engine of your business system, you have to create a business system instance in the SLD when implementing an outbound Java proxy scenario. This information is used by JPR to determine the sender service when creating an outbound message, and by the Adapter Engine to locate the address of the Integration Server when sending the message. See System Landscape Directory for more information.

A JPR instance used by Java applications is represented in the SLD by a technical system of type Web AS Java and must be associated with a business system. The technical system is specified by a system name and the name of the host of the J2EE Engine.

During installation of the Adapter Engine a technical system of type Web AS Java is created in the SLD. It contains the following values:

●      Web AS ABAP:         none (Standalone J2EE)

●      System Name (SID):  C11

●      System Home:          <your hostname>

Use the built-in wizard of the SLD to create a business system instance by specifying the following:

●      An arbitrary name

●      The type of the associated technical system (Web AS Java)

●      The name of the associated technical system (to be selected from the dropdown list; C11 on <your hostname> in the above example)

●      The related Integration Server (to be selected from the dropdown list)

This configuration data is accessible by JPR and the Adapter Engine only after the CPA cache on your J2EE Engine has been updated.

Security Roles for the Java Proxy Runtime

...

       1.      Use the Security Provider service of the Visual Administrator to verify that the following security roles are assigned to the appropriate user groups as follows:

Security Role Assignments

Security Role	User Group
xi_jpr_register_bindings	SAP_XI_ADMINSTRATOR_J2EE SAP_XI_DEVELOPER_J2EE
xi_jpr_list_bindings	SAP_XI_ADMINSTRATOR_J2EE SAP_XI_DEVELOPER_J2EE SAP_XI_CONFIGURATOR_J2EE
xi_jpr_admin	SAP_XI_ADMINSTRATOR_J2EE SAP_XI_CONFIGURATOR_J2EE

       2.      Verify that these user groups are also available on the J2EE side.

Configuring an Inbound Service for the Java Proxy Runtime

This is an additional configuration step, which is only required if the JPR is to be used by inbound services, that is, by EJB beans implementing inbound interfaces on a J2EE application server.

For more information, see Configuring the Channel for Java Proxy Receivers.

Running a Non-Central Adapter Engine in Java Proxy Mode

The non-central Adapter Engine provides a configuration option called Java Proxy mode (JPR mode). In this mode, the adapter registration in the SLD is disabled so that the underlying system becomes a plain Java proxy application system (just like an ABAP system with ABAP proxies). The collaboration partner agreement (CPA) service no longer reads the CPA cache data from the Integration Directory.

In this case, you can use a service property to configure the user for sending messages to the Integration Server (outbound scenario). The Integration Server uses an access control list (ACL) to check receiving messages based on this configuration setting (see SAP Note 852237). The ACL check is always skipped when the Adapter Framework service user (usually PIAFUSER) is used for sending.

To switch the Adapter Engine to JPR mode, perform the following configuration settings:

...

       1.      In the Visual Administrator, choose the SAP XI AF CPA Cache service and set the SLDAccess property to false.

       2.      Save your settings and restart the service.

       3.      Make sure that the cacheType property still has the value DIRECTORY.

       4.      In the Visual Administrator, choose the SAP XI Adapter: XI service and set the respective values (user, password, Integration Server URL, client, and language) for the properties xiadapter.isconfig.*.

       5.      On the Integration Server, call transaction SMICM to ensure that you have maintained the correct Integration Server URL.

       6.      On the Integration Server, call transaction SU01 to create the new user and assign it the role SAP_XI_AF_SERV_USER_MAIN. You can copy PIAFUSER for this purpose.

If a password change is required, log on to the Integration Server with the new user and change the initial password. Otherwise the communication will fail.

       7.      In the Visual Administrator, check if the ABAP-Java user synchronization was successful.

       8.      Log on to the SLD and choose Content Maintenance ® XI Adapter Framework.

       9.      Select your non-central Adapter Engine and remove it.