Model Manager

Overview

The MIW product is capable of storing information about products, versions, and data or metadata in several different formats. You are presented with a directory structure when you log on. The top directory is presented as a node with the name of the MIR server. To the MIR server directory you may add new products that represent the products in your enterprise. The repository manager, like the model browser, is always presented as a tree. The tree itself contains hyper links that are represented by arrows; thus, when you click on an object with an arrow to the left you will jump to the location of that object in the tree. To add or remove elements from the parent root tree you need only select the tree and right click to have the following menu entries:

• Add Product - to add a new product to the root tree,
• Refresh - to refresh the screen and collapse the tree, and
• Paste - to paste a product on the root.

Fig. 1. A typical model manager presentation

In the above diagram there is one product MetaIntegration that is attached to the root localhost Repository. Under this are several more products, these products are: Data Movement Tutorial, Models, Tutorial. One can continue to follow this hierarchical product structure down through the tree structure

Meta-data-Management
1 - Information Management Architecture
1.1 - Data Stores
1.1.1 - ODS - Operational Data Stores
AP - Accounts Payable

There may be several versions associated with a given product and a product may have several sub products associated with it. These products have sub products (or child products). The child product above (AP - Accounts Payable)has only one version associated with it, Current AP - Accounts Payable.

There are several types of formats that may be saved in the database and each of these types of formats may only be attached to a version object. The list of formats are:

• Model Format - this type of format is used for saving model metadata information in the repository, this type of information can originate from the bridges
• Mapping Format - this type of metadata information is used for mapping schemas amoung model formats.
• File Format - this is used for storing a file on the server, the file is copied to the server for storage and may be copied locally by users that have permission to access this file. When creating a File Format, you must select the file to be transferred.
• Data Movement Format - this type of metadata information is used for mapping schemas amoung model formats.

Log Manager window

The Log Manager consists of several logs which can be selected by using a tab at the bottom. Above in Figure 1., the Log Manager only contains one log, the Status Log. The Status Log is used for viewing the messages that take place between the client and the user, and also between the client and the server.

There are three types of messages that will be displayed:

• informational messages are used to display messages about communication between client and server,
• warnings are used to indicate when a transaction has found something abnormal but could continue functioning, and
• errors are messages that report an irrecovarable error and the transaction or current action is aborted.

Some messages have an object associated to them. You can double-click on a message, to select this object. If there is no associated object, double-clicking will do nothing.

The other actions, you can perform on a log are:

• Select Save As in the File menu to save the contents of a log in a file
• Select Print in the File menu to print the contents of a log
• Select one or several lines and select Copy in the Edit menu to copy these lines to the clipboard so that you can paste them in another window
• Select Clear in the Log Manager menu to remove all the lines of a log

Some tools, like the Model Mapper, have their own log.