Switch servlets to quiesce mode

In quiesce mode, all users or all users except those with the SysAdmin capability may not connect. You can set quiesce mode for a single, multiple or all servlets. This allows the System Administrator to apply maintenance changes without being interfered by or interfering with other sessions.

Command line:

sm –quiesce:<mode> [-group:<group>][-host:<host>]

Whether the servlet that the current session is running on is in quiesce mode or not can by tested by the sysinfo.get(“Quiesce”) system language function.

The following table describes different restriction levels of quiesce mode.

Restriction level

Description

Level 0

Service Manager has no login restrictions and accepts all logins normally.

Level 1

Service Manager restricts login to operators who have the SysAdmin capability word. Service Manager denies login to all other operators and displays the message:

System quiesced, you cannot login at this time.

When you issue sm -quiesce:1 -group on a primary or secondary host, all Service Manager processes (except the Service Manager load balancer) are set to quiesce mode 1. The Service Manager load balancer updates its list of available nodes to 0. If users try to connect to the Service Manager load balancer at this time, they receive the following message, because there are no Service Manager processes currently available:

Max sessions exceeded.

Level 2

Service Manager denies login to all operators and displays the message:

System quiesced, login restricted at this time.

Related topics

Operation tasks

System quiesce: Login restrictions

Startup parameter: quiesce

RAD function: sysinfo.get("Quiesce")

Quiesce all servlet container processes in a servlet implementation

Quiesce all servlet container processes on a host