Example: Automating startup and shutdown of SAP systems
A typical productive SAP system consists of multiple Amazon EC2 instances that host several critical SAP components, such as SAP database servers, SAP application servers, SAP Central Services and SAP enqueue replication services. SAP customers also integrate their core SAP systems with other mission-critical solutions, such as archiving engines, tax management solutions, content servers, and job management systems. The startup and shutdown procedure for such a complex and tightly integrated SAP solution requires following a specific sequence of tasks.
You can automate startup and shutdown of SAP systems by using AWS services. This
consistent and controlled process requires significantly less human intervention because it
automates the monotonous, repetitive tasks and follows the sequence designed by SAP
administrators. You can optionally add scheduling, notification, and alerts by using AWS
services built for the cloud. In addition, this automation is capable of defining and handling
dependencies between multiple SAP and non-SAP applications. For more information, see the blog
post Automate Start or Stop of Distributed SAP HANA systems using AWS Systems Manager
-
Significantly reduces costs by reducing the need for manual operational efforts
-
Reduces the risk of human error and the need for expensive corrective activities
The following image and process describe how you can automate startup and shutdown of SAP systems:
-
A time-based event causes an Amazon EventBridge rule to start a Systems Manager document. For more information, see Systems Manager documents.
-
Systems Manager connects to the target EC2 instances and stops or starts the SAP application and its associated instances.
-
After the SAP system has stopped or started, another EventBridge rule responds to the change in the EC2 instance state and uses a Lambda function handler to notify the stakeholders of the change.
