Create Session Manager Database

This section outlines how to create Session Manager databases on the Enterprise and on the field machines. Engine Mobile uses the Session Manager database to transfer sessions between the field and the Enterprise. This database is necessary for all implementations except View Only.

An Enterprise user (e.g., Editor) creates a session which is stored in the Process Framework (PX) schema in the SDE database. The Editor can then send the session (or redline session on inspection) to a field user. The field user logs into an Access version of the Session Manager database in the field and retrieves the session from the Enterprise. This process requires a method to send/receive designs. This is covered later in the configuration.

Schneider Electric provides sample Session Manager databases for the Enterprise (SessionManager.mdb) and the field (Field SessionManager.mdb). The steps in this section illustrate how you can leverage the sample data to update your Enterprise to include the Process Framework workflow and create a new field Session Manager database.

Configure Enterprise Process Framework Database

IMPORTANT: Engine Mobile The Process Framework Administration Tool is not installed with ArcFM Engine applications. You will need to install ArcFM Desktop in order to access this tool and configure your Process Framework Database.

Your Enterprise server must be properly configured to receive and manage sessions and designs from the field. Follow the steps below to configure your Process Framework database on the Enterprise server for Engine Mobile. This configuration is required for all Engine Mobile implementations that transfer sessions or designs between the field and Enterprise. This includes all implementations except View Only.

Schneider Electric provides sample Process Framework databases with the ArcFM Solution sample data (i.e., SessionManager.mdb and WorkflowManager.mdb). These databases contain the necessary workflow for your Process Framework database on the Enterprise.

Determine whether you intend to work with sessions (SessionManager.mdb) or designs (WorkflowManager.mdb) or both (WorkflowManager.mdb).
Login to your sample Process Framework database using the Process Framework Administration tool (use Process as the User Name; no password is required).
Select the Import/Export tab.
Select the Export radio button and select the checkbox for Process Framework Workflow. You do not need to export the Users or Workflow Manager CUs as these are just samples.
In the "File to contain exported data" field enter the path to where the XML file should be saved and give the file a name.
Click Export.
Select which extensions you want to export, MMSessionManager, MMWorkflowManager, or both.
When the export has completed, close the Process Framework Administration tool.
Next, you will need to import the XML file into your database on the Enterprise. This provides your Process Framework database with the necessary workflow for working with sessions and designs.

