DataFlux Data Management Studio 2.6: User Guide

Add or Edit Repository Definition

You can use the Repository Definition dialog to add or update a repository definition file. DataFlux Data Management Studio and DataFlux Data Management Server use a repository definition file to access a DataFlux repository.

When you click OK for a new definition, a new repository definition file (.RCF file) will be created. It will be saved to the location specified by the selection or deselection of the Private checkbox. A new repository database will be created in the location that is specified in the Data storage section of the definition. You will be connected to the new repository. DataFlux Data Management Studio jobs and related objects will be stored in the folder specified in the File storage section of the definition.

Here is a description of the fields and controls on this dialog.

Name - Specifies the name of the repository as it appears in DataFlux Data Management Studio.

Data Storage

The Data storage section of the dialog enables you to specify a storage method for the repository database. This database stores metadata such as business rules, tasks, and profiles. The Data storage section has two sets of controls: database file controls and database connection controls. Use one or the other to specify a metadata storage method.

Database File Controls

Database file - When selected, enables you to specify an SQLite database file for a new repository or an existing repository. The tables for the repository are stored in the SQLite file that is specified in the Location field.

Location - Specifies the physical path for an SQLite database file. Specify an .RPS file at the end of the path, such as Repository2.rps. If this file does not exist, it will be created when you click OK in this dialog.

The path to the SQLite database file can be almost any physical path that is accessible by DataFlux Data Management Studio. File-based repositories should not be stored in the File storage location below, however.

It is possible to specify a location that is remote from the DataFlux Data Management Studio host. However, the client might perform best when the SQLite database file is local to DataFlux Data Management Studio. Use a UNC path, not a path with a mapped drive letter, to specify a location that is remote from the DataFlux Data Management Studio host.

Example: \\HostName.MyDomain.com\path.

NoteNote: Due to locking issues, file-based repositories are not recommended for production systems. Use a database connection for production systems.

Database Connection Controls

Database connection - When selected, enables you to specify a DBMS connection for a new repository or an existing repository. The tables for the repository will be stored in the database format that is specified in the Name field.

Name - Enables you to select an ODBC DSN connection or a SAS Federation Server connection for a new repository or an existing repository. This connection must be created before you can select it here.

Table prefix (optional) - Specifies a table prefix. A unique table prefix enables you to distinguish the tables that are associated with a particular repository from other tables that might be stored in the same database connection. If you enter a prefix that includes a period, the portion to the left of the period will be considered to be the name of an existing schema. For example, you specify WIP.REPOS as a prefix, the repository creation will fail if there is no WIP schema in the database.

Test Connection - Enables you to test the database connection, when applicable.

Save Repository DDL (optional) - Active for repositories that are stored in a database management system. This button enables you to save a Database Definition Language (DDL) file for the current repository. The file includes a series of statements that create the repository, such as DROP TABLE, DROP INDEX, CREATE TABLE, CREATE INDEX, AND INSERT VALUES. Use the Browse button to specify a path to the DDL file. You can use the DDL file to understand what permissions are required in order for DataFlux Data Management Studio to create a repository in the target database. Also, in some cases you might not have appropriate privilege to create a repository in the target database. In that case, you can save a DDL file and give it to a database administrator. The administrator can use the DDL file as a reference for creating the repository in the target database.

File Storage

The File storage section of the dialog enables you to specify a folder for DataFlux Data Management Studio objects that are stored as files, such as data jobs, process jobs, queries, SAS code files (.SAS files), and Entity Resolution Output files (.SRI files).

NoteNote: DataFlux Data Management Server ignores the File storage section of a repository definition. It puts jobs in the default location for the server or in a folder specified in the DMSERVER/JOBS_ROOT_PATH option in dmserver.cfg.

Folder - Specifies the physical path where DataFlux Data Management Studio jobs and other file-based objects are stored. The file storage location can be any physical path that is accessible by DataFlux Data Management Studio. It is possible to specify a location that is remote from the DataFlux Data Management Studio host. However, the client might perform best when the file storage location is local to DataFlux Data Management Studio.

Connect to repository at startup - When selected, specifies that a connection is established to the repository when DataFlux Data Management Studio is started.

Private - Specifies whether the repository definition file is saved to a private location for the current user or to a public location that might be accessible to other users. The default is private. The default is best in most cases. The default private location is a user-specific folder, such as: C:\Documents and Settings\<userid>\Application Data\DataFlux\. The default public folder is the etc/repositories folder in the DataFlux Data Management Studio installation directory.

OK - When you click OK for a new definition, a new repository definition file (.RCF file) will be created. It will be saved to the location specified by the selection or deselection of the Private checkbox. A new repository database will be created in the location that is specified in the Data storage area of the definition. You will be connected to the new repository.


Related Topics

Documentation Feedback: yourturn@sas.com
Note: Always include the Doc ID when providing documentation feedback.

Doc ID: dfU_AddEdit_RepCon.html