Add background
...
The process definition is the core and the first step of the start/stop process. It is where the instruction that the automation will follow will be coded. Several process definitions make up a workflow.
...
Form Templates
The form template is where you instruct which variables, fields, or data will serve as input parameters for the start/stop wizard.
...
Execution Configs
Execution configs are a list of variables that you pre-configure to use in the future, for example, if you’re going to schedule a process to run in the future. Ad-hoc execution configs won’t appear on this list.
Wizard
The wizard in IT-Conductor is a combination of the form template and the process definition. It’s where the user will launch the start/stop workflow.
...
Dashboards
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
...
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.
...
While When you’re creating the start-stop workflow, you must take note of the following:
The external variables that are going to be serve as input in the form
The steps that are going to be in the workflow
The workflow’s sequence
...
Each step in the workflow represents a process definition. 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 must have assigned on its accounts an OS user that can run sudo commands (for Linux) and SQL commands (for Windows)
...
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 name variable will be used later in the form template
...
Command: This is the core and main instruction of the process definition. You can use both Linux and SQL commands for start/stop processes. sapcontrol? However, it is important that you manually test the command to make sure it works before testing it on the process definition in IT-Conductor. In this case, the name of the database is ORACLE_SID. This name will be used later in the form template.
...
Adding verifications to the workflows
You can also create a verification process definition.
...
In this example, this verification asks for the status of the SAP system. To specify this process definition, you need to add the following:
...
Name: Name of process definition
Owner: Robot user owner of the process definition, as specified before
Left object: Insert the name of the object that’s being verified. In this case, the name of the variable is APPSAP. This name variable will be used later in the form template.
Criteria: The criteria that is being asked from the object in the “Left object” field
In the example, the criteria is asking if the object’s status id is different than 40. If the criteria is true, then it’ll move on 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 the system’s class. In this example, it’s asking if the object’s class is from an ABAP system.
what other types of criteria to include?
...
In case, it’s an ABAP system, you can create process definitions for running jobs/programs. This job is launched via the interface with ABAP.
...
*the command to stop/start java is the same for abap from a subcontrol standpoint and database standpoint
Form Templates
To create the form templates you need to have identified the fields, variables, or data that will serve as input parameters for the start/stop wizard.
...
Otherwise, you can duplicate the one with the closest parameters. You can see which variable, app, class, or object the form is calling on the “Property” column. To edit the template, you can select a row and click on “Modify row.”
...
Execution Configs
...
Wizard
The wizard in IT-Conductor is a combination of the form template and the process definition. It’s where the user will launch the start/stop workflow.
...
Same as with process definitions and form templates, you may copy an existing wizard and modify the “Input parameters” and “Create process” steps, and change the name, description, process definition, and form template.
...
Dashboards
You may design a dashboard for start/stop automation like the one for OZsoft and add them to the tenant’s main menu if necessary.
...
The Start/Stop automation dashboard for OZsoft has a tile for the Start/Stop Wizards that you can modify by entering the Design Mode (to enter design mode you need to use your admin IT-Conductor account, not impersonate the tenant’s admin), or by going to the dashboard tiles button and selecting the Wizard
...
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. how to create a saved search?
...