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.
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
- Navigate to the
<folder>/bcce-<version>/deployment/config
directory. - Open the
deployment.properties
file and configure the properties listed in the following table. -
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).
- Save and close the
deployment.properties
file. -
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
- Kubernetes: Navigate to the
-
Follow the command-line interface instructions, review the license agreement, and enter
y
to accept it. -
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
5. OpenShift
q. Quit
Enter
1
,2
,3
,4
, orq
. -
When prompted:
Do you want to deploy TIBCO Auth Server service?
(y/n)Enter
y
to deploy Auth Server.Waiting for the Auth Server to start for about 90 seconds...
-
When prompted:
Do you want to deploy TIBCO AuditSafe Services?
1. Data Server
2. Web ServerEnter
y
. -
When prompted:
Do you want to run TIBCO BCCE Server docker containers?
1. ConfigStore Management Server 2. Admin Server 3. Configuration API 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. -
Perform the following steps to configure JMS Server settings; before you deploy Poller Server and Interior Server.
- 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 thedeployment.properties
file. -
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. - Click Private Process JMS, select or enter information in all the mandatory fields, and click Save.
- Click Intercomponent JMS, select or enter information in all the mandatory fields, and click Save.
- 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.
- Log in to the BusinessConnect Container Edition application using the URL:
-
On the command-line interface, when prompted:
Do you want to deploy TIBCO BCCE Server services?
4. Poller Server
5. 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. -
Perform the following steps to download the
GSToken.zip
file; before you deploy Gateway Server.- Go to System Settings > Transport Protocols > Inbound Protocols.
- Select the HTTP checkbox and click Save.
- Click Configure Service of HTTP and click Add
.
- 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 thedeployment.properties
file. To use another Gateway Service Name, set <service name> forgs_services
=HTTP:<service name>
in thedeployment.properties
file. -
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.
- On the Admin UI, go to System Settings tile > General, click Installation Properties.
- Click Export GS configuration to download the
GSToken.zip
file, which containsintercomProps
,hostKey
, andpeerCert
files that are required to deploy Gateway Server. - Extract the contents of
GSToken.zip
to the<gstoken_unzip>
directory.Tip: Use the<gstoken_unzip>
that you have set in thedeployment.properties
file.
-
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.
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.
|
Database properties | |
|
The default value in |
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_url =jdbc:sqlserver://<database_machine_ip> :1433;encrypt =false;databaseName =xxxx; integratedSecurity =false; for MSSQL database |
<database_machine_ip> is the IP address of the machine where the database resides.
|
tas_database_username= aus_database_username= |
<username> is the name of the user accessing the database.
|
database_password=<password> tas_database_password= aus_database_password= |
<password> is the password to access the database. |
|
Configure the database driver property accordingly. |
ElasticSearch Properties | |
elasticsearch_host=<elasticsearch_ip> | <elasticsearch_ip> is the IP address of the machines where the ElasticSearch database resides. |
elasticsearch_username=<usr_name> | <usr_name> is the name of the user accessing the ElasticSearch database. |
elasticsearch_password=<pwd> | <password> is the password to access the ElasticSearch database. |
gstoken_unzip =<gstoken_unzip> |
<gstoken_unzip> is the directory path where you should extract the contents of
GSToken.zip file.
|
SSO Properties | |
ws_https=true ws_redirect_url=<host_ip>:<ws_port>/tas/sso/oidc/callback |
The properties must be set to either true or false. By default, it is set to false. To enable Web Server HTTPS for SSO redirect set ws_https=true and configure ws_redirect_url=<host_ip>:<ws_port>/tas/sso/oidc/callback ws_https is a boolean value to enable https for auditsafe, <ws_port> is web server port, which is by default 31000, and the redirection url is for SSO authentication redirection for login purposes on AuditSafe web server and TIBCO BusinessConnect™ Container Edition Admin server |
as_https=true as_redirect_url=<host_ip>:<as_port>/sso/oidc/callback |
Enables HTTPS of Admin server for SSO redirect by setting as_https=true and configuring as_redirect_url=<host_ip>:<as_port>/sso/oidc/callback |
Optional
|
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 |
|
|
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. |
|
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. |