Manta Flow Open Manta Integration Export Configuration

Transformation Object and Lineage Export

Common Configuration

The basic configuration of this feature is on the Configurations > Integrations > Open Manta Integration Export > Open Manta Integration Export Common page in the Manta Admin GUI.

Property key	Description	Default value	Example
manta.openExport.url	Specific URL for services provided by the internal metadata repository server	${manta.repository.private.api}/openexport	${manta.repository.private.api}/openexport
manta.openExport.exportTransformationLogic	Flag whether or not to export the transformation logic	true	false
manta.openExport.exportTransformationTag	Flag whether or not to export the transformation tags	false	true
manta.openExport.exportViewDefinition	Flag whether or not to export lineage for view definitions	false	true
manta.openExport.exportDetailedLineage	Flag whether or not to export detailed lineage	false	true
manta.openExport.exportIndirectLineage	Flag whether or not to export indirect lineage	false	true
manta.openExport.exportInputLevelSourceCode	Flag whether or not to export the source code of nodes at the input level	false	true
manta.openExport.exportStructureItems	Flag whether or not to export structure items of non-atomic columns	false	true
manta.openExport.mantaLineageLink.baseUrl	Base URL of links to Automatic Data Lineage in the format `http(s)://<host>:<port>/<application context>` Leave empty if the Manta Server URL (the property `manta.repository.url`) should be used Only applicable when `manta.openExport.exportMantaDirectLineageLink` or `manta.openExport.exportMantaIndirectLineageLink` is set to true		https://manta.mycompany.com:8443/manta-dataflow-server
manta.openExport.exportMantaDirectLineageLink	Flag whether or not to export a hyperlink leading to Automatic Data Lineage direct lineage visualization as an Open Manta Integration Export node attribute	true	false
manta.openExport.directLineageFilter	Filters applied to Automatic Data Lineage direct lineage referenced by the link	Everything	Database objects
manta.openExport.directLineageInitialDepth	Initial depth of the Automatic Data Lineage direct lineage referenced by the link	3	2
manta.openExport.directLineageDirection	The direction of Automatic Data Lineage direct lineage referenced by the link	Both	Forward
manta.openExport.exportMantaIndirectLineageLink	Flag whether or not to export a hyperlink leading to Automatic Data Lineage indirect lineage visualization as an Open Manta Integration Export node attribute	true	false
manta.openExport.indirectLineageFilter	Filters applied to Automatic Data Lineage indirect lineage referenced by the link	Everything	Important objects
manta.openExport.indirectLineageInitialDepth	Initial depth of Automatic Data Lineage indirect lineage referenced by the link	3	2
manta.openExport.indirectLineageDirection	The direction of Automatic Data Lineage indirect lineage referenced by the link	Both	Backward
manta.openExport.exportedAttributes	List of object types and attributes to export The object type and attribute are to be provided in the format `type/attribute`. Each part is evaluated as a regular expression. The type/attribute pairs are separated by a comma ( `,`). For available types, see Export Metamodel. The type may be omitted, but keep the slash: `/attribute`. The attribute may be omitted along with the slash: `type`. Leave blank to export all attributes for all types.		com.getmanta.openmanta.Schema,/OBJECT_SOURCE_TYPE,com.getmanta.openmanta.Transformation/QUERY
manta.openExport.excludedAttributes	List of object types and attributes to exclude from export Syntax as above If left blank, all attributes matching the `manta.openExport.exportedAttributes` list will be exported. If the `manta.openExport.exportedAttributes` list is blank, all attributes not matching this list will be exported. If both are specified, only the attributes matching the `manta.openExport.exportedAttributes` list and not matching this list will be exported. If both are left blank, all attributes will be exported.	/sourceLocation,/sourceEncoding,/RESTRICTION,/CUSTOM_SOURCE,/NODE_SCRIPT_POSITION,/NODE_SCRIPT_STOP_POSITION,/NODE_TRANSFORMATION,/TRANSFORMATION_DESC_OBJ, /DESCRIPTION,/COMMENT_STRING	com.getmanta.openmanta.Schema,/OBJECT_SOURCE_TYPE,com.getmanta.openmanta.Transformation/QUERY

Dictionary Export

