This document explains the elements for creating a start/stop automation at a high level.
...
When creating new start/stop automation procedures, always test on OZSoft tenant first.
Ensure that the prerequisites for Start/Stop automation have been met. This includes the creation of an OS user, granting necessary permissions, configuring web methods, etc. Also, confirm that the user is capable of initiating Start/Stop procedures for both the SAP system and the database at the OS level.
Elements of Start/Stop
Impersonating as OZSoft admin, navigate to Management → Automation → Definition and expand the menus
...
You may design a dashboard for start/stop automation like the one for OZSoft where the users can see all the elements related to performing a start/stop process, as well as monitoring the execution workflow, checking activity logs, and observing the system status such as Availability when they are stopped/started. Each system object can also be drilled into or zoomed in to visualize the full application stack’s status.
...
Configuring the Start/stop Process
...
Create process definitions and assemble the workflow
Impersonate as OZSoft admin
Navigate to Management → Automation → Definitions → OZSoft menu → All Process Definitions
...
Create a new process definition by clicking on “+” or make a copy of an existing process definition and modify it.
...
When you’re creating the start-stop workflow, you must take note of the following:
The external variables that are going to serve as input
The steps that are going to be in the workflow
The workflow’s sequence, which has been tested manually at each unit/activity, to ensure the logic works
...
Each step in the workflow represents a process definitionan activity. Inside a process definition, you can modify the following fields.
...
Name: Name of step
Owner: All process definitions in a workflow must have a robot user as owner, otherwise the process won’t run. This robot user (aka, technical user) must have assigned on its accounts an application user with required roles/privileges to perform the automation action. For example, on Linux the robot user’s assigned application account must be defined on the managed Linux system with appropriate group/s and can run sudo commands planned to be used in the automation action/s.
...
Work queue: This is where the activity is going to run. For start/stop, make sure to use a dynamic work queue. In this example, it’s running on Linux, so it’s specified in the name DBLINUX. This variable will be used later in the form template
...
In this example, this verification asks for the status of the SAP system. To specify define this process definitionactivity, you need to add the following:
...
In the example, the criteria is asking if the object’s status id is NOT equal to 40 (which means it’s not ‘In Progress’ and thus is not currently running. If the criteria is true, then it’ll move on to the step to the right. If it’s false, it’ll do the final step and end the workflow.
In other types of criteria, you can about check the system’s class. In this example, it’s asking if the object’s class is from an ABAP system.
...
Adding jobs to the workflow
...
The main requirements for this step are:
...
Name: Name of step
Work queue: The object has to be specified on the “Work queue” field
Program name: In this example, it’s BTCTRNS2 to release jobs after the system starts up, since they were suspended when stopped in prior automation during shutdown.
Owner and User name: The user name’s account has to be specified under the owner (the automation user)
Job name: It’ll be assigned by default after creating the job step
...
Add elements by clicking on the “+” to the right, or to edit the template, select a row and click on “Modify row.”
...
Creating the Wizard
The creation of the wizard is divided into three steps:
...
Create process: In this step, on the “Wizard_Element.Definition” option, you’ll select the previously created process definition
...
View process: It’ll show you a final view of what the workflow looks like before you save the wizard
...
How to select the items that the Wizard tile will display?
...
The wizard tile contains the following options:
Dashboard: Select the dashboard that it’ll belong to
Title: Name of the tiletitle
Parameters: Insert the id of the tenant that this tile/dashboard will be associated to
...
Menu item: Here you insert the pre-created wizard items that the tile will display. The items are inserted inside a saved search which has the object ids of the pre-created wizards. In the saved search, in “Display mode” you may also select how the wizard items will be displayed on the dashboard.
...