You are here: Administration Riser Bar>Maintaining Repository Definitions>Adding New Repositories

DataFlux Data Management Studio 2.5: User Guide

Adding New Repositories

Overview

You can add a new DataFlux Data Management Studio repository to store profiles, business rules, jobs, and other objects. You can perform the following tasks:

See also Repository Usage Notes.

Plan a New Repository

To add or update a repository, you will access the Repository Definition dialog. This dialog is used to create a repository definition file (.RCF file). There are two main sections of the Repository Definition dialog, as shown in the next figure: 

Data storage - specifies a database for the storage of data explorations, profiles, and all objects in the Business Rule Manager (rules, tasks, custom metrics, etc.). Supported databases include SQLite and other database formats.

File storage - specifies a separate storage location for objects that are stored as files, such as data jobs, process jobs, queries, *.sas files (SAS code files), and Entity Resolution Output files (*.sri files).

Administrators should review the storage options for repositories, identify the appropriate databases and physical paths, and create the required DSN connections, as described in Maintaining Data Connections. For more information about supported database formats, see "Repository Storage" in the DataFlux Data Management Studio Installation and Configuration Guide. See also Repository Usage Notes.

Use the following table to plan how you will set the attributes for your new repository.

Goal Repository Attributes
Create a standalone repository for your own use. For more information, see Work with Private and Public Repositories.
Share a repository among multiple Data Management Studio users.

Due to locking issues, file-based repositories and Microsoft Access-based repositories are not recommended for production systems. Accordingly, see the "Store the repository in a database format other than SQLite" row in this table.

Set your repository definition to public. For more information, see Work with Private and Public Repositories.

Store the repository in SQLite database format.

Specify a Database file.

Note Note: You can perform only one transaction at a time in a repository based on the SQLite database format.

Store the repository in a database format other than SQLite.

Specify an existing Database connection. For information about connections, see Maintaining Data Connections.

Note Note: To create a new repository in a database, you must have the appropriate permissions to create a table for the database and schema in which the repository will be stored. Contact your Database Administrator for information about access privileges.

Note Note: Repositories are supported on Teradata via ODBC. However, repositories on Teradata via the SAS Federation Server are not supported.

Note Note: If you create a repository that stores tables on an SQLServer database or Sybase database, take one of the following actions to prevent collisions with existing keyword definitions on the database: (a) Specify a table prefix in the database connection definition; or (b) Specify Enabled Quoted Identifiers on the Advanced tab of the database connection definition.
Work with DataFlux Data Management Studio objects that are stored as files, such as data jobs, process jobs, queries, *.sas files (SAS code files), and Entity Resolution Output files (*.sri files). Most users will want to do this. Specify a Data storage location and a File storage location.
Work exclusively with objects that are stored in database format, such as profiles, rules, and tasks. Never work with DataFlux Data Management Studio objects that are stored as files. Specify a Data storage location but no File storage location.
Change the default location of the DataFlux Master Data Foundations content for a repository. Specify a path for the macro variable MDM_REPOSITORY_ROOT_FOLDER in a configuration file, such as app.cfg. By default, the DataFlux Master Data Foundations content will be stored the master_data subfolder in the File storage area.

For more information about the databases that are supported for data storage, or the platforms that are supported for file storage, see "Repository Storage" in the DataFlux Data Management Studio Installation and Configuration Guide.

Work with Private and Public Repositories

At start up, DataFlux Data Management Studio looks for repository definition files (.RCF files) in two locations: 

For best performance, each DataFlux Data Management Studio user should work in his or her individual repository. Accordingly, when you add a new repository, the Private checkbox is selected by default. If Private is selected, then the repository definition file will be saved in a user-specific folder. Other users will not be able to see a repository whose definition file is stored in a user-specific folder.

If Private is not selected, then the repository definition file will be saved to a subfolder in the DataFlux Data Management Studio installation directory. All users who can access DataFlux Data Management Studio on that computer will be able to see a repository whose definition file is stored in the installation directory. These users would also need to be able to access the Data storage location and File storage location (if any) that is specified in the repository definition file.

Note Note: If you attempt to create a public repository, and you get an error that says that you cannot access the path that is specified for Data storage or File storage, then change the path to a path that is accessible to those who will share the public repository.

It is possible for multiple users to share a repository over a network if these users can access the repository definition file, the Data storage area, and any File storage area for that repository.

Add a New Repository

If you want to create a repository in a database management system, you must first create a DSN connection to that system, as described in Maintaining Data Connections. Perform the following steps to add a repository definition file (.RPS file) and create a new repository in the location that is specified in the definition file.

  1. Click on the Administration riser bar.
  2. In the Repository Definitions pane, click on the New button to create the new repository.
  3. The New Repository Definition dialog appears. Enter the name of your repository in the Name field.
  4. In the Data storage section of the dialog, specify a Database file or a Database connection for your new repository. The Database connection must have been created earlier.

    Example Database file: 
    C:\Documents and Settings\USER_NAME\Application Data\DataFlux\Repository\Sample\DataStorage\DataManagement.rps

    Example Database connection: 
    DB2_SERVER1_ODBC_REPOS
  5. If you want to have multiple repositories defined in the same database scheme, consider adding a unique prefix in the Table prefix field. A unique table prefix would enable you to identify the tables that are associated with a particular repository.
  6. If you want to work with DataFlux Data Management Studio objects that are stored as files, specify a File storage location. This physical path must be accessible to everyone who needs to access the data jobs, process jobs, queries, *.sas files (SAS code files), or Entity Resolution Output files (*.sri files) that will be stored there.
  7. Select or deselect the Connect to repository at startup checkbox or the Private checkbox as appropriate. For more information, see Work with Private and Public Repositories.
  8. Click on the OK button. A new repository definition file (.RCF file) will be created in the user settings area or in the etc/repositories folder in the Data Management Studio installation directory. A new repository will be created in the location that is specified in the Data storage field of the definition file. You will be connected to the new repository.
  9. To verify that you are connected to the repository, select the repository in the Administration riser bar. The Status pane should indicate that you are connected to the repository.

Note Note: Do not create a repository definition file (.RPS) in the file storage location. This practice prevents manipulating the file through DataFlux Data Management Studio, and it triggers unneeded update events in the file storage area every time that the definition file is updated.

Convert Repositories from Earlier Releases

If you upgrade DataFlux Data Management Studio from an earlier release, you might be prompted to upgrade your repository. Be sure to back up any repository before upgrading it.

If you specify the location of a dfPower Studio repository in the Add Repository dialog, the repository will be converted to DataFlux Data Management Studio format. Some objects in the repository will be converted and will be ready to use, and others will require additional processing. For more information, see the DataFlux Migration Guide.

Note Note: DataFlux Data Management Studio does an in-place upgrade of a dfPower Studio repository. dfPower Studio cannot access a repository that has been converted to DataFlux Data Management Studio format.

Accordingly, make a copy of the dfPower Studio repository to be upgraded, and then upgrade the copy rather than the original. Upgrading a copy of your repository enables you to preserve your original dfPower Studio content.

Save Repository DDL

The Save Repository DDL button is active for repositories that are stored in a database management system. This button enables you to save a Data Definition Language (DDL) file for the current repository. Use the Browse button to specify a path to the DDL file.

At some sites, a DataFlux Data Management Studio user might not have appropriate privilege to create a repository in the target database. In such a case, you can use this field to create a DDL for the repository. Then a database administrator can use the DDL as a reference for creating the repository in the target database.

 

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

Doc ID: dfU_T_ReposAdd.html