Setting up the product library in an ArcSDE environment

Two different procedures are used to create and set up an ArcSDE geodatabase for the product library. One is used for setting up the product library on an ArcSDE geodatabase for Microsoft SQL Server Express licensed for ArcGIS Desktop (instance of SQL Server Express). The other is used for setting up the product library on an ArcSDE geodatabase licensed for ArcGIS Server Enterprise. The steps in this workflow are for setting up the product library on an ArcSDE geodatabase for Microsoft SQL Server Express licensed for ArcGIS Desktop, but additional information and links are provided for setting up the product library on an ArcSDE geodatabase licensed for ArcGIS Server Enterprise.

Adding a database server

This section describes how to add a database server connection under the Database Servers node in the Catalog window. This is a connection to a Microsoft SQL Server Express instance set up to store geodatabases. You can skip this section if you are using Oracle, SQL Server Enterprise, or another ArcSDE geodatabase licensed for ArcGIS Server Enterprise to store the geodatabase you are using as the product library.

You will need to install SQL Server Express, if you have not already, and enable it to store geodatabases.

Étapes :

1. Démarrez ArcMap, ouvrez la fenêtre Catalogue, puis développez le nœud Serveurs de bases de données dans l'arborescence du catalogue.
2. Double-cliquez sur Ajouter un serveur de base de données.
3. In the Add Database Server dialog box, provide the name of the ArcSDE database server. This is in the form <server_name>\<instance_name>, where the server name is the name of the server on which SQL Server Express is installed and the instance name is the name of the SQL Server Express instance.

   For example, if a database server is named SOPHIE\SQLEXPRESS, SOPHIE is the server name, and SQLEXPRESS is the instance name. Using 127.0.01 for the server name will avoid sourcing issues if multiple users are going to be accessing the product library.

4. Cliquez sur OK.

L'icône de serveur apparaît sous Serveurs de base de données dans l'arborescence du catalogue.

Conseil :

Si vous ajoutez le serveur de base de données et que l'icône apparaît dans l'arborescence du Catalogue accompagnée d'un carré blanc vierge, le serveur de base de données a été ajouté mais son état est inconnu. Essayez de double-cliquer dessus pour vous connecter. Si vous êtes incapable de vous connecter, contactez l'administrateur de ce serveur de base de données pour savoir si l'instance SQL Server Express s'exécute et est connectée au réseau et connaître le type d'autorisation dont vous disposez au niveau de ce serveur de base de données.

Creating the administrator database connection

If the product library is stored in an ArcSDE geodatabase licensed for ArcGIS Server Enterprise, you need to create an administrator database connection. If your product library is stored in SQL Server Express, you can skip this section, since you only need to add a database server connection (first section of this workflow).

If you want to create a database connection for SQL Server, go to Making a direct connection from ArcGIS Desktop to a geodatabase in SQL Server. If you want to create a database connection for Oracle, go to Making a direct connection from ArcGIS Desktop to a geodatabase in Oracle.

Creating an ArcSDE geodatabase

The server administrator needs to create a new geodatabase from Oracle, SQL Server, SQL Server Express or another enterprise database management system (DBMS) that can be used as the product library. The steps in this section are for creating an ArcSDE geodatabase for Microsoft SQL Server Express licensed for ArcGIS Desktop (SQL Server Express geodatabase). If you want to create a geodatabase from Oracle, SQL Server, or another ArcSDE geodatabase licensed for ArcGIS Server Enterprise, see the following topics for information:

• A quick tour of setting up a geodatabase in DB2
• A quick tour of setting up a geodatabase in Informix
• A quick tour of setting up a geodatabase in Oracle
• A quick tour of setting up a geodatabase in PostgreSQL
• A quick tour of setting up a geodatabase in SQL Server

Recommendations for Oracle databases

It is recommended that you ensure that the following parameter values are used when creating an Oracle database:

Parameter name	Value
Configure with Database Enterprise Manager	Enabled
Shared memory management	AUTOMATIC
Character Sets	Unicode (AL32UTF8)
OPEN_CURSORS	2000–10000
SESSION_CACHED_CURSORS	50–150
pre_page_sge	True

