Prerequisites

Whether you are developing a Java connector events application or using the sample Java connector events client, these prerequisites must exist on the machine running the events application or client sample:

• A Java Development Kit (JDK) that corresponds to the version of the JDK under which the JD Edwards EnterpriseOne Transaction server is running.

  For example, when connecting to a JD Edwards EnterpriseOne Transaction server hosted on WebSphere, you must run the Java connector events client or application using the same IBM JDK. Generally, the IBM JDK is located in <WebSphere installation directory>/java).

• An installation of IBM WebSphere MQ, if the JD Edwards EnterpriseOne Transaction Server is hosted on WebSphere.

  This software comes installed as part of the installation of many different WebSphere-related software, including the WebSphere Application Client.

• A completed set of configured files for the environment:

  • jdeinterop.ini

  • jdbj.ini

  • jdelog.properties

• A JAVA_HOME environment variable that points to this JDK.

• A PATH environment variable that includes the entry, %JAVA_HOME%\bin, which assumes that JAVA_HOME has already been defined.

• Copy jar files to the CLASSPATH.

  • The following jar files must be in the CLASSPATH:

    • ApplicationAPIs_JAR.jar

    • ApplicationLogic_JAR.jar

    • Base_JAR.jar

    • BizLogicContainer_JAR.jar

    • BizLogicContainerClient_JAR.jar

    • BusinessLogicServices_JAR.jar

    • castor.jar (Tools Releases prior to 9.2.6)

    • commons-codec.jar

    • commons-lang2.6.jar

    • commons-logging.jar

    • Connector.jar

    • EventProcessor_JAR.jar

    • Generator.jar

    • httpclient.jar

    • httpcore.jar

    • httpmime.jar

    • j2ee1_3.jar

    • jakarta.activation.jar (Tools Releases 9.2.6 and greater)

    • jakarta.xml.bind-api.jar (Tools Releases 9.2.6 and greater)

    • jaxb-core.jar (Tools Releases 9.2.6 and greater)

    • jaxb-impl.jar (Tools Releases 9.2.6 and greater)

    • JdbjBase_JAR.jar

    • JdbjInterfaces_JAR.jar

    • JdeNet_JAR.jar

    • jmxremote.jar

    • jmxremote_optional.jar

    • jmxri.jar

    • ManagementAgent_JAR.jar

    • Metadata.jar

    • MetadataInterface.jar

    • PMApi_JAR.jar

    • Spec_JAR.jar

    • System_JAR.jar

    • SystemInterfaces_JAR.jar

    • xerces.jar

    • xml-apis.jar

    • xmlparserv2.jar

The following items are required to compile and run the application or client.

• The JDBC driver files that correspond to the database to which you are connecting.

  The directory location for these files:

  • jdeinterop.ini

  • jdbj.ini

  • jdelog.properties

    The files must all be in the same directory. It is important to note that you put the directory in the CLASSPATH without the file names, so there is just one entry for these three files. Also, this entry must end in a slash (/), indicating that it is a directory entry and not a file name.

• If you connect to a Transaction server hosted on WebSphere, you also need these files:

  • com.ibm.ws.ejb.thinclient_7.0.0.jar

  • com.ibm.ws.sib.client.thin.jms_7.0.0.jar

  • com.ibm.ws.orb_7.0.0.jar

    Note: These files can be found at <Windows client installation directory>\system\classes on the generation machine that is used for the JD Edwards EnterpriseOne environment to which you are connecting.The files that you place on the CLASSPATH must be the exact same files that are on the Transaction server installation directory.

  • com.ibm.ws.orb_7.0.0.jar

    Typically this .jar file is located in the <WebSphere installation directory>/runtime folder.

• If you connect to a Transaction Server hosted on Oracle WebLogic Server, you also need these files:

  • wlclient.jar

  • wljmsclient.jar

    These files can be found in the WebLogic server directory, <WebLogic_Directory>\server\lib.

    Note: Newer versions of the WebLogic server include a new lightweight library called wlthint3client.jar (located at <WebLogic_Directory>\server\lib) that you can use instead of wlclient.jar and wljmsclient.jar.