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 Export and Import
- Data Processor Transformation Validation
  - Using a Speed-enhanced Data Transformation Engine for VRL Validations
- 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 Files
- Schema Object Overview View
- 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
  - Java Interface Example
  - Sample Custom Java Components
- Configuring a Custom Component
  - Sample Scripts Containing Custom Components

User Guide

10.5.2
- 10.5.6
- 10.5
- 10.4.0

Back Next

Parser

A Parser reads a source document in any format. You can add child components to perform transformations on the data.

Define Parsers at the global level of the Script. Set a main Parser as the startup component. Call a secondary Parser with the

RunParser

action. For more information, see Parser.

The properties of the

Parser

appear above the

contains

line. Below the line, you can insert child components such as anchors and actions.

The following table describes the properties of the

Parser

component:

Property	Description
example_source	Defines a sample source document to process in the development environment. You can choose one of the following options: Empty. The Developer tool prompts you for a source document when you run the Parser. InputPort. Defines an input port. LocalFile. Defines a file on the local file system. Text. Defines a string. URL. Defines a URL. Default is empty. If the sources_to_extract property is set, the example_values property is ignored in the design environment.
example_values	Defines simulated values that another transformation might pass to the Parser. Use this property to design a Parser that is called by another Parser. A Parser uses the example_values property only when it processes the example source. It ignores the property when it parses a source document. In the nested ExampleValue components, specify the data holders that the calling Parser passes to this Parser and their simulated values.
ExampleValue	Defines an example value under the example_values property.
format	Defines the format of the source document. You can choose one of the following options: BinaryFormat CustomFormat HtmlFormat Rtf Format TextFormat XmlFormat Default is CustomFormat. For more information, see Format Component Reference.
name	A descriptive label for the component. This label appears in the log file and the Events view. Use the name property to identify the component that caused the event.
no_initial_phase	Determines whether the Script searches for nested anchors in the main phase. You can choose one of the following options: Cleared. Search for nested anchors according to their individual properties. Selected. Search for nested anchors in the main phase. Default is cleared.
notifications	Defines a list of NotificationHandler components that the Parser runs on notifications triggered by nested components. For more information, see Notifications.
on_fail	The action to take if the component fails. You can choose one of the following options: Cleared. Take no action. CustomLog. Write to the user log. LogError. Write an error message to the engine log. LogInfo. Write an information message to the engine log. LogWarning. Write a warning message to the engine log. NotifyFailure. Send a notification. Default is cleared. For more information about handling component failures, see Failure Handling.
reject_recurring_pages	Determines the number of times the Parser parses the same page. You can choose one of the following options: Selected. The Parser parses a page only once. Cleared. The Parser parses a page each time it follows a link to the page. Use reject_recurring_pages when a web site contains many links to the same page. The ResetVisitedPages action resets the history list and allows a Parser to process a page again, even if reject_recurring_pages is selected.
remark	A user-defined comment that describes the purpose or action of the component.
serialization_mode	Defines how the Script processes portions of the example source that the Parser does not output to XML, when you create a serializer from a Parser. For more information, see Controlling How the Create Serializer Command Works. You can choose one of the following options: Full. Causes the Create Serializer command to copy the non-XML text to the serializer configuration. Outline. Causes the Create Serializer command to copy only the delimiters of the non-XML text to the serializer configuration. When Outline is selected, you can set the use_markers property.
source	Defines a sequence of data holders for input to the Parser. Each data holder is identified by one of the following properties: Locator. Identifies a single-occurrence or a multiple-occurrence data holder. For multiple-occurrence data holders, each iteration accesses a new occurrence. LocatorByKey. Identifies a multiple-occurrence data holder by key. LocatorByOccurence. Identifies a multiple-occurrence data holder by sequence number. In a secondary Parser, set Parser source Locator data_holder to the data holder defined in the associated AdditionalInputPort data_holder . For more information, see Source Property.
sources_to_extract	Defines a hard-coded list of source documents that the Parser processes. You can choose one of the following options: DocList. Defines a list of LocalFile , Text , and URL components. Empty. The Parser processes the example_source . FileSearch. Defines a folder on the local file system and a file name filter. InputPort. Defines an input port. Do not use this option. LocalFile. Defines a file on the local file system. Text. Defines a string. URL. Defines a URL. Default is empty. Use the sources_to_extract property only in the design environment.
target	Defines a sequence of data holders for output from the Parser. If the data holder does not yet exist, the Parser creates it. Each data holder is identified by one of the following properties: Locator. Identifies a single-occurrence or a multiple-occurrence data holder. For multiple-occurrence data holders, each iteration creates a new occurrence. LocatorByKey. Identifies a multiple-occurrence data holder by key. LocatorByOccurence. Identifies a multiple-occurrence data holder by sequence number. Use the target property when the output of the Parser is used by another component. For more information, see Target Property.
use_markers	Determines whether the Create Serializer command copies the content of the Marker anchors but only the delimiters of other non-XML text. use_markers is an option under the serialization_mode property when outline is selected. Default is selected.

Rename Saved Search

Table of Contents

User Guide

User Guide

Parser

Parser