Transitioning between deployment modes


The features and enhancements in this topic are under controlled availability to select customers.

BMC Helix Service Management supports two deployment modes, CORE and FULL:

  • CORE mode—Deploys only essential platform components such as BMC Helix Innovation Suite, CMDB, and Foundation data. Optional components like HelixGPT and Clam AntiVirus can also be included.
  • FULL mode—Deploys the complete suite of BMC Helix Service Management applications and components.

You can switch between these modes based on your business needs. For example, if you are using the CORE mode deployment and want to use BMC Service Management applications to expand operations, you can transition from CORE to FULL mode.
 

 


The following scenarios describe the use case for transitioning between the modes:

Scenario 1: Transitioning from FULL to CORE mode
Apex Global has developed its own internal ticketing system by using the BMC Helix Innovation Suite platform and does not require BMC Helix ITSM and smart applications. To optimize resource usage and streamline operations, Apex Global opts for a selective deployment approach, choosing only the BMC Helix Innovation Suite components. 
A system administrator at Apex Global transitions their environment from FULL mode to CORE mode. This configuration ensures that only required components are loaded into memory, while non-essential components are excluded. The deployment is lightweight and reduces CPU and memory consumption.

Scenario 2: Transitioning from CORE to FULL mode
Apex Global currently uses BMC Helix Service Management in the CORE mode. To expand its IT operations, Apex Global needs a comprehensive service management solution that includes BMC Helix ITSM, Smart Reporting, and BMC Helix Digital Workplace. Apex Global opts for a FULL mode deployment approach.
A system administrator at Apex Global transitions their environment from CORE mode to FULL mode to enable all components of BMC Helix Service Management. This deployment provides BMC Helix Service Management capabilities such as automated workflows, service catalogs, and analytics.

Before you begin

To transition between deployment modes

  1. In the HELIX_ONPREM_DEPLOYMENT pipeline, in the Build History section, select the last successful build, and click Rebuild.
  2. In the ENVIRONMENT DETAILS section, specify the following parameter values:
    ParameterDescription
     DEPLOYMENT_TYPESpecify 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.

  3. 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.

  4. In the PIPELINES section, select the HELIX_GENERATE_CONFIGHELIX_PLATFORM_DEPLOY, HELIX_NONPLATFORM_DEPLOY, and HELIX_SMARTAPPS_DEPLOY options.
  5. 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

Administering

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*