Oracle parameters for product library

The steps below are for creating an ArcSDE geodatabase for Microsoft SQL Server Express licensed for ArcGIS Desktop (an instance of SQL Server Express).

Étapes :

1. Connectez-vous en tant qu'administrateur de serveur, démarrez ArcMap, puis ouvrez la fenêtre Catalogue.
2. Dans l'arborescence du catalogue, cliquez avec le bouton droit de la souris sur le serveur de base de données sur lequel vous souhaitez créer une géodatabase.
3. Cliquez sur Nouvelle géodatabase.
4. Tapez un nom pour la nouvelle géodatabase dans la zone de texte Nom de la géodatabase.

   Le nom doit commencer par une lettre, ne peut pas contenir d'espaces ou de caractères spéciaux (tels que #, @ ou *) et avoir une longueur maximale de 31 caractères lorsqu'il est combiné au nom du serveur.

5. Si vous voulez modifier l'emplacement du fichier de base de données, spécifiez le nouvel emplacement dans la zone de texte Fichier de géodatabase en cliquant sur le bouton représentant des points de suspension (...) et en recherchant l'emplacement.
6. Saisissez la taille de la nouvelle géodatabase dans la zone de texte Taille initiale.
7. Choisissez Mo ou Go dans le menu déroulant Unités ou utilisez la taille par défaut 100 Mo.

   Quelle que soit sa taille initiale, la géodatabase s'accroît selon ses besoins jusqu'à 4 Go.

   Remarque :

   La taille initiale de la géodatabase ne peut pas être inférieure à celle du modèle de base de données dans l'instance SQL Server Express. Le modèle de base de données est le modèle système pour toutes les nouvelles bases de données. La taille du modèle de base de données détermine la taille minimale de toute base de données créée dans cette instance SQL Server Express. Si vous essayez de créer une géodatabase plus petite que cette taille minimale, la création échoue et le message d'erreur suivant est renvoyé :

   Error creating this geodatabase
   CREATE DATABASE failed. 
   Primary file must be at least <size of model> to accommodate a copy 
   of the model database.

8. Click OK.

Une barre de progression s'affiche pendant que le fichier de base de données et la structure de géodatabase sont créés. Lorsque le processus est terminé, la nouvelle géodatabase apparaît dans l'onglet Contenu de l'arborescence du catalogue.

Creating geodatabase users

You can choose to add users to a geodatabase stored in SQL Server through Microsoft SQL Server Management Studio Express.

Learn how to add users for an Oracle database

Learn how to add Windows-authenticated users or groups to a SQL Server database

Learn how to add database-authenticated users to a SQL Server database

The steps below are for creating users for the product library geodatabase in ArcCatalog on a database server (an instance of SQL Server Express) and SQL Server.

Étapes :

1. Connectez-vous en tant qu'administrateur de serveur, démarrez ArcMap, puis ouvrez la fenêtre Catalogue.
2. Cliquez avec le bouton droit sur le serveur de base de données auquel vous voulez ajouter un utilisateur ou un groupe.
3. Cliquez sur Autorisations.
4. Cliquez sur Ajouter un utilisateur dans la boîte de dialogue Autorisations.
5. Spécifiez où vous voulez rechercher l'utilisateur ou le groupe.

   Il peut s'agir de l'ordinateur local ou d'un domaine.

6. Saisissez le nom de l'utilisateur ou du groupe à ajouter. Vous pouvez cliquer sur le bouton Avancé si vous voulez lancer une requête plus spécifique pour trouver l'utilisateur recherché.
7. Cliquez sur Vérifier les noms pour vérifier la validité du nom de connexion.
8. Click OK.

Granting geodatabase roles/permissions

A role needs to be assigned to the users that are going to be working with the product library so they can view or add components, information, and data to the product library. These permissions are at the geodatabase level, assigned separately from the product library permissions. The roles are assigned through ArcCatalog as permissions for users that are using a product library stored in SQL Server Express or SQL Server. For Oracle and any other ArcSDE geodatabase licensed for ArcGIS Server Enterprise, the role CKB_USERS must be created for the users to be recognized by the product library. This can be done by using the following statement:

