Switching Operation Modes Manually

You can switch an operation mode manually at any time.

However, you must always ensure that a manual operation switch does not disrupt system operation, for example, by providing too few dialog processes.

Before you switch the operation mode in the system manually you can carry out a simulation of this switch.

To switch an operation mode manually:

1. From the R/3 main menu, select Tools
® CCMS ® Control ® Control Panel

Alternatively, use transaction code RZ03 .

Information on operation modes and server statuses is displayed.



2. Select Choose OP mode.

A list of the defined operation modes is displayed.

3. Choose the operation mode that you want to switch to.

You return to the list of operation modes and server statuses. The servers normally have the status non-standard operation mode because they are still running in the currently active operation mode.

4. To switch the operation mode on all servers, select Control
® Switch OP 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, for example, if automatic switching has not worked correctly.

You receive an error message if the operation mode switch cannot be performed on all the chosen servers. The test log for operation mode switching (Log) helps you decide whether or not to go ahead with the switch.

Switching Operation Modes

When operation modes are switched, the R/3 System 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 may 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 switched work process.

Exception Operation Mode

To define exception operation:

1. From the R/3 main menu, select Tools
® CCMS® Configuration ® OP mode timetable

Alternatively, use transaction code SM63 .

2. Select Exception operation, and Display.

The timetable for the 24hr cycle is displayed.

3. Select Exception operation, and Change.
4. You can now change the date on which the operation mode is to be activated. Select Day+1, Day-1, Specify a day accordingly.
5. Select Assign to set the time at which the operation mode is to activated.




You do not need to define a full 24hr cycle for exception operation. You must only define the period, in which you want the operation mode to be active.

6. Save the changes.

Normal Operation Mode

For normal operation, you must maintain the operation mode timetable.

To maintain the timetable:

1. From the R/3 main menu, select Tools
® CCMS ® Configuration ® OP mode timetable

Alternatively, use transaction code SM63 .

2. Select Normal operation (24 hr), and Display.

The timetable for the 24hr cycle is displayed.

3. To assign other times to the operation mode, select Normal operation (24 hr) and Maintain.
4. Double-click to select the desired start time and the end time.
5. Select Assign to assign these times to the operation mode.
6. Enter the name of the operation mode to be active for the time period that you defined.

You can only select productive operation modes.

7. Save the changes.
8. Finally, save the table.

You must always define a full 24-hour cycle, that is the operation modes must be set up for 24-hour system operation. If the timetable is not defined:

• the start configuration according to the profile will remain active

• no unattended automatic operation mode switch is possible

• the Job Scheduling Monitor will not function properly

• when a job is created or released with start date/time, it will not be possible to check whether background processes are available at the start time

• jobs that are scheduled to start when the operation mode is switched are not started.

Scheduling an Operation Mode Switch

You can:

• Switch operation modes automatically.

There are two ways of switching operation modes automatically:

Normal Operation	the defined time intervals for the operation modes are repeated in a 24h cycle
Exception Operation	the defined time intervals 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.

• Switch operation modes manually.

Prerequisites for Maintaining Operation Modes

Definition

Before you can maintain operation modes and instances in the CCMS, you must have correctly installed the SAP system with the SAP R/3 initialization program R3INST. The installation procedure for distributed instances ensures that the following actions are performed:

· The shared file systems in the SAP system are automatically mounted on the host system of the distributed instance.

· The instance directories are created

· The SAP R/3 users are defined in the host system

· The operating system kernel for the instance is generated in accordance with the host system attributes

· Entries in the configuration files of the host system are maintained (such as hosts and services).

· Start and system profiles are generated for the instances

You can use the program sapstartand the installed profiles to start the SAP R/3 system.

After starting the SAP system, you being the required configuration tasks in SAP R/3.

Defining Operation Modes

Use

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

Procedure

...

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. 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	Enter a short description of the operation mode, such as “Day operation with 6 dialog processes”.
Monitoring Properties Variant	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. 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.

Monitoring Servers and Work Processes

Use

When an operation mode has been switched, you can see in the process overview whether the work process types have been changed correctly.

Procedure

To monitor the work processes on your current application server:

From the R/3 initial screen, choose Tools ® Administration ® Monitor ® System monitoring ® Process overview. Alternatively, call Transaction SM50.

The system displays an overview of the work processes for the server you have logged onto.

The information for each work process is displayed in a line. The Ty. column shows the work process type: for example, DIA is a dialog process, BTC is a background process.

To monitor the work processes on a different application server:

From the R/3 initial screen, choose Tools ® Administration ® Monitor ® System monitoring ® Servers. Alternatively, call Transaction SM51.

The system displays a list of the R/3 servers. To display the processes for a particular server, position the cursor on the line containing the server name, then choose Processes.

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	The time intervals defined for the operation modes are repeated in a 24 hour cycle
Exception operation	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.

Defining Day and Night Operation

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.

You are most likely to use the R/3 System for dialog processing between 6:00 and 20:00. Outside that time, system resources are normally required primarily for non-dialog processing (background jobs).

You can reconfigure your R/3 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 R/3 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	Day operation 6 a.m. to 8 p.m.	Night operation 8 p.m. to 6 a.m.
Dialog Background Update Enqueue Spool	5 1 2 1 1	2 4 2 1 1

Most R/3 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.

Operation Modes

Purpose

Operation modes let you flexibly adapt R/3 System configuration to varying requirements, maximizing the use of available system resources.

An operation mode defines a resource configuration for the instances in your R/3 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 R/3 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 R/3 instance is not created through an operation mode. Instances are created when the R/3 System is installed, and can be assigned to operation modes.