Deploying BusinessConnect Container Edition Component’s Docker Images

To deploy the BusinessConnect Container Edition component’s Docker images on the Docker or Kubernetes platform, perform the following steps.

Before you begin
Important: Before you deploy Docker images, if you are using MySQL 5.7.x or later versions; then in the my.ini file under [mysqld] section, you must add skip_ssl, set max_allowed_packet to 1024M and set explicit_defaults_for_timestamp to 0
    Procedure
  1. Navigate to the <folder>/bcce-<version>/deployment/config directory.
  2. Open the deployment.properties file and configure the properties listed in the following table.
    3. Property Description
    Docker Properties  
    docker_repository=<docker_registry_ip>:<docker_registry_port> <docker_registry_ip> is the IP address and <docker_registry_port> is the port of the machine from which you want to pull the Docker images from.
    docker_username Specify the user name required to log in to Docker.
    host_ip=<host_ip> <host_ip> is the IP address of the host machine, host name, or Kubernetes cluster.
    gstoken_unzip=<gstoken_unzip>

    <gstoken_unzip> is the directory path where you should extract the contents of GSToken.zip file.

    gstoken can be downloaded from Admin UI after the deployment of Admin server.

    Database properties

    database_url=jdbc:mysql://<database_machine_ip>:3306/<database_schema>?useSSL=false\\&allowPublicKeyRetrieval=true for MySQL database

    <database_machine_ip> is the IP address of the machine where the database resides.

    The default value in deployment.properties is bcce.
    database_url=jdbc:oracle:thin:@<machine_ip>:1521:<serv_id> for Oracle Database <machine_ip> is the IP address of the machine where the database resides. <serv_id> is the service identifier for oracle instance.

    database_username=<username>

    		 <username> is the name of the user accessing the database.
    database_password=<password> <password> is the password to access the database.

    database_driver=com.mysql.cj.jdbc.Driver for MySQL database

    database_driver=oracle.jdbc.OracleDriver for Oracle Database

    		 Configure the database driver property accordingly.

    Optional

    mount_path=<nfs_path>

    <nfs_path> is the path for Poller Server and Interior Server to monitor or get the files mount_path.

    Note: You need to install and configure a working NFS for this feature to work.

    Optional

    mount_path2=<nfs_path>/<folders>

    Path for Interior Server to store the large EDI files.

    Note: The value of mount_path2 should be different from the value of mount_path.

    Optional

    Poller Server Properties     		 

    bcce_poller_engine and bcce_poller_other_servers_instances

    		Default value is 1. One server is deployed unless the value is explicitly set to 0 (zero)
    bcce_poller_other_servers_refresh_rate The time intervals for which the changes for these pollers are dynamically updated to servers from the UI Default value is 300 seconds.

    bcce_poller_other_servers_weight

    		The priority given to each server. 10 being the highest and 1 being the lowest. Server with 10 weight starts first and server with weight 1 starts last.

  3. Configure additional properties that are specific to Kubernetes services: Amazon Elastic Kubernetes Service (AWS EKS), Azure Kubernetes Service (AKS), or Google Cloud Kubernetes Engine (GKE).

  4. Save and close the deployment.properties file.

  5. To deploy the BusinessConnect Container Edition component’s Docker images, run one of the following commands depending on the platform:

    • Kubernetes: Navigate to the <folder>/bcce-<version>/deployment/k8s-scripts directory and run the following command: 
      ./deploy-bcce.sh

    • Docker: Navigate to the <folder>/bcce-<version>/deployment/samples/docker-scripts directory and run the following command: 
      ./docker-run-bcce-all.sh

  6. Follow the command-line interface instructions, review the license agreement, and enter y to accept it.

  7. This step is applicable only if you want to deploy BusinessConnect Container Edition services on Kubernetes, otherwise skip this step.

    When prompted:

    Which Kubernetes environment do you want to deploy TIBCO BCCE services?
    1. Native Kubernetes
    2. AWS EKS
    3. Azure AKS
    4. Google Cloud GKE
    q. Quit

    Enter 1, 2, 3, 4, or q.

  8. When prompted:

    Do you want to deploy TIBCO BCCE Server services?
    1. ConfigStore Management Server
    2. Admin Server
    (y/n)

    Enter y to deploy ConfigStore Management Server and Admin Server.

    Note: To reflect the dynamic updates from ConfigStore Management Server to Interior Server or Poller Server, restart the ConfigStore Management server after the JMS details are configured.

  9. Perform the following steps to configure JMS Server settings; before you deploy Poller Server and Interior Server.

    1. Log in to the BusinessConnect Container Edition application using the URL: http://<host_ip>:<as_port>.
      Tip: Use the <host_ip> and <as_port> that you have set in the deployment.properties file.

    2. Go to System Settings > General, click Internal Messaging (JMS).

      Note: For more information on how to configure Private Process JMS, Intercomponent JMS, or Intercomponent DMZ-JMS, see the Configuring JMS Settings topic in TIBCO BusinessConnect™ Container Edition Administration Guide.
    3. Click Private Process JMS, select or enter information in all the mandatory fields, and click Save.
    4. Click Intercomponent JMS, select or enter information in all the mandatory fields, and click Save.
    5. Optional: To use different JMS between Gateway Server and Interior Server, click Intercomponent DMZ-JMS (Optional), select or enter information in all the mandatory fields, and click Save.

  10. On the command-line interface, when prompted:

    Do you want to deploy TIBCO BCCE Server services?
    3. Poller Server
    4. Interior Server
    Please make sure the JMS Server settings are done properly from the BCCE Admin UI.
    Otherwise, the Poller Server and Interior Server won't work.
    (y/n)

    Enter y to deploy Poller Server and Interior Server.

  11. Perform the following steps to download the GSToken.zip file; before you deploy Gateway Server.

    1. Go to System Settings > Transport Protocols > Inbound Protocols.
    2. Select the HTTP checkbox and click Save.
    3. Click Configure Service of HTTP and click Add .
    4. Enter Gateway Service Name, select HTTP from the Gateway Service Type list and click Proceed.
      Tip: Default Gateway Service Name is set to http in the deployment.properties file. To use another Gateway Service Name, set <service name> for gs_services=HTTP:<service name> in the deployment.properties file.

    5. Select the Enable checkbox to enable the Gateway Service and configure the Ports, Advanced, and Credentials tabs. For more information on how to configure these tabs, see the Configuring Gateway Services (HTTP) topic in TIBCO BusinessConnect™ Container Edition Administration Guide.

    6. On the Admin UI, go to System Settings tile > General, click Installation Properties.
    7. Click Export GS configuration to download the GSToken.zip file, which contains intercomProps, hostKey, and peerCert files that are required to deploy Gateway Server.
    8. Extract the contents of GSToken.zip to the <gstoken_unzip> directory.
      Tip: Use the <gstoken_unzip> that you have set in the deployment.properties file.

  12. On the command-line interface, when prompted:

    Do you want to deploy TIBCO BCCE Gateway Server services?
    Please make sure that you have downloaded the GSToken.zip from Admin UI, extracted it
    in a folder and set the property gstoken_unzip in the deployment.properties file.
    Otherwise, the Gateway Server won't work.
    (y/n)

    Enter y to deploy Gateway Server.

ResultYou have deployed all the components of the BusinessConnect Container Edition application.
What to do nextConfigure the Outbound Email poller to receive an email in the event of a forgotten password.