Decentralised Adapter Engine Configuration

Question

hi all,
I have already installed DAE for a XI server.
Right now i am able to see it in RWB.But it is not visible in Adapter engine dropdown of communication channel.
I wanted to know whether some settings in visual admin of XI server also has to be done.
regards,
ujjwal kumar

Answer 1

Hi Ujjwal,
Please ignore my previous post and follow this as i would like to add to it:
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.
Also refer:
http://help.sap.com/saphelp_nw2004s/helpdata/en/3e/e3fb40f17af66fe10000000a1550b0/content.htm
After you are done with your installations there are some verifications that needs to be done at the visual admin side before monitoring your Decentral Adapter engine:
1)Start the J2EE from SAP management console and start the J2EE
(If you have dynamic IP address, then hosts file in server should be changed before starting decentral AE)
2)Start Visual Administrator & login to your Default connection
3)Navigate to Services à SLD Data Supplier and
verify the SLD connection
4)Navigate to Services à Security Provider and verify the users (its synchronized with the XI Server)
Now check in RWB -> Component Monitoring -> Non-central AE
Also refer page 25-29 of the following pdf:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/webinars-nw-rig/configuring%20a%20local%20adapter%20engine%20to%20work%20with%20a%20central%20instance%20-%20webinar%20powerpoint.pdf
Hope this helps.
Regards,
Shibani
*Ps reward with points if helpful*