Working with Decentralized J2EE Adapter Engine - Part2 (XI)

By Kalyan Chakravarthy, Fujitsu Consulting India Pvt ltd

This document is in continuation to the part 1 (installation of Decentralized Adapter Engine. For Part 1, click here.

This document provides information on post-installation activities.

Following three Steps are mandatory to ensure proper working of the decentralized adapter engine.

  1. Configuring the SLD Data Supplier Service in the Visual Administrator
  2. Configuring the Gateway Service of the Central Integration Server
  3. Adding Connection Parameters to Central Exchange Profile

 1. Configuring the SLD Data Supplier Service in the Visual Administrator: 

1.       Start the J2EE Engine Visual Administrator.

2.       Choose Cluster->Server-> Services->SLD Data Supplier.

3.       On the Runtime tab in the right frame, select the tab HTTP Settings.

4.       Enter the data required for the HTTP connection from the SLD service to the SLD as follows:

Host: Enter the name of the host where the SLD Bridge runs.

Port: specify the HTTP standard access port of the SLD where this is the HTTP port of the J2EE engine.

User: Specify a Java user that already exists on the host where the SLD Bridge runs (XISUPER, for example).

Password: Enter the user password.

5.       You can test your settings by sending test data to the SLD; click the blue arrow with the quick info text Trigger data transfer to System Landscape Directory.

2.Configuring the Gateway Service of the Central Integration Server

On the Adapter Engine host, you need to provide the gateway service of the central Integration server.


  1. GO to Run ->drivers ->etc -> hosts 
  2. Enter the gateway service as follows: sapgw<xx> <port>/tcp and sapgws<xx> <port>/tcp 
  3. You can copy and paste the correct entry from the services file on the PI host.

3. Adding Connection Parameters to Central Exchange Profile

1.       Enter the following URL in a browser for entering the values in exchange profile of decentralized adapter engine: http://<AE_server>:<AE_HTTP_Port>/exchangeProfile.

2.       Choose Connections.

3.       Enter the respective values.

Note : You can open the following  url : http://<PI_server>:<_HTTP_Port>/exchangeProfile and choose Connections here and copy the same values in decentralized adapter engine exchange profile parameters. 

Make sure the Connections are successfully done.

 Checking the Decentralized Adapter Engine in Runtime Workbench:

1.       Go to Runtime Workbench; click on Non-Central Adapter Engine. There you must find your installed Adapter engine. 

And also check in the Message Monitoring

2. Select your Adapter engine, from there you can ping the server and send a test message.

  Refresh the cache using transaction SXI_CACHE in Integration server client.

Then select go to ---> Adapter Engine Cache and the cache is automatically refreshed. There also you can see your Decentralized AE.

4. After all the above settings the Decentralized Adapter Engine should appear in drop down of Adapter Engine in Communication channel in ID. 

 5. The CPACache of Integration server should also be refreshed.

You can use the URL:


Problems may occur If you change the HTTP port of Decentralized Adapter Engine.

Communication between the PI Integration Server and the decentralized Adapter Engine fails after you change the default HTTP port of the Adapter Engine. The Sending of XML messages from the Integration Server of the Adapter Engine fails.


Use the Visual Admin Tool, log on as an administrator to the J2EE Engine and navigate to the Service “SAP XI AF CPA Cache”.

Enter the values you have changed for properties

“SLD.selfregistration.httpPort”, “SLD.selfregistration.httpsPort” and “SLD.selfregistration.hostName” . Always enter the host name. Save and start the service.  

 Caution: The Integration Server stores the SLD data in the cache. To update this: In the Integration Server transaction SXI_CACHE, start ---> Go ----> Adapter Engine Cache. Select the relevant row with the obsolete port and delete the cache entry (Delete symbol). All cache entries are deleted. The next time a message is sent to the relevant adapter engine, the updated data is read from SLD.

 Check: After you restart the J2EE applications in the SLD, choose “Content Maintenance” ---> XI Adapter Framework” to navigate to your Adapter Engine.

For example, under the “associated instances” and “XI Adapters Service XIRA ---> Associated Instances ----> Port for XIRA of af.<SID>.<hostname>”, you will find the URL that is used by the Integration Server to send messages to the AE. After the message is resent, check whether the Adapter Engine cache was also updated in the Integration Server (SXI_CACHE ---> Go to---> Adapter Engine Cache).


  1. We can also deploy Adapter Modules in Decentralized Adapter Engine.
  2. Here our Decentralized Adapter works as same as Centralized Adapter Engine (When you call Decentralized adapter in XI).
  3. In the RWB we can check the Adapters from Decentralized by choosing Adapter Monitoring (before this we have to choose our Non-Centralized Adapters).
  4. As the Decentralized Adapter Engine runs separately (means a part from XI Server) Burden on XI reduces and increases the performance.
I hope this document will be helpful to work on Decentralized J2EE Adapter Engine.

Please send us your feedback/suggestions at webmaster@SAPTechnical.COM 

HomeContribute About Us Privacy Terms Of Use • Disclaimer • SafeCompanies: Advertise on SAPTechnical.COM | Post JobContact Us  

Graphic Design by Round the Bend Wizards

footer image footer image