Licenses and entitlements

IBM Business Automation Insights can be licensed in different ways. The type of license and the deployment license parameters that you set in the custom resource can determine and alter your entitlements.

Note: Use the following information to help you install IBM Business Automation Insights within your purchased entitlement. Your license agreement, such as the IBM International Program License Agreement (IPLA) or equivalent, and its transaction documents, including the license information for Business Automation Insights, is the sole and complete agreement between you and IBM regarding the use of Business Automation Insights.

If you are not familiar with the concepts of how licensing works for IBM software, see the Licensing Basics External link opens a new window or tab, Essential Elements External link opens a new window or tab, and Licensing & Compliance External link opens a new window or tab pages.

The licensing information for Business Automation Insights is divided into the following sections.

License types

Business Automation Insights has only one license type, which does not include OCP. See https://www.ibm.com/support/customer/csol/terms/?id=L-UXBF-EQ4UGB External link opens a new window or tab.

License ratios

Virtual processor core (VPC) is a unit of measurement that is used to determine the licensing cost of IBM products. When you license a virtual machine (VM), VPC is based on the number of virtual cores that are assigned to the VM. One VPC license is required for every core that is available to the IBM program. A ratio defines the factor that is used to move from the VPCs running a program to the VPC licenses consumed. A ratio of 2:1 for example, specifies that 2 VPCs consume 1 VPC license. A ratio of 1:2 specifies that 1 VPC consumes 2 VPC licenses.

Business Automation Insights has a ratio of 1:1.

License reporting

The Container deployment metering of Business Automation Insights is IBM License Service and non-container deployment metering is not available.

Licensing for Disaster Recovery or Backup

In situations where your production or non-production deployments go offline and business workloads are transferred to an offline configuration, your Disaster Recovery (DR) site must continue to be licensed. For more information about qualifying for licensing as DR, see the Backup and Disaster Recovery Licensing Guide External link opens a new window or tab.

IBM license and deployment license parameters

All Business Automation Insights deployments must accept the terms set out in the license agreement before installation. The agreement is marked as valid when the ibm_license custom resource parameter is set to "accept". The custom resource file must include the following YAML:

spec:
  ibm_license: "accept"
A deployment of Business Automation Insights (BAI) has two license values that you can set in the sc_deployment_license parameter of the custom resource file.
  • production

    Any type of use that involves production workload.

  • non-production

    Any type of use that involves non-production workload. Examples of non-production workloads are development, testing, user acceptance testing (UAT), and staging environments. For more information, see Licensing IBM Programs in Non-Production Environments External link opens a new window or tab.

When the sc_deployment_license is set to production, the pods on the OpenShift® cluster are licensed for a production license type. 

shared_configuration:
  sc_deployment_license: "production"

When the sc_deployment_license is set to non-production, the pods on the OpenShift cluster are licensed for a non-production license type.

shared_configuration:
  sc_deployment_license: "non-production"