Working with Decentralized J2EE Adapter Engine - Part 1 (XI)

By Kalyan Chakravarthy, Fujitsu Consulting India Pvt ltd

 This document provides you the information on how to install the J2EE Adapter Engine and also the Configuration settings need to be done after the installation. 

  • Explain why de-central Adapter engines may be necessary
  • Setup the connection between decentral adapter engine & XI
  • Use the decentral adapter engine to configure communication Channel using Integration Directory
  • Monitoring the local adapter engine using runtime workbench

Here this document is divided into two parts. In the part1 we discuss about Installing J2EE Adapter Engine and in part2 - steps needed after installing and also checking the decentralized adapter in the central instance. 

Reasons for Decentral SAP J2EE-based AE:

  • Protocol of Sender/Receiver system (e.g. FTP not allowed)
  • Driver OS – dependent
  • Firewall between Integration server and Business sys
  • Closer proximity to Business systems
  • Performance
  • Organizational Aspects.

When the above-mentioned situation occurs we can use either Plain J2SE Adapter Engine (or) Decentralized J2EE Adapter Engine. 

Here is a simple Diagram on J2EE Adapter Engine. This diagram shows only when Firewalls comes in between Integration server and Business systems. The reason behind using J2EE Adapter can be anyone of the reasons mentioned above. Most of the cases when customer is not interested in FTP, we can go for this option. 

 Let’s see how to install the Local J2EE Adapter Engine and the prerequisites needed while installing the J2EE adapter engine.

Important UserId’s and Password’s from XI Server

  1. SAPJSF

  2. J2EE_ADMIN

  3. J2EE_GUEST

  4. XISUPER

  5. XILDUSER 

The above information is mandatory for installing J2EE adapter Engine. 

Download the necessary components for J2EE & XI (different Components will be needed based on the installation option)

Before Installation:

The support package of the XI Server and the Decentralized Adapter Engine should be the same. For example if XI Server has SP14 then the DAE should also have SP14.

Step1:

Now execute the sapinst.exe

 

Now Select SAP Net weaver 2004s support Release 2 -->Optional Standalone Units -->J2EE Adapter Engine -->Oracle (Select related Database on which our Adapter is going to install) -->

Click on J2EE Adapter Installation.

 

Step2: 

Provide the password for Administrator (this is for local J2EE engine) 

 

This is for the local system. Please store it!

You will need it later. 

 

Step3: 

Provide the password for XILDUSER (this must match the SAP XI host, if not XI will

Become unstable) 

Here one more point we should remember is give full path of the host name of XI including domain also. I hope that would be better.

 

Step4:

Make sure the password matches the password in XI system 

 The above steps are very important to configure while installing. 

The installation is now complete  

 

Now Start the J2EE from SAP management console and starting the J2EE 

If you have dynamic IP address, then hosts file in server should be changed before starting Decentral Adapter Engine. 

 

I followed the above-mentioned steps and installed the Decentralized Adapter Engine Successfully.
 

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