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 > SAP Software > Deploying the module > Deploying the module for production

Adding external software dependencies on the server

You must copy the required sapjco3.jar jar file and related files to your runtime environment before you can run your adapter applications.

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

  1. Obtain the sapjco3.jar file and the associated files for your operating system from your SAP administrator or from the SAP Web site. Also obtain the CWYAP_SAPAdapterExt.jar in the <IID_INSTALL_ROOT>>/ResourceAdapters/SAP_7.0.0.0/ext folder from the adapter. The files are listed in the following table.

    The software dependencies differ, depending on the version of SAP Software Tools you use.

    External software dependency files required by SAP Software
    Operating system Files to be copied
    Windows sapjco3.jar, sapidoc3.jar, and any *.dll files that come with the SAP JCo download from the SAP Web site. CWYAP_SAPAdapterExt.jar from the SAP adapter.
    UNIX (including UNIX System Services on z/OS ) sapjco3.jar, sapidoc3.jar and any .so and .o files that come with the SAP JCo download from the SAP Web site. CWYAP_SAPAdapterExt.jar from the SAP adapter.

  2. For SAP Releases 6.40 and 7.0, unzip the R3DLLINST.ZIP archive (C runtime 7.1) from the SAP note 684106 and run the"R3DLLINS.EXE" file in the subdirectory NTPATCH. For SAP releases 4.6D EX2, Web AS 6.40 EX2, SAP NetWeaver 7.01 and 7.10 and higher, download the installation program vcredist_<platform>.exe. Then process the program. The vcredist_<platform > installation packages are delivered with the installation master DVDs of SAP releases 7.01 and 7.10 and are located in NPATCH directory.
  3. SAP JCo requires dbghelp.dll on Windows environment. This dll is found in the system32 directory on most Windows systems. Copy this dll onto your Windows environment if you do not have it.

  4. Copy the files to the server.

    • In a testing environment in IBM Integration Designer, copy the files to the appropriate directory such as ${IID_INSTALL_ROOT}/runtimes/bi_v7/lib/ext directory or ${WPS_INSTALL_ROOT}/lib/ext directory.

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

    • For z/OS, add the specified files to the following locations:

      1. Add the sapjco3.jar file, sapidoc3.jar file, and the CWYAP_SAPAdapterExt.jar file to the ${}/classes directory.

      2. Add the .so files to the ${ WPS_INSTALL_ROOT}/lib directory.

    • For IBM i system, add the specified files and variables to the /SAPJCO directory:

      1. Add sapjco3.jar, sapidoc3.jar file, and any *.dll files that come with the SAP JCo download from the SAP Web site.

      2. Add the CWYAP_SAPAdapterExt.jar from the SAP adapter.
      3. Set the following at the *SYS level on the IBMi server:

        • Add a LIBPATH variable for the SAPJCO folder

        • Add a CLASSPATH variable that points to the /SAPJCO/sapjco3.jar directory

        • Add a system-wide variable QIBM_JAVA_PASE_STARTUP that points to the /usr/lib/start64 directory

      4. Restart the server and deploy the application again

    • For all other operating systems, add the specified files to the following locations:

      1. Add the SAP Java™ Connector interface (sapjco3.jar, sapidoc3.jar, and CWYAP_SAPAdapterExt.jar) to the lib subdirectory of the IBM BPM or WebSphere Enterprise Service Bus.

      2. Add the other SAP JCO files to the bin subdirectory of the IBM BPM or WebSphere Enterprise Service Bus installation directory.

        The installation directory is typically in the runtimes\bi_v6 directory of the IBM Integration Designer installation directory.


Results

The sapjco3.jar and associated files 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)