Getting Started With the Integration Manager Connect for J.D. Edwards OneWorld

This chapter describes how to set up and configure the Integration ManagerTM Connect for J.D. Edwards OneWorld.

Setup and Configuration

The following requirements must be completed before you can use the Integration Manager Connect for J.D. Edwards OneWorld:

Determine the release number of your J.D. Edwards OneWorld system. The Novell Integration Manager Connect for J.D. Edwards OneWorld supports J.D. Edwards OneWorld 7.3.2 and above.
Locate or acquire the J.D. Edwards JAR files. See J.D. Edwards JAR Files.
Update the classpath in xconfig.xml, in both the design environment and on the server, to reflect the addition of the J.D. Edwards JAR files. See Adding the J.D. Edwards JAR Files to the Design-Time Environment and Adding the J.D. Edwards JAR files to the Novell Application Server Environment.
Update the license for your Integration Manager Connect for J.D. Edwards OneWorld installation. See Updating the Design-time Software License and Updating the Runtime License.
Create GenJava wrappers for J.D. Edwards business functions. See Creating GenJava Wrappers.

The steps necessary to accomplish these requirements are discussed in detail in the following sections.

J.D. Edwards JAR Files

Before attempting to use the Integration Manager Connect for J.D. Edwards OneWorld (which is installed automatically as part of the default Integration Manager installation process), you must complete the installation by obtaining and installing two J.D. Edwards JAR files. These files are proprietary to J.D. Edwards and are not shipped by Novell nor installed as part of Integration Manager.

You need the following jar files:

Kernel.jar
Connector.jar

These JAR files should be included in the \systems\classes directory in your J.D. Edwards environment. If they are not, contact your J.D. Edwards representative to obtain copies of the JAR files.

When you have located the J.D. Edwards JAR files, you must add the JAR files to the classpath in both your design-time and runtime environments, as described in the following sections.

Adding the J.D. Edwards JAR Files to the Design-Time Environment

Procedure To add the J.D. Edwards JAR Files to your design-time configuration

If Integration Manager is running, shut it down before proceeding.
Obtain the J.D. Edwards JAR files (see J.D. Edwards JAR Files), if it is not included in your J.D. Edwards OneWorld installation.
Copy the J.D. Edwards JAR files to the /Common/lib folder of the Integration Manager installation directory on your design-time computer.

Procedure To add the J.D. Edwards JAR Files to the design-time classpath

Locate your xconfig.xml file under /Composer/Designer/bin and open the file in a text editor.
Scroll to the bottom. Within the <RUNTIME> element, you should see many <JAR> entries.
Add additional <JAR> elements that specify the path to the J.D. Edwards JAR files, as follows:
```
  <JAR>..\..\..\Common\lib\Kernel.jar</JAR>
  <JAR>..\..\..\Common\lib\Connector.jar</JAR>
```
These entries tell the class loader where it can find the J.D. Edwards JAR files.
Save and close xconfig.xml.

Adding the J.D. Edwards JAR files to the Novell Application Server Environment

If the application server is running, shut it down before proceeding.
Obtain the J.D. Edwards JAR files (see J.D. Edwards JAR Files), if they are not included in your J.D. Edwards OneWorld installation.
Copy the J.D. Edwards JAR files to a suitable location on your application server. The exact location doesn't matter, as long as you create a classpath entry pointing to the J.D. Edwards JAR files location, as described in the following steps.
Update the application server classpath. For the Novell exteNd application server, locate the AgJars.conf file in the AppServer/bin directory and open the file in a text editor.
Create new entries in the "MODULE COMMON" section, as follows:
```
  $SS_LIB ../../Common/lib/Kernel.jar
  $SS_LIB ../../Common/lib/Connector.jar
```
This example assumes that you have placed the JAR files in the application server /Common/lib directory. Edit this path as required to reflect the actual target directory.

NOTE: For application servers other than Novell exteNd, follow the application server vendor's instructions for updating the classpath.

Updating the Design-time Software License

Obtain a valid license string from your Novell representative.

NOTE: You use the same license string to activate the design-time and runtime versions of Integration Manager Connect for J.D. Edwards OneWorld.
Start Integration Manager.
Select About Integration Manager from the Help menu. The About Integration Manager dialog box is displayed.
Select System. The System Information dialog box is displayed.
Click on the Licenses tab, located in the upper left corner of the System Information dialog box. The license information for your Integration Manager installation is displayed.
Scroll down until you see the row for J.D. Edwards.

NOTE: The Connect ships with an Evaluation license string which may be used for 90 days.
To use the evaluation license string, select the check box in the Enabled column and skip to Step 10. To enter a different license string, select the check box in the Enabled column. The Edit button in the J.D. Edwards row is enabled.
Select Edit in the J.D. Edwards row. The Edit License dialog box is displayed.
Type the license string for the Integration Manager Connect for J.D. Edwards OneWorld in the New License field.
Scroll down until you see the row for J.D. Edwards Service.
Repeat Step 7 through Step 9 for the J.D. Edwards Service row.
Exit out of all dialogs by selecting OK.

Updating the Runtime License

NOTE: If you are using the Tomcat application server, copy the jca10apis.jar from the \NIM6\Server Resources\Tomcat directory (Windows) or nim/Server Resources/Tomcat directory (Linux) to the Tomcat Composer\lib and shared\lib directories before attempting to update the runtime license.

Make sure that the Novell Integration Manager Enterprise Server is installed.
Start the application server. The Novell Integration Manager Enterprise Server starts automatically when you start the application server.
Open a browser window and navigate to the Novell Integration Manager main administrative console. Typically, this is at:
```
  http://localhost/exteNdComposer
```
In the upper left corner of the console window, click the Integration Manager logo immediately above the words "Server Console," as shown in the following illustration.
```
  
```
In the content area of the main frame, near the bottom, click Licenses. The Manage Licenses window is displayed. This window shows the license status of every Integration Manager Connect. See the following illustration.
Scroll down to the entry labeled "jde".

NOTE: The Connect ships with Evaluation license strings which may be used for 90 days.
Type a license string in the text field in the "jde" row; then select Enabled in the "jde" row. To use the evaluation license string, just select Enabled.
Select Update in the "jde" row.
Scroll down to the entry labeled "jdeservice".
Type a license string in the text field in the "jdeservice" row; then select Enabled in the "jdeservice" row. To use the evaluation license string, just select Enabled.
Select Update in the "jdeservice" row.

Creating GenJava Wrappers

Before you can use the Integration Manager Connect for J.D. Edwards OneWorld, you must create GenJava wrappers. J.D. Edwards OneWorld provides a utility, GenJava, that generates Java wrappers for the business functions running as part of the OneWorld server. Once GenJava is executed, it creates Java class files for all the interface classes and associated data structures. GenJava is supplied as a command line process with several run-time options. For more information about GenJava, see the J.D. Edwards Interoperability Guide for OneWorld Xe.