Product library distribution (Production Mapping)

A product library is a database that allows multiuser environments to centralize information and behavior for cartographic and digital data production. The distribute functionality in the Product Library window and the Distribute Product Library tool are designed to help you share product information more effectively. You can distribute a data model, data model version, solution, and product class; all associated files are automatically distributed as well. You can't distribute a series or any individual products using this tool.

A data model is a container for groups of data model versions. When distributing data models, you have the option to choose any that are contained within the product library. Any files that are associated with the data models, such as batch jobs and field configurations, are automatically distributed.

A data model version is the workspace schema that is used for specific editing tools. You can distribute any data model version that is contained within the product library. The data model and any files that are associated with the data model version are automatically distributed.

A solution is essentially the name of the specific projects or industry grouping that corresponds to the products being created. When distributing a solution, you have the option to choose any of the product classes that are associated with the solution.

The product class is a type of geographic product designed for a particular use, typically unique types of maps, charts, or digital data that share common properties. A product class has a product class version and a default data model version that are used to define the schema of the data used for a product. The product class version, default data model version, and associated files are automatically exported.

When distributing a product library, you have the option to copy the product information directly into another product library or to save the information into an XML workspace. If you choose to save the information to an XML workspace, the XML file can later be imported into a database by pointing to the XML file as the source. When you choose to import into a geodatabase, the geodatabase is validated to ensure it has the latest product library schema. You may be prompted to upgrade the schema of the database if it is not current, so you may need permissions to modify the schema of the database. If the schema is current, you only need permissions to write records to the database.

When you distribute a product library with one of the Esri 制图和制表解决方案, the source and target must support the same extension. For example, if the source product library only supports ArcGIS for Maritime:Charting, it can only be distributed to another product library with just ArcGIS for Maritime:Charting. The source can't also support one solution, and the target support two solutions; for example, if the source product library supports ArcGIS for Maritime:Charting, it can't be distributed to a target product library that supports both ArcGIS for Aviation:Charting and ArcGIS for Maritime:Charting. You can also create a target product library. If you choose to create a product library as the target, it will support the same extensions as the source product library.

Scenarios for distributing a product library

Merging multiple product classes

The product library is designed to be a central repository for your business rules. Your business may require that you support multiple types of products. If you have created or received multiple product libraries, you might decide to merge them so you can manage one central product library rather than multiple product libraries. The Distribute Product Library tool allows you to copy the data model, data model version, solution, and product class information from one product library to another.

When importing product information into an existing product library, only items that do not already exist in the target product library are imported. For example, suppose you are importing the State solution and the Highways product class into a database that already has a State solution and a Counties product class. When you import, because the State solution already exists, it is not re-created, and the new Highways product class is added to the existing State solution.

Distributing schema updates

When distributing a product class, the default product class version, default data model version, and any associated files, such as batch jobs and field configurations, are automatically exported. The product class and data model version are used to define the schema of the data, which is used to create a product.

If the schema of your database changes, you can also choose to create a new data model version. You might choose to create this new version in a staging database, or you might receive these updates as part of a solution. The Distribute Product Library tool can be used to merge the new schema and business rules into your existing product library.

When distributing a product class, this tool also looks for existing product classes with the same name. So if you want the new schema and business rules added to an existing product class, the name in the source and target product libraries must match. If the names do not match, the imported information is added as a new product class.

Working in a distributed environment

Many users work in a distributed environment where there is a central office with either multiple regional offices or other organizations that work is contracted out to. In this scenario, the central office may want to keep a product library with all types of supported solutions and product classes. However, the regional offices or contractors may only need a subset of these. The central office can export only those product classes that are needed for the individual region or contractor, which can then be imported into a product library at the distributed location.