IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > JD Edwards EnterpriseOne > Deploying the module > Deploying the module for production

Adding external software dependencies on the server

You must copy the required software dependency files to your runtime environment before you can run your adapter applications.

To copy the required files to IBM BPM or WebSphere Enterprise Service Bus, use the following procedure.


Procedure

  1. Obtain the external software dependency files from your JD Edwards EnterpriseOne administrator. The files are listed in Table 1.

    External software dependency files required by JD Edwards EnterpriseOne Tools
    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
    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 BizLogicContainerClient_JAR.jar
    kernel.jar jdeutil.jar BizLogicContainerClient_JAR.jar BizLogicContainer_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

    JDBC driver files

    For example, if you are using an Oracle database server, use the following JDBC driver files:

    • tnsnames.ora
    • ojdbc6.jar

    log4j.jar EventProcessor_JAR.jar Connector.jar
      xalan.jar EventProcessor_EJB.jar EventProcessor_EJB.jar
      xerces.jar jdbj.ini EventProcessor_JAR.jar
     

    JDBC driver files

    For example, if you are using an Oracle database server, use the following JDBC driver files:

    • tnsnames.ora
    • ojdbc6.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 MetadataInterfaces_JAR.jar
        xerces.jar PMApi_JAR.jar
       

    JDBC driver files

    For example, if you are using an Oracle database server, use the following JDBC driver files:

    • tnsnames.ora
    • ojdbc6.jar

    Spec_JAR.jar
          SystemInterfaces_JAR.jar
          System_JAR.jar
          xalan.jar
          xerces.jar
          xmlparserv2.jar
         

    JDBC driver files

    For example, if you are using an Oracle database server, use the following JDBC driver files:

    • tnsnames.ora
    • classes12.zip

  2. Copy the files to the server.

    • In a testing environment in IBM Integration Designer, copy the files to the ${WAS_INSTALL_ROOT}/runtimes/bi_v7/lib/ext directory.

    • In a production environment, copy the files to the ${WAS_INSTALL_ROOT}/lib/ext directory of IBM BPM or WebSphere Enterprise Service Bus.


Results

The external software dependency files for JD Edwards EnterpriseOne are now part of your runtime environment.

Deploying the module for production


Next topic: Installing the RAR file (for modules using stand-alone adapters only)