Checking the status of workflow systems

Edit online

 Workflow: 
 If any of your workflow systems become unstable because of a problem with one or more clusters in an environment, you receive a notification directly in the cloud portal. You can then check the status of all the clusters in each of the environments from the System operations view.

Before you begin

To view that status of your environments and to receive status notifications, you must have the Operator role.

About this task

The overall status of the workflow system is determined by the status of each of its cluster members. The environments and each of the clusters can have the following statuses:
Table 1. Statuses of servers and clusters
Status Description
Running All the clusters and their members are running normally.
Partial Some cluster members aren't running normally. Your workflow system is still operational, but you should check its status to determine which clusters are affected.
Stopped One or more clusters are stopped. Check to see which clusters aren't running and try restarting the clusters with issues.
Unknown The status of the workflow system cannot be determined, for example, because the node agent isn't running. Try restarting the workflow environment. If the status doesn't change after the restart, contact IBM® Support.

To receive notifications outside of the cloud portal, you can use the Cluster Status REST API to build a status checking application that can push notifications, for example, to Slack or to email. For more information about the API, see the Cloud Pak for Business Automation as a Service instance services APIs in the API reference section.

Procedure

To check the status of the clusters in an environment, complete the following steps:

  1. Log in to your cloud subscription.
  2. Navigate to the System operations view of the environment you want to work with.
    • Select the environment you want to work with in the drop down menu and Click System operations.
  3. Check the status of the clusters in the environment with the issues by clicking Server Status and Recovery.
  4. Get further insights into cluster issues by using the Log Retrieval option to download a log for the associated cluster.
    Depending on which cluster has issues, you might be able to resolve the problem by taking the following actions:
    Application cluster (AppCluster)
    If you determine that the problem might be caused by one or more process applications, you can use the Process Admin Console to investigate the problem further and take remedial action. For more information, see Process Admin Console. If the problem is with an enterprise application, such as a BPEL process, try using Business Process Choreographer Explorer to investigate and fix the issue. For more information, see Business Process Choreographer Explorer.
    Support cluster (SupCluster) or Messaging cluster (MECluster)
    The problem might be due to an infrastructure problem. Try restarting the cluster, which has the issues.
  5. If restarting individual clusters doesn't resolve the problem, try restarting the entire workflow environment.

    The restart procedure stops and starts all workflow servers and clusters in the environment. The progress of the restart is shown and depending on your workflow system, it might take several minutes to complete.

    When all your workflow systems are running normally again, you'll receive the corresponding notification in the cloud portal. If the problem persists after the restart, contact IBM Support.