Objects can be moved from the left hand object tree by double clicking on an object name or by using the > button. This tab allows you to select the objects to delete in the destination repository.

 

 

Applications are loaded via the Setup Administrator utility. The normal process for implementing an application would be as follows:

Refer to the Setup Administrator manual for more information about loading an application.

Any group of objects can be imported into the current metadata repository from another repository. If an object already exists in the target repository then it is either skipped or replaced depending on the type of import undertaken. If an object is to be replaced as part of an import, a version of the object is created prior to its replacement.

To import an object or group of objects select the Tools/Import Metadata Objects menu option. A dialog as below will appear. The two options are IMPORT or REFRESH. An import will not replace an existing object of the same name. A refresh will version and replace any existing object of the same name.

Enter the connection, and a database user name and password that has access to the source metadata repository. Finally, enter the user name of the metadata repository you want to import from. In most situations the 'user name' and 'meta repository' would be the same. However, if you only have read access to a meta repository then it may be necessary to login to the database under a different user name from that of the repository you are trying to import from.

You are not permitted to select the current meta repository in the 'Meta Repository' field, but are permitted to login using the existing repository username. Once a successful logon is completed the contents of the source repository are loaded and the following dialog appears.

Select an object by double clicking on it or by selecting and using the > button. If an object such as a table is chosen then any related scripts, procedures and indexes are also selected. They can be removed if required. A target project can be selected.

Once all required objects are selected the import will commence when the OK button is clicked.

On completion a dialog box will appear notifying of the number of each type of object imported, and skipped.

Language Files are loaded via the Setup Administrator utility. The normal process for implementing a Language file would be as follows:

Refer to the Setup Administrator manual for more information about loading a Language File.

 

Testing applications are loaded via the Setup Administrator utility. Refer to the Setup Administrator manual for more information on how to load an application.

A testing application set consists of a Procedure and an XML script and provides the ability to define a series of tests against data warehouse objects; either comparing them to an expected value or to the results of a query.

Once the application set has been loaded, the Procedure and the XML script will be visible in the left pane.

The XML script contains the test definitions. Each test is a new XML node in the comparison query. The procedure simply runs the test and determines whether the tests are passed or not. This is most likely to be run as a scheduled job within QAD Data Warehouse Designer. To create a job

 

 

 

It is possible to create and load applications from the command line by running a bat file. The QAD Data Warehouse Designer Application directory contains an example bat file WSL_Application_Create_Restore_Point_and_Load.bat for creating and loading.

If you right mouse on this file and choose Edit you will see the steps outlined as well as the details on the options available.

The first step creates a restore point application (R) based on objects about to be loaded. This process calls the command line functionality of Data Warehouse Designer and creates the application file.

The second step loads an application (A) into a test QAD Data Warehouse Designer repository. It uses an xml file to specify various options, calls the command line automation functionality of Setup Administrator and loads the application (A). The QAD Data Warehouse Designer Application directory contains example xml files:

The tags in the xml file need to be edited as the login/connection details etc need setting.

The Batch Application Create options and the Batch Application Load options are listed at the end of the bat file. The values for these variables will also need to be customized before running this file.

The process typically involves the following steps: