Adding external software dependencies for JD Edwards EnterpriseOne

Before you can develop message flows that use WebSphere® Adapters nodes, you must add prerequisite files to the runtime environment.

Before you begin

Obtain the relevant prerequisite files for your JD Edwards EnterpriseOne system from your JD Edwards EnterpriseOne administrator. The necessary files are listed in the following table. The software dependencies differ, depending on which version of JD Edwards EnterpriseOne Tools you use.
JD Edwards EnterpriseOne Tools, version 8.9 (SP1, SP2), 8.93 JD Edwards EnterpriseOne Tools, version 8.94 JD Edwards EnterpriseOne Tools, version 8.95, 8.96 JD Edwards EnterpriseOne Tools, version 8.97, 8.98
JDBC driver files

(For more information, see the following table.)

JDBC driver files

(For more information, see the following table.)

JDBC driver files

(For more information, see the following table.)

JDBC driver files

(For more information, see the following table.)

connector.jar Common_Jar.jar ApplicationAPIs_JAR.jar ApplicationAPIs_JAR.jar
database.jar Connector.jar ApplicationLogic_JAR.jar ApplicationLogic_JAR.jar
jdeinterop.ini database.jar Base_JAR.jar Base_JAR.jar
jdeLog.properties EventProcessor_EJB.jar BizLogicContainer_JAR.jar BizLogicContainer_JAR.jar
kernel.jar jdeutil.jar BizLogicContainerClient_JAR.jar BizLogicContainerClient_JAR.jar
log4j.jar jdbj.ini bootstrap.jar BusinessLogicServices_JAR.jar
owra.jar jdeinterop.ini castor.jar castor.jar
xalan.jar jdelog.properties Connector.jar commons-httpclient-3.0.jar
xerces.jar kernel.jar ecutils.jar commons-logging.jar
  log4j.jar EventProcessor_JAR.jar Connector.jar
  xalan.jar EventProcessor_EJB.jar EventProcessor_EJB.jar
  xerces.jar jdbj.ini EventProcessor_JAR.jar
    JdbjBase_JAR.jar Generator_JAR.jar
    JdbjInterfaces_JAR.jar jdbj.ini
    jdeinterop.ini JdbjBase_JAR.jar
    jdelog.properties JdbjInterfaces_JAR.jar
    JdeNet_JAR.jar jdeinterop.ini
    lmproxy.jar jdelog.properties
    log4j.jar JdeNet_JAR.jar
    messagingClient.jar jmxremote.jar
    naming.jar jmxremote_optional.jar
    PMApi_JAR.jar jmxri.jar
    Spec_JAR.jar log4j.jar
    System_JAR.jar ManagementAgent_JAR.jar
    urlprotocols.jar Metadata.jar
    xalan.jar MetadataInterface.jar
    xerces.jar PMApi_JAR.jar
      Spec_JAR.jar
      System_JAR.jar
      SystemInterfaces_JAR.jar
      xalan.jar
      xerces.jar
      xmlparserv2.jar
JDBC driver files
Database JDBC driver files Implementation class
Oracle
tsnames.ora
classes12.zip
oracle.jdbc.driver.OracleDriver
SQLServer sqljdbc.jar com.ibm.microsoft.sqlserver.jdbc.SQLServerDriver
AS/400 jt400.jar com.ibm.as400.access.AS400JDBCDriver
DB2® Type-2 (JDK 1.4/1.5) db2java.zip com.ibm.db2.jdbc.app.DB2Driver
DB2 Type-4 (JDK 1.4/1.5)
db2jcc.jar
db2jcc_license_cu.jar
com.ibm.db2.jcc.DB2Driver
DB2 Type-4 (JDK 1.6) db2jcc4.jar com.ibm.db2.jcc.DB2Driver
Copy the external dependency files to a temporary location. For example, copy them to C:\temp\JDE_dependencies\.
Tip: The Adapter Connection wizard can browse the JDBC driver files more easily if they are stored in their own folder. For example, if you are using an Oracle database server, you put the tnsnames.ora and classes12.zip files in the following location: C:\temp\JDE_dependencies\.

About this task

Locating the JD Edwards support files in the runtime environment on Windows

To add the JD Edwards prerequisite files to the runtime environment, complete the following steps.

Procedure

  1. Ensure that the integration node has started.
  2. Either open the Command Console, or open a Windows command prompt and enter mqsiprofile to initialize the environment.
  3. Enter the following command to display the locations of the prerequisite JAR files:
    mqsireportproperties IBNODE -c AllTypes -o AllReportableEntityNames  -r  
    The following example shows what typically is displayed when you run this command:
    ReportableEntityName='' 
    	EISProviders 
    		JDEdwards=''
    			jarsURL='default_Path'
    			nativeLibs='default_Path' 
    		PeopleSoft='' 
    			jarsURL='default_Path' 
    			nativeLibs='default_Path' 
    		SAP='' 
    			jarsURL='default_Path' 
    			nativeLibs='default_Path' 
    		Siebel='' 
    			jarsURL='default_Path' 
    			nativeLibs='default_Path' 
  4. Set the location of the JD Edwards prerequisite files by using the following command:
    mqsichangeproperties IBNODE -c EISProviders -o JDEdwards -n jarsURL 
    -v C:\temp\JDE_dependencies\
    mqsichangeproperties IBNODE -c EISProviders -o JDEdwards -n nativeLibs 
    -v C:\temp\JDE_dependencies\
  5. To check that the values have been set correctly, run the following command:
    mqsireportproperties IBNODE -c EISProviders -o JDEdwards -r  
    The following example shows what is displayed by the mqsireportproperties command.
    ReportableEntityName=' '
    EISProviders
    	JDEdwards=' '
    		jarsURL='C:\temp\JDE_dependencies'
    		nativeLibs='default_Path' 
    		
    BIP8071I: Successful command completion.
  6. Restart the integration node.