Automation assets deployment by using the Platform UI

Use the Platform UI to deploy IBM Automation foundation assets (Automation assets), a capability in IBM Cloud Pak® for Integration that lets you store, manage, and retrieve integration assets.

For more information about deployment considerations, see Automation assets deployment.

Before you begin

Complete these prerequisites before you create an Automation assets instance. An Integration Specialist should carry out these tasks:

  • Ensure that the operator for Automation assets is installed. For more information, see Installing the operators by using the Red Hat OpenShift console.

  • Identify the namespace where the Platform UI is already deployed. You need to deploy Automation assets in the same namespace as Platform UI; otherwise, it will not function properly.

  • Decide whether to deploy Automation assets in "single replica-only" mode or "scalable" mode:

    • Single replica-only mode restricts the number of replicas to one. This mode allows you to use a Block RWO volume for storing your asset data.
      Important: If using this mode, you can't increase the number of replicas after deployment. Also, upgrading an instance of Automation assets that was deployed in single replica-only mode causes Automation assets to become unavailable while the upgrade completes.
    • Scalable mode allows you to deploy Automation assets using one or more replicas. This mode requires you to use a File RWX volume for storing your asset data.
      Tip: This mode allows you to modify the number of replicas after deployment. Also, you can upgrade Automation assets without any downtime.
  • Provide two different types of storage class for use by the Automation assets:

    • Asset data storage - This requires either a Block RWO volume (when deploying in single replica-only mode) or a File RWX volume (when deploying in scalable mode), depending on which mode you are using. For IBM Cloud Block, use the ibmc-block-gold storage class. For IBM Cloud File, use the ibmc-file-gold-gid storage class (specifically the gid variant).

    • Asset metadata storage - This requires a Block RWO volume that meets POSIX requirements and has other characteristics as required by CouchDB persistence storage. For IBM Cloud Block, the ibmc-block-gold storage class must be used. For more information on storage classes in OpenShift, see Understanding persistent storage or Cluster storage.


  1. Log in to Platform UI.

  2. Click Integration instances.

  3. Click Create an instance.

  4. Click Automation assets, then click Next.

  5. Click the tile for your desired deployment option, then click Next.

  6. Set the following fields to configure Automation assets. The UI form perspective is selected by default; it opens a form that lets you view or modify the resource configuration.

    1. In the Name field, enter a name for your instance of Automation assets.

    2. From the Namespace list, select the namespace that contains your Platform UI instance. Automation assets must be deployed in the same namespace as Platform UI to function properly.

    3. For License accept, read through the license agreement and click the toggle if you agree.

    4. For License LI, the correct license is selected by default. For details about specific licenses, see the "Table of license versions" section in Licensing.

    5. From the Asset data storage class list, select one of the compatible Matching storage classes.

    6. From the Asset metadata storage class list, select one of the compatible Matching storage classes.

    7. For Version, the optimal channel is selected by default. For more information on operator and resource version compatibility, see Operator channel versions for this release.

    If you need advanced configuration options, consult Using Automation assets. The Advanced settings toggle is not needed for most common installations.

  7. Click Create to initiate deployment. You are redirected to the "“Integration instances" page. Automation assets begins installing and is initially in the Pending state. Click Pending to check the progress of the deployment. When the deployment completes, the status changes to Ready.

    Pending state Ready state

When ready, click the name of the instance you need to access. Your Automation assets is auto-initialized with a catalog.