CREATE ROLE CKB_USERS NOT IDENTIFIED

User names for the role are required for any users who are going to be working with the product library and need to read from or write to the product library tables and other components. The administrators are considered the owners of the data, so they already have this privilege.

Below are suggested user names and the permissions required for each level for Oracle (and SQL Server if using Microsoft SQL Server Management Studio Express).

For product library administrators, the following is suggested:

User type	Role	Oracle permissions	SQL Server permissions
Data owner	CONNECT	CREATE PROCEDURE CREATE SEQUENCE CREATE SESSION CREATE TRIGGER CREATE VIEW CREATE TABLE	CREATE TABLE CREATE VIEW CREATE PROCEDURE

Administrator permissions

For product library editors, the following is suggested:

User type	Role	Oracle permissions	SQL Server permissions
Data editor/Data viewer	CONNECT CKB_USERS	CREATE SESSION	CREATE TABLE

Editor permissions

Learn more about user permission levels for Oracle

Learn more about user permission levels for SQL Server

The steps below are for granting roles/permissions on a database server (an instance of SQL Server Express), and SQL Server.

Étapes :

1. Cliquez avec le bouton droit sur la géodatabase pour laquelle vous voulez accorder l'autorisation.
2. Cliquez sur Administration, puis sur Autorisations.
3. Choisissez l'utilisateur ou le groupe souhaité dans la liste de la boîte de dialogue Autorisations.
4. Click the appropriate role:
   • Aucune : aucun accès spécifique à la géodatabase ou aux jeux de données dans la géodatabase n'a été accordé.
   • Lecture seule : l'utilisateur peut uniquement afficher et sélectionner des données.
   • Lecture/écriture : l'utilisateur peut lire, écrire sur, et créer des jeux de données dans une géodatabase ou lire et écrire dans un jeu de données existant.
   • Admin : l'utilisateur peut effectuer des tâches administratives dans une géodatabase spécifique.
   • Administrateur de serveur : cet utilisateur gère le serveur de base de données.
5. Click Apply.

Configuring the database in ArcSDE

You need to configure the MAXBLOBSIZE and TCPKEEPALIVE parameters for the ArcSDE geodatabase used as the product library. The product library can be set up in a central or local geodatabase. A central geodatabase is usually an ArcSDE geodatabase with Oracle, SQL Server, SQL Server Express, or another enterprise DBMS installed. A local geodatabase is usually an ArcSDE geodatabase with SQL Server Express installed locally to house and manage the product library.

The DBMS used for the geodatabase should be configured before the product library is set up with the default geometry storage. See geodatabase storage in relational databases or geodatabase parameters for more information.

The MAXBLOBSIZE value is -1 by default. However, if you are using Oracle or another enterprise DBMS, make sure that this value is set to -1 and the TCPKEEPALIVE value is set to 1. This command should be used from the command prompt of a machine where ArcSDE is installed.

For example:

sdeconfig -o alter -v MAXBLOBSIZE=-1-i <service> -u sde -p <sde_password>

For more information, see the ArcSDE Administration Command Reference.

You can download a Portable Document Format (PDF) version of the book from the ESRI Support Center Web site (login required): ArcSDE Server documentation

Remarque :

The ArcSDE documentation refers to the parameter name as Property Name in the command line examples.

Use the steps below if you are using SQL Server Express or SQL Server to configure the MAXBLOBSIZE and TCPKEEPALIVE parameters.

Étapes :

1. Open SQL Server Management Studio Express.
2. Click Connect on the Connect to Server dialog box that appears.
3. Expand Databases, the geodatabase you are using for the product library, and Tables.
4. Right-click on the SDE_server_config table and click Edit Top 200 rows.
5. Find MAXBLOBSIZE in the prop_name field and change it to -1 in the num_prop_value field if it is another value.
6. Find TCPKEEPALIVE in the prop_name field and change it from 0 to 1 in the num_prop_value field.
   Attention :

   If you are using a local geodatabase and you modify the parameters while the Catalog window is open, you need to refresh (or disconnect and reconnect to) your SQL Server Express instance to confirm that the geodatabase has the new settings. You can right-click the database server and click Refresh.

