Prerequisites

MAS License File

From the Get Keys menu, select IBM AppPoint Suites, then select IBM MAXIMO APPLICATION SUITE AppPOINT LIC and complete the form with the following information:

Field	Content
Number of Keys	Number of AppPoints that will be used in this installation.
Host ID Type	A unique value (for example, Ethernet Address). This value will be used in SLS_LICENSE_ID=46d9....
Host ID	Enter any 12-digit hexadecimal string.
Hostname	Set to the hostname of your OCP instance. Any value is acceptable.
Port	Set to 27000

Leave all other values as default. Click Generate and download the license file (license.dat). Save the file for later use.

IBM Entitlement Key

Access the Container Software Library using your IBMId to obtain your entitlement key.

This values will be defined at:

export IBM_ENTITLEMENT_KEY=YOUR_KEY

MAS Catalog and versions

Field	Content
--mas-catalog-version v9-260326	Access the https://ibm-mas.github.io/cli/catalogs/ to get MAS catalog version
--mas-channel 9.1.x	Access the https://www.ibm.com/support/pages/node/7267465 to get MAS channel
--manage-channel 9.1.x	Access the https://www.ibm.com/support/pages/node/7267465 to get MAS Manage channel
--storage-class-rwo ocs-external-storagecluster-ceph-rbd	run command "oc get storageclass"
--storage-class-rwx ocs-external-storagecluster-cephfs	run command "oc get storageclass"
--manage-base-language --manage-secondary-languages	https://www.ibm.com/docs/en/masv-and-l/maximo-manage/cd?topic=SSLPL8_cd/com.ibm.mam.doc/manage_deploy/c_mas_man_lang_support.htm

Running the MAS CLI

Pull the image and run the MAS CLI container. From a terminal:

mkdir -p mas-cli-workspace
podman run -it --rm -v $(pwd)/mas-cli-workspace:/mnt/home:Z --pull always quay.io/ibmmas/cli:latest

for Mac (Apple Silicon M1) add --arch arm64

Result

IBM Maximo Application Suite CLI Container v3.xx.0
...
Available commands:
- mas install to launch a MAS install pipeline
- mas uninstall to launch a MAS uninstall pipeline
...

Exit the container using the following command:

[ibmmas/cli:X.XX.X]mascli$ exit

Internal Image Registry

Full article here: IBM Maximo: Install MAS - Image Stream Cannot Be Used as Build Output

1) Check if the image registry pods are running:

oc get pods -n openshift-image-registry

Expected output should include image-registry-* pods. If only the operator pod is present:

NAME                                               READY   STATUS    RESTARTS   AGE
cluster-image-registry-operator-6b56b8cfc9-whpwq   1/1     Running   0          24h
node-ca-n7lxk                                      1/1     Running   0          24h

This confirms the registry is not deployed.

2) I need to Delete and Recreate the existing PVC:

oc delete pvc image-registry-storage -n openshift-image-registry

Create a new PVC with CephFS storage class:

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: image-registry-storage
  namespace: openshift-image-registry
  annotations:
    imageregistry.openshift.io: 'true'
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 100Gi
  storageClassName: ocs-storagecluster-cephfs  # Changed from ceph-rbd
  volumeMode: Filesystem

Apply the new PVC:

oc apply -f new-pvc.yaml

3) Enable Registry with Persistent Storage (Production) ===

oc patch configs.imageregistry.operator.openshift.io cluster --type merge \
  --patch '{"spec":{"managementState":"Managed","storage":{"pvc":{"claim":""}}}}'

This configures the registry to use a PersistentVolumeClaim for storage.

Installing MAS Core via MAS CLI

Run the container:

mkdir -p mas-cli-workspace

cp license.dat mas-cli-workspace/.

podman run -it --rm -v $(pwd)/mas-cli-workspace:/mnt/home:Z --pull always quay.io/ibmmas/cli:latest

for Mac (Apple Silicon M1) add --arch arm64

Login to OpenShift:

oc login --token=sha256~XXXX --server=https://api.ocp-XXXX:6443

Export the entitlement key:

export IBM_ENTITLEMENT_KEY=YOUR_KEY

Check license file:

cat /mnt/home/license.dat

Run the MAS installation (MAS Core + Mas Manage + DB2 container + Maximo demo data):

mas install \
  --non-prod \
  --mas-instance-id dev01 \
  --mas-workspace-id mas01 \
  --mas-workspace-name "mas-dev-01" \
  --mas-catalog-version v9-260326-amd64 \
  --mas-channel 9.1.x \
  --manage-channel 9.1.x \
  --manage-jdbc workspace-application \
  --manage-components base=latest \
  --license-file /mnt/home/license.dat \
  --contact-email [email protected] \
  --contact-firstname Enio \
  --contact-lastname Basso \
  --storage-class-rwo ocs-external-storagecluster-ceph-rbd \
  --storage-class-rwx ocs-storagecluster-cephfs \
  --storage-pipeline ocs-storagecluster-cephfs \
  --storage-accessmode ReadWriteMany \
  --superuser-username superuser \
  --superuser-password ibm-MAS-superuser-passw0rd-123! \
  --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \
  --skip-grafana-install \
  --db2-manage \
  --manage-demodata \
  --accept-license \
  --no-confirm

Others Installations

IBM Maximo: Installing MAS Core + Manage + DB2 Container

Known installation issues

IBM Maximo: Install MAS - Known installation issues

IBM Maximo: Install MAS - Image Stream Cannot Be Used as Build Output

IBM Maximo: Troubleshooting Maximo Manage Workspace activation

IBM Maximo: Troubleshooting - Unable to Delete a Project (Namespace)

Accessing MAS Core

1) Log in to the OpenShift Cluster Web Console

2) Navigate to Networking > Routes

3) Select the mas-inst1-core project

4) Click the inst1-admin route to open it in a new browser tab

Retrieving Credentials

1) Log in to the OpenShift Cluster Web Console

2) Navigate to Workloads > Secrets

3) Select the mas-inst1-core project

4) Filter by superuser

5) Open the secret inst1-credentials-superuser

6) Click Reveal to view the credentials

IBM Maximo: Install Maximo Application Suite using MAS CLI