Difference between SAP J2EE Adapter Engine and normal SAP JAVA AS

[Former Member]

Hello all,

I face the problem, how to install SAP J2EE AE with DB on different host. Simply the SAPINST doesn't offer the choice to do that. It's probably built up in a way too install J2EE AE separately on the HW far from systems center and is supposed to have the DB on same machine as J2EE itself.

Nevertheless I need to install J2EE AE as a "distributed system".

I got two ideas, how could it be done:

1) Instal full SAP Java AS as a distributed system. After proper installation and patching I would use a SDM tool and deploy all necessary components to get a J2EE Adapter Engine "like" system.

2) Make a installation of SAP J2EE Adapter Engine as SAPINST allows. After installation and pathing, shutdown the system and move database to desired host, change all settings and start SAP J2EE AE as a distributed system.

Now since I have a SAP Java AS installed already, it seems to me that less time-consuming is the solution no.1. I found on SAPINST DVD, that during J2EE AE installation, SAPXIAF.SAR and SAPXIAFC.SAR are deployed.

Do you think, it would be enough to set the JAVA AS to mode PI/XI usage and to deploy those two SAR files to get workable J2EE Adapter Engine ?

Thank you for your opinions in advance.

Best regards

Tomas

[Former Member · Accepted solution]

hi

You must go with option 1.

Install Java WAS separately and deploy the adapter engine components in to it and register it as a decentral adapter engine in to the XI SLD.

rgds,

Arun

[Former Member]

Hello all,

just the information - after some more setup solution number 1 works.

Rgds

Tom