Planning for Maximo Application Suite deployable architecture

Verify access role

IAM access roles are required to install this deployable architecture and create all the required elements.

You need the following permissions for this deployable architecture:

• Create services from IBM Cloud catalog.
• Create and modify IBM Cloud VPC services, virtual server instances, networks, network prefixes, storage volumes, SSH keys, and security groups of this VPC.
• Create and modify IBM Cloud direct links and IBM Cloud Transit Gateway.
• Access existing Object Storage services.

For information about configuring permissions, contact your IBM Cloud account administrator.

Access for IBM Cloud projects

You can use IBM Cloud projects as a deployment option. Projects are designed with infrastructure as code and compliance in mind to help ensure that your projects are managed, secure, and always compliant. For more information, see Learn about IaC deployments with projects.

You need the following access to create a project and create project tooling resources within the account. Make sure you have the following access:

• The Editor role on the Projects service.
• The Editor and Manager role on the Schematics service
• The Viewer role on the resource group for the project For more information, see Assigning users access to projects.

Before you install Maximo Application Suite Core or Maximo Application Suite Core + Manage, you must complete the following tasks.

1. Create an Red Hat OpenShift cluster
2. Obtain an IBM® Entitled Registry key
3. Retrieve the IBM Cloud API Key
4. Get the Maximo Application Suite license file

Platform and Service IBM Cloud IAM roles and policies are only used for the VPC, Red Hat OpenShift, and other IBM Cloud resources, while the users and roles for Maximo Application Suite are defined and managed within the product.

Red Hat OpenShift Cluster

You must have a target Red Hat OpenShift cluster ready to install Maximo Application Suite. If you do not already have one, then install it using Red Hat OpenShift Container Platform on VPC landing zone available on IBM Cloud public catalog or refer to the Red Hat OpenShift Container Platform installation overview.

• Make sure that your existing Red Hat OpenShift cluster has outbound access to quay.io registry site.

  By default the outbound traffic is disabled for Red Hat OpenShift Container Platform 4.15.x. You must enable it on your cluster.

• Make sure that the status of your Red Hat OpenShift cluster for the Master node is Normal, and that of Worker nodes, Add-ons, and Ingress is Healthy.

• Make sure that your cluster nodes are configured to use a secondary storage of 300 GB with 10 iops (input/output operations per second). This is used for ephemeral storage and is configurable in the override.json file. For more information, see override.json.

For more information about steps to deploy, see Deploying Red Hat OpenShift Kubernetes Service VPC cluster.

IBM® Entitled Registry key

To access your software in the entitled registry, obtain an IBM® Entitled Registry key.

For more information, see Entitlement keys.

Maximo Application Suite license

The Maximo Application Suite license needs to be retrieved from the IBM® License Key Center.

If you do not already have your Maximo Application Suite license key file, you can create and download it in the IBM Cloud License Key Center.

For more information, see how to request specific license keys for IBM software products.

IBM Cloud API Key

Your IBM Cloud account's API key. The user who owns this key must be assigned the Administrator role.

If you do not have the API key, see Managing user API keys.

Known limitations

• Compliance policies

  If you validate against FS Cloud compliance policy or stricter policies which require private network use, deploying Maximo Application Suite on Red Hat OpenShift with VPC landing zone require changes (via override.json) to the default landing zone configuration that will:

  1. Open public gateway access to quay.io to pull Maximo Application Suite operator images.
  2. Open public ingress through transit gateway to Maximo Application Suite endpoints for console and api running on the workload cluster.

  These changes cause the FS Cloud profile rules that Red Hat OpenShift with VPC landing zone is validated against, to fail in Security and Compliance Center.

• Version upgrades for the Maximo Application Suite deployable architecture in IBM Cloud projects are not supported.