Metadata Manager Custom Metadata Integration Guide

10.5.9
- 10.5.8
- 10.5.7
- 10.5.6
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.0

Back Next

Rule Element Configuration for Endpoints

Use the rule element to define a linking rule that Metadata Manager uses to link endpoints in the source resource to matching objects in the target resource.

The following table describes the attributes for the rule element:

Attribute	Description
name	Required. Name of the rule. The rule name must be unique in the rule set.
direction	Optional. Indicates whether the link originates from the source object or from the target object. For endpoint links, the direction must be Auto. If you do not use the direction attribute, Metadata Manager uses Auto by default.

A rule element must contain the following elements:

sourceFilter: Filters the list of possible endpoints in the source resource that you want to link. A sourceFilter element must contain an endpoint element.

The following table describes the attributes for the endpoint element:

Attribute
Description

class
Optional. Name of the class that the endpoint belongs to. Use a pipe (|) to separate multiple class names.
Either the class attribute or the type attribute is required.

type
Optional. Type of the class that the endpoint belongs to. Use a pipe (|) to separate multiple class types.
Either the class attribute or the type attribute is required.

connection
Optional. Name of the connection that the endpoint uses to connect to an external source database. To view the list of all connections in the Business Intelligence, Data Integration, or Data Modeling resource, view the
Connection Assignment
tab in the resource properties.
In a rule set definition file, you can use a parameter to represent the connection name. Enter the connection name in the following format:

connection="${<parameter_name>}"

package
Optional. Name of the package or the database schema that the endpoint connects to in the external source database. To view the list of all schema names, view the
Connection Assignment
tab in the properties of the Business Intelligence, Data Integration, or Data Modeling resource.
In a rule set definition file, you can use a parameter to represent the package name. Enter the package name in the following format:

package="${<parameter_name>}"
targetFilter: Filters the list of possible objects in the target resource that you want to link. A targetFilter element must contain an XML element named element.

The following table describes the attributes for the XML element named element:

Attribute
Description

class
Optional. Name of the class that the object belongs to. Use a pipe (|) to separate multiple class names.
Either the class attribute or the type attribute is required.

type
Optional. Type of the class that the object belongs to. Use a pipe (|) to separate multiple class types.
Either the class attribute or the type attribute is required.

condition
Optional. Expression that filters the list of possible objects to link.

An element can contain another element. The objects selected through the class, type, and condition attributes for this element must be immediate children of the objects selected through the containing element.

To specify a feature in a packaged or universal resource, the structure or the parent class must also be selected in the targetFilter. For example, the following targetFilter element includes the parent table as a containing element of an Oracle column:

<targetFilter> <element class="Oracle Table"> <element type="Column"/> </element> </targetFilter>
link: Defines the expression that specifies which filtered source and target objects Metadata Manager links. Contains a required condition attribute.

Attribute	Description
class	Optional. Name of the class that the endpoint belongs to. Use a pipe (\|) to separate multiple class names. Either the class attribute or the type attribute is required.
type	Optional. Type of the class that the endpoint belongs to. Use a pipe (\|) to separate multiple class types. Either the class attribute or the type attribute is required.
connection	Optional. Name of the connection that the endpoint uses to connect to an external source database. To view the list of all connections in the Business Intelligence, Data Integration, or Data Modeling resource, view the Connection Assignment tab in the resource properties. In a rule set definition file, you can use a parameter to represent the connection name. Enter the connection name in the following format: connection="${<parameter_name>}"
package	Optional. Name of the package or the database schema that the endpoint connects to in the external source database. To view the list of all schema names, view the Connection Assignment tab in the properties of the Business Intelligence, Data Integration, or Data Modeling resource. In a rule set definition file, you can use a parameter to represent the package name. Enter the package name in the following format: package="${<parameter_name>}"

Attribute	Description
class	Optional. Name of the class that the object belongs to. Use a pipe (\|) to separate multiple class names. Either the class attribute or the type attribute is required.
type	Optional. Type of the class that the object belongs to. Use a pipe (\|) to separate multiple class types. Either the class attribute or the type attribute is required.
condition	Optional. Expression that filters the list of possible objects to link.