Operation Modes

Purpose
Operation modes let you flexibly adapt the system configuration to varying requirements, maximizing the use of available system resources. An operation mode defines a resource configuration for the instances in your system. It can be used to determine which instances are started and stopped, and how the individual services are allocated for each instance in the configuration. You can define operation modes to suit specific system requirements, for example, to provide additional dialog or background processing resources during a particular period of time without having to restart the system. Operation modes define: The number of work processes used for each service in the instance The times that the services are available Operation modes support: 24 hour uninterrupted system operation Automatic switching of work process types An instance is not created through an operation mode. Instances are created when the system is installed, and can be assigned to operation

Defining Operation Modes

Use
You can define a new operation mode or change an existing operation mode.

Procedure
1. 1. Choose CCMS Configuration Operation Modes/Instances, or call transaction RZ04.
The system displays a list of productive instances. If you have not yet defined any operation modes, the test operation mode DUMMY will be displayed. This operation mode is automatically configured so that system functions such as the Control Panel and the scheduling of background jobs can be used. If there is already a DUMMY operation mode, this is updated every time that the server is started, and is therefore adjusted to different system relationships. The operation mode DUMMY cannot be used for operation mode switching.

2. 3.

2. Create an operation mode (which can be automatically switched).

To do this, choose Operation Mode Create.

3. Enter the data in the following fields:

Operation Mode Enter a name for the operation mode, such as DAY_OPERATION,

and a short description. You can enter any name for the operation mode, but it is advisable to choose a name that is meaningful and that makes the task of the operation mode clear. Short Description Monitoring Properties Variant Enter a short description of the operation mode, such as Day operation with 6 dialog processes. Enter the name of the monitoring properties variant in monitoring architecture assigned the operation mode. When the operation mode is started, the settings that the monitoring properties variant contains are automatically activated in the alert monitor.

4. 5.

4. Save the data by choosing Operation Mode Save. 5. Repeat this procedure for all required operation modes.
When you have defined and saved your operation modes, you can define the instances and servers. You can call the operation mode maintenance from the Control Panel.

Defining Day and Night Operation

Use
You can define separate operation modes for day and night operation. This means you can guarantee response times for important data entry transactions during the day, and use more work processes at night for job processing. Between 6:00 and 20:00, you will predominantly use the system for dialog processing. Outside that time, system resources are primarily required for background jobs. You can reconfigure your system dynamically at set times by switching operation modes and thus avoid the disadvantages of a system restart. The diagram below illustrates the effect of an operation mode switch:

Procedure
You can display the status of the operation modes and instances using the control panel. To do this, choose CCMS Control/Monitoring Control Panel. Assume that your system has a total of ten work processes available. Define an operation mode for night operation to allow more efficient data processing at night. In the timetable for automatic operation mode switching, enter the times for the two operation modes: 6 a.m. to 8 p.m. for day operation 8 p.m. to 6 a.m. for night operation Table: Operation mode switching: Day/night operation Work Process Distribution Dialog Background Update Enqueue Spool Day Operation 6 a.m. to 8 p.m. 5 1 2 1 1 Night Operation 8 p.m. to 6 a.m. 2 4 2 1 1

Most resources will then be available for dialog processing during the day. At 8 p.m. the operation mode will be switched automatically, making more system resources available for background jobs and data transfer from other systems. At 6 a.m. the next day, the day operation mode will automatically be activated, making more system resources available for dialog processing.

Switching Operation Modes

Use
When operation modes are switched, the work processes are redistributed automatically without stopping and restarting the instances. Only the work process types are changed. For example, a work process used as a dialog process can be switched for use as a background process. The new process type is not activated until the process is free. This means that a process might not be switched immediately. Instead, a process is set to be switched when next possible. For example, if all background processes to be switched to dialog processes still have jobs, the processes are switched one by one when the jobs are completed. Processing is not interrupted. Normal system operation continues uninterrupted during the operation mode switch. Operation mode switches are recorded in the system log. The old process type and the new process type are recorded for each work process that is switched.

Additional Information About Switching Operation Modes

