Configure Mobile - Engine

Follow these steps ONLY if you're installing Mobile for the first time. If you have a previous version of Mobile, use the Upgrade steps in the Set Up Process Framework Tools section. Below are three possible scenarios and the actions that should be taken.

  • I have no previous Mobile product installed and no existing Process Framework database. Implementation. Follow the implementation steps below.

  • I have no previous Mobile product installed, but I do have an existing Process Framework database. Implementation. Follow the implementation steps below.

  • I have previously installed Mobile. Upgrade. Follow the Upgrade steps on the What's New page for your current release (and every release between) and the Set Up Process Framework Tools section.

    • Workspace packets are no longer supported. By default, all new sessions and designs sent to the field have XML packets. 

    • You need to convert any existing workspace packets before you can open or send designs or sessions.

    • XML packet edits are not supported for non-ArcFM (or non-Designer) tables. Ensure the objects you're editing are ArcFM or Designer objects. Use the ArcFM Solution Object Converter to convert them if necessary.

The ArcFM Mobile Solution allows utilities to leverage ArcFM Solution functionality in the field. A user can sketch in the field, then send the edits back to the Enterprise to be used for editing the enterprise geodatabase.

Using the instructions in this section, the ArcFM Mobile Solution may be configured in a wide variety of ways in order to provide your mobile users with the tools they need in the field. Each implementation provides a varying degree of functionality to the field users and has specific licensing requirements.

Because configuring Mobile is tightly integrated with configuring Geodatabase Replication, it is a wise idea to review the Geodatabase Replication Before You Begin page before starting the Mobile configuration.

Regional Settings: All machines involved in the Mobile process (enterprise and field machines) must have identical regional settings. Varied settings between machines will cause errors. For example, dates may be displayed incorrectly or the date value may be wrong when sent between Mobile machines.

Once you have your Enterprise database configured, select the Mobile configuration that best suits your needs.

View Only: Allows the user to view and query utility data while in the field.

Basic Redliner: In addition to viewing and querying data in the field, the user may place redline graphics that may be sent to the enterprise with a session or design.

Advanced Redliner: This implementation provides all the functionality of Basic Redliner in addition to the ability to place redline graphics as annotation. The annotation can be sent to the enterprise with a session or design and posted to SDE.

Inspector: ArcFM Engine Only. The Inspector extension allows the user to edit non-spatial attributes and create related objects in the field. This implementation also includes the ability to place redline graphics (either as simple graphics or as annotation).

Steps in the above sections walked you through setting up Geodatabase Replication on the client machines for the Backdrop and Login databases. You also may have created a Process Framework replica in order to implement Send/Receive functionality. The following steps guide you through setting up the Replication Server and Web Service to complete the Geodatabase Replication configuration for the Backdrop and Login databases as well as your Process Framework replica.

Geodatabase Replication: Once you have configured Mobile on a client machine, this section describes how to easily distribute that configuration to any number of client machines.

Distribute Mobile Configuration: Configure multiple Mobile client machines.

Sample Data for Mobile: Schneider Electric provides sample data that may be used with Mobile. Process Framework databases (SessionManager.mdb, Field SessionManager.mdb, WorkflowManager.mdb and Field WorkflowManager.mdb) in a zip file. The Mobile Login and Backdrop geodatabases are also available for download as zip files.

Annotation: If you have a feature-linked annotation class for which annotation is automatically placed, and you have the same feature in the backdrop with the same setting, annotation will be placed twice. To avoid this turn off the option to create annotation when new features are added on the feature class in the backdrop. To do this, right-click the feature in ArcCatalog and select Properties. On the Annotation tab, deselect the checkbox for "Create annotation when new features are added."  

QR code for this page

Was this helpful?