Monitoring Maximo Manage activation by using the Red Hat OpenShift console

Monitor the IBM® Maximo® Manage activation in the Red Hat® OpenShift® console.

Procedure

After the Maximo Manage activation starts, confirm if the ManageWorkspace custom resource of the Maximo Manage instance is created from the Red Hat OpenShift web console.
  1. In Red Hat OpenShift console, from the side navigation menu, click Administration > CustomResourceDefinitions.
  2. In the CustomResourceDefinitions list search field, specify ManageWorkspace and then click ManageWorkspace
  3. On the CustomResourceDefinitions details page, on the Instances tab, click the name of the custom resource for your instance.
    For Amazon Web Services customer-managed automated deployment, the name is mas-<uniqueid>-wsmasocp.
  4. Check the section conditions.
    If error messages are displayed, wait several minutes to see whether the Maximo Manage operator resolves the error. In the Red Hat OpenShift console, from the side navigation menu, click Workloads > Pods and check whether the new pod admin-build-config pod was started. Otherwise, review the logs of the entity-mgr-ws pod and look for keywords such as level:error, FAIL, FATAL strings. These messages might clarify the reason that the process is stuck.
  5. If no errors occurred to prevent the deployment process to progress after activation, an admin-build-config pod is created. The admin-build-config pod is where the Maximo Manage image is created based on the settings that you chose.
    Tip:
    • You can check the progress of the build image by clicking the name of the admin-build-config pod and selecting the Logs tab. If it takes too long to view the admin-build-config pod that is being created, select the Logs tab, and you can access the entitymgr-ws pod. Review the log and look for error messages, such as level:error, FATAL, FAIL, or error strings.
  6. After the admin-build-config pod changes its status to complete, the server bundle build config pods are created. Their quantity and names might vary depending on how you configure the server bundle options before you activate Maximo Manage. After several minutes, the pod or pods change status to Complete, and the deployment process creates the maxinst pod, which installs Maximo Manage in the previously configured database.
    1. You can monitor the status of these additional build config pods in the Red Hat OpenShift console by clicking Workloads > Pods and in the Project list, select the mas-<yourinstance>-manage namespace.
      Tip: Click in the Created column and sort by descending order so the most recent pod appears first in the list of pods displayed.
    2. If your existent database is empty, the maxinst pod installs a new database. Otherwise, the maxinst pod validates whether updates to the database are supported in that version.
      Tip:
      • You can check the progress of the maxinst process, or updatedb process in the maxinst pod, by accessing the pod and selecting the Logs tab. After some time, the logs can run quicker showing several commands and outputs, such as scripts that were run. You can select the Terminal tab and use the following commands to show you the logs that were updated during the process:
        
cd log
ls -ltr
      • If completed successfully, you see the message maximo install or update completed. The message is displayed as one of the most recent messages on the Logs tab of the maxinst pod.
  7. After completing the maxinst process, its pod continues to display the Running status until new server bundle pods are created. If you sorted the pods in descending order, the new pods appear listed first in the maxinst pod. The pod names and number vary depending on how you configured them before you activate Maximo Manage. When all containers for the server bundle pods display Ready. Usually, you see 2/2 displayed in the Ready column of the pod view in the standard server bundle configuration, which uses only one pod. Then, the Maximo Manage deployment is complete.
    Tip:
    • If you access Administration/Custom Resource Definitions through the Red Hat OpenShift console, search for ManageWorkspace, click its name and select the Instances tab, then select the CR of your Maximo Manage instance. Review the Conditions and the following information is displayed:
      1. Line Ready with the column Status True, Reason Ready and Message: Manage deployed in workspace <yourworkspacename>
      2. Line Failure with the status False
      3. Line BuildReady with the status Build completed.
      4. DeploymentReady with the status True and Reason Ready and Message: UpdateDB/Maxinst Completed, all - X of X pods ready.... This message specifies that the updatedb or maxinst was completed and the server bundle are all started and ready.
    • You can check the logs of the server bundle pods and the entity-mgr-ws pod to look for error messages in case the statuses do not change to Ready after several minutes.