Containerized data stores

Important: IBM Cloud Pak® for Data Version 4.7 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.

Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.7 reaches end of support. For more information, see Upgrading IBM Software Hub in the IBM Software Hub Version 5.1 documentation.

For each containerized data store for where compliance reporting is required, you must follow specific guidelines.

Note: The following instructions are for installing custom resource files for data stores running in Openshift or Kubernetes clusters. These instructions are not applicable when the data source runs on other types of containers.

For each containerized data store where compliance reporting is required:

Add the License Service Annotations for Data Replication to the pods for the data store by using the custom resource (CR) file.
Install the License Service.

Ensure License Service is installed.

License Service annotations for IBM® Data Replication

For each data store used as a replication source in a production environment create a CR file to update the pods for the source database. The following is an example of the custom resource:

apiVersion: operator.ibm.com/v1 
kind: IBMLicensingDefinition
metadata:
  name: idr-ls
  namespace: cpd-instance #Specifiy  namespace for Database otherwise License Service will check all PODS in the cluster
spec:
  action: cloneModify
  condition:
    metadata:
      annotations:
        <key: value>
        ... 
# For the <key:value>, use existing annotations in your pod where data replication licensing needs to be counted. 

  scope: cluster
  set:
# License Service Annotation for IDR for Cp4D
    cloudpakId: "0ac0b413c9ab4fd6bc5b8b987e735de9"
    cloudpakName: "IBM Data Replication Cartridge for IBM Cloud Pak for Data"
    productID: "4b6998f20e3c4c20a214f0d30bfe8667"
    productName: "IBM Data Replication Cartridge for IBM Cloud Pak for Data"
    productMetric: "VIRTUAL_PROCESSOR_CORE"
    productChargedContainers: "All"
    productCloudpakRatio: "1:1"

For each data store used as a replication source in a non-production environment create a Custom Resource file (CR) to update the pods for the source database. The following is an example of the custom resource:

apiVersion: operator.ibm.com/v1 
kind: IBMLicensingDefinition
metadata:
  name: idr-ls
  namespace: cpd-instance #Specifiy  namespace for Database otherwise License Service will check all PODS in the cluster
spec:
  action: cloneModify
  condition:
    metadata:
      annotations:
        <key: value>
        ... 
# For the <key:value>, use existing annotations in your pod where data replication licensing needs to be counted. 

  scope: cluster
  set:
# License Service Annotation for IIDR for Cp4D
    cloudpakId: "0ac0b413c9ab4fd6bc5b8b987e735de9"
    cloudpakName: "IBM Data Replication Cartridge for IBM Cloud Pak for Data Non-Production"
    productID: "4b6998f20e3c4c20a214f0d30bfe8667"
    productName: "IBM Data Replication Cartridge for IBM Cloud Pak for Data Non-Production"
    productMetric: "VIRTUAL_PROCESSOR_CORE"
    productChargedContainers: "All"
    productCloudpakRatio: "1:1"

License Service annotations for IBM InfoSphere Data Replication

For each data store used as a replication source or target in a production environment create a CR file to update the pods for the source database. The following is an example of the custom resource:

apiVersion: operator.ibm.com/v1 
kind: IBMLicensingDefinition
metadata:
  name: idr-ls
  namespace: cpd-instance #Specifiy  namespace for Database otherwise License Service will check all PODS in the cluster
spec:
  action: cloneModify
  condition:
    metadata:
      annotations:
        <key: value>
        ... 
# For the <key:value>, use existing annotations in your pod where data replication licensing needs to be counted. 

  scope: cluster
  set:
# License Service Annotation for IIDR for Cp4D
    cloudpakId: "0ac0b413c9ab4fd6bc5b8b987e735de9"
    cloudpakName: "IBM Infosphere Data Replication Cartridge for IBM Cloud Pak for Data"
    productID: "4b6998f20e3c4c20a214f0d30bfe8667"
    productName: "IBM Infosphere Data Replication Cartridge for IBM Cloud Pak for Data"
    productMetric: "VIRTUAL_PROCESSOR_CORE"
    productChargedContainers: "All"
    productCloudpakRatio: "1:1"

For each data store used as a replication source or target in a non-production environment create a CR file to update the pods for the source database. The following is an example of the custom resource:

apiVersion: operator.ibm.com/v1 
kind: IBMLicensingDefinition
metadata:
  name: idr-ls
  namespace: cpd-instance #Specifiy  namespace for Database otherwise License Service will check all PODS in the cluster
spec:
  action: cloneModify
  condition:
    metadata:
      annotations:
        <key: value>
        ... 
# For the <key:value>, use existing annotations in your pod where data replication licensing needs to be counted. 

  scope: cluster
  set:
# License Service Annotation for IIDR for Cp4D
    cloudpakId: "0ac0b413c9ab4fd6bc5b8b987e735de9"
    cloudpakName: "IBM Infosphere Data Replication Cartridge for IBM Cloud Pak for Data Non-Production"
    productID: "4b6998f20e3c4c20a214f0d30bfe8667"
    productName: "IBM Infosphere Data Replication Cartridge for IBM Cloud Pak for Data Non-Production"
    productMetric: "VIRTUAL_PROCESSOR_CORE"
    productChargedContainers: "All"
    productCloudpakRatio: "1:1"