Installing Helm Chart

By using a Helm chart, you can deploy all the services and pods at once, instead of deploying each service and package manually. For TIBCO Order Management, Helm chart supports on the following cloud platforms:

  • Azure Kubernetes Service (AKS)

  • Amazon Elastic Kubernetes Service (EKS)

  • Google Kubernetes Engine (GKE)

Before you begin
  1. Helm Client version 3.5.0 to 3.9.x must be installed on your Kubernetes cluster.
  2. EMS server must be deployed on the same Kubernetes cluster (in the same subnet) with all the required queues, topics, and bridges.
  3. Create database users by running the scripts present under the $OM_HOME/db/dbscripts directory. Ensure that the database is in the same subnet for the cloud instance that you use.
  4. Create Docker images as follows:
    1. Ensure that the <third-party libraries>link is present in the virtual machine that you are working on and then run the $OM_HOME/roles/copyLib.sh script.
    2. Run the $OM_HOME/docker/copy-required-files.sh script.
    3. Create Docker images for all the services. For supporting commands, see the$OM_HOME/docker/Readme.txt file.
    4. Push the Docker images to the required Docker registry.
    Procedure
  1. Log in to the Kubernetes cluster.

  2. Copy the /om_services folder from the $OM_HOME/helm directory to the Kubernetes cluster.

  3. Set the environment variables and Docker image names for all the required services in the values.yaml file that is present at the /om_services folder.
  4. Run the helm chart from the location where the copied directories are present.
    Example: helm installsom ./om_services
    Note: The values.yaml file contains the required properties for starting authorization service, configurator service, and configurator UI services. Create required users from the authorization service and upload required app_properties, metadata, andconfig files as per components from the configurator service. Then you can deploy all services. For more details, refer to the README.md file from the helm directory.
  5. Modify and configure the values.yaml file to deploy required Order Management services by selecting components to be deployed as true.
    Mostly changes are related to database, EMS, and intercommunication of microservices.

  6. Choose your desired ingress controller by adding the value for ingressClassName field in the values.yaml file. The default supported one is nginx. You can configure all the services for ingress control in the om_ingress.yaml file present inside the templates directory.

  7. Run the helm chart again.

ResultA Helm chart is deployed with all the services present in the chart. See the $OM_HOME/samples/helm/values.yaml file for reference.
Note: If you want to enable SSL for Order Management services in helm chart, see 'Configuring SSL for TIBCO® Order Management' section in the TIBCO® Order Management Administration.