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

You can deploy applications using Helm charts. RMS deployment is supported for Storage classes with Read-Write-Many access mode.Example: Azure File in Azure cluster.

• For dynamic provisioning of RMS volumes use storage class with RWM access mode in persistence.storageClass value.
• For static provisioning, set persistence.storageClass to -.
• Set persistence.scSupportsReadWriteMany to true.

Additional settings for applications are given below:

1. For RMS application:

   • Set rmsDeployment to true
   • Set enableRMS to false
   • When persistence.rmsWebstudio is set to false,the default files in RMS security folder and RMS WebStudio folder are used. If persistence.rmsWebstudio is set to true persistent volumes are created for RMS security and RMS WebStudio with empty folders. Make sure to copy required files to the respective mount paths. Note: Set persistence.rmsWebstudio to true for multiple replicas.

2. For Business Events application with RMS enabled:

   • Set rmsDeployment to false
   • Set enableRMS 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.

Note: Refer to Helm charts for information on setting other variables for BE application deployment.

Testing

• See Testing