IMPORTANT: If you already have a Process Framework database on the Enterprise and are upgrading to use the Engine Mobile Solution (i.e., you're implementing the Engine Mobile Solution for the first time), be sure to select the Append Data option when prompted to Replace or Append during import. This ensures you don't lose any custom workflow components (e.g., tasks, roles).

The next steps walk you through configuring the Process Framework database you just created on your Enterprise server.
Open the Process Framework Administration Tool and login to your Enterprise Process Framework database (Session Manager or Workflow Manager).

NOTE: Different ArcFM Solution products use different values. You can add those values during this procedure.
On the Users tab, enter user names and select roles for your users.
Select the Extensions tab and look for the DatabaseID field at the bottom.
In the Database ID field, enter a value for your Enterprise server. Each Engine Mobile field machine will enter a value in the DatabaseID field that corresponds to this value. This allows the field machines to always send sessions and designs to the appropriate Enterprise server. It is critical that the Database ID value on the field machines match exactly the value on the Enterprise. If they do not match, sessions and designs will not be transferred properly and may be lost.
Select the Configuration tab. This tab requires several configuration values.
- Px_MobileDatabase Optional. If you don't add this configuration to the enterprise process framework database, it will still work. Note that the value is '0' to indicate the enterprise geodatabase.
- ProcessFrameworkEnterprise: Enter the path to your ProcessFrameworkServer directory on the Enterprise.
- SessionEnterpriseAfterImportTask: Session Manager Only. Optional. Specify the task that should be executed after a session has been imported. After a session has been imported into the enterprise, Process Framework (Session Manager or Workflow Manager) looks at this field for a task name and executes it if one exists.
- WMSEnterpriseAfterImportTask: Workflow Manager Only. Optional. Specify the task that should be executed after a design has been imported. After a design has been imported into the enterprise, Process Framework (Session Manager or Workflow Manager) looks at this field for a task name and executes it if one exists.
Save changes and close the Process Framework Administration tool.

Configure Field Process Framework Database

IMPORTANT: Engine Mobile: The Process Framework Administration Tool is not installed with ArcFM Engine applications. You will need a valid ArcFM Desktop license in order to access this tool and configure your Process Framework database. Schneider Electric recommends that you use the Administrator machine to configure your field databases. This machine must include an instance of ArcFM Desktop.

If you are installing Process Framework for the first time, you will need to create a field Process Framework database in Access (.mdb). It is strongly recommended that you copy one of the sample field databases provided with the ArcFM Solution sample data (i.e., Field SessionManager.mbd or Field WorkflowManager.mdb). These databases contain the necessary workflow for your Engine Mobile solution. Follow the steps below to use a sample Process Framework database to create your own.

Install the Process Framework sample data provided along with the ArcFM Solution installers. This is a zip file.
Determine whether you need to create a Session Manager or Workflow Manager database. If you elect to use Workflow Manager in the field, you must have Designer on the Enterprise in order to open designs.
- Basic Redliner: Session Manager or Workflow Manager
- Advanced Redliner: Session Manager or Workflow Manager
- Inspector: Session Manager
- Engine Mobile: Session Manager
- Engine Mobile Designer: Workflow Manager
If you're creating a Session Manager database, create a copy of Field SessionManager.mdb. If you're creating a Workflow Manager database, create a copy of Field WorkflowManager.mdb. Be sure you select the Field versions of these databases. They contain the correct workflow information. Copy your new Process Framework database into the shared network directory created on the Enterprise in the Set Up Directory Structure step. You may change the name of the database if you wish.
Login to your Process Framework database using the Process Framework Administration tool (use Process as the User Name; no password is required).
On the Users tab, delete the sample users and enter user names and select roles for your users.
Select the Extensions tab and set the Database ID. The Database ID is a unique value that identifies the enterprise server. This allows multiple servers to use the same network to store mobile sessions and designs. An administrator must assign a unique value to each server. Each client machine must have a field personal geodatabase (e.g., Field SessionManager.mdb, Field WorkflowManager.mdb) with a Database ID that matches the Database ID assigned to the database to which its packets are sent. It is critical that the Database ID value on the field machines match exactly the value on the Enterprise. If they do not match, sessions and designs will not be transferred properly and may be lost.

For example, Utility XYZ has an enterprise server for gas and another for electric. The Gas server has a Database ID of Gas.1234 (assigned using the Process Framework Admin Tool). The Electric server has a Database ID of Electric.1234. All field gas editors must have a value of Gas.1234 assigned in the Database ID field of the field personal geodatabase on their local drive. This value must be Electric.1234 for all field electric editors.
Select the Configuration tab. This tab requires a few configuration values.
- Px_MobileDatabase: When using ArcFM or Designer in the field, the user logs into a Process Framework database on the field unit. The Process Framework database specifies whether it is meant for field or desktop (enterprise) use. Process Framework Configuration Parameters are used to make this designation. The value is '1' to indicate a field database. Any non-zero number will designate the database for field use. A value of 0 indicates an enterprise database. Because you are configuring this Process Framework database for use in the field, set this value to 1. If the config value doesn't already exist, you may need to add it.
- ProcessFrameworkEnterprise: Enter the path to your ProcessFrameworkServer directory on the Enterprise. This directory was created in the Set Up Directory Structure step.
- ProcessFrameworkField: Enter the path to the ProcessFrameworkField directory created on the field machine in the Set Up Directory Structure step. By default, this directory is used: C:\Documents and Settings\[login user]\Application Data\Miner and Miner\ProcessFrameworkField. Replace [login user] with your user name.
Close the Process Framework Administration tool and save changes when prompted.
Place the field Process Framework database on the Administrator or client machine in the location where users will access it. Note this location as you may need to set up Geodatabase Replication to maintain this database.