System Startup When a server is started, it first runs without an operation mode. The number of work processes and their distribution is defined in the instance profile used to start the server. The status of the operation mode is checked at regular time intervals and the operation mode defined as active in the operation mode calendar is automatically activated. If no operation mode is entered for the current time in the operation mode calendar, the system does not activate any operation mode. Initial Operation Mode Switch The first time an application server is switched to an operation mode, this is done by the ABAP program SAPMSSY6. This program runs cyclically, collects the alert values, performs profile checks and creates DUMMY operation modes. The profile parameter rdisp/autoabaptimecontrols the intervals at which the program runs. The default cycle is 300 seconds. SAPMSSY6 only switches operation modes if the application server is not running in an operation mode. Normally, the system is switched within 5 minutes of system startup to the operation mode defined in the operation mode calendar. SAPMSSY6 does not perform a continuous switch. This means that a manual operation mode switch will not be switched back after 5 minutes.

Timed Operation Mode Switch The exact times for operation mode switches are defined in the operation mode calendar. A timed operation mode switch is started by the job scheduler (SAPMSSY2). The operation mode switch can therefore only be performed automatically if at least one job scheduler is running in the system. This means that at least one background work process and parameter rdisp/btctime > 0 must be available. The switch is always done for all servers defined in the operation mode. If more than one job scheduler is running, only one job scheduler can activate an operation mode switch.

Switching Operation Modes Automatically

Use
You can: Switch operation modes automatically. Switch operation modes manually.

Procedure
There are two ways to switch operation modes automatically: Normal operation Exception operation The time intervals defined for the operation modes are repeated in a 24 hour cycle The time intervals defined for the operation modes are activated once for a specified time period

Only productive operation modes can be switched automatically. Test operation modes cannot be entered in the timetable.

Switching the Operation Mode Manually

Use
You can switch an operation manually at any time. However, you must always ensure that a manual operation mode switch does not interrupt system operation, for example because there are too few dialog processes available.

Before you switch the operation mode manually in the system, you can perform a simulation of the switch.

Procedure
1. 1. Choose CCMS Control/Monitoring Control Panel, or call transaction RZ03. The system displays information about operation modes and server status. 6. 2. Choose Choose Operation Mode. The system displays a list of defined operation modes. 7. 3. Choose the operation mode that you want to switch to. You return to the list of operation modes and servers. 4. To switch the operation mode for all servers, choose Control Switch operation mode All servers. The servers remain in the manually activated operation mode until the next switch time.
You can also switch the operation mode on individual servers. However, you should only do this in exceptional cases; if the automatic switch was not performed correctly, for example.

8.

If an operation mode switch cannot be performed on all of the selected servers, the system displays an error message. The test log of the operation mode switch (Log) provides information that can help you to decide whether you should perform the switch or not despite the errors.

Checking the Operation Mode with the Control Panel

Use
The main function of the control panel is starting and stopping instances. However, you can also use it to check whether instances were started correctly and whether they are running in the correct operation mode; that is, whether automatic operation mode switching is possible.

Procedure
To display an overview of operation modes and instances: 9. 1. Start the Control Panel by choosing CCMS Control/Monitoring Control Panel.
The control panel displays a list of the host systems and the instances in your system. The list contains:

Instance names Status Services running on your application server

 10.

Active operation mode

2. Select a server.

To find out the cause of a non-standard operation mode: 11. 3. Choose Monitoring Status Details.
The system displays a dialog box showing the details of the server. The most frequent reason for an operation mode switch failing is inconsistencies in the total number of work processes or in the profiles.

12.

4. Once you have solved the problem, switch the operation mode manually from the Control Panel.

Operation Mode Errors

Purpose
If an operation mode switch fails, the most frequent cause is inconsistency in the instance definition. Two examples of this are: A different number of profiles or a different total number of work processes are defined for day operation and for night operation. A server was started with a different configuration than the configuration described in the instance definition.

If these problems occur, the Control Panel displays the message Operation mode non-standard or Work processes non-standard.

Process Flow
To solve this problem: or Copy the current instance status to the instance definition. Make the necessary changes to the instance definition