Transitioning between deployment modes
The following scenarios describe the use case for transitioning between the modes:
Before you begin
- Make sure that you are using BMC Helix Service Management 25.3.01 or later and BMC Helix Platform Common Services 25.3.00 or later.
You cannot switch to the CORE deployment mode while upgrading BMC Helix Service Management to version 25.3.01. - Review the sizing requirement and the pods installed in the CORE mode and FULL mode.
See Sizing and scalability considerations for CORE mode and Performing the BMC Helix Service Management installation.
To transition between deployment modes
- In the HELIX_ONPREM_DEPLOYMENT pipeline, in the Build History section, select the last successful build, and click Rebuild.
- In the ENVIRONMENT DETAILS section, specify the following parameter values:
Parameter Description DEPLOYMENT_TYPE Specify the parameter value as SERVICE. DEPLOYMENT_MODE To transition to the CORE deployment mode, select CORE.
To transition to the FULL deployment mode, select FULL.
In the PRODUCTS section, specify the parameter values based on the deployment mode you selected:
For CORE mode, make sure that all product option checkboxes are selected, except for HELIX_CLAMAV and HELIX_GPT.
If you want to include BMC HelixGPT or Clam AntiVirus in your CORE mode deployment, select the HELIX_GPT checkbox for HelixGPT and the HELIX_CLAMAV checkbox for Clam AntiVirus.For FULL mode, clear the checkboxes for any products you do not want to install.
- In the PIPELINES section, select the HELIX_GENERATE_CONFIG, HELIX_PLATFORM_DEPLOY, HELIX_NONPLATFORM_DEPLOY, and HELIX_SMARTAPPS_DEPLOY options.
- Click Rebuild.
When you transition from FULL to CORE mode mode deployment, only essential platform components are loaded and the application pods are scaled down.
Where to go from here
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*