Installing WebSphere Automation

Before you install WebSphere Automation, more preparation might be needed.

Make sure that you understand the prerequisites and requirements before you start your installation to ensure that your installation goes as smoothly as possible. For more information about planning your deployment and implementation, see Preparing for installation of WebSphere Automation. For more information about setting up Red Hat® OpenShift® Container Platform, see Installing Red Hat OpenShift Container Platform clusters.

Note: IBM Cloud Pak foundational services are deployed to the ibm-common-services namespace by default. However, you can install them in a different namespace. The installation must be done before the WebSphere Automation installation. For more information, see Installing IBM Cloud Pak foundational services in a custom namespace. After a different namespace is set up, you must indicate your chosen namespace within the WebSphereAutomation custom resource, specifically by using the .spec.commonServices.registryNamespace field.

The following tasks represent the typical task flow for installing WebSphere Automation:

  1. Installing Red Hat OpenShift Container Platform
  2. Mirroring images to a private container registry

    You can use this optional step if you want to use the ibm-pak plug-in to install WebSphere Automation into an air gap environment. Although WebSphere Automation supports installation in an air gap environment, it does not support operating in one due to its dependency to obtain information and fixes for vulnerabilities and exposures (CVEs) from the IBM web site.

  3. Adding the IBM operator catalog
  4. Installing the WebSphere Automation operator prerequisites
  5. Installing the operator
  6. Creating the entitlement key secret
  7. Creating the WebSphere Automation instance