Adding the Plug-in to TIBCO BusinessWorks™ Container Edition

Prior to running the plug-in in TIBCO BusinessWorks™ Container Edition, set the following Java property: 

java.property.javax.xml.datatype.DatatypeFactory=com.sun.org.apache.xerces.internal.jaxp.datatype.DatatypeFactoryImpl

To add the plug-in to TIBCO BusinessWorks™ Container Edition, you must perform the following steps:

    Procedure
  1. Open the physical media or download the TIB_bwsp_version_buildnumber_bwce-runtime.zip installation package from the TIBCO eDelivery site.

    To download the installation package, a user name and password are required. If you do not have a user name and password, contact TIBCO Technical Support.

  2. Copy the com.tibco.bw.tpcl.jde.runtime_version_number wrapper folder with the third-party JDE libraries from bwce_home/palettes/jde/version_number/runtime/plugins to the resources/addons/jars location.
  3. Copy the com.tibco.tpshell.pijdbc_6.3.0.001 directory, which contains the third party PIJDBCDriver.jar from bwce_home/palettes/pi/6.4/runtime/plugins to the resources/addons/jars location.
  4. Perform the postinstallation task described
  5. Copy the com.tibco.tpshell.snowflake.jdbc_version-number.xxx wrapper folder present in the bwce_home/palettes/snowflake/ver/runtime/plugins directory, and place this folder in the resources/addons/jars folder for creating the image or buildpack on docker or cloud foundry.
  6. Copy the com.tibco.tpshell.sap.jco_3.0.8.002 wrapper folder with the third party SAP libraries present in the bwce_home/palettes/sap/version_number/runtime/plugins directory to the resources/addons/jars folder.
  7. EMS libraries must be placed in resources/addons/jars as SAP Activities require JMS.

    Copy the following EMS libraries from the bwce_home/bwce/version_number/system/shared folder to the in resources/addons/jars folder:

    • com.tibco.jms.jmsclient_8.x.0.0xx
    • com.tibco.jms.jmsclient.ufo_8.x.0.0xx
    • com.tibco.jms.jmsclient.rv_8.x.0.0xx
    • com.tibco.jms.jmsclient.admin_8.x.0.0xx
    • com.tibco.tpcl.javax.jms_x.0.0.00x
    Note: The EMS libraries are not needed if Apache Kafka message source is used for IDoc activities.
  8. Add the .zip file to TIBCO BusinessWorks™ Container Edition at run time.

    For the procedure, see the following section in TIBCO BusinessWorks™ Container Edition Application Development:

    PlatformReference
    Cloud Foundry platform"The TIBCO BusinessWorks™ Container Edition Buildpack"
    Docker or Docker-based platforms"Creating the TIBCO BusinessWorks™ Container Edition Application Docker Image"
    Note:
    When configuring the Server Connection Configuration tab for the SAP Connection shared resource, make sure that the value of the Gateway Service field is set to a TCP/IP port number such as 33xx, where xx is the range from 00 to 99, depending on the instance number of the SAP server. 

Windows Container Edition

Before you begin

Ensure that all paths configured in the shared resource and config files follow Windows directory structure and is set to C:\<folderName>\ jdeinetrop.ini (example C:\config) at design time; all the config files required for JDE are placed in C:\<folderName> (jdbj.ini, tnsname.ora, jdeinetrop.ini, jdelog.ini). Default drive in the Docker image is C.

    Procedure
  1. Copy configuration files from host to the Docker image. Example: 
    FROM bwce:latest
RUN mkdir config
ADD config C:\config
RUN net user administrator \active:yes
ADD <earfilename.ear> \
    Note: Administrator rights are required to run the docker image provided in the dockerfile using net user administrator /active:yes.
  2. Disable the Firewall on the host OS when running the application on Docker.

Linux Container Edition

Before you beginEnsure that all paths configured in the shared resource and config files follow Linux directory structure and is set to “C:/<folderName>/ jdeinetrop.ini” (example “C:/config”) at design time; all the config files required for JDE are placed in C:/<folderName> (jdbj.ini, tnsname.ora, jdeinetrop.ini,jdelog.ini). Default drive in the Docker image is C.
    Procedure
  1. Copy configuration files from host to the Docker image. Example: 
    FROM <BASE_IMAGE>
MAINTAINER <MAINTAINER_NAME> 
USER <USER_NAME> 
RUN mkdir -p <DIR_NAME> 
COPY <FILES_TO_COPY> <DIR_NAME>
ADD <earfilename.ear> /
    Note: Administrator rights are required to run the Docker image provided in the dockerfile using USER root.