Preface
Introduction to Data Transformation
- Data Transformation Overview
- Data Transformation Process Architecture
- Data Transformation Components
Data Processor Transformation
- Data Processor Transformation Overview
- Data Processor Transformation Views
- Data Processor Transformation Ports
- Startup Component
- References
- Data Processor Transformation Settings
- Events
  - Event Types
  - Data Processor Events View
- Logs
- Data Processor Transformation Development
- Data Processor Transformation Import and Export
- Data Processor Transformation in a Non-native Environment
Wizard Input and Output Formats
- Wizard Input and Output Formats Overview
- COBOL Processing Library
- JSON
- XML
  - Creating a Transformation that Transforms XML
Relational Input and Output
- Relational Input and Output Overview
- Relational Input
- Relational Output
Using the IntelliScript Editor
- IntelliScript Editor Overview
  - Creating a Script
- Opening an IntelliScript Editor
- Editing Procedures
- IntelliScript Editor Menus
XMap
- XMap Overview
- XMap Schemas
- Mapping Statements
- XPath Expressions
- XMap Variables
  - Creating a Variable in the XMap Editor
- XMap Example
Libraries
- Libraries Overview
- Library Structure
- Element Properties
- Library Management
- Edit Libraries with the Library Editor
- Edit Libraries with the IntelliScript Editor
Schema Object
- Schema Object Overview
- Schema Object Overview View
  - Schema Files
- Schema Object Schema View
- Schema Object Advanced View
- Creating a Schema Object
- Schema Updates
  - Schema Synchronization
  - Schema File Edits
    - Setting a Default Schema File Editor
    - Editing a Schema File
Command Line Interface
- Command Line Interface Overview
- CM_console
Scripts
- Scripts Overview
- Script Components
- Script Component Properties
- Script Startup Components
  - Setting the Startup Component with the IntelliScript Editor
- Example Sources
- IntelliScript Editor
- Validate a Script
- Sample Scripts
  - Importing a Sample Script
Parsers
- Parsers Overview
- Platform-Independent Parsers
  - Newline Markers
  - File Paths
- Parser Component Reference
  - Parser
Script Ports
- Script Ports Overview
- Script Port Component Reference
Document Processors
- Document Processors Overview
- Defining a Document Processor
  - Display of Document Processor Output
- Document Processor Component Reference
- TextML XML Schema
- PdfToTxt_4 Table Configuration Editor
  - Editor Options
  - PDF Conversion Example
    - Configuring the First Table
    - Configuring the Second Table
Formats
- Formats Overview
- Standard Format Properties
- Format Component Reference
- Delimiters Component Reference
- Format Preprocessor Component Reference
  - HtmlProcessor
  - RtfProcessor
Data Holders
- Data Holders Overview
- XML Schemas
- Using a Schema to Map Anchors
- Generating Valid XML
  - Role of Schemas in Parsing
  - Role of Schemas in Serialization and Mapping
- Variables
- Variable Component Reference
  - Variable
- Multiple-Occurrence Data Holders
Anchors
- Anchors Overview
- Mapping Content Anchors to Data Holders
- Defining Anchors
- Standard Anchor Properties
- How a Parser Searches for Anchors
- Anchor Component Reference
- Searcher Component Reference
- Anchor Subcomponent Reference
Transformers
- Transformers Overview
- Defining Transformers
- Standard Transformer Properties
- Transformer Component Reference
Actions
- Actions Overview
- Standard Action Properties
- Action Component Reference
- Action Subcomponent Reference
Serializers
- Serializers Overview
- Serialization Anchors
  - Example of Serialization Anchors
  - Sequence of Serialization Anchors
- Standard Serializer Properties
- Serializer Component Reference
  - Serializer
- Serialization Anchor Component Reference
Mappers
- Creating a Mapper
- Components Nested within a Mapper
- Mapper Example
- Standard Mapper Properties
- Mapper Component Reference
  - Mapper
- Mapper Anchor Component Reference
Locators, Keys, and Indexing
- Overview of Locators, Keys, and Indexing
- Example of Locators
- Example of Indexing by Key
- Source and Target Properties
  - Source Property
  - Target Property
- Standard Locator and Key Properties
- Locator and Key Component Reference
Streamers
- Streamers Overview
- Text Streamers
- XML Streamers
- Standard Streamer Properties
- Streamer Component Reference
- Streamer Subcomponent Reference
Validators, Notifications, and Failure Handling
- Overview of Validators, Notifiers, and Failure Handling
- Failure Handling
  - Using the Optional Property to Handle Failures
  - Writing a Failure Message to the User Log
    - Configuring User Log Output
    - Viewing the User Log
