Add background
This document explains the elements for creating a start/stop automation at a high level.
Example: OZSoft tenant.
When creating new start/stop automation procedures, always test on OZsoft tenant first.
Elements of Start/Stop
Impersonating as OZSoft admin, navigate to Management → Automation → Definition and expand the menus
Process Definitions
The process definition is the core and the first step of the start/stop process.
While you’re creating the start-stop workflow, you must take note of the following:
The external variables that are going to be 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 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 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. 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.
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 will be used later in the form template.
Criteria: The criteria that the verification is following. In the example, the criteria is asking if the object’s status 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 end the workflow. Other types of criteria include asking if the system is an ABAP system.
You can also create process definitions for running jobs/programs.
*it doesn't matter if the sap or the database are in different hosts*en el workflow del ejemplo (start) esta haciendo un paso adicional que es el de verificar si el sistema NO esta disponible (check SAP status), si el status es diferente != 40, entonces sigue con el proceso de start y termina el flujo.*status list: https://gui.itconductor.com/statusList?
*Si el status es = 40, hace la validacion de start oracle db, start sap y pregunta si el sistema es abap.*how does the workflow know that it's an abap system? (la otra opcion es que sea java)the app (in the "left object" field) has a class. los abap classes tienen JCO2 / JCO3 en el nombre*si el sistema SI es abap, se crea un job step para correr un sap job. this job is launched via the interface to abap.
main requirements of this job
la app tiene que estar especificada en el work queue
especificar el program name
especificar el user name (el user name debe estar ingresado tmb en las sistem accounts)
job name se pone por default cuando se crea este job step
luego termina el workflow
*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.
Chances are that there already exists a form template with the necessary inputs, in that case, you may reuse it instead of creating a new one.
Otherwise, you can duplicate the one with the closest parameters. You can see which variable, app, or class the form is calling on the “Property” column. To edit the template, you can select a row and click on “Modify row.”
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.
The creation of the wizard is divided into three steps:
Input parameters: Here, the user will enter the parameters needed to run the workflow. These parameters are specified in the selected form template.
This step also includes entering the name and description of the wizard, the owner (usually the admin user of that tenant), the target class (choose execution config), and the form template
Create process: In this step, on the “Wizard_Element.Definition” option, you 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
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).
You can add a Wizard tile to display a few pre-created wizards upfront.
The wizard tile contains the following options:
Dashboard: Select the dashboard that it’ll belong to
Title: Name of the tile
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?
Row: Select the row where the tile will be placed
Column: Select the column where the tile will be placed
Parameters: Insert the id of the tenant that this tile/dashboard will be associated to
0 Comments