Upgrading IBM Content Collector for SAP Applications

If you deployed Content Collector for SAP Applications, you must upgrade the iccsap_configuration section in the custom resource YAML file that is used in the previous version.

Before you begin

The custom resource file includes several mandatory configuration parameters. Depending on the version of your custom resource YAML file, you must add these mandatory parameters to the file, or provide specific values for parameters that previously used the default value. For more information about these parameters see the IBM® Content Collector for SAP Applications parameters.

About this task

No specific steps are needed for Content Collector for SAP Applications beyond the changes that the cp4a-deployment.sh -m upgradeDeployment command already made.

ICCSAP now supports multiple independent instances in a single Cloud Pak for Business Automation deployment. This enhancement improves scalability, enables workload isolation, and supports multi-tenant environments.

Procedure

  1. To enable multiple ICCSAP instances after you upgrade to operator version 25.0.0-IF005 or later, add the required instance definitions in the CR by using the iccsap_configuration_multi format.

    The following example shows how to define two ICCSAP instances:

    spec:
  iccsap_configuration_multi:
    - instance_id: "sap1"
      replica_count: 1
      # ... other ICCSAP configuration parameters
    
    - instance_id: "sap2"
      replica_count: 1
      # ... other ICCSAP configuration parameters

    Each instance configuration must contain an instance_id value that uniquely identifies the instance. The operator uses this value to generate unique names for deployments, PVCs, and services.

  2. Apply the updated CR. The operator automatically recognizes the new configuration sections and provisions multiple ICCSAP instances accordingly.

    For each instance, the operator generates two URLs:

    • SSL WebPort URL for the instance
    • Plugin URL for the same instance
    For more information about how to connect the SSL WebPort URL to SAP, see Connecting to SAP. When you connect the SSL WebPOrt URL to SAP, note that:
    • Each instance is provisioned with its own dedicated PVC and service for complete isolation.
    • All instances operate independently from one another.
    • The operator automates the creation of deployments, PVCs, and services for the requested number of instances.

What to do next

  1. Continue to configure the other capabilities that are in your CR file, and make sure that you complete the last step Validating the YAML in your custom resource file before you apply the CR to the operator.
  2. Apply the modified custom resource file as described in Applying the upgraded custom resource for the upgrade to take place.