What's new in product library for Esri Production Mapping (Production Mapping)
In Esri Production Mapping 10.1, major enhancements have been made to the properties associated with the product library and production database. The most commonly used production and product library properties were moved to the Product Library window tree view. New geoprocessing tools have been added to assist in automated workflows and data management. Tools that are specific to Esri Mapping and Charting solutions have been hidden for all but that solution to keep the interface as clean as possible. You can now have multiple production databases associated with a single product library.
New at Service Pack 1 Patch 2
The Add File geoprocessing tool was added to the Product Library toolset. The tool adds a file to a product library and associates the file with the appropriate product library level.
New at Service Pack 1
The following are enhancements to the user experience and updates to functionality:
- Guide books have been created to help database administrators set up a product library in an enterprise geodatabase in SQL Server and a geodatabase in Oracle.
- Product library and production database tables are not registered for versioning by default.
- If conflicts arise when adding, moving, copying, or copying a file as a link in the file manager, a dialog box appears with options to resolve those conflicts. You can choose to leave the target version of a file or overwrite it with another one.
Production Properties and Product Library dialog box
The following functionality was moved from the Production Properties and Product Library Properties dialog boxes to the Product Library tree view and can be accessed through context menus.
- Selecting the product library
- Creating data models for the product library
- Creating data model versions
- Associating data models with the production database
- Defining the current data model version for the production database
- Setting instances maintained
- Creating entry types
- Adding and deleting users for the current product library
- Creating views
- Creating visual specifications
The following properties were removed from the Production Properties and Product Library Properties dialog boxes.
- Current Entry
- Auto Update
- Production Database Workspace
- Product Class Version
- Tools
The following properties were added to the Production Properties and Product Library Properties dialog boxes.
- Enable Performance Logging—Creates a log file that contains a summary of the average times for product library file read/write and startup/shut down times for Esri Production Mapping.
- Remember Product Library Connection—When ArcMap is started and the property is set to True, it will connect to the last product library to which you connected. If the property is set to False, the product library connection will be null.
- ArcSDE Geodatabase Access section—Can be configured to automatically retry save operations to minimize errors that can occur when multiple users are creating products in the same series or checking in products.
|
|
Product Library window
Several enhancements were made to the Product Library window.
- Manage Files was moved from the context menu to the toolbar on the Product Library window and is still context sensitive, so it will open at the level you have selected in the tree view.
- There are now two top levels: Product Library and Production Data.
 |
Product Library
The Upgrade Product Library command adds all the components necessary for your geodatabase to perform as an up-to-date product library and is available when you right-click the Product Library level.
The Product Library level is subdivided into the Data Models and Products levels. In the Data Models level, you can create, modify, and delete data models and data model versions. In the Products level, you can continue to create and modify the tree structure to manage data and products for your projects and solutions.
When no product library workspace is defined, and you add data that is stored in a geodatabase, which is a product library and a production database, the product library workspace points to this geodatabase; the data model versions are also set automatically.
Production Data
The ability to set a production database workspace was removed from the Production Properties and Product Library Properties dialog boxes to support using multiple production databases for data editing. Every time you load data, the database in which it is stored is listed in the Production Data level. Multiple databases can show up in this level when you have data from more than one workspace loaded in the map, whether it's a production database or not.
In the Production Data level, you can do the following:
- Create a production database if the data that is loaded belongs to a database that doesn't have the schema of a production database.
- Upgrade a production database that is out of date.
- Associate data models with a production database.
- Set the active data model version for a production database.
- Set the instances maintained.
An additional enhancement sets the product library workspace automatically upon loading data if no product library is set and that data is from a database that has the current product library schema; the data models for this product library are listed in the Product Library level. The product library database is listed in the Production Data level, and you have the option of adding the production database schema.
Other enhancements
- Distribute Product Library and the functionality to distribute solutions and product classes now includes the ability to choose data models.
- Product library permissions now support different domains.
- File versions include a revision (can be viewed in the file manager), for example, 2.01.
New Geoprocessing tools
The following are new geoprocessing tools in the Product Library toolset of the Production Mapping Tools toolbox.
- Attach Database—Attaches a .mdf file to an instance of SQL Server Express
- Checkin File—Checks in the specified product library file
- Checkout File—Checks out the specified product library file to the specified location
- Create Product Library—Creates a product library in a geodatabase
- Create Production Database—Creates a new production database
- Detach Database—Detaches a .mdf file from an instance of SQL Server Express
- Get Local Copy—Creates a local, editable copy of a file in a product library without exclusively locking the file
- List Files—Lists files associated to the specified parent item in a product library
- List Items—Lists child items of the specified item in a product library
- Upgrade Product Library—Upgrades a product library schema
- Upgrade Production Database—Upgrades a production database schema