7. Close SQL Server Management Studio Express.

Defining and upgrading the geodatabase as a product library

After the geodatabase has been created, various tables and feature classes that are part of the product library need to be added to it. This process can be completed in ArcMap.

The steps in this section are for defining and upgrading the geodatabase as a product library in ArcMap.

Étapes :

1. Start ArcMap.
   Conseil :

   If the ArcMap - Getting Started dialog box appears, you can open a new or existing map document. You can also check the Do not show this dialog box in the future check box and click Open.

2. On the main menu, click Customize > Production > Production Properties.

   The Production Properties dialog box appears.

3. If necessary, click Data Management.
4. Click the cell next to Workspace in the Product Library section and click the ellipsis (...) that appears.

   The Please browse to the location of the Product Library Workspace dialog box appears.

5. Navigate to the product library database.
6. Click Open.

   The Upgrade Workspace dialog box appears.

7. Click Yes to upgrade the geodatabase you want to use as the product library.

   The Product Library Workspace Upgrade window appears and displays a progress bar while the geodatabase is updated. The Production Properties dialog box appears once the process is complete.

8. Click OK.

Granting privileges to product library components

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

The permissions need to be assigned to the CKB_USERS role.

Both the administrator and other user accounts in the underlying database management system should have appropriate privileges and roles assigned to them. When you set up your connection to your spatial database, ensure you are connecting as the appropriate user.

Étapes :

1. Start ArcCatalog.
2. Expand one of the following:
   • Database Servers if using a SQL Server Express geodatabase
   • Database Connections if using an Oracle, SQL Server, or another enterprise geodatabase
3. Double-click the product library administrator connection geodatabase to connect to it.
4. Select all tables except PCAT_PERMISSION, right-click, then click Privileges.
5. Type CKB_USERS into the text box on the Privileges dialog box.
6. Check the check box next to SELECT, UPDATE, INSERT, and DELETE.
7. Click OK.
8. Select PCAT_PERMISSION, right-click, then click Privileges.
9. Type CKB_USERS into the text box on the Privileges dialog box.
10. Check the check box next to SELECT.
11. Click OK.

Versioning within product library

You need to register product library components for versioning to allow them to be editable.

You need to register the product library feature classes and tables for versioning.

Étapes :

1. Start ArcCatalog.
2. Expand one of the following:
   • Database Servers if using a SQL Server Express geodatabase
   • Database Connections if using an Oracle, SQL Server, or another enterprise geodatabase
3. Double-click the product library administrator connection geodatabase to connect to it.
4. Right-click each feature class in your product library and choose Register as Versioned.

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

5. Click OK.
6. Right-click each table in your product library and choose Register as Versioned.

   If you are using the Aeronautical Solution, do not register the following tables as versioned:

   • ELM_CATEGORIES
   • ELM_ELEMENTS
   • ELM_PRODUCTS
   • ELM_SOLUTIONS
   Conseil :

   If you do not have the four ELM_ tables, you can add them to your product library now or wait for them to be generated when you store a database element in an element table.

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

7. Click OK.

Creating database connections for product library users

Database connections need to be created for the other product library users if the product library is stored in Oracle, SQL Server, or another ArcSDE geodatabase licensed through ArcGIS Server Enterprise. If your product library is stored in SQL Server Express, you can skip this section, since other users will only need to add a database server connection (first section of this workflow).

If you want to create a database connection for SQL Server, go to Making a direct connection from ArcGIS Desktop to a geodatabase in SQL Server. If you want to create a database connection for Oracle, go to Making a direct connection from ArcGIS Desktop to a geodatabase in Oracle.

Remarque :

For step 6, if using database authentication, type the user name of the product library user for which you want to create a database connection.

Once you have performed all the steps in this workflow, the product library workspace is ready for you to create the solution, product class, series, and users and user permissions. Other users still need to define the product library workspace in their client machine to be able to create and manage data and/or products.