Integrating JD Edwards with XI using IWAY adapters part 2

There appears to be no central information source on all the installation and configuration steps of the JD Edwards adapter, or instructions on how to create a scenario for calling a business function in a JD Edwards system. Until now, that is, thanks to this in-depth guide by SDN member Yomesh Sharma.

There appears to be no central information source on all the installation and configuration steps of the JD Edwards adapter, or instructions on how to create a scenario for calling a business function in a JD Edwards system. Until now, that is, thanks to this in-depth guide by SDN member Yomesh Sharma. This is part 2 of this guide. Click here to read part 1.

1. JD Edwards adapter software installation.

Install the JD Edwards adapter on the XI server, or if you don't wish to play with the central adapter engine, install it on local adapter engine. Once the installation is complete, you can find the resource adapter in the form of an sda (software deployment archive) file named iwxijca_JDEdwards.sda. The default location on Windows platform is:

C:Program FilesiWay55sap

2. Add JDE specific files to iwxijca_JDEdwards.sda.

The sda file contains a rar (resource archive) file. We need to add two files, kernel.jar and connector.jar, to this rar file. These files will be available on JD Edwards server.

The following commands will help you do this:

jar xvf iwxijca_JDEdwards.sda iwxijca_JDEdwards.rar
jar uvf iwxijca_JDEdwards.rar Kernel.jar Connector.jar
jar uvf iwxijca_JDEdwards.sda iwxijca_JDEdwards.rar

3. Deploy the adapter

Now deploy the sda file using software deployment manager (Remotegui.bat).

4. Registering the adapter in SLD.

Create a new product in SLD named IWAY_XI_ADAPTERS.
Create a new Software Component named IWAY_XI_ADAPTER_FOR_J.D._EDWARDS inside the previously created product.
Import the software component in the integration repository and create a new namespace.

For example: http://iwaysoftware.com/iwaf/XI/System

Right click on the adapter metadata node inside adapter objects and select "new."
In the name field, type the exact adapter name. This name is case sensitive and the software component name and namespace values will be automatically populated.

Import the adapter metadata from the location C:Program FilesiWay55sap. The metadata file will be an XML file named "JDEdwardsAdapterMetaData.xml".

Save and activate all your changes in IR.

5. Logging and trace settings.

For logging configuration, you can log on to the Visual Administrator and set the logging details in the log manager.
1. Open the J2EE Engine Administrator application, and log on to the desired cluster server.
2. Expand the Server -> kernel branch and choose LogManager.
3. From the properties panel, select the SingleTraceFile_UnrestrictedLocations key and set the value to include: com.ibi.afjca.sapxi.iwxijca.JDE.
4. Click Update and restart the J2EE Engine cluster.

To adjust the log settings of the IWAY adapter trace location:
1. Expand the Server -> Services branch and choose the Log Configurator service.
2. Click the To advanced mode button.
3. Select the Runtime -> Locations tab, and in the Log Controllers tree select Root Location -> com -> ibi -> afjca -> sapxi.
4. Adjust the settings for this location, then click the Save icon.

Now you can see your JD Edwards adapter in the list of deployed adapters on XI server, but you cannot use it to call a business function, because we don't have the interface for the any business function yet. So for this purpose we will deploy the application explorer on the XI server. Read part 3 for detailed steps of how to accomplish this.


This content is reposted from the SAP Developer Network.
Copyright 2006, SAP Developer Network

SAP Developer Network (SDN) is an active online community where ABAP, Java, .NET, and other cutting-edge technologies converge to form a resource and collaboration channel for SAP developers, consultants, integrators, and business analysts. SDN hosts a technical library, expert blogs, exclusive downloads and code samples, an extensive eLearning catalog, and active, moderated discussion forums. SDN membership is free.

Want to read more from this author? Click here to read Yomesh Sharma's weblog. Click here to read more about Exchange Infrastructure on SDN.


Dig Deeper on SAP integration

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchContentManagement

SearchHRSoftware

Close