Operational modes and statuses

A tenant environment can operate in these modes:

Operational

The default mode for a tenant. The environment is fully operational, no limitations.

Maintenance

The Maintenance mode is automatically set when an application upgrade is started. The mode can also be set manually in the Manage Operation Status (ttmtm3501m000) session if maintenance by the tenant is planned otherwise (for example in case of a Convert to Runtime).

In Maintenance mode jobs are no longer activated.

Migration

This mode means that the iterations for the migration are not finished. The Migration mode is automatically set when the migration process is started. The status can also be set manually in the Initiate and control migration (ttmtm3520m000) session, if the tenant has started a migration before.

You cannot run application upgrades when the tenant is in Migration mode.

A tenant environment can have these operational statuses:

Online

All users can login. Shared memory initialized.

Admin Only

Admin (super) users can only login. Shared memory is down.

If switched to this mode normal users that were already logged on are forcibly logged off.

The status can be set manually in the Manage Operation Status (ttmtm3501m000) session.

Offline

No user can login. Shared memory is down.

Take Offline (state transition)

No user can login, existing connections are terminated. Shared memory is stopped.

Blocked

No user can login, existing connections are accepted. Shared memory initialized.

System Message

Notify the users about a planned mode or status change. You can use the implemented System Message feature to define and send an announcement to the users. See the online help of the System Messages (ttaad3290m000) session.