|Home • Trainings •Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
Working with Decentralized J2EE Adapter Engine - Part2 (XI)
By Kalyan Chakravarthy, Fujitsu Consulting India Pvt ltd
document is in continuation to the part 1 (installation of Decentralized Adapter
Engine. For Part 1, click here.
document provides information on post-installation activities.
three Steps are mandatory to ensure proper working of the decentralized adapter
Configuring the SLD Data Supplier Service in the Visual Administrator:
Start the J2EE Engine Visual Administrator.
Choose Cluster->Server-> Services->SLD Data Supplier.
On the Runtime tab in the right frame, select the tab HTTP Settings.
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.
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
the Gateway Service of the Central Integration Server
the Adapter Engine host, you need to provide the gateway service of the central
Adding Connection Parameters to Central Exchange Profile
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.
3. Enter the respective values.
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.
sure the Connections are successfully done.
the Decentralized Adapter Engine in Runtime Workbench:
Go to Runtime Workbench; click on Non-Central Adapter
Engine. There you must find your installed Adapter engine.
also check in the Message Monitoring
Select your Adapter engine, from there you can ping the server and send a test
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
4. After all the above settings the Decentralized
Adapter Engine should appear in drop down of Adapter Engine in Communication
channel in ID.
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.
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.
the Visual Admin Tool, log on as an administrator to the J2EE Engine and
navigate to the Service “SAP XI AF CPA Cache”.
the values you have changed for properties
“SLD.selfregistration.httpsPort” and “SLD.selfregistration.hostName” .
Always enter the host name. Save and start the service.
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
After you restart the J2EE applications in the SLD, choose “Content
Maintenance” ---> XI Adapter Framework” to navigate to your Adapter
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
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM
©2006-2007 SAPTechnical.COM. All rights reserved.
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
Graphic Design by Round the Bend Wizards