You can use the IBM® Rational® Data Architect MetaBroker® to
transfer metadata between Rational Data Architect version 7 and the repository
of IBM WebSphere® Metadata Server.
The MetaBroker supports
both Rational Data
Architect version 7 and Rational Data Architect version 6 Fixpack 1. With
either version of Rational Data Architect, you can use the MetaBroker to
transfer metadata in the following ways:
- Import categories and terms from the repository into Rational Data
Architect to create glossary models.
- Export metadata from glossary models in Rational Data Architect to create categories
and terms in the metadata repository.
- Export metadata from physical models in Rational Data Architect to the repository.
- Import metadata into the repository from physical models in Rational Data
Architect.
- Import metadata from glossary models in Rational Data Architect into the repository
to create categories and terms.
When you use the MetaBroker with Rational Data Architect version 7,
you have the following additional options when working in Rational Data
Architect:
- You can transform a domain model or logical model to a glossary model
when you are exporting metadata to the repository.
- You can import categories and terms from the repository and transform
the glossary model to a logical model during the import process.
In addition, when you use the MetaBroker with Rational Data
Architect version 7, you can use the glossary model editor to see the following
properties of categories and terms that are not available in Rational Data
Architect version 6 Fixpack 1:
- Subcategories and referenced terms of a category
- Synonyms and related terms of a term
- Usage, example, and status of a term
By using the MetaBroker,
you can combine the business semantics of the
IBM WebSphere Business Glossary with
the modeling capability of Rational Data Architect to create standardized data
models that comply with your business rules. You can then transform the data
models into physical models, and use the physical models to create jobs in
the Designer client. A typical scenario might involve the following steps:
- A business analyst defines categories and terms in the glossary by using
standard synonyms and abbreviations for the terms.
- A data architect uses the MetaBroker to import the structure
of categories and terms into Rational Data Architect either as a glossary model
or as a logical model.
- The data architect uses the terms to develop the glossary model or logical
model and eventually transform it into a physical model with tables, functions,
and stored procedures.
- The data architect can use term synonyms to discover relationships between
the imported model and a legacy data model.
- A WebSphere DataStage® developer
imports the physical model into the Designer client, where the model can be
used to create jobs.
You can also use the MetaBroker in the following scenarios:
- Import metadata from a glossary model in Rational Data Architect to the metadata
repository, where the metadata appears as categories and terms. In WebSphere Business Glossary, use
those terms to classify metadata objects in the repository.
- Import metadata from a physical model in Rational Data Architect to the metadata
repository, where the metadata can be used by tools that interact with the
repository. For example, you can use the imported table definitions in a job
in IBM WebSphere DataStage and QualityStage Designer,
analyze the columns in IBM WebSphere Information Analyzer,
or assign stewards to the metadata objects by using WebSphere Business Glossary.
For detailed information on using the MetaBroker from Rational Data
Architect version 7, see the information center for Rational Data Architect. For detailed
information on using the MetaBroker from Rational Data Architect version 6 Fixpack
1, see the documentation for Fixpack 1.
You can to start the MetaBroker from Rational Data Architect, from the Designer
client, and from Import Export Manager. Where you start the MetaBroker determines
the types of metadata that you can import and export.
If you want to |
Start the MetaBroker here |
Import metadata from physical models in Rational Data
Architect into the repository for use primarily in WebSphere DataStage and QualityStage jobs. |
Designer client |
- Import metadata from physical models in Rational Data Architect into the repository
for use by software tools that access the repository.
- Import metadata from Rational Data Architect into the repository to create
glossary metadata.
- Export glossary metadata from the repository to Rational Data Architect.
|
Import Export Manager |
- Import glossary information from the metadata repository.
- Export metadata to the repository as categories and terms.
- Export metadata from physical models to the repository.
|
Rational Data Architect |