Create Login Database
If using a login for a database through Designer, see the topic Create Login for Designer for instructions.
When ArcFM starts, the user is prompted to log in to a database. The ArcFM Login database is one that contains the ArcFM System Tables which house the various snapping settings, stored displays, page templates, and favorites. As its name implies, the Login database is the database to which mobile users will log in.
On the enterprise, the ArcFM Login database is typically the same SDE database that hosts the enterprise geodatabase. However, on field machines the Login database is a separate personal geodatabase. The mobile login database will not contain any feature or object classes since it is never going to be edited. The sole purpose of the mobile Login database is to store feature favorites, graphic favorites, stored displays, and other standard items managed by ArcFM.
In the steps below, you will copy stored displays from your enterprise database into your Login database. You may wish to create on the enterprise a stored display that contains only the layers that the field user will require.
Create the Login Datatabase
- In ArcCatalog, browse to the directory in which the login database will reside. If you're using Geodatabase Replication to maintain the login database in the field, the database should reside in a sub-directory in the Base Path on the Replication Server. Because Geodatabase Replication uses a Directory replica to maintain the login, it will likely be the only database in the directory.
- Right-click the file folder, select new, then File Geodatabase.
- Name the database to indicate it is a Login database (for example, LoginDB).
- Select the Login database in ArcCatalog and run the Create/Update ArcFM Solution System Tables tool.
- Select the Login database in ArcCatalog and run the Upgrade ArcFM Solution Database tool.
- Select the Login database in ArcCatalog and run the ArcFM Solution Object Converter tool, set to convert to ArcFM.
- Delete MM_SYSTEM_STORED_DISPLAYS and MM_SYSTEM_PACKAGES from the sample login database.
- In ArcCatalog, copy MM_SYSTEM_STORED_DISPLAYS and MM_SYSTEM_PACKAGES from your Enterprise database and paste them into the sample login database.
- Select the Login database and click the Data Source Wizard button on the ArcFM Solution toolbar in ArcCatalog. In the next few steps you will use this tool to connect the stored display layers in the login database to the backdrop geodatabase.
- Read the information provided on the first screen and click Next.
- Select the stored display(s) and/or document(s) you'd like the mobile user to access in the field. All unnecessary stored displays and documents will be removed later. Click Next.
- You will need to set all data sources, so accept the default setting on the next screen. Click Next.
- Browse to the Backdrop geodatabase when selecting the destination data source. This connects the layers in the selected stored displays/documents to the backdrop. Click Next.
- Review the Summary and click Next to connect the stored display/document layers to the Backdrop geodatabase.
- Next, open the Login database in ArcMap and delete any stored displays and/or documents that the user will not require in the field. This will likely include any stored displays you chose not to connect to the Backdrop using the Data Source Wizard.
Stored Displays in the Field
You may need to create or modify stored displays for use in the field. When doing this, keep the following in mind:
Modify the size and color of symbology to make map features easily viewed on a small screen in the field.
Remove extraneous layers from stored displays to decrease the amount of time it takes to load.
Use simple symbology to increase performance.
Do not use Definition Queries (unless absolutely necessary) to increase performance.
If the stored display(s) and/or document(s) to be accessed by the field user have any broken data sources, you may delete those layers and re-save the stored display. This just means that the stored display/document contains layers that the backdrop does not. These layers can be removed from the stored display/document.
Geodatabase Replication: Copy the finished Login database to the appropriate sub-directory in the Base Path directory on the Replication Server. It is from this location that the Login database will be initially distributed (and permanently maintained) to client machines using a Directory Replica. Refer to the Geodatabase Replication section.
Create or Import Graphic Favorites
If your Engine Mobile users will be placing redline graphics in the field, then you will need to populate the login or backdrop database with graphic favorites before sending it to the field machines. There are a few ways to do this.
Sample Graphics: The login database provided with the ArcFM sample data contains sample graphic favorites. You may choose to use these. No further configuration is required.
Create Graphics: Open the backdrop or login database in ArcMap and use the Graphics tab to create graphics. With an edit session started, select a graphic on the map, right-click the Graphics tab and select Create Graphic Favorite.
Import Graphics: You can use the ArcFM System Favorites tool in ArcCatalog to export graphics from an existing geodatabase and import that XML into your backdrop or login database. Note that the Graphics tab in the ArcFM System Favorites Manager does not display the graphic favorites in the database. Also, if you import graphic favorites into a database that already has graphic favorites (such as the Login database provided with the sample data), all existing graphic favorites will be overwritten.
Stored Displays and Geodatabases
When using either Basic and Advanced Redliner, your stored display must contain at least one valid layer on which your license allows an edit session. Your license determines the rules around whether your ArcFM Annotation feature class can reside in the same dataset as a geometric network, and whether that dataset can contain relationships:
If you use an ArcGIS for Desktop Standard license (formerly ArcEditor) or an ArcGIS for Desktop Basic license (formerly ArcView), this valid layer must be from a dataset which contains no relationships or geometric networks. Because Advanced Redliner must edit annotation classes, all annotation layers used as redlining targets must be valid editing layers.
If you use an ArcGIS for Desktop Basic license with the Geodatabase Update Extension, your dataset can contain relationships but cannot contain a geometric network.
If you use an ArcGIS for Desktop Standard or an ArcGIS for Desktop Advanced (formerly ArcInfo) license, your dataset can contain both relationships and geometric networks.
Valid layers are required because both Redliner and Inspector must start edit sessions. To begin an edit session, your map must include at least one editable layer. This is true even for Basic Redliner, even though it cannot edit any features.
If all the layers in your stored display come from a single geodatabase, the order of the layers does not matter because ArcFM automatically uses valid layers to start the edit session. The layer rules for multiple geodatabases depend on which product you use:
If you use Redliner in Engine Viewer, and your stored display uses layers from multiple geodatabases, the first layer in the stored display must be from the geodatabase with the valid layers. An editing workspace can only be started on a single geodatabase at a time, and ArcFM attempts to start the edit session only on the first geodatabase listed in the stored display.
If you use Engine Mobile instead of Redliner, you will receive a prompt from ArcMap after running the Open Graphic Session command. Here you can choose which workspace to start editing.