Model Bridge

Exporting a Model

Export Tab

For most tools the first step in exporting a model to select the export format or API to use, and ensure that the application programming interface (API) connection for the bridge is installed and configured properly. See the bridge tools tips section for more details on how to verify that these interfaces are properly configured.

Once you have ensured that any API configuration is completed, you should:

1. Specify the mandatory (identified by *) bridge parameters, e.g., the export file/directory,
2. Possibly modify the other default bridge parameters,
3. Optionally specify subsets of the model to be exported,
4. Optionally specify a remote MIMB Web Service to execute the bridge on, and
5. Click on the "Export" button.

Upon bridge execution, the Log Manager window shows the bridge progress, any warnings or errors, and notifies you of bridge completion.

Once the export bridge has completed successfully, you may open the resulting model in the tool that you exported to. For additional detailed information and instructions on how to view the model in the tool, please again refer to the tool tips for the export bridge referred to above.

Tip:For many bridges, the export format filename extension (e.g. .er1 for CA AllFusion Erwin Data Modeler v4.x) is already associated by the operating system with the actual application. If this is the case, you may quickly view the exported model. Simply click on the browse button in the File * parameter. Then, in the Find a File dialog box, right click on the exported file, and selection Open using the appropriate design tool. You may also use the Open button to perform the same action.

5.3.2. Bridge Parameters

For most bridges, you specify a path to an import file, or the path to the API in the bridge parameters. Additionally, you may change the behavior of the bridge by modifying one or more of its parameters.

To modify a parameter, simply select the parameter line and click in the value area. You will then be allowed to choose a new value from a predefined list or to enter a specific value. In the case of a path or filename parameter, you will be given a browse button, which opens a file find dialog box, allowing you to select the file or directory for that bridge parameter.

You can save permanently the values you have set by clicking on the Save Current Settings button. If you switch to another bridge and back to this one or if you stop the tool and restart it, the values you have saved will be reestablished.

The Bridge Defaults button allows you to reset the values to the default values provided by the bridge.

The Recall Settings button allows you to restore previously saved parameter values.

Creating Model Subsets

Oftentimes it is necessary to export only part of a model. Saving only part of a model allows you to place only the classes/diagrams you want into the exported model. It can also be a workaround for capacity limitations in the destination design tool.

When MIMB creates a subset of a model, it starts from the elements which you have selected for inclusion in the destination model and then adds whatever elements that are necessary to keep the model consistent and meaningful. For instance if you have selected a class, MIMB will add the classes it inherits properties from, the parent's attributes, the types used by these additional attributes, etc.

When a package or a diagram is included in the destination model, its elements are also included. These elements may include the classes and/or the relationships between classes. If a relationship is inserted in the sub-models, the ends of the relationship are also included.

Note:Some objects in the imported metadata do not constitute a consistent subset, and thus cannot be moved by themselves to the model subset that you are creating.

Now select the elements you want to subset and click on the single right arrow button to include those elements in the subset model. To include all of the elements in the subset model click on the double right arrow button. To remove elements from the subset model, click on that element and click on the single left arrow button. To remove all of the elements in the subset model, click on the double left arrow button.

Once you are satisfied with the subset model, click on the Subset button. The Log Manager window will display progress of the subset creation process and will indicate successful completion.

Once you are satisfied with the subset model, click on the Subset button. The Log Manager window will display progress of the subset creation process and will indicate successful completion.

Upon successful completion of the subset model creation, you may return to the Export tab to export the subset model, or the View tab to view the current subset model.

Mapping Specification

The Mapping... button provides an interactive report detailing how the selected bridge maps (and thus imports) the meta-data from any the source tool into the MIR Meta-model, as well as, how this meta-data in turn maps (and thus exports) the same meta-data to any export format or tool. These mapping specifications reflect the format bridge validation and operational specifications.

You may save the list to a comma separated file format (.CSV) or as XML using the Save As... button.

Remote MIMB Web Service Bridge Execution

Many bridges use an application programming interface (API) provided by the tool vendor in order to execute. In these cases a particular client software version generally must be installed on the machine (e.g., the workstation) on which MIMB is installed and running.

If you are attempting to run such an API-based bridge and do not have the appropriate tool client installed, you may still execute the bridge remotely, using either a local or remote file reference. The Execute On option allows you to execute the bridge on another machine. In order for this operation to work, the following items MUST be configured correctly on the remote machine (where you wish to run the bridge from):

1. Meta Integration Web Services must be installed and have a valid license key or shared license from a license server (see MIMBReadme.html)
2. Meta Integration Web Services must be started either directly as a service or using the Meta Integration Web Services Start selection in the Start->Meta Intetegration menu
3. The client for the particular tool must be installed and functioning in conformance with the tool tip for the bridge selected.

In order to run the bridge remotely on that machine, simply select it from the Execute On pull-down. If the particular remote machine you want is not in the list, then you may select Add/Remove/Edit or choose the "..." button, and add the host name/ip address and port (as specifed in MIRSetup.xml on the remote machine).

When executing a bridge remotely, references to supporting files may either refer to the local machine, or the remote machine, but not both. You select which to use with the pull-down to the right of the Execute On pull-down.