Set Up New Mart Instances

Owned by Kavitha Thangaswamy (Unlicensed)
Last updated: Jul 25, 2023 by Pamela Totas (Deactivated)
4 min read

You set up and manage all of your mart instances from the same interface, and you configure them all using the same set of available field attributes and rules as you would use to build a single mart. Once you have set up your marts, all of their configuration information, for all models in all instances, is located together in the same set of tables in the Eagle warehouse.

Your database administrator (DBA) sets up new Data Mart instances. Eagle provides a set of database scripts that your DBA can run to do this. The Eagle scripts are provided with the product installation. There are two folders, one with scripts for Oracle databases, and one with scripts for SQL Server databases. You can use both types to set up schemas in both types of database management system. There are Read Me files in the EAGLE_DOCUMENTS/ folder that explain the use of the installation and upgrade scripts for setup of a new Mart instance.

An exception to the rule is the instance EAGLEMART used by Eagle's new packaged reports. EAGLEMART is created when upgrade scripts are run.

Setup for Remote Marts Running from Solaris or Linux to SQL Server

You can build a Data Mart table in a SQL Server database where the Eagle application runs on a UNIX or Linux platform.

Use this functionality in Data Mart the same way as you any would use any of the other multiple data marts. You must complete the following setup before using this feature:

  1. Use the scripts supplied by the Eagle installation to create Data Mart schemas as required in the SQL Server database.

  2. Click http://web.datadirect.com/product-downloads/odbc-64-bit-unix-linux.html to obtain the required driver from Data Direct.
    Eagle has used and tested this version of the driver: Progress Data Direct Connect 64 for ODBC UNIX and Linux Platforms Release 6.0 Service Pack 3 February 2010

  3. Install the Data Direct driver on the Unix/Linux machine.

  4. Add an ODBC data source for the SQL Server database in the odbc.ini file.

  5. Use tests supplied with the driver to verify a successful connection from the Unix/Linux machine to the SQL Server database.
    For each PACE server and application server that has to be able to connect to a SQL Server database, you must modify the appropriate "paceserver" and "paceappserver" scripts, located in the "server" and "appserver" directories of the Unix/Linux server respectively.

  6. Add the following lines below the "export ORACLE_HOME" line: LD_LIBRARY_PATH=<path_to_directory_where_odbc_is_installed>/lib export LD_LIBRARY_PATH ODBCINI=<path_to_odbc_ini_file>/odbc.ini export ODBCINI

  7. Replace <path_to_directory_where_odbc_is_installed> and <path_to_odbc_ini_file> with the appropriate absolute paths.

  8. From Data Mart, use Manage Database Connections to register the connection to the SQL Server Database. You must use the name of the ODBC data source that you created in step 3 and referenced in step 4 when registering this connection.

  9. Once you have registered and tested the connection, use Manage Data Marts to register the particular mart or marts you have set up on the SQL Server database.

Multiple Mart Specific Features

There are four options you use when working with multiple marts. They are located on the Data Mart Manage Mart, Execution Log, and View Mart data windows.



The following table lists the multiple mart specific features.

Option

Description

Option

Description

Data Mart Instance drop-down

Use to select which instance you want to control. You can change your selection at any time to control a different instance. Once you have selected a Mart instance to control, all of your work pertains only to that instance. This includes Mart configuration, setup of models, snapshots, schedules, and extensions. It also includes the execution logs you monitor and the Mart data you view with View Mart Data. As you move from one section of the Mart to another, you continue to work on the instance you have selected. Also, when you start a new user session, the instance you are working on is the instance you last had selected.

Manage Data Marts link

Click this link to enter name and location information used to register the presence of each schema set up by your DBA. You do not have to enter any information for the default instance, the DATAMART schema in the Eagle warehouse that exists even if you are not using multiple marts. The same is true for EAGLEMART.

Manage Database Connections link

Click this link to record connection information for each separate database housing your mart instances. You do not have to enter any information for the default connection to the Eagle warehouse.

Copy Model between Marts

Select to quickly and easily copy models and selected model fields from one Mart instance to another within the same environment. See Run Copy Model for more details.

If you do not want to use multiple marts, you do not have to select any of these options. The Default Mart instance appears by default as the selection in the Data Mart Instance dropdown. You do not have to register the Default Mart.