- Validators
- Standard Validator Properties
- Validator Component Reference
- Notifications
- Notification Component Reference
Validation Rules
- Validation Rules Overview
- Validation Rules Element Reference
- Edit the Validation Rules in an External Editor
- Create a Validation Rules Object
- Import a Data Transformation Service with Validation Rules
Custom Script Components
- Custom Script Components Overview
- Custom Component Example
- Custom Component Properties
- Developing a Custom Component in Java
  - Java Interface Example
  - Sample Custom Java Components
- Developing a Custom Component in C or C++
- Configuring a Custom Component
  - Sample Scripts Containing Custom Components

User Guide

10.4.0
- 10.5.6
- 10.5.2
- 10.5

Back Next

XML Streamers

XmlStreamer

component splits a large XML document into smaller portions. The

XmlStreamer

divides the XML source into header, body, and footer segments. The body segments can contain repeating or non-repeating elements. The

XmlStreamer

can pass each XML segment to an appropriate transformation, typically a Mapper or a Serializer.

XmlStreamer

works in much the same way as a

Streamer

, with a few differences due to the structured XML input. The following are the main features:

The body segments are defined as XML elements. You can configure the body with multiple elements of the same or different types, in any sequence.

The header is defined as the entire portion of the XML that precedes the first body segment. In the

XmlStreamer

configuration, it is not necessary to define the elements that comprise the header.

The footer is defined as the entire portion of the XML that follows the last body segment. In the

XmlStreamer

configuration, is not necessary to define the elements that comprise the footer.

In many cases, the header and footer segments are not well-formed XML. To enable passing the segments to a Mapper or Serializer, you can configure modifier components that convert the segments to well-formed XML.

To help understand these features, consider the following source XML structure:

<stream>
  <headerline1>MainHeader</headerline1>
  <substreams>
    <substream>
      <subheaderline1>SubHeader</subheaderline1>
      <segments>
        <segment1>Segment1A</segment1>
        <segment1>Segment1B</segment1>
        <segment2>Segment2A</segment2>
        <segment1>Segment1C</segment1>
        <segment2>Segment2B</segment2>
      </segments>
      <subfooterline1>SubFooter</subfooterline1>
    </substream>
    <substream>...</substream>
    <substream>...</substream>
  </substreams>
  <footerline1>MainFooter</footerline1>
</stream>

In this example, you might define the body segments as the

substream

elements. The header is everything that precedes the first

substream

<stream>
  <headerline1>MainHeader</headerline1>
  <substreams>

The footer is everything that follows the last

substream


  </substreams>
  <footerline1>MainFooter</footerline1>
</stream>

The header and footer segments are not well-formed XML. You can apply modifiers that add closing or opening tags to make them well-formed. For example, a modifier can convert the header to:

<stream>
  <headerline1>MainHeader</headerline1>
  <substreams>
  </substreams>
</stream>

You can configure the

XmlStreamer

to pass the header segment, the footer segment, and each instance of the

substream

segment to an appropriate transformation, such as a Mapper or Serializer.

The header segment elements are available when processing the body elements. The footer elements, however, are not yet available when processing body elements. Footer elements are only processed after the transformation finishes reading body elements.

Alternatively, you might subdivide the

substream

elements into

segment1

and

segment2

segments, and send each of these to its own Mapper or Serializer. Notice that

segment1

and

segment2

follow each other in a random sequence. The

XmlStreamer

ignores the sequence and processes

segment1

and

segment2

in whatever order they occur.

The following figure illustrates the configuration for this purpose. The Script defines independent Serializers for the header, footer,

segment1

, and

segment2

segments.

global level XmlStreamer1 = XmlStreamer level 2 Header = XmlSegment level 3 run_component = HeaderSerializer level 2 Footer = XmlSegment level 3 run_component = FooterSerializer level 2 sub_elements = level 3 ComplexXmlSegment >> level 4 locator = /stream/*s/substreams/*s/substream level 4 sub_elements = level 5 SimpleXmlSegment >> level 6 locator = /stream/*s/substreams/*s/substream/*s/segments/*s/*s1/segment1 level 6 run_component = Segment1Serializer level 5 SimpleXmlSegment >> level 6 locator = /stream/*s/substreams/*s/substream/*s/segments/*s/*s1/segment2 level 6 run_component = Segment2Serializer level 4 ... level 3 ... global level HeaderSerializer = Serializer() global level FooterSerializer = Serializer() global level Segment1Serializer = Serializer() global level Segment2Serializer = Serializer()

Even through the footer run component appears before the body elements in this example, footer elements are only processed after the transformation finishes reading body elements.

As a further refinement, you can define transformations for the nested headers and footers within each substream element.

Rename Saved Search

Table of Contents

User Guide

User Guide

XML Streamers

XML Streamers