HowToTemplate

WebSphere Adapter for J. D. Edwards OneWorld

The WebSphere Adapter for J.D.Edwards OneWorld provides access to J.D.Edwards OneWorld applications. This resource adapter has the following Quality of Service capabilities:

Security - Application Sign-On, Container Managed Sign-On
Transactions - No Support
Connection Pooling - Supported
Tracing - Supported

Deployment in WebSphere

For general help in deploying resource adapters in WebSphere, refer to the Information Center item located under the Help menu of the Administrative Console.

RAR File Contents

/HowTo.html               this file
/jdeconn.jar                 J.D.Edwards resource adapter jar file
/lcfw.jar                       Framework for Resource Adapter java libraries
/lcapi.jar                      API java libraries for Resource Adapter
/ccf2.jar                       Support library for managing Resource Adapter in non-managed scenario
/lccmn2.dll                   Windows native library
/lcjava.dll                     Windows native library
/lcapi.dll                       Windows native library
/lcci2.tlb                       Windows native libary
/njde.lcx                       Windows native library
/lc.ini                            Configuration file
/jdeconntest.exe            Test program for verifiying connectivity to J.D.Edwards
/META-INF/ra.xml      Resource Adapter's deployment descriptor

Application Server Requirements

The Resource Adapter requires the following to be available on the Application Server:

J2EE Connector Architecture libraries

Java Authentication and Authorization Service libraries

Deployment of the RAR file

Java Libraries
The following jar files, included in the RAR file, should be added to the Application Server CLASSPATH:

jdeconn.jar

lcfw.jar

lcapi.jar

ccf2.jar

Native Libraries
The following libraries, included in the RAR file, need to be added to the system or Application Server PATH:

lccmn2.dll

lcjava.dll

lcapi.dll

lcci2.tlb

Additional Configuration

Place njde.lcx and lc.ini in any directory on the system where the Application Server resides.

In the Application Server, set the environment variable: LOTUS_CONNECTOR_INIT to the fully qualified file name of lc.ini. For example, if lc.ini is in D:\JDEdwardsConnector then:

LOTUS_CONNECTOR_INIT=D:\JDEdwardsConnector\lc.ini

The contents of the lc.ini file should read as follows:

[Configuration]
Directory=D:\JDEdwardsConnector

Where Directory points to the directory where njde.lcx is located.

Testing Configuration
Once the above configuration steps are complete and the J.D.Edwards OneWorld client is installed, connectivity can be tested by executing the following program: jdeconntest.exe
When the following window pops up, enter the required information:

If your system is configured properly, the following window will pop up.

Other Dependencies

In order to use the WebSphere Adapter for J. D. Edwards OneWorld, J.D.Edwards OneWorld Client, version B7.3.3.1 must be on the system where the Application Server resides.

Deployment of a J.D.Edwards OneWorld Application

The deployment of a J.D.Edwards OneWorld application requires the following two JAR files: lcfw.jar, lcapi.jar. However, when you generate deployment code for your application, do not include these two jar files in your EJB-JAR file. Rather, put them in your deployment tool's CLASSPATH..
===