Show TOC

Procedure documentationManaging Work Modes

 

You use this procedure to plan, notify, and execute work modes for technical systems, databases, hosts, technical scenarios, instances, connections,logon groups, and End User Experience Monitoring (EEMon) robots during activities such as:

  • Patch upgrades

  • Database, hardware, or operating system maintenance

  • Configuration or customizing changes

  • Migration

  • Execution of EEMon scripts

EEMon robots are grouped by region, country, and location. You plan work modes on EEMon robots to enable execution of scripts only during certain period. For more information on EEMon, see End User Experience Monitoring.

Example Example

You ensure the following with robots installed in European locations:

  • On work days from 8:00 to 18:00 hours CET the robots do alerting and reporting

  • During rest of the time they do only reporting

End of the example.

The types of technical work modes are:

Type

Description

Planned Downtime

Work mode during which the system is technically down and you do not have access. System administrators can use this work mode to perform planned administration tasks that can only be performed during downtime.

Maintenance

Work mode during which the system is technically up and you have no access. System administrators can use this work mode to perform planned administration tasks that can only be performed during maintenance.

Note Note

For information about which downtimes occurred in which systems and when, see Analyzing Downtimes.

End of the note.

The types of business work modes are:

Type

Description

Peak Business Hours

Work mode during which the system is technically up and you have access. Most users are logged on to the system and load peaks are expected.

Non-Peak Business Hours

Work mode during which the system is technically up and you have access. Less users are logged on to the system, and load peaks are not expected.

Non-Business Hours

Work mode during which the system is technically up and you have access. Most users are not logged on to the system and load peaks are not expected

Note Note

For information about how to display what workload occurred in which system and when, to allow you to correctly set and adjust the business work modes, see Analyzing Work Modes.

End of the note.

Prerequisites

You have generated a report using the transaction SE38, if you are migrating from Downtime Management to Work Mode Management (SAP Solution Manager 7.1 SP01 or SP02).

For SAP Solution Manager 7.1 SP03 and above the migration is done automatically. For more information on migrating from Downtime Management to Work Mode Management, see SAP Note 1517275Information published on SAP site.

Procedure

  1. Plan the work mode for component using one of the following methods:

    • If you want to reduce the effort required, copy an active or inactive work mode planned for another component.

      For more information, see Reusing Work Modes (Optional).

    • If the work mode planned for another component does not match with your requirement, plan a new work mode.

      For more information, see Planning a Work Mode.

    • If you want to maintain reusable information for creating work modes, create templates.

      For more information, see Managing Templates.

    Note Note

    The threshold for alerts from the Technical Monitoring infrastructure depends on the work mode for technical components.

    End of the note.

    Note Note

    You cannot plan overlapping work modes. Plan your work mode and ensure that downtime does not:

    • Occur during critical and peak business hours of system availability

    • Have any impact on the Service Level Agreement (SLA), and avoids any penalty

    End of the note.
  2. If you have defined a work mode of type planned downtime, perform the following substeps:

    1. If you have planned a downtime for the first time on the system, maintain notification settings for the system.

      Notification settings of a system are the default notification settings for any technical work mode scheduled for the system. For more information, see Setting Notification for Systems.

    2. Notify the users about the work mode.

      You maintain notification settings for a work mode if you want to override the default system settings. For more information, see Managing Notification of Work Modes.

    3. If you are not using the Technical Monitoring infrastructure, set the level of monitoring to be performed by the monitoring infrastructure.

      Technical Monitoring infrastructure pauses the alerts due to planned work modes. For more information, see Defining the Level of Monitoring.

    4. Perform the planned work mode.

      For more information, see Performing a Downtime.

    Note Note

    Key events, such as creation and modification of work modes, modification of notification data (e-mail address, SMS number), and performance of downtimes, are logged in the Business Application Log (SLG1 transaction, object = SOLAR, sub-object = DTM).

    End of the note.

More Information

For more information on migrating from Downtime Management to Work Mode Management, see SAP Note 1517275Information published on SAP site.