Step 5: Set up HWM (HORIZONT Workflow Manager)
Last updated
ProcMan Admin Guide V6.0.0
Last updated
To verify the installation of ProcMan, go to . The ProcMan UI should appear, but login is not yet possible because no database has been configured.
The next step is to set up HWM (HORIZONT Workflow Manager). To do this, go to
Or, if you are not opening from a remote desktop, something like
The configuration dialog has the following two parts: Basic configuration, Database configuration. Go through the dialog screens, fill the requested data and continue to the next screen by clicking the Continue button.
In this section the Single Sign-on authentication may be selected. Select ‘-‘, if there is none in use. Currently only the IBM Tivoli Access Manager WebSEAL is supported here.
This section of the dialog allows specifying where to write the log files and what message level shall be logged. If the dialog is started for the first time, the path of the log file is preset depending on the settings in the etc/hwi_config.php file. The file name may contain the sequence $D$, which means that every day will be opened a new log file and the sequence is replaced in the real file name by the current date, e.g.
Following Message levels are accepted:
1
Errors, Information
2
Errors, Information, Warnings
3
Errors, Information, Warnings, Traces
This section allows configuring the feature that for long time active activities automatically change their status to pending.
The user login status interval specifies how often the information that a user is logged-in is actualized in ProcMan. The value means count of minutes. The value must be an integer greater or equal 0 (zero). If set to 0 (zero) the updating of the user login-in status as well as the automatic change of activity status from active to pending is switched off.
The activity status interval specifies that after the last update user of an active activity is not logged-in for this time, the status of the activity shall be automatically set to pending.
The value means count of minutes. The value must be an integer greater or equal 0 (zero). If set to 0 (zero) the automatic change of activity status from active to pending is switched off.
Here the SMTP server for sending alarm e-mails can be configured. If the SMTP server supports SSL encryption it can be used by specifying the SMTP server IP/DNS prefixed by ‘ssl://’ (e.g. ssl://smtp.my_company.com) and the port on which the SMTP server accepts the SSL encrypted communication (default is 465).
Put the IP address or DNS of the ProcMan Server in the Client computer for identification at the server field.
On the second page, the DB2 parameters must be set so that ProcMan/HWM can communicate with the DB2 database. The customer normally provides the DB2 database information.
The checkboxes for "Create Database", "Initialize Database", and "Only generate Scripts..." should be set.
Important note:
If you continue now, no DB2 database or tables will be created for this ProcMan installation. This can only be done by the DB2 administrator. If the User provided has no permission to create tables then the checkbox "Only generate scripts..." must be checked. The generated scripts, which contain the sql queries, then have to be given to your database administrator.
Basically HWF supports following Database system types: DB2 (z/OS), Oracle, PostgreSQL. The dialog differs slightly depending on the Database system type selected.
The current ProcMan version and HOS (JCL) supports only DB2 on z/OS,
Special parameters for DB2 are the Alias and the Table Qualifier.
Special parameters for Oracle are Host (IP address or DNS name), Port and Database Name.
Special parameters for PostgreSQL are Host (IP address or DNS name), Port, Database Name and Schema. Other parameters are the same.
Table name and Index name templates are optional and are dedicated for cases, when the Customer has special conventions for table/index names.
For example if the tables shall be named in the range ABCDT00 – ABCDT99 and indexes in the range ABCDI00 – ABCDI99, put in as the Table name template ABCDT__ and as the Index name template ABCDI__. The __ (two underscores) is then replaced by a running number in the generated SQL statements.
In User, Password and Repeat Password put in the information about the technical user which will be used by HWM for the Database access. The information about the technical user will be stored in a configuration file, the password will be encrypted.
Check the Drop database checkbox if you want to replace already existing Database.
Check the Create Database checkbox if:
you want that a new Database (schemas, tables, indexes, etc.) shall be created by the dialog
the Database already exists and you want to drop it and create newly,
you want only to generate the Database definitions in a file. The file can be reviewed and maybe send to z/OS and executed there by e.g. SPUFI or a batch job.
Check the Initialize Database checkbox if:
you want to fill a newly created Database with initial data,
you want to delete all data in the Database and initialize it newly.
Check the Migrate data checkbox if:
you want to migrate data in a newly created migration database,
you want to reinitialize the data in the current database with the data from an existing migration database.
If at least one of the Create Database and Initialize Database checkboxes is checked and the dialog is submitted, the configuration procedure generates a file DBDefinition.sql in the database subdirectory of the ProcMan installation. It contains all SQL statements needed for creation and/or initialization of the database. This file has no influence on the run of HWM.
It may be useful if you do not have database administration rights at the time of HWM configuration. In this case you can send this file to your database administrator to check, adjust and execute the SQL statements in this file.
If none of the Create Database and Initialize Database checkboxes is checked and the dialog is submitted, only the Database access settings are saved.
Check the ‘Only generate scripts checkbox’ if you only want to generate the SQL statements into the file database/DBDefinition.sql described above without creating and/or initializing the database.
If the Drop/Create Database checkbox has been checked a further dialog is being shown after submitting.
The user specified in admin user and password is being used only for the Database creation. The information about the admin user will not be stored anywhere (in opposite to the technical user on the previous screen).
The Database Name, Table Space, Database creation parameters, Tablespace creation parameters, Table creation parameters and Index creation parameters fields are shown only in the DB2 variant of the dialog. Put in meaningful parameters as they will be used for the Database creation. The Table Space name may contain a sequence of two or more underscores to specify that for every table a new table space shall be created. The sequence of underscores is in the generated SQL statements replaced by a running number like in the Table name and Index name templates in the previous dialog screen.
The Database/Tablespace/Table/Index creation parameters may contain any parameters accepted by DB2 for the respective database object type. When the dialog is running for the first time they are initialized by default values.
In the Users to be admin granted parameter database users which shall be granted to be admins of the database can be specified as a list (one user name in each line).
The Only generate scripts checkbox is the same like on the previous screen.
Because the Configuration dialog is being started via an Internet Browser it could be started later by any user of HWM from any client computer. To allow this could have fatal follow-ups because everyone could change the HWM configuration. Therefore the Configuration dialog has a built in protection. At the end of the first successful run of the dialog, it generates a file hwm_install_blocker.php in the etc subdirectory of the ProcMan installation. This file contains only one option:
If the file exists and the value of the option $hwm_install_blocker in the file is true, every try to start hwm_install.php by any user ends with an error message. If you need to start the Configuration dialog later, you have two possibilities:
delete the etc/hwm_install_blocker.php file
set the value of the option $hwm_install_blocker in the etc/hwm_install_blocker.php file to false
If you delete the etc/hwm_install_blocker.php, you will be allowed to start the Configuration dialog only once. At the end it generates the etc/hwm_install_blocker.php again and disables repeated starts.
If you change the value of the option $hwm_install_blocker in the etc/hwm_install_blocker.php file to false, you will be able to start the Configuration dialog arbitrary times. Do not forget to change the value of the $hwm_install_blocker option back to true at the end of your configuration work. Otherwise the protection is switched off and any user may start the Configuration dialog from any client computer.
With a click on "Continue" the HWM setup is completed.
The file hwm_db_config.php is overwritten after finishing the setup. All other files in case of an existing ProcMan installation are not changed.
Now there should be a DBDefinition.sql file in the installation directory, e.g. in c:/horizont/procman/database/.
This DBDefinition.sql file contains all queries to created the tables needed for the Procman installation. The file should be forwarded to the responsible DB2 administrator. He needs to execute the SQL queries contained in the file to create the tables needed for the ProcMan installation on the DB2 database.
Follow the steps below to run and execute the queries in the DBDefinition.sql file.
Start the db2cmdadmin.exe as admin. A CLI should open.
Type and execute the command db2
Connect to the database.
Execute the command "quit"
Navigate with the command cd to the directory where the DBDefinition.sql file is located.
Execute the file with the following command.
You should see a lot of successful responses that the commands have been executed successfully.
Now the HWM setup is complete. Finally, it is recommended to check the parameters contained in the hwm_db_config.php file in the installation directory (e.g. c:/horizont/procman/etc/hwm_db_config.php) to check if everything is correct (e.g. db_alias, db_name).
Additional information
If the HWM installation has to be performed again, it may be that the call of is prevented. To unlock the page again, simply edit the file c:/horizont/procman/etc/hwm_install_blocker.php and set it to false. See the image below.
