Workflow Manager Database Set Up - SQL
The following scripts are provided to create the Process Framework and Workflow Manager schema on a SQL Server instance:
Database Set Up:
The tables required by the Process Framework engine can be placed on the same SQL instance that provides the SDE Geodatabase. The tables (created by the SQL scripts) must exist under a user named "PROCESS." Note that if the database has already been set up to run Session Manager, then you may skip steps 1-4.
- Optional. Create a new database on your SQL Server instance to house the Process Framework database. An existing database can be used, but it might be easier to manage (backups, disk storage, etc.) if you create a new database dedicated to the Process Framework tables.
- Create the PROCESS user in the SQL Server instance. Remember that it is mandatory the user name is "PROCESS." Grant this user access to the database discussed in step 1.
- Open the SQL Server Query Analyzer window, connecting to the database discussed in step 1 as the new PROCESS user.
- Run the CreatePXTables_MSSQL script. This script will create the tables required by the Process Framework engine.
- Run the CreateWFMTables_MSSQL script. This will create the tables required by Workflow Manager.
- Run AddWFMData_MSSQL script. This will populate the Workflow Manager tables with the data they require.
- As a DBA user in SQL Server, create a role called "WMS_USER."
This can either be done in a Query Analyzer window or the Enterprise
Manager. This role will be used to assign the appropriate table privileges
to users of Workflow Manager. The name of this role is not mandatory;
however, if you use a different name for this role you will have to
alter the SQL script in the next step. The following SQL syntax will
create a role in SQL Server:
- With the Query Analyzer, connect to the database as the PROCESS user and Run the GrantWFMRole_MSSQL script. This script grants the appropriate table privileges to the "WMS_USER" role. Again, if you changed the role name as discussed in step 8, you’ll need to alter this script to use the name you chose.
- Grant the various existing SQL Server users access to the database discussed in step 1. Since the number of users involved in this step is probably equal to the number of users that access SDE, you’ll probably want to make a script to perform this task.
- Add the various existing SQL Server users to the "WMS_USER"
role. Since the number of users involved in this step is probably
equal to the number of users that access SDE, you’ll probably
want to write a script to perform this task.
Workflow Manager Administration
Add each user involved in step 9 above to the Process Framework with the "Users" tab in the Process Framework Administration Tool. After you have imported the workflow (see Add Workflow, below), you can also use "Users" tab to assign the Workflow Manager user roles to each user.
The following steps allow you to export the workflow from the sample database provided with the ArcFM Solution installation and import that workflow into your own Process Framework database. Once imported, this workflow can be modified to meet your specific business needs.
- To add a workflow, use the Import/Export tab in the Process Framework Administration tool and the sample Workflow Manager database (WorkflowManager.mdb) provided with the ArcFM Solution install.
- Log in to WorkflowManager.mdb as "Process."
- Select the Import/Export tab.
- Select the Export radio button and select the Process Framework Workflow Importer/Exporter checkbox.
- Designate an XML file name to which the workflow will be exported.
- Click Export and select the MMWorkflowManager extension.
- Close the Process Framework Admin tool when the export is complete.
- Log in to your Workflow Manager database as "Process."
- Select the Import/Export tab.
- Select the Import radio button and browse to the XML file you just exported from the sample data.
- Click Import.
For more information about the Process Framework Administation Tool and the Import/Export tab, see the Using ArcFM Solution online help and the Process Framework Administration section.
Access the Process Framework Administration Tool in the Start menu > ArcFM Solution > Process Framework > Admin.
Support Workflow Manager with TLS 1.2
When you disable Transport Layer Security (TLS) 1.0 and enable TLS 1.2 on the Windows Server that hosts Microsoft SQL Server, Designer Workflow Manager and other ArcFM applications that use SQLOLEDB for SQL Server connectivity are unable to connect. Further, you receive an error, “[DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.”
To resolve this issue, perform the following configurations:
Install the 64–bit Microsoft OLE DB Driver for SQL Server.
Install the ODBC Driver for SQL Server.
Visit the Microsoft help topic TLS 1.2 Support for Microsoft SQL Server to verify your server settings. In particular, read the section, “What is the correct registry setting to enable TLS 1.2 for SQL Server communication?” and verify your registry setting.
In addition to the registry settings found in the Microsoft document above, add the following registry key on the client machines: