Setting up an AML production environment involves the following steps:
- Setting up the product library
- Defining the nautical properties
- Creating and setting the AML Nautical Information System (NIS) workspace
Setting up the product library
Before you begin with production, set up the product library. You can then define your product library workspace. The product library workspace stores 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 ArcGIS for Maritime: Charting. The product library also contains runtime validation rules and other production configuration. For more information about the product library, see What is the product library.
Maritime Charting provides a preconfigured product library that includes all six AML vector profiles held in the workspace XML file format. The preconfigured AML product library will have the applicable AML workspace XML files loaded. Contact your local Esri distributor for more information on acquiring the sample AML product library.
Defining the Nautical properties
In addition to the product library settings, you also need to set the nautical-specific properties. These properties define your Feature Identification Subdivision (FIDS), among other optional settings.
Specify a central workspace if you are using the enterprise production environment; you can set this to the NIS database.
Creating and setting the AML NIS workspace
Once you have the product library defined and the Nautical properties set, you can start building an AML NIS. The AML NIS can be one or many databases and can store one or many AML datasets of the same type (SBO, RAL, or MFF, for example).
Whether you choose to use one or many databasesor use file or enterprise geodatabases depends on a couple of factors. If you have many products and many editors, you may want to use an enterprise geodatabase to take advantage of multiuser editing. In this case, you would have one enterprise AML NIS per AML product type. If you have many editors but do not want to use an enterprise geodatabase, you would want to store one cell per production database, using file geodatabases set at the Product level in the Product Library window. If you have very few editors, you may want to store all datasets of a common type in a single AML NIS file geodatabase. Any combination is allowed; it is up to the organization to determine what combination to employ for its needs.
To create the AML NIS, you will need to import one of the AML workspaces into a geodatabase. Once the geodatabase is created, you will need to set this geodatabase as the NIS workspace at the Class, Series, or Product level in the Product Library window, depending on how you want to design and deploy your production system.