Helm Chart RMS

The Helm chart installs TIBCO BusinessEvents application on a Kubernetes cluster using the Helm package manager. The same chart supports RMS TIBCO BusinessEvents application deployment. This page lists down the key points while deploying RMS.

Steps to deploy RMS application and Business Events application with RMS

1. Deploy RMS application using Helm charts. Follow below:

   • Set rmsDeployment to true
   • Set enableRMS to false
   • When persistence.rmsSecurity and persistence.rmsWebstudio are set to false,the default files in RMS security folder and RMS WebStudio folder are used. If persistence.rmsSecurity or persistence.rmsWebstudio are set to true persistent volumes are created respectively with empty folders. Make sure to copy required files to the respective mount paths.
   • For dynamic provisioning use storage class with RWM access mode in persistence.storageClass value. For static provisioning, set persistence.storageClass to -.Note that RMS deployment is supported for Storage classes with Read-Write-Many access mode. Example: Azure Disks in Azure cluster.
   • Set persistence.scSupportsReadWriteMany to true
   • Refer to Helm charts for information on setting other variables for BE application deployment.

2. Deploy Business Events application using Helm charts. Follow below:

   • Set rmsDeployment to false
   • Set enableRMS to true
   • For dynamic provisioning use storage class with RWM access mode in persistence.storageClass value. For static provisioning, set persistence.storageClass to -.Note that RMS deployment is supported for Storage classes with Read-Write-Many access mode. Example: Azure Disks in Azure cluster.
   • Set persistence.scSupportsReadWriteMany to true
   • Set persistence.rmsSharedPVC to <rms helm deployment name>-rms-shared where rms helm deployment name is the RMS deployment to be used for hot deployments.
   • Refer to Helm charts for information on setting other variables for BE application deployment.

Testing

• See Testing