Start/Stop Automation
Last updated
Last updated
IT-Conductor enables users to automate the Start/Stop process of SAP and non-SAP systems . It can be applied to a single system or multiple systems and can be manually executed or scheduled. The feature is highly adaptable to any customer environment and can be a crucial component of IT maintenance operations.
For instance, a single process definition can be created to initiate the Start/Stop activity of all the SAP and non-SAP systems at a specific time.
To use this feature, users need to add their systems to IT-Conductor for monitoring.
Once the system is added, depending on the system and requirements from the customer, process definitions will be created. An IT-Conductor robot account should be created and associated to the application/DB/OS users with assigned role/privilege to execute the local action on the system to be stopped/started. This IT-Conductor robot account should own the Process definition.
For example, the following process is for an SAP System with a HANA Database running on AWS.
When running the process definition, the user can determine if the process will be run immediately or if it will be scheduled to run at a later time:
Once the process is instantiated, the first step of the process starts the VM where the system is running.
Note: For this automation, an object for work queue must have been previously created in order to link IT-Conductor to the AWS Account. This object, will allow us to start or stop the VM as part of the process definition.
This object will allow us to start or stop the VM as part of the process definition.
The start process contains the work queue that will link to the AWS Account and select the VM to start it.
The following step on the process will start the HANA Instance running on the VM. This process will execute am SSH Command on the VM via the SAP Hostagent. In the scenario below, there is only ONE tenant in a multi-tenant HANA system, thus a single start of the HANA system will start the tenant. IT-Conductor also supports start/stop operations for a specific tenant in a multi-tenant system with support for SQL command executed against the HANA SYSTEMDB database to control an individual tenant.
Once the HANA System is running, the process will execute the last step, to start the SAP System via SSH Command
With this step, the process definition will be completed and all the steps will change color from blue to green.
After this step, the logs will be available for review.
Once the process has ended, all system components are discoverable again in IT-Conductor
To stop the system, we need to have previously created process definition to STOP operations.
Once the process definition to STOP System is instantiated, the workflow will start.
The first step will stop the SAP System using SSH Commands:
Once the SAP System has stopped, the next step in the process will stop the HANA System. Similar to the Start of HANA step, IT-Conductor can also support stopping of a specific tenant via SQL command executed on the HANA SYSTEMDB database.
The last step is to stop the running VM
Once all the steps have run successfully, the process definition will change color from blue to green.
A customized dashboard can be deployed for the tenant for the start/stop operations of the VMs running on the AWS Account.
In conclusion, IT-Conductor’s Start/Stop Automation feature provides a comprehensive solution for remote automation of SAP and non-SAP systems on a large scale. With its high level of customization, selective execution, and conditional options, it is an essential tool for IT maintenance operations. By allowing users to manage multiple systems and components remotely, it streamlines and simplifies IT processes, making it an ideal choice for any organization looking to enhance their IT operations.
This activity can be integrated into the IT process automation for system lifecycle tasks like OS patching and SAP kernel patching.
