Deploying BusinessEvents Cluster for Shared All Storage on AWS

BusinessEvents cluster can be deployed for shared all storage on AWS based Kubernetes cluster using the configuration files (YAML format).

Prerequisites

Ensure that your application connection properties for database use global variables. For deploying BusinessEvents cluster for Shared All storage on AWS, you must first set up Kubernetes cluster on AWS and then upload your Docker image to an AWS Docker registry. For more information, see Running TIBCO BusinessEvents® on AWS Based Kubernetes Cluster.

Procedure

  1. Create an Amazon RDS based instance and configure it to connect to a BusinessEvents supported database (Oracle, MySql, DB2, and so on).
    For configuration details, refer to the Amazon RDS documentation at https://aws.amazon.com/documentation/rds/.
  2. Create Kubernetes resources, required for deploying BusinessEvents cluster, using the YAML files.
    These resources include deployment, services, and ConfigMap for the cluster. Thus, to deploy a BusinessEvents cluster, create:
    • A ConfigMap to specify environment variables for database connection
    • A discovery node (pod) to start the cluster
    • A service to connect to discovery node
    • A cache agent node that connects to the discovery node service
    • An inference agent node that connects to the discovery node service
    • A service to connect to the inference agent
    You can find the sample YAML files for shared all storage at BE_HOME\cloud\kubernetes\sa\. For details, see Sample Kubernetes Resource Files for Shared All Storage.
  3. Run the create command of kubectl utility using the YAML files to deploy the BusinessEvents cluster.
    For example, deploy the cluster using the sample files:
    kubectl create -f db-configmap.yaml
    
    kubectl create -f bediscovery.yaml
    
    kubectl create -f bediscovery-service-sn.yaml
    
    kubectl create -f becache.yaml
    
    kubectl create -f beinference.yaml
    
    kubectl create -f befdservice.yaml
    You can also get the external IP to the external service of the cluster using the get services command. You can then use that IP to connect to the cluster.
    kubectl get services befdservice
    You can check the logs of individual BusinessEvents container pods using the following command:
    kubectl logs <pod>