Unlike transformation object and lineage export, dictionary export requires a connection configuration in addition to the common configuration.

Connection Configuration

This is the most important part, specifying which Manta Connections the metadata will be exported for. Each connection configuration defines the specific part(s) of the repository tree that dictionaries have to be exported for. So, at least one connection must be configured to export dictionaries.

The connection configuration can be added on the Open Manta Integration Export page under the Manta Admin GUI Connection tab.

Property key	Description	Example
manta.openExport.dictionaries.id	Name of the connection It will be used as a subdirectory name for output files	Oracle_DWH
manta.openExport.dictionaries.filter.hierarchy	Path to nodes to be exported Path entries are separated by a slash (`/`). Use a backslash (`\`) to escape a slash or backslash. Each path entry can be set as a regular expression to define a set of nodes. Leave blank to export all nodes. There is no separate filter to exclude objects from the export in cases when the user does not want to explicitly specify a list of objects that should be exported. This filter can be used to exclude assets from exports by using zero-negative lookahead (?!X), which allows the user to specify what the path to the asset must not match.	Oracle/ORCL/DWH ((?!Salesforce).) To exclude Salesforce assets from the export ((?!Salesforce\|Netezza).) To exclude Salesforce and Netezza from the export

Property key

Description

Example

manta.openExport.dictionaries.id

Name of the connection

It will be used as a subdirectory name for output files

Oracle_DWH

manta.openExport.dictionaries.filter.hierarchy

Path to nodes to be exported

Path entries are separated by a slash (/). Use a backslash (\) to escape a slash or backslash. Each path entry can be set as a regular expression to define a set of nodes.
Leave blank to export all nodes.
There is no separate filter to exclude objects from the export in cases when the user does not want to explicitly specify a list of objects that should be exported. This filter can be used to exclude assets from exports by using zero-negative lookahead (?!X), which allows the user to specify what the path to the asset must not match.

Oracle/ORCL/DWH

((?!Salesforce).) To exclude Salesforce assets from the export

((?!Salesforce|Netezza).) To exclude Salesforce and Netezza from the export

Common Configuration

The basic configuration of this feature is on the Configurations > Integrations > Open Manta Integration Export > Open Manta Integration Export for Dictionaries Common page in the Manta Admin GUI.

Property key	Description	Default value	Example
manta.openExport.dictionaries.url	Specific URL for services provided by the internal metadata repository server	${manta.repository.private.api}/openexport/dictionaries	${manta.repository.private.api}/openexport/dictionaries
manta.openExport.dictionaries.exportStructureItems	Flag whether or not to export structure items of non-atomic columns	false	true
manta.openExport.dictionaries.mantaLineageLink.baseUrl	Base URL of links to Automatic Data Lineage in the format `http(s)://<host>:<port>/<application context>` Leave empty if the Manta Server URL (the property `manta.repository.url`) should be used Only applicable when `manta.openExport.exportMantaDirectLineageLink` or `manta.openExport.exportMantaIndirectLineageLink` is set to true		https://manta.mycompany.com:8443/manta-dataflow-server
manta.openExport.dictionaries.exportMantaDirectLineageLink	Flag whether or not to export a hyperlink leading to Automatic Data Lineage direct lineage visualization as an Open Manta Integration Export node attribute	true	false
manta.openExport.dictionaries.directLineageFilter	Filters applied to Automatic Data Lineage direct lineage referenced by the link	Everything	Database objects
manta.openExport.dictionaries.directLineageInitialDepth	Initial depth of Automatic Data Lineage direct lineage referenced by the link	3	2
manta.openExport.dictionaries.directLineageDirection	The direction of Automatic Data Lineage direct lineage referenced by the link	Both	Forward
manta.openExport.dictionaries.exportMantaIndirectLineageLink	Flag whether or not to export a hyperlink leading to Automatic Data Lineage indirect lineage visualization as an Open Manta Integration Export node attribute	true	false
manta.openExport.dictionaries.indirectLineageFilter	Filters applied to Automatic Data Lineage indirect lineage referenced by the link	Everything	Important objects
manta.openExport.dictionaries.indirectLineageInitialDepth	Initial depth of Automatic Data Lineage indirect lineage referenced by the link	3	2
manta.openExport.dictionaries.indirectLineageDirection	The direction of Automatic Data Lineage indirect lineage referenced by the link	Both	Backward
manta.openExport.dictionaries.exportedAttributes	List of object types and attributes to export The object type and attribute are to be provided in the format `type/attribute`; each part is evaluated as a regular expression The type/attribute pairs are separated by a comma ( `,`) The type may be omitted, but keep the slash The attribute may be omitted along with the slash Leave blank to export all attributes for all types		com.getmanta.openmanta.Schema,/TABLE_TYPE,com.getmanta.openmanta.Column/ORDER
manta.openExport.dictionaries.excludedAttributes	List of object types and attributes to exclude from export Syntax as above If left blank, all attributes matching the `manta.openExport.dictionaries.exportedAttributes` list will be exported If the `manta.openExport.dictionaries.exportedAttributes` list is blank, all attributes not matching this list will be exported If both are specified, only the attributes matching the `manta.openExport.dictionaries.exportedAttributes` list and not matching this list will be exported If both are left blank, all attributes will be exported	/CHECK_CONSTRAINT_MODEL,/COLUMN_CONSTRAINT_MODEL,/FOREIGN_KEY_MODEL_TECHNICAL,/INDEX_MODEL, /sourceLocation,/sourceEncoding,/RESTRICTION,/CUSTOM_SOURCE,/NODE_SCRIPT_POSITION,/NODE_SCRIPT_STOP_POSITION,/NODE_TRANSFORMATION,/TRANSFORMATION_DESC_OBJ, /DESCRIPTION,/COMMENT_STRING	com.getmanta.openmanta.Schema,/TABLE_TYPE,com.getmanta.openmanta.Column/ORDER

Model Export

Unlike transformation object and lineage export, the export of models requires a connection configuration in addition to the common configuration.

Connection Configuration

This is the most important part, specifying which Manta Connections the metadata will be exported for. Each connection configuration defines the specific part(s) of the repository tree that the models are to be exported for. At least one connection must be configured to export models.

The connection configuration can be added on the Open Manta Integration Export page under the Manta Admin GUI Connection tab.

Property key	Description	Example
manta.openExport.models.id	Name of the connection It will be used as a subdirectory name for output files	Erstudio_DWH
manta.openExport.models.filter.hierarchy	Path to nodes to be exported Path entries are separated by a slash (`/`). Use a backslash (`\`) to escape a slash or backslash. Each path entry can be set as a regular expression to define a set of nodes. Leave blank to export all nodes. There is no separate filter to exclude objects from the export in cases when the user does not want to explicitly specify a list of objects that should be exported. This filter can be used to exclude assets from exports by using zero-negative lookahead (?!X), which allows the user to specify what the path to the asset must not match.	ER\/Studio/dwh ((?!Erwin).) To exclude Erwin from the export ((?!Erwin\|PowerDesigner).) To exclude Erwin and PowerDesigner from the export
manta.openExport.models.filter.layer	Comma-separated list of layer names; each layer name is interpreted as a regular expression against the actual layer name Use a backslash (`\`) to escape a comma if it is part of a regular expression Leave blank to export all layers except the physical layer	Logical Logical,Conceptual

Property key

Description

Example

manta.openExport.models.id

Name of the connection

It will be used as a subdirectory name for output files

Erstudio_DWH

manta.openExport.models.filter.hierarchy

Path to nodes to be exported

Path entries are separated by a slash (/). Use a backslash (\) to escape a slash or backslash.
Each path entry can be set as a regular expression to define a set of nodes.
Leave blank to export all nodes.
There is no separate filter to exclude objects from the export in cases when the user does not want to explicitly specify a list of objects that should be exported. This filter can be used to exclude assets from exports by using zero-negative lookahead (?!X), which allows the user to specify what the path to the asset must not match.

ER\/Studio/dwh

((?!Erwin).) To exclude Erwin from the export

((?!Erwin|PowerDesigner).) To exclude Erwin and PowerDesigner from the export

manta.openExport.models.filter.layer

Comma-separated list of layer names; each layer name is interpreted as a regular expression against the actual layer name
Use a backslash (\) to escape a comma if it is part of a regular expression
Leave blank to export all layers except the physical layer

Logical

Logical,Conceptual

Common Configuration

The basic configuration of this feature is on the Configurations > Integrations > Open Manta Integration Export > Open Manta Integration Export for Models Common page in the Manta Admin GUI.

Property key	Description	Default value	Example
manta.openExport.models.url	Specific URL for services provided by the internal metadata repository server	${manta.repository.private.api}/openexport/models	${manta.repository.private.api}/openexport/models
manta.openExport.models.exportStructureItems	Flag whether or not to export structure items of non-atomic columns	false	true
manta.openExport.models.mantaLineageLink.baseUrl	Base URL of links to Automatic Data Lineage in the format `http(s)://<host>:<port>/<application context>` Leave empty if the Manta Server URL (the property `manta.repository.url`) should be used Only applicable when `manta.openExport.exportMantaDirectLineageLink` or `manta.openExport.exportMantaIndirectLineageLink` is set to true		https://manta.mycompany.com:8443/manta-dataflow-server
manta.openExport.models.exportMantaDirectLineageLink	Flag whether or not to export a hyperlink leading to Automatic Data Lineage direct lineage visualization as an Open Manta Integration Export node attribute	true	false
manta.openExport.models.directLineageFilter	Filters applied to Automatic Data Lineage direct lineage referenced by the link; applicable only when `manta.openExport.models.exportMantaDirectLineageLink=true`	Everything	Database objects
manta.openExport.models.directLineageInitialDepth	Initial depth of Automatic Data Lineage direct lineage referenced by the link; applicable only when `manta.openExport.models.exportMantaDirectLineageLink=true`	3	2
manta.openExport.models.directLineageDirection	The direction of Automatic Data Lineage direct lineage referenced by the link; applicable only when `manta.openExport.models.exportMantaDirectLineageLink=true`	Both	Forward
manta.openExport.models.exportMantaIndirectLineageLink	Flag whether or not to export a hyperlink leading to Automatic Data Lineage indirect lineage visualization as an Open Manta Integration Export node attribute	true	false
manta.openExport.models.indirectLineageFilter	Filters applied to Automatic Data Lineage indirect lineage referenced by the link; applicable only when `manta.openExport.models.exportMantaIndirectLineageLink=true`	Everything	Important objects
manta.openExport.models.indirectLineageInitialDepth	Initial depth of Automatic Data Lineage indirect lineage referenced by the link; applicable only when `manta.openExport.models.exportMantaIndirectLineageLink=true`	3	2
manta.openExport.models.indirectLineageDirection	The direction of Automatic Data Lineage indirect lineage referenced by the link; applicable only when `manta.openExport.models.exportMantaIndirectLineageLink=true`	Both	Backward
manta.openExport.models.exportedAttributes	List of object types and attributes to export The object type and attribute are to be provided in the format `type/attribute`; each part is evaluated as a regular expression The type/attribute pairs are separated by a comma ( `,`) The type may be omitted, but keep the slash The attribute may be omitted along with the slash Leave blank to export all attributes for all types		com.getmanta.openmanta.System,/NOTE,com.getmanta.openmanta.LogicalAttribute/Definition
manta.openExport.models.excludedAttributes	List of object types and attributes to exclude from export Syntax is the same as for `manta.openExport.models.exportedAttributes` If left blank, all attributes matching the `manta.openExport.models.exportedAttributes` list will be exported If the `manta.openExport.models.exportedAttributes` list is blank, all attributes not matching this list will be exported If both are specified, only the attributes matching the `manta.openExport.models.exportedAttributes` list and not matching this list will be exported If both are left blank, all attributes will be exported	/CHECK_CONSTRAINT_MODEL,/COLUMN_CONSTRAINT_MODEL,/FOREIGN_KEY_MODEL_TECHNICAL,/INDEX_MODEL, /sourceLocation,/sourceEncoding,/RESTRICTION,/CUSTOM_SOURCE,/NODE_SCRIPT_POSITION,/NODE_SCRIPT_STOP_POSITION,/NODE_TRANSFORMATION,/TRANSFORMATION_DESC_OBJ	com.getmanta.openmanta.System,/NOTE,com.getmanta.openmanta.LogicalAttribute/Definition