In the IBM Maximo 7.6 (on‑premises) architecture, this process was straightforward: all Maximo JVMs could be stopped, providing full control over database connectivity during maintenance windows.

With the introduction of MAS running on OpenShift, this approach is no longer applicable. The platform automatically manages workload pods and deployments, causing application components to restart automatically.

Procedure

1. Stop Maximo Manage Application

First, access the Manage maxinst pod and stop the Maximo application:

export MAXINST=masdemo

# Switch to the MAS Manage namespace
oc project mas-$MAXINST-manage

# List pods to find the maxinst pod
oc get pods

# Remote shell into the maxinst pod
oc rsh <instance-id>-<workspace-id>-manage-maxinst-<pod-hash>

# Example: oc rsh masdemo-maslocal-manage-maxinst-66998dbd64-vwshn

# Inside the pod, stop Maximo
./managestop.sh

wait until, <instance-id>-<workspace-id>-manage-<pod-hash> not available

oc get pods

NAME                                                     READY   STATUS    RESTARTS         AGE
...
masdemo-maslocal-all-779b7864d6-lcmqp                    2/2     Running   0                363d
masdemo-maslocal-manage-maxinst-66998dbd64-vwshn         1/1     Running   6                363d

2. Start Maximo Manage Application

First, access the Manage maxinst pod and stop the Maximo application:

export MAXINST=masdemo

# Switch to the MAS Manage namespace
oc project mas-$MAXINST-manage

# List pods to find the maxinst pod
oc get pods

# Remote shell into the maxinst pod
oc rsh <instance-id>-<workspace-id>-manage-maxinst-<pod-hash>

# Example: oc rsh masdemo-maslocal-manage-maxinst-66998dbd64-vwshn

# Inside the pod, stop Maximo
./managestart.sh

Ver também