Workflow Manager Postinstallation

Available with Standard or Advanced license.Available with Workflow Manager license.

About the postinstallation

For the Workflow Manager applications to function, all the Workflow Manager system tables must exist in the database, and of those, the tables that host required configuration information must be populated with values that will drive the application behavior. The following section will detail how to create and start configuring the Workflow Manager system tables.

What is the postinstallation?

The Workflow Manager Post Installation utility is used to insert the Workflow Manager System Tables into the workspace you've created for the Workflow Manager Repository (also referred to as the Workflow Manager Database).

This repository contains a set of geodatabase tables (Workflow Manager system tables) used to store the job and configuration information for your work management system and one feature class that is used to store the geometries for the areas of interest (AOIs) for your jobs.

For specific guidance on how to prepare your enterprise Data Workspace, see the Preparing the database section below.

Note:

The Workflow Manager system tables added by the postinstallation utility are geodatabase tables and are registered with your enterprise geodatabase. If at any time you are unsure of the state of the database, please connect to the repository using ArcCatalog. Because the Workflow Manager system tables are geodatabase tables, it is strongly advised that you not delete or modify these tables using your RDBMS tools.

Preparing the database

Before you can install the Workflow Manager system tables into a geodatabase instance, you must carry out the following:

1. Determine which geodatabase will host your Workflow Manager system tables.

   Take note of the connection information (Server, Instance, Database).

2. Using the native RDMBS management tools for your database, create a new user/login within your database.

   This user will be the owner of the Workflow Manager system tables. You can name this login anything you like. Once created, the user must have the following privileges granted to it:

   • Update
   • Insert
   • Select
   • Delete

   Note:

   These privileges are equivalent to those granted to the data creator user. DB-level permissions such as those required for the Workflow Manager database login should be assigned by your DB administrator. Users should consult the ArcGIS for Server Help regarding DB-level permissions.

Minimum configuration contents

The application needs the values included in WMXMinimumConfiguration.jxl function property (with two exceptions noted below, whose values can typically be used as-is by most implementations, so were provided here). The configuration elements included in this configuration file are

• Privileges
• Status Types
• Activity Types
• Notification Types
• Settings
• Priorities (can be configured to other values or removed if desired)
• Holds (can be configured to other values or removed if desired)

Quick-start configuration contents

The WMXQuickStartConfiguration.jxl includes all the values in the Minimum Configuration plus examples of the following:

• Users
• User Groups
• Job Queries
• Step Types
• Hold Types
• Settings
• Job Types
• Default Properties
• Workflow
• Naming Schemes

Running the Postinstallation

The postinstallation creates all the system tables required for you to use ArcGIS Workflow Manager.

1. From the Start menu, navigate to ArcGIS Workflow Manager and click Workflow Manager Post Installation.

   The Workflow Manager Post Installation wizard appears.

2. Enter the connection information for the designated workspace, then test the connection information.

   Note:

   On a Windows 2000 operating system, to change the default version on a project instance database or a SQL Express database (for example, DBO.DEFAULT) an input box has been provided that pops up to allow you to enter the default database when the Change button is clicked.

   Note:

   For connecting to an Oracle database, the Easy Connect syntax must be used instead of the TNS names. For more information on Easy Connect strings, see the Oracle section in Database connections in ArcGIS for Desktop.

   
   Step One: Enter connection information for the enterprise geodatabase that will be the container for the Workflow Manager Repository.

3. Click Next.
4. Choose a configuration keyword for your Workflow Manager geodatabase if you have created one.

   Note:

   Using the DEFAULT keyword, in most cases, is a reasonable choice. If you are unsure, consult your enterprise geodatabase manager.

   
   Step Two: Choose the configuration keyword.

5. Click Next.
6. Define the spatial reference for the area of Interest feature class.

   A separate two-page wizard appears allowing you to select the coordinate system and extents.

   

   Step Three: Define the spatial reference for the Area of Interest feature class.
7. Click Next.
8. Choose your starting configuration for the Workflow Manager repository.
   • No configuration will put the Workflow Manager system tables schema into your designated geodatabase and not prepopulate any of the configuration elements.
   • Minimum configuration imports just the basic elements that the Workflow Manager system requires.

     Note:

     If you plan to use all the functionality available in the Workflow Manager client application, it is recommended that you import at least the minimum configuration.

   • Quick configuration includes the minimum elements plus predefined job types as an example.
   • Custom configuration allows you to import a preexisting Workflow Manager Configuration File.
   
   Step Four: Choose the starting configuration and user store for your repository.

   Note:

   If you plan to import a Workflow Manager configuration exported from a 3.x database, choose the No Configuration Import option. Tools are provided in the Workflow Manager Administrator to import the legacy configuration files.

9. Choose your starting user store for the Workflow Manager repository.
   • Traditional—Users and group are defined in the Workflow Manager Administrator and the user name of the users is the Windows login.
   • Portal—The users belong to an ArcGIS Portal or Organization, and the user name of the users is as defined in the Portal.

     Note:

     If you choose Portal, a dialog box to login to the Portal will be displayed.

10. Click Next.
11. Choose whether you would like to create a Workflow Manager Database connection to this new repository when the postinstallation is complete.
    • Specify a connection alias.
    • Specify a repository name.

      Note:

      This is used as a unique identifier when defining cluster for Repository Replication.

      Note:

      The following characters must not be used in the connection alias and repository name \ / : * ? < > | ".

    • Specify to set the database as default.

    

    Step Five: Decide if you want Workflow Manager to add a Workflow Manager Database connection for you

12. Click Finish.

    The system tables needed to use Workflow Manager are created in the database. Also, the current user running the postinstallation is automatically added to the list of users and is added to the Administrator group, which grants the user administrator access.

    The final page in the wizard appears, indicating if the postinstallation was successful or not.

    Note:

    Administrator access means that the current user can connect to the selected database through the Workflow Manager Administrator to make edits to components of your system.

13. Choose whether you would like to view the log.

    

    The final page of the wizard indicates the success of the postinstallation and offers you a chance to see a log of the process

14. Click Close.

Note:

If you are using Oracle or DB2 as your RDMBS, you may want to manually create a spatial grid on your AOI feature class to improve performance. See The spatial grid index in the ArcGIS for Desktop help for more information.

Feedback on this topic?