[JMSEVENTS]

This section has a single setting, CLASSPATH. Note that you must include the full directory path of each file, separating each file by a semicolon. For example, CLASSPATH=connector.jar;EventProcessor_JAR.jar;System_JAR.jar.

Copy the following files from the <JD Edwards EnterpriseOne Windows client installation directory>\system\class folder:

• 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.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 path to the directory where the jdeinterop.ini, jdbj.ini, and jdelog.properties files exist, which must all be in one directory.

• The full path to the JDBC driver files including the filenames.

  The CLASSPATH entry must end with a slash (\), which indicates it is a directory name and not a file name.

Note: For all releases, the files on the client side and Transaction server side must always match. This is important if the Transaction server is updated.