Deploying a Metadata Model

Deploying a metadata model makes the data services, database operations, or provisioned tables that are mapped to the model’s tables accessible by the table names in the model through JDBC.

When you deploy a metadata model, the mapped tables are deployed and any unmapped tables are silently ignored.

Right-click a mapped table in your metadata model and select Deploy.
Type a name in the Model Name field.
The Model Name field accepts two-part names of the form [<catalog>.]<schema>, where the optional <catalog> part defaults to your Data Federation domain name and <schema> is the arbitrary name that you give this model. The string that you enter must contain no spaces or punctuation other than - (hyphen), _ (underscore), and at most one . (period).

The names of mapped tables in the model, then, have three parts: [<catalog>.]<schema>.<table>. If you choose to enter the database name as the model name (<schema>), you can refer to objects mapped to tables in this model as [<catalog>.]<database>.<table>.
Click OK.

If Data Federation encounters errors, a message appears. Otherwise the deployment begins.

The metadata model is added to the data catalog’s Metadata directory when you see a message reporting successful deployment.

You can check your newly deployed object in the data catalog:

If the deployment fails, the operation stops, newly provisioned objects are removed from the grid, and WorkSpace Data Federation displays an error.