Configuring the nautical product library geodatabase (Maritime Charting)

This workflow provides steps for configuring log file tables and importing the preconfigured XML workspace that contains all the necessary feature classes and tables that can be used in an enterprise geodatabase in SQL Server to manage nautical data and products. It is highly recommended that you use it.

Configuring log file tables

Enterprise geodatabases use log file tables to maintain lists of selected records. Records are written to log file tables for later use by the application whenever a selection of a specific size is made, a reconciliation or post on a versioned database is performed, or a disconnected editing checkout is done in a client application. The log file tables store the ObjectIDs of the selected features so they can be redisplayed. This allows for faster analysis and processing of information.

In ArcGIS, by default, log file tables are used if the selection set contains 100 or more records. This selection threshold of 100 features is set in the registry. It can be changed; however, Esri does not recommend you do so. There is no proven performance reason for changing it, and doing so could cause performance problems.

Log file options are set using specific parameters in the SDE_server_config and SDE_dbtune tables.

Parameters in these tables are altered using the sdeconfig and sdedbtune commands, respectively. These commands and the other ArcSDE administration command line tools must be downloaded from the Esri Customer Care Portal with the ArcSDE application server. Syntax and examples for how to use the commands are provided in the ArcSDE Administration Command Reference, which is provided with the ArcSDE application server installation.

For SQL Server, the default log file configuration is session-based log files created in the temporary database (tempdb).

With the default settings, one table is created in the tempdb in the format ##SDE_SESSION<SDE_ID>_<DBID>. The <SDE_ID> is the unique session ID from the SDE_process_information table. The <dbid> is the database ID from SQL Server. This table is truncated when the connecting application deletes its log files, and the table is dropped when the session disconnects. If you use the recommended SQL Server settings for on-premises databases, users only require the ability to connect to the database and do not require CREATE TABLE privileges.

In most cases, the default ArcSDE log file table configuration for your database management system (DBMS) should be sufficient and is the recommended setting.

For more information on log file tables, see Log file table configuration options for geodatabases in SQL Server.

Importing the product library schema workspace

The XML workspace contains the standard product library tables. It is also preconfigured with a solution node (Nautical) and many class nodes (ENC, Chart, and so on) and has the unit conversion, Element, and VST tables.

Steps:
  1. Unzip the nautical product library file.

    The preconfigured workspace XML for ENC and Chart is available on the Resource Center. There is also one .gdb installed for DNC in the following location, based on your operating system.

    • On Windows XP, browse to <Installation location>\Documents and Settings\All Users\Application Data\Esri\Production10.2.2\Desktop\ProductLibraryFiles.
    • On Windows Vista, Windows 7, and Windows Server 2008, browse to <Installation location>\ProgramData\ESRI\Production10.2.2\Desktop\ProductLibraryFiles.
  2. Start ArcMap.
  3. In the Catalog window, expand Database Connections.
  4. Double-click the product library administrator connection geodatabase to connect to it.
  5. Right-click the geodatabase you just connected to and click Import > XML Workspace Document.
  6. Click the Data option if it is not already selected.
  7. Select the nautical product library located in the directory from step 1.
  8. Click Open.
  9. Click Next.
  10. Click Finish.

Versioning within product library

If you manually import the product library tables and feature classes, such as importing an XML file, you need to verify that all the tables and feature classes are registered as versioned. This allows the software to edit the tables as you create and work with your product library. However, you shouldn't create new versions of the product library tables; this can result in inconsistencies within the versions.

Steps:
  1. Click the Toggle Contents Panel button Toggle Contents Panel at the top of the window.

    The Toggle Contents Panel dialog box appears.

  2. Select every table feature stored in the product library with the exception of the following:

    • ELM_CATEGORIES
    • ELM_ELEMENTS
    • ELM_PRODUCTS
    • ELM_SOLUTIONS
    • PLTS_UCE_CONVERSIONS
    • PLTS_UCE_MAPPINGS
    • PLTS_UCE_ROUNDINGRULES
    • PL_CHART_AOI
    • PL_ENC_AOI
    • PL_NIS_AOI

    TipTip:

    Press SHIFT and/or CTRL, and then the tables to make multiple selections.

  3. Right-click within your selected tables and click Manage > Register as Versioned.

    Do not check the Register the selected objects with the option to move edits to base check box.

  4. Click OK.
  5. Select the following feature classes stored in your product library and click Manage > Register as Versioned.
    • PL_ENC_AOI
    • PL_NIS_AOI
    • PL_CHART_AOI

    Do not check the Register the selected objects with the option to move edits to base check box.

  6. Click OK.

Granting privileges to the database role

You need to assign privileges to the components in the enterprise geodatabase in SQL Server.

All features imported with the product library XML workspace need privileges.

All the tables in the product library need to have read/write privileges assigned to them, except the PL_Permission table. The PL_Permission table only needs read privileges assigned to it.

Grant the following privileges to the CKB_USERS database role.

Objects

Role

Privileges

PL_Permission

CKB_USERS

Select

All tables except PL_Permission

CKB_USERS

Select, Insert, Update, Delete

Steps:
  1. In the Toggle Contents Panel dialog box, select the PL_Permission table, right-click, then click Manage > Privileges.

    The Privileges dialog box appears.

  2. Click Add.
  3. Type CKB_USERS into the User/Role text box.
  4. Check the Select check box to assign view privileges to the CKB_USERS for the PL_Permission table.
    Privileges for viewers
  5. Click OK.

    The Toggle Contents Panel dialog box appears.

  6. Select every table stored in the product library with the exception of the following:
    • PL_PERMISSION
    • PL_CHART_AOI
    • PL_ENC_AOI
    • PL_NIS_AOI
  7. Right-click the selected tables and click Manage > Privileges.

    The Change Privileges dialog box appears.

  8. Type CKB_USERS in the User text box.
  9. Click the View (Select) (optional) drop-down arrow and choose GRANT.
  10. Click the Edit (Update/Insert/Delete) (optional) drop-down arrow and choose GRANT.
  11. Click OK.
  12. Select the following feature classes stored in the product library:
    • PL_CHART_AOI
    • PL_ENC_AOI
    • PL_NIS_AOI
  13. Right-click the selected feature classes and click Manage > Privileges.

    The Change Privileges dialog box appears.

  14. Type CKB_USERS in the User text box.
  15. Click the View (Select) (optional) drop-down arrow and choose GRANT.
  16. Click the Edit (Update/Insert/Delete) (optional) drop-down arrow and choose GRANT.
  17. Click OK.
  18. Close ArcMap.
Copyright © 1995-2015 Esri. All rights reserved.
2/17/2015