Setting up the JD Edwards Connectivity sample

The JD Edwards Connectivity sample has been developed for a level of JD Edwards that has a given definition of various JD Edwards business functions.

The following sections describe the configuration setup that is required to run the samples that demonstrate the JDEdwardsRequest node.

• Enable the Adapter Connection project to locate the JD Edwards libraries and JAR file
• Configure the IBM Integration run time with JD Edwards libraries
• Configure the JD Edwards outbound adapter

Enable the Adapter Connection project to locate the JD Edwards libraries and JAR file

After you have imported the JD Edwards Connectivity sample, for the sample to be built successfully you must make the JD Edwards interface libraries files available to the Adapter Connection project. You can get these libraries from your JD Edwards administrator.

• On Windows:
  1. Copy the dependency libraries to the local subdirectory, C:\JDEdwards.
• On Linux:
  1. Copy the dependency libraries to the local subdirectory, /opt/SAP_JCO.
  2. Modify the attributes of the files so that you have read and execute access to all the files.

Update the JD Edwards library location:

1. Import the sample.
2. Right-click the Adapter Connection project, CWYED_JDE_SAMPLE, select Properties > Java Build Path > Library Tab, and specify the correct location of local subdirectory for the appropriate operating system, for example Windows or Linux.

Configure the IBM Integration run time with JD Edwards libraries

To deploy message flows with JDEdwards nodes, you must configure the IBM Integration run time with the prerequisite JD Edwards libraries. These libraries are used by the underlying JD Edwards adapter component to establish connections with the JD Edwards system.

To set the location of the directories that contain the JD Edwards libraries, run the following mqsichangeproperties commands from a command environment.

1. Run the following commands, changing the JD Edwards client directory to match your operating system and choice of location:

   mqsichangeproperties  IB9NODE -c EISProviders -o JDEdwards -n jarsURL -v C:\JDEdwards

   mqsichangeproperties IB9NODE -c EISProviders -o JDEdwards -n nativeLibs -v C:\JDEdwards

2. To verify that the properties are set up correctly, run the following command:

   mqsireportproperties IB9NODE -c EISProviders -o JDEdwards -r

3. Stop and restart the integration node by using the following commands:

   mqsistop IB9NODE

   mqsistart IB9NODE

Configure the JD Edwards outbound adapter

1. Import the JD Edwards Connectivity sample into your workspace.
2. Expand the JDERequestSampleMessageSet message set project.
3. Click Adapters > Outbound > JDEdwards.
4. To open an editor in which you can specify the connection parameters that are required to access your JD Edwards system, double-click Adapter_JDEdwards_Request.outadapter.
5. Enter the following settings in the editor:
   1. Environment. Typically the host name of the JD Edwards application server.
   2. Role.
   3. Username for the JD Edwards system.
   4. Password. The password that corresponds to the user name.
   5. Timeout. Optional
6. Save the updated adapter.
7. Expand the JDERequestSample Integration project.
8. To open the Broker Archive editor, double-click JDERequest_Sample_BAR.bar.
9. Click the Prepare tab.
10. Click Build broker archive.
11. Save the broker archive.
12. Deploy the JDERequest_Sample_BAR.bar BAR file to the JDERequestSample broker execution group by right-clicking the BAR file and selecting Deploy, or by dragging the BAR file to the execution group.

Back to sample home