Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • PowerCenter 10.5
  • All Products

Table of Contents

Search

  1. Preface
  2. XML Concepts
  3. Using XML with PowerCenter
  4. Working with XML Sources
  5. Using the XML Editor
  6. Working with XML Targets
  7. XML Source Qualifier Transformation
  8. Midstream XML Transformations
  9. Appendix A: XML Datatype Reference
  10. Appendix B: XPath Query Functions Reference

XML Guide

XML Guide

Back Next

Properties Tab

Properties Tab

Configure the midstream XML transformation properties on the Properties tab.
The following table describes the options you can change on the Properties tab:
Transformation
Description
Runtime Location
Location that contains the DLL or shared library. Default is $PMExtProcDir. Enter a path relative to the Integration Service node that runs the XML session.
If this property is blank, the Integration Service uses the environment variable defined on the Integration Service node to locate the DLL or shared library.
You must copy all DLLs or shared libraries to the runtime location or to the environment variable defined on the Integration Service node. The Integration Service fails to load the procedure when it cannot locate the DLL, shared library, or a referenced file.
Tracing Level
Amount of detail displayed in the session log for this transformation. Default is Normal.
Transformation Scope
Indicates how the Integration Service applies the transformation logic to incoming data. You can choose one of the following transformation scope values for the XML Parser transformation:
  • Row. Applies the transformation logic to one row of data at a time. Flushes the rows generated for all the output groups before processing the next row.
  • Transaction. Applies the transformation logic to all rows in a transaction. Flushes generated rows at transaction boundaries, when output blocks fill up, and at end of file.
  • All Input. Applies the transformation logic to all incoming data. Flush generated rows only when the output blocks fill up and at end of file.
For the XML Generator transformation, the Designer sets the transformation scope to all input when you set the On Commit setting to Ignore Commit. The Designer sets the transformation scope to the transaction level if you set On Commit to Create New Doc.
Output is Repeatable
Indicates if the order of the output data is consistent between session runs.
  • Never. The order of the output data is inconsistent between session runs.
  • Based On Input Order. The output order is consistent between session runs when the input data order is consistent between session runs.
  • Always. The order of the output data is consistent between session runs even if the order of the input data is inconsistent between session runs.
Default is Based on Input Order for the XML Parser transformation. Default is Always for the XML Generator transformation.
Requires Single Thread per Partition
Indicates if the Integration Service must process each partition with one thread.
Output is Deterministic
Indicates whether the transformation generates the same output data between session runs. You must enable this property to perform recovery on sessions that use this transformation. Default is enabled.
If you configure a transformation as repeatable and deterministic, it is your responsibility to ensure that the data is repeatable and deterministic. If you try to recover a session with transformations that do not produce the same data between the session and the recovery, the recovery process can result in corrupted data.
0 COMMENTS
We’d like to hear from you!