Configuration and the Nautical Solution

Before you can begin using the Nautical Solution, configuring it requires that the database administrator (DBA) and users perform several tasks. The following are descriptions of the different sections for configuration and the persons that are involved.

Setting up the product library

The agency, in conjunction with the IT group's DBA, needs to determine the appropriate database administration system (DBMS) and production environment for the data and products the agency will manage. Once the production environment has been determined, the DBA can set up the product library and load the XML workspace. The product library is where the products can be managed.

Learn more about the product library

Setting up the central database repository

If you will be working with an enterprise production environment, the DBA must implement a central database repository, which is also referred to as the Nautical Information System (NIS) database.

Scale bands XML file

Each hydrographic agency administrator needs to modify the ScaleBands.xml file to reflect the scales of their catalog of digital products. This ensures that the product refresher process references the proper agency-specific scale ranges when features are sent between the NIS and the production databases.

Configure the Scale bands XML file

Configuring the desktop client

The DBA or someone with administrator permissions needs to install SQL Server Express where the production databases will reside. Once the DBA configures the product library and the production environment, you must choose a product library from your ArcMap session and define nautical properties.

Configuring advanced settings

The Nautical Solution includes a preconfigured product library that contains a model, solution, and product class. However, the DBA or someone with training can work with the advanced settings listed below:

Versioning and archiving data

Several feature classes and tables in each of the nautical data models must have versioning and archiving enabled before editing occurs to track the changes.


4/19/2012