Setting up the ENC production environment

Both the NIS enterprise and desktop workflows reference the configuration settings stored within the product library. Setting up an enterprise or desktop environment involves a few similar steps and some that only apply to an enterprise or desktop workflow.

Steps for setting up both enterprise and desktop production environments

Setting up the production environment

Step	Enterprise Environment	Desktop Environment	Desktop Environment for New Products
1	Setting up the product library	Setting up the product library	Setting up the product library
2	Setting up the central database repository	Defining the Nautical properties	Defining the Nautical properties
3	Defining the Nautical properties	Building the product library tree	Building the product library tree
4	Building the product library tree	Creating the production geodatabase	Creating the production geodatabase
5	Creating the production geodatabase	Checking out the production geodatabase	Populating the production geodatabase
6	Populating the production geodatabase	Configuring the production geodatabase for ENC import in the desktop production environment for existing products	Checking out the production geodatabase
7	Checking out the production geodatabase	N/A	N/A

Steps for setting the production environments

Setting up the product library

Before you begin with the desktop production environment, you will need to set up the product library. You can then define your product library workspace on the. The product library workspace can store data model versions that consist of workspace XML files. These workspace XML files represent the geodatabase schema, the S-57 objects and attributes, for all products supported by the Nautical Solution.

Setting up the central database repository in the enterprise production environment

If you are working in the NIS enterprise production environment, you will also need to set up the central database repository.

Defining the Nautical properties

In addition to the Product Library settings, you will also need to set the nautical specific properties. These properties allow you to define your unit conversion and rounding rule settings if your agency requires you to export data using different units of measurement, Feature Identification Subdivision (FIDS), and other settings.

You will need to specify a Central Data Repository workspace if you are using the enterprise production environment; set the NIS as the CDR.

Building the product library tree

Once you have the product library defined and the Nautical properties set, you can start building the product library tree in ArcMap. You need to create the tree structure that follows this hierarchy:

Solution > Product Class > Series > Product > Instance > Area of Interest (AOI)

If you are using the preconfigured nautical product library XML workspace provided with the Nautical Solution, the Solution and Product Class are already built. See About building the product library for an explanation of all the product library components. You should have already created the series in Setting up the product library. See Creating products with product library for Nautical details about creating products.

Creating the product geodatabase

With the product library tree structure built and the product class, series, product, instance, and AOI defined, you can implement your instance, which will actually build the geodatabase. You can find instructions on implementing product instances here.

Populating the product geodatabase in the enterprise production environment

Now that you have built the geodatabase, it is time to load data into the product by populating the instance, which populates the product geodatabase with data from NIS. Populate Instance performs an extraction using the AOIs and definition queries that you set previously. Once the data is extracted, additional processing in the product database is performed: populating NAME and DSNM fields, clipping extraneous features, creating your CM and URGENT versions, and establishing your replicas.

Populating the production geodatabase in the desktop production environment for creating new products

When using the desktop production environment for creating new products, you need to run the Populate Instance process. However, you will use a different populate method than that used for the enterprise production environment. At the product class level, you will need to set the Population method property to the Nautical Desktop Populator before running the populate process. This will configure your production geodatabase to allow you to build new S-57 data.

Checking out the production geodatabase

For the enterprise production environment, once you have populated your geodatabase, you need to check out the product to apply changes from the central database repository (NIS) to the product. For the desktop production environment for new products, you need to check out the product before you start creating new data. For the desktop production environment for existing products, once you have successfully implemented your product, you need to check out the product before you can start loading data into your geodatabase.

By checking out your product, you simply attach the product geodatabase from the product library to your database server.

Configuring the product geodatabase for ENC import in the desktop production environment for existing products

Now that the geodatabase is attached to the database server, you need to configure the desktop or workgroup geodatabase for the ArcSDE versioning and archiving environment.

In ArcCatalog, you will need to register as versioned and enable archiving for the following items stored in the Nautical geodatabase:

• Nautical Feature Dataset
• ClosingLinesL feature class
• PLTS_NAUTICAL_DELETES_A feature class
• PLTS_NAUTICAL_DELETES_L feature class
• PLTS_NAUTICAL_DELETES_P feature class
• PLTS_COLLECTIONS table
• PLTS_FREL table
• PLTS_PRODUCT table
• PLTS_SREL table

With these geodatabase items versioned and archive enabled, you can now begin your desktop workflow using the Nautical Solution.

メモ:

These steps need to be completed for each implemented production database.