XML Guide

10.4.0
- 10.5

Back Next

Working with XML Views

The Designer displays views as groups in the source definition.

The XML Wizard provides options for creating views in the definition or you can create the views manually in the XML Editor.

You can choose from the following options to create XML views:

Generate entity relationships
. If you create entity relationships, the XML Wizard generates views for multiple-occurring or referenced elements and complex types.

Generate hierarchy relationships.
When you create hierarchical relationships, each reference to a component expands under its parent element. You can generate normalized or denormalized XML views in a hierarchy relationship.

Normalized XML views.
When you generate a normalized XML view, elements and attributes appear once. Multiple-occurring elements, or elements in one-to-many relationships appear in different views related by keys.

Denormalized XML views.
When you generate a denormalized XML view, all elements and attributes appear in one view. The Designer does not model many-to-many relationships between elements and attributes in an XML definition..

Create a custom XML views
. You can specify any global element as a root when creating a custom XML view. You can choose to reduce metadata explosion for elements, complex types, and inherited complex types.

Synchronize XML definitions
. You can update one or more XML definitions when their underlying schemas change.

Skip Create XML views.
When you choose to skip creating the XML views, you can define them later in the XML Editor. When you define views in the XML Editor you can define the views to match targets and simplify the mapping.

Create XML views for the elements and attributes in the XML file.
When you import an XML file with an associated schema, you can create XML views for just the elements and attributes in the XML file, instead of all the components in the schema.

If you choose to generate entity or hierarchy relationships, the Designer chooses a default root and creates the XML views. If the XML definition requires more than 400 views, a message appears that the definition is too large. You can manually create views in the XML Editor. Import the XML definition and choose to create custom views or skip generating XML views.

When you import a definition from a XML schema that has no global elements, the Designer cannot create a root view in the XML definition. The Designer displays a message that there is no global element.

After you create an XML view, you cannot change the configuration options you set for the view. For example, if you create a normalized XML view, you cannot change the view to denormalized. You must import a new XML source definition and select the denormalized option.

For information about XML sizing in PowerCenter, see Using XML with PowerCenter Overview. For more information about the limitations that apply to XML handling in PowerCenter, see Limitations.

To create a transformation with other element types, and to transform larger XML input files, use a Data Processor transformation. For more information about how to create Data Processor transformations, see the

Informatica Data Transformation User Guide

and the

Informatica Data Transformation Getting Started Guide

Working with XML Sources

Importing Part of an XML Schema

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal