Manage Serverbundle dependencies configuration and Configurable Startup and Shutdown Sequence for MAS Manage Server Bundles

Background:

Currently, in Maximo Application Suite (MAS) Manage, the startup and shutdown sequence of server bundle pods (e.g., JMS, MEA, CRON, RPT, UI) cannot be explicitly controlled. While users can influence the creation order by defining the sequence of serverBundles in the Manage Workspace CR or MAS UI, the actual readiness order depends on OpenShift scheduling, available resources, and runtime conditions.

This behavior can cause issues when certain components depend on others being available. For instance:

CRON jobs that rely on JMS may fail if JMS is not ready.

RPT (Report) should ideally start before UI, as users may initiate reporting immediately after logging in.

Problem Statement:

The inability to guarantee startup and shutdown order leads to potential application errors and inconsistent behavior during restarts, upgrades, or failover events.

Next to that the dependencies between the pods are not managed. If for example the JMS pod shuts down UI pods should halt and continue when the JMS is avaiable again. This should be configurable.

Proposed Solution:

Provide a mechanism that allows administrators to define dependencies and an explicit startup/shutdown sequence for server bundles.

Possible implementations:

Introduce a startupOrder and shutdownOrder field in the Workspace CR.

Support annotations or dependency relationships between bundles.

Example Desired Startup Order:

JMS

MEA

CRON

RPT

UI

Expected Benefits:

Prevents dependency-related startup failures.

Ensures consistent startup behavior across environments.

Provides flexibility for customers with custom server bundle configurations.