downtime management with task management - sap · pdf filewith task management ... process...
TRANSCRIPT
Downtime Manager
with Task ManagementIntroduction and Key Operations
Sapna Subramaniam
SAP NetWeaver Product Management
© SAP 2008 / Page 2
1. Downtime Manager – Key Facts
2. Downtime Manager & Task Management - Operation Methodology
3. Downtime Planning
4. Notification Management
5. Alert Management
6. Task Management
7. Downtime Execution
8. New Features of Downtime Manager with EhP1 of SAP Solution Manager7.0
9. Task Management for System Administrators
Agenda
© SAP 2008 / Page 3
1. Downtime ManagerKey Facts
Solution Manager Support Package Stack 15 – Feb 2008INITIAL SHIPMENT
Suppression of Spurious CCMS Alerts, Planning & scheduling of Downtimes , Comprehensive User Notifications, Execution of Downtimes
KEY FEATURE &
OPERATIONS
End–to-End Manager for working with Downtimes resulting in better planning, optimized
usage of systems and better tracking
Valid for Systems, Instances (Double stack, Java, ABAP, Central Instance ) ,
Databases.OPERABILITY
From “System Landscape Management” Work Centre of Solution Manger 7.0 or
through the transaction – “SOLMAN_DOWNTIME_MGMT”ACCESSIBILITY
For business & technical outage situations like necessary patch upgrades, DB
maintenance, hardware maintenance, OS maintenance, configuration/customization
changes, migration (throughout a certain period of time)
THE NEED FOR
DOWNTIMES
© SAP 2008 / Page 4
Alert
ManagementPlan the level of suppression
of CCMS alerts
Downtime
PlanningPlan a Downtime in the System
Landscape Management Work
Center with the system,
recurrence, date and time
details
Task
ManagementCreate & set a task –assigning it
a processor , assigning its
completion criteria to
delegate/process the execution
of a released Downtime
ExecutionExecute the Downtime using
SAPControl or ACC, based on
the task properties that
appears in the Task Inbox, in
the System Admin Work Center
Notification
ManagementPlan varied forms of
notifications to all users at
various time instances
2. Downtime Manager & Task ManagementOperation Methodology
Kindly follow the numbers in
the screen shots for the
process flow
2) Red boxes and fonts
indicates mandatory fields
3) Blue boxes and fields
indicate optional fields
© SAP 2008 / Page 5
3. Downtime PlanningKey Steps
Planning a Single Downtime
Planning a Recurring Downtime
� Supported options – Monthly and Weekly Pattern
Editing a Downtime
� Changing time and other properties of a Downtime
Deleting a Downtime
� Deleting - A single Downtime , single constituent Downtime
from a recurrence pattern, complete recurrence pattern
Planning a Uptime
� Supported options – Creation and Deletion of Single and
Recurrence Uptimes
§§§§ System Administrators can
select one or more systems or their
instances based on business
requirement and plan a Downtime
§§§§ A single Downtime serves a one
time Downtime occurrence , while
a Recurring Downtime serves a
repeated pattern of Downtime
occurrence
§§§§ Business Users can configure
Downtime Manager, to ensure ,
availability of system during critical
business hours through creation of
Uptimes
§§§§ Downtimes can remain in “Draft”
or “ Review” stage for multiple
revisions , until all stakeholders
give their consent for it to be
“ Released ”
© SAP 2008 / Page 6
3. Downtime PlanningPlanning a Single Downtime
Planning a Single Downtime §§§§ System Administrators can
select one or more systems or their
instances based on business
requirement and plan a Downtime
§§§§ A single Downtime serves a one
time Downtime occurrence , while
a Recurring Downtime serves a
repeated pattern of Downtime
occurrence
§§§§ Business Users can configure
Downtime Manager, to ensure ,
availability of system during critical
business hours through creation of
Uptimes
§§§§ Downtimes can remain in “Draft”
or “ Review” stage for multiple
revisions , until all stakeholders
give their consent for it to be
“ Released ”
© SAP 2008 / Page 7
3. Downtime PlanningPlanning a single Downtime
1. Choose SLM Work
Center
2.Choose Downtime Management
3. Choose the system
from the list
4. Choose a
Single Planned
Downtime
© SAP 2008 / Page 8
3. Downtime PlanningPlanning a single Downtime
1.Choose the status as “ Draft ”
2. Enter start/end date &
start/end time, time zone
Enter title and category
Enter purpose of
Downtime & related impact
Upload any supporting/related
documents
© SAP 2008 / Page 9
3. Downtime PlanningPlanning a Recurring Downtime
Planning a Recurring Downtime
� Supported Options – Monthly and Weekly Pattern
§§§§ System Administrators can
select one or more systems or their
instances based on business
requirement and plan a Downtime
§§§§ A single Downtime serves a one
time Downtime occurrence , while
a Recurring Downtime serves a
repeated pattern of Downtime
occurrence
§§§§ Business Users can configure
Downtime Manager, to ensure ,
availability of system during critical
business hours through creation of
Uptimes
§§§§ Downtimes can remain in “Draft”
or “ Review” stage for multiple
revisions , until all stakeholders
give their consent for it to be
“ Released ”
© SAP 2008 / Page 10
3. Downtime PlanningPlanning a Monthly Recurring Downtime
1. Choose SLM Work
Center
2.Choose Downtime
Management
3. Choose the system
from the list
4. Choose the required
recurrence pattern
© SAP 2008 / Page 11
3. Downtime PlanningPlanning a Monthly Recurring Downtime
1. Choose the status
2. Enter Start/End period of the recurrence
3. Choose the monthly frequency4. Choose Time zone
5. Choose the Weekly
frequency
6. Choose day of the week 7. Choose Downtime start time
8. Choose Downtime end time
9. Choose “Save” to view the Downtime
Sequence Recurrence Pattern
© SAP 2008 / Page 12
3. Downtime PlanningEditing a Downtime
Editing a Downtime
� Changing time and other properties of a Downtime
§§§§ System Administrators can
select one or more systems or their
instances based on business
requirement and plan a Downtime
§§§§ A single Downtime serves a one
time Downtime occurrence , while
a Recurring Downtime serves a
repeated pattern of Downtime
occurrence
§§§§ Business Users can configure
Downtime Manager, to ensure ,
availability of system during critical
business hours through creation of
Uptimes
§§§§ Downtimes can remain in “Draft”
or “ Review” stage for multiple
revisions , until all stakeholders
give their consent for it to be
“ Released ”
© SAP 2008 / Page 13
3. Downtime PlanningEditing a Downtime
1.Choose SLM
Work Center
2. Choose the System
3. Choose the single /
constituent Downtime
4. Start/End Dates,
Times, Status can be
changed
The data in these fields
can be optionally
changed
© SAP 2008 / Page 14
3. Downtime PlanningDeleting a Downtime
Deleting a Downtime
� Deleting - A single Downtime , single constituent Downtime
from a recurrence pattern, complete recurrence pattern
§§§§ System Administrators can
select one or more systems or their
instances based on business
requirement and plan a Downtime
§§§§ A single Downtime serves a one
time Downtime occurrence , while
a Recurring Downtime serves a
repeated pattern of Downtime
occurrence
§§§§ Business Users can configure
Downtime Manager, to ensure ,
availability of system during critical
business hours through creation of
Uptimes
§§§§ Downtimes can remain in “Draft”
or “ Review” stage for multiple
revisions , until all stakeholders
give their consent for it to be
“ Released ”
© SAP 2008 / Page 15
3. Downtime PlanningDeleting a Single Downtime
1. Choose SLM Work
Center
2.Choose Downtime Management
3. Choose the
system from the
list
4. Choose a
Single Downtime
5. Choose “Delete”
© SAP 2008 / Page 16
3. Downtime PlanningDeleting a constituent Downtime
1. Choose SLM Work Center
3. Choose the system
from the list
4. Choose a
constituent from a
family of Downtime
5. Choose “Delete”
2.Choose Downtime
Management
© SAP 2008 / Page 17
3. Downtime PlanningDeleting a family of Downtimes
1. Choose the system
from the list
2. Choose the
parent Downtime
3. Choose “Delete”
© SAP 2008 / Page 18
3. Downtime PlanningPlanning a Uptime
Planning a Uptime
� Supported options – Creation and Deletion of Single and
Recurrence Uptimes
§§§§ System Administrators can
select one or more systems or their
instances based on business
requirement and plan a Downtime
§§§§ A single Downtime serves a one
time Downtime occurrence , while
a Recurring Downtime serves a
repeated pattern of Downtime
occurrence
§§§§ Business Users can configure
Downtime Manager, to ensure ,
availability of system during critical
business hours through creation of
Uptimes
§§§§ Downtimes can remain in “Draft”
or “ Review” stage for multiple
revisions , until all stakeholders
give their consent for it to be
“ Released ”
© SAP 2008 / Page 19
3. Downtime PlanningPlanning a Single Uptime
1. Choose SLM
Work Center
2.Choose Downtime Management
3. Choose the
system from the list
© SAP 2008 / Page 20
1. Enter status, Start/End
time , Start /End Date of
the Uptime , Time Zone
These fields
can be filled
optionally
3. Downtime Planning
Planning a Single Uptime
© SAP 2008 / Page 21
4. Notification Management
Key Steps
Sending Instant Notifications to active System Users
§§§§ System Administrators can
decide to notify System Users
and Business Owners about a
Downtime well in advance and
also just prior to the Downtime
– so that all active tasks can
be completed/stopped.
§§§§ Administrators can choose
to send E-Mail, SMS, Instant
system Notifications
§§§§ SAPConnect is the default
connection gateway for Email
§§§§ Business partners recorded
in the Solution Manager can
be listed as recipients for
notifications as well
Choosing Recipients
� Adding System Level Recipients, Internal recipients, External
recipients
Choosing Notification Schedule
� Viewing and Editing Default Schedule for all Recipients ,
Selective Editing of Default Pattern for selected Recipients
Choosing Mode of Notification
� Viewing and Editing Text Templates for Email and SMS
© SAP 2008 / Page 22
4. Notification Management
Choosing Recipients
§§§§ System Administrators can
decide to notify System Users
and Business Owners about a
Downtime well in advance and
also just prior to the Downtime
– so that all active tasks can
be completed/stopped.
§§§§ Administrators can choose
to send E-Mail, SMS, Instant
system Notifications
§§§§ SAPConnect is the default
connection gateway for Email
§§§§ Business partners recorded
in the Solution Manager can
be listed as recipients for
notifications as well
Choosing Recipients
� Adding System Level Recipients, Internal recipients, External
recipients
© SAP 2008 / Page 23
4. Notification Management
Choosing Recipients at System Level
1.Choose SLM
Work Center
3. Choose the System
2. Choose “Downtime Management”
4. Choose “ Notification Settings”
© SAP 2008 / Page 24
4. Notification Management
Choosing Recipients at System Level
1. Choose recipients from Systems Users/ Business Partners
2. Record External Recipients
© SAP 2008 / Page 25
4. Notification Management
Choosing Recipients at Downtime level
1. Choose the system
from the list
2. Choose a Single Downtime
© SAP 2008 / Page 26
1. Choose “Notification” Tab
2.Add/choose
the default
recipients from
the recipient list
defined at System
Level
4. Enter details of new
external recipients3.Add internal recipients,
that are exclusive of the
System Level Recipients
4. Notification Management
Choosing Recipients at Downtime level
© SAP 2008 / Page 27
4. Notification Management
Choosing Notification Schedule/Pattern
§§§§ System Administrators can
decide to notify System Users
and Business Owners about a
Downtime well in advance and
also just prior to the Downtime
– so that all active tasks can
be completed/stopped.
§§§§ Administrators can choose
to send E-Mail, SMS, Instant
system Notifications
§§§§ SAPConnect is the default
connection gateway for Email
§§§§ Business partners recorded
in the Solution Manager can
be listed as recipients for
notifications as well
Choosing Notification Schedule
� Viewing and Editing Default Schedule for all Recipients ,
Selective Editing of Default Pattern for selected Recipients
© SAP 2008 / Page 28
4. Notification Management
Choosing Notification Schedule/Pattern
1.Choose SLM Work
Center
3. Choose the System
2. Choose “Downtime Management”
4. Choose “ Notification Settings”
© SAP 2008 / Page 29
1.Choose “Edit Default Schedule” tab
at the System Level Notification
screen
2. Note the tab for Default Schedule here
3. You can choose to add /delete row
for Emails (or) SMS Notification
4. You can
choose the
days
preceding
the
Downtime
day for
Downtime
notification5 You can
choose time of
delivery of the
notification
4. Notification ManagementChoosing Notification Default Schedule/Pattern for all
recipients
© SAP 2008 / Page 30
2 .Choose “Edit Schedule” tab at the
System Level Notification screen
1. Choose the specific recipient for whom, notification
changes have to be made
3. You can choose to add /delete
row for Emails (or) SMS
Notification
4. You can
choose the days
preceding the
Downtime day
for Downtime
notification
5 You can
choose time of
delivery of the
notification
View the notification schedule for the specific recipient here
4. Notification ManagementChoosing Notification Schedule/Pattern for selective
recipients
© SAP 2008 / Page 31
4. Notification Management
Choosing Mode of Notification
§§§§ System Administrators can
decide to notify System Users
and Business Owners about a
Downtime well in advance and
also just prior to the Downtime
– so that all active tasks can
be completed/stopped.
§§§§ Administrators can choose
to send E-Mail, SMS, Instant
system Notifications
§§§§ SAPConnect is the default
connection gateway for Email
§§§§ Business partners recorded
in the Solution Manager can
be listed as recipients for
notifications as well
Choosing Mode of Notification
� Viewing and Editing Text Templates for Email and SMS
© SAP 2008 / Page 32
4. Notification Management
Choosing Email Mode of Notification
1. Choose the System Level Notification for the required system to arrive on this screen
2. Choose your preferred mode of notification and
select the corresponding option to edit the notification
content template
© SAP 2008 / Page 33
4. Notification Management
Choosing Email Mode of Notification
3. By Default , the keyword
drawn from the standard text
element table will be available
as a message here , however
the user can completely edit
and send a message of his/her
choice
4. You can preview your message
here using the “Preview” tab
Standard text elements used as email/SMS content are seen in this table
© SAP 2008 / Page 34
4. Notification Management
Sending Instant Notifications
Sending Instant Notifications to active System Users
§§§§ System Administrators can
decide to notify System Users
and Business Owners about a
Downtime well in advance and
also just prior to the Downtime
– so that all active tasks can
be completed/stopped.
§§§§ Administrators can choose
to send E-Mail, SMS, Instant
system Notifications
§§§§ SAPConnect is the default
connection gateway for Email
§§§§ Business partners recorded
in the Solution Manager can
be listed as recipients for
notifications as well
© SAP 2008 / Page 35
1. Enter the properties screen of the Downtime , you wish to notify about
2. Choose the “Notification” Tab
3. After deciding the “
Notification Schedule” , and only
after setting the Downtime to
“Released”, the “Release
Schedule Notification” option is
enabled . This tab must be
chosen , to send out any planned
notifications , else users remain
un-notified about the Downtime ,
irrespective of its completion
4. At any point you
can choose to send
instant notifications
to all listed recipient
or just active
system Users
4. Notification Management
Releasing Scheduled and Instant Notifications
© SAP 2008 / Page 36
5. Alert Management
Key Steps
Any option any be availed for any Downtime
System Administrators
can decide what level of CCMS
Alert Suppression they would
prefer to see in their Alert Inbox
Options provided :
§§§§ Full Monitoring :
Enables complete monitoring
without suppression of any
form
§§§§ Monitoring Pause
Enables total pause on all
forms of monitoring , for the
duration of the Downtime
§§§§ Suppress Alerts
Enables suppression of all
alerts throughout the duration
of the Downtime
© SAP 2008 / Page 37
5. Alert Management
Choosing the Alert Suppression Option
1. Choose “Alerting
Properties” tab on
the Downtime
2. Choose your preferred
monitoring status
© SAP 2008 / Page 38
6. Task Management
Key steps
§§§§ For managing Downtimes,
System Administrators can
create tasks from the DTM
application
§§§§Tasks appear in the Task Inbox
of the processor (s)
§§§§ The Execution tab specifies on
the mode of execution of the
Downtime
a) Shutdown/Restart using SAP
Control taking care of
instantaneous execution
b) Shutdown/Restart managed
systems, that are controlled by
ACC. This option takes care of
intra-system dependencies
Choosing Mode of Execution
� Supported options : Through SAPControl and through ACC
Task Creation from Downtime Manager
� Setting Task properties
Task Completion Criteria
� Adding information on the Task Processor and completion
criteria
© SAP 2008 / Page 39
6. Task Management
Choosing Mode of Execution
§§§§Tasks are self created reminders
reminding the User of a
impending task
§§§§ For managing Downtimes,
System Administrators are
provided with the option of
creating a reminder from the
DTM application itself. This
feature is invoked from the
Execution tab of the DTM
application
§§§§ The Execution tab specifies on
the mode of execution of the
Downtime
a) Shutdown/Restart using SAP
Control taking care of
instantaneous execution
b) Shutdown/Restart managed
systems, that are controlled by
ACC. This option takes care of
intra-system dependencies
Choosing Mode of Execution
� Supported variations : Through SAPControl and through ACC
© SAP 2008 / Page 40
6. Task Management
Choosing Modes of Execution
What is ACC execution ?The Adaptive Computing concept
starts/stops Application Services at
the instance level. An Application
Service is the smallest currently
installable unit of an SAP system. This
can be the central instance, the dialog
instance, and the database. Execution
through ACC, takes care of intra –system dependencies
What is SAPControl ? The SAP Start Service (sapstartsrv)
provides basic management services
for systems and instances and single
server processes. Services include
starting and stopping, monitoring the
current run-time state, reading logs,
traces and configuration files,
executing commands and retrieving
other technology-specific information,
like network access points, active
sessions, thread list etc. They are
exposed by a SOAP Web service
interface named “SAPControl”.
1. Choose “Execution” tab
2. Choose mode of execution
© SAP 2008 / Page 41
6. Task Management
Task Creation from Downtime Manager
§§§§Tasks are self created reminders
reminding the User of a
impending task
§§§§ For managing Downtimes,
System Administrators are
provided with the option of
creating a reminder from the
DTM application itself. This
feature is invoked from the
Execution tab of the DTM
application
§§§§ The Execution tab specifies on
the mode of execution of the
Downtime
a) Shutdown/Restart using SAP
Control taking care of
instantaneous execution
b) Shutdown/Restart managed
systems, that are controlled by
ACC. This option takes care of
intra-system dependencies
Task Creation from Downtime Manager
� Setting Task properties
© SAP 2008 / Page 42
6. Task Management
Task Creation from Downtime Manager
1. Create a Shutdown/Restart Task from the
Execution Tab of Downtime Manager
© SAP 2008 / Page 43
6. Task Management
Task Creation from Downtime Manager
2. Choose the Task
due Dates and Task
Times, time zone
© SAP 2008 / Page 44
6. Task Management
Task Creation from Downtime Manager
3. Enter Description about the
Task in this area and Save
© SAP 2008 / Page 45
6. Task Management
Task Creation from Downtime Manager
4. Enter the highlighted
details and choose
“Save “
© SAP 2008 / Page 46
6. Task Management
Task Completion Criteria
§§§§Tasks are self created reminders
reminding the User of a
impending task
§§§§ For managing Downtimes,
System Administrators are
provided with the option of
creating a reminder from the
DTM application itself. This
feature is invoked from the
Execution tab of the DTM
application
§§§§ The Execution tab specifies on
the mode of execution of the
Downtime
a) Shutdown/Restart using SAP
Control taking care of
instantaneous execution
b) Shutdown/Restart managed
systems, that are controlled by
ACC. This option takes care of
intra-system dependencies
Task Completion Criteria
� Adding information on the Task Processor and completion
criteria
© SAP 2008 / Page 47
6. Task Management
Task Completion Criteria
1. Choose the “Execution” tab
2. Enter task completion criteria
for the processor of the task, to
verify the completion of the task
3. Choose the Processor of the Task
from Business Partners/ System Users
© SAP 2008 / Page 48
7. Downtime Execution
Key Steps
Checking your Task Inbox for pending Downtime related
Tasks
Executing the Downtime task through the Downtime
Manager application based on the Task Properties
§§§§ System Administrators can
visit their Task Inbox, in the
Task Management tab of the
System Monitoring Work
Center to view all their
Downtime Management
related tasks
§§§§ Based on the task
execution and completion
criteria , the System
Administrator can execute the
task by once again logging
into the DTM application or
direct the processor of the
task to do so.
Viewing the Task execution details
© SAP 2008 / Page 49
7. Downtime ExecutionChecking your Task inbox
Checking your Task Inbox for pending Downtime
related Tasks
§§§§ System Administrators can
visit their Task Inbox, in the
Task Management tab of the
System Monitoring Work
Center to view all their
Downtime Management
related tasks
§§§§ Based on the task
execution and completion
criteria , the System
Administrator can execute the
task by once again logging
into the DTM application or
direct the processor of the
task to do so.
© SAP 2008 / Page 50
7. Downtime Execution
Checking your Task inbox
1.Choose System
Admin Work Center
2. Choose “Task Management” tab
3. Choose
“Downtime
Management”
category of Tasks
4. Choose the Task that’s
nearing execution
© SAP 2008 / Page 51
7. Downtime ExecutionViewing Task Execution Details
§§§§ System Administrators can
visit their Task Inbox, in the
Task Management tab of the
System Monitoring Work
Center to view all their
Downtime Management
related tasks
§§§§ Based on the task
execution and completion
criteria , the System
Administrator can execute the
task by once again logging
into the DTM application or
direct the processor of the
task to do so.
Viewing the Task execution details
© SAP 2008 / Page 52
7. Downtime ExecutionViewing Task Execution Details
The processor can view Task
completion criteria here
The Processor of the task can
be identified here
1. Go to the “Execution” tab of the Task Properties
© SAP 2008 / Page 53
7. Downtime Execution
Executing the Downtime
§§§§ System Administrators can
visit their Task Inbox, in the
Task Management tab of the
System Monitoring Work
Center to view all their
Downtime Management
related tasks
§§§§ Based on the task
execution and completion
criteria , the System
Administrator can execute the
task by once again logging
into the DTM application or
direct the processor of the
task to do so. Executing the Downtime task through the Downtime
Manager application based on the Task Properties
© SAP 2008 / Page 54
7.Downtime Execution
Executing the Downtime
1. Choose the “Execution” tab from the
Downtime Management application
2. Choose the mode of execution
© SAP 2008 / Page 55
7.Downtime Execution
Executing the Downtime
Enter the Wait Time Out & Soft
Time Out in seconds
© SAP 2008 / Page 56
7.Downtime Execution
Executing the Downtime
1. Choose Continue 2. Choose “Yes” to
Shutdown the system
© SAP 2008 / Page 57
8. Downtime Manager – New Features for EhP1
for SolMan 7.0
Planning Downtimes
� Text Calendar display of Downtimes
� Exclusivity of Uptimes and Downtimes
� Scheduled status vs Actual status of component available
� Introduction of Downtime Mass Copy functionality
� Introduction of Factory and Holiday Calendar
� Logon Groups introduced
� Uploading facility for supporting documents
Notification Management
� UI Optimization
� Business Partners recorded in Solution Manager, now
available for notification purposes
� User friendly Instant Notification Pop–ups
Alert Management� New Available alerting options - Monitoring Pause, Suppress Alerts
� A Calendar is included in the Alert Inbox to shows users of current
of future Downtimes
Execution
� Logging facility provided - SLG1
� Tasks are now integrated into DTM – Users can
remind themselves through tasks reminders for system
shutdown/restart
� Execution tab provided to start/stop systems using
(1) SAPControl (2) Adaptive Computing Controller
© SAP 2008 / Page 58
9. Task Management for System Administrators
The “C” s of Task
ManagementTask in SAP Solution Manager
� An Elementary unit of work to be performed by an assigned processor to a specified deadline and completion criteria
Task Management for System Administration :
A consolidated Task Inbox that represents a one-stop shop for tasks created in applications throughout Solution Manager, for example in the areas of:
�CSA – Central System Administration
�Job (Scheduling) Management
�Downtime Management
� Issue and Top Issue Management
� In addition it is possible to create Ad Hoc Tasks directly within the Task Management tool without having to go the detour through another Solution Manager application.
Consolidated view across Solution Manager of, for
example, pending Tasks, overdue Tasks etc
"Contextualization” of each Task making
clear to which key objects in SolMan the Task
refers to from a technical/business point of
view: Solutions, Systems, projects, business
processes, or from a SolMan application point
of view: Issues, Downtimes, Job Scheduling
Objects etc
Collaborative
features allowing them
to be delegated,
processed for approval
& related simple
workflow actions
Incre
asin
g B
usin
ess B
enefits
© SAP 2008 / Page 59
Additional Information
� Please refer to SAP notes the Service Market Place
� Note Numbers :1129052
� Note Number: 1129385
� Please refer to the blog on Downtime Manager on the SAP Developer Network
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9838
� Please refer to the ppt on Downtime Manager Operations on the SAP Developer Network
https://www.sdn.sap.com/irj/sdn/operations?rid=/library/uuid/a00fb19b-7b6b-2b10-e5b0-
bec0eaa49532
© SAP 2008 / Page 60
Thank you!
© SAP 2008 / Page 61
Copyright 2008 SAP AG
All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document
contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,
and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or
other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation
shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these
materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch
SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.
Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die
dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen
von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu
Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen
Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten
Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die
Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder
ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck
sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.
SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung
dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.
Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks
zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über
Internetseiten Dritter ab.
Alle Rechte vorbehalten.