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
  • Data Integration
  • All Products

Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. B2B transformation
  7. Aggregator transformation
  8. Cleanse transformation
  9. Data Masking transformation
  10. Data Services transformation
  11. Deduplicate transformation
  12. Expression transformation
  13. Filter transformation
  14. Hierarchy Builder transformation
  15. Hierarchy Parser transformation
  16. Hierarchy Processor transformation
  17. Input transformation
  18. Java transformation
  19. Java transformation API reference
  20. Joiner transformation
  21. Labeler transformation
  22. Lookup transformation
  23. Machine Learning transformation
  24. Mapplet transformation
  25. Normalizer transformation
  26. Output transformation
  27. Parse transformation
  28. Python transformation
  29. Rank transformation
  30. Router transformation
  31. Rule Specification transformation
  32. Sequence Generator transformation
  33. Sorter transformation
  34. SQL transformation
  35. Structure Parser transformation
  36. Transaction Control transformation
  37. Union transformation
  38. Velocity transformation
  39. Verifier transformation
  40. Web Services transformation

Transformations

Transformations

Back Next

Configuring the transformation

Configuring the transformation

When you configure the web services transformation, you connect a source object, configure properties for the transformation, map incoming fields to requested fields for the web service, and map the response to output fields to create one or more success groups.
Data Integration
 creates a fault group automatically but you can choose whether to map it to the output fields.
  1. Create a mapping and add the source objects you want to work with.
  2. Add a Web Services transformation to the canvas.
  3. Connect the source to the Web Services transformation.
  4. Select the business service and operation in the
    Web Service
     tab.
  5. On the
    Request Mapping
     and
    Response Mapping
     tabs, create the field mappings between the source fields and the web service request.
    For an illustration of the mapping process, see Web Services transformation example.
  6. On the
    Output Fields
     tab, review the success groups, fault group, and field details. You can edit the field metadata, if needed. The success groups contain the SOAP response from the web service. The fault group contains SOAP faults with the fault code, string, and object name that caused the fault to occur.
  7. Define the advanced properties.
  8. Save and run the mapping.
For additional information about the mapping process, see the following sections:

Advanced properties

The following table describes the properties available for the Web Services transformation from the
Advanced
 tab:
Property
Description
Cache Size
Memory available for the web service request and response. If the web service request or response contains a large number of rows or columns, you might want to increase the cache size. Default is 100 KB.
Allow Input Flush
The
mapping
 task creates XML when it has all of the data for a group. When enabled, the
mapping
 task flushes the XML after it receives all of the data for the root value. When not enabled, the
mapping
 task stores the XML in memory and creates the XML after it receives data for all the groups.
You cannot select the option to allow input flush if you are connecting to multiple source objects.
Transaction Commit Control
Control to commit or roll back transactions based on the set of rows that pass through the transformation. Enter an IIF function to specify the conditions to determine whether the
mapping
 task commits, rolls back, or makes no transaction changes to the row. Use the transaction commit control if you have a large amount of data and you want to control how it is processed.
You cannot configure a transaction commit control if you are connecting to multiple source objects.

Mapping incoming fields

When you define the request mapping, you can configure relationships between more than one source object. You configure relationships between the response mapping and the output fields separately.
When you map incoming fields, note the following guidelines:
  • If you need to apply an expression to incoming fields, use an Expression transformation upstream of the Web Services transformation.
  • To ensure that a web service request has all the required information, map incoming derived type fields to fields in the request structure.
You can map the incoming fields to the request mapping as shown in the following image:
The image shows incoming field "item_int_id" mapped to the "internalid" element in the request structure.
Drag each incoming field onto the node in the request structure where you want to map it.

Working with multiple source objects

If you have multiple sources, note the following requirements:
  • Any source fields you want to designate as primary key and foreign key must use the data type Bigint or String. If needed, you can edit the metadata in the Source transformation.
    If the Bigint data type is not available for a source, you can convert the data with an Expression transformation upstream of the Web Services transformation.
  • Ensure that the source data is sorted on the primary key for the parent object and sorted on the foreign key and primary key for child objects.
  • Map one of the fields or a group of fields to the recurring elements. In the incoming fields, you can see where each recurring element is mapped.
  • Map at least one field from each child object to the request structure.
  • You must map fields from the parent object to fields in the request structure that are higher in the hierarchy than fields from the child object.
  • For child objects, select a primary key and a foreign key.
    • On the
      Incoming Fields
       tab, select the source object you want to designate as the parent object.
    • Right-click on an incoming field in the tree to designate the primary key and foreign key.
    • For the foreign key, specify the parent object.
  • Do not choose a foreign key for the parent object.

Mapping outgoing fields

On the
Response Mapping
 tab, you map the response structure to the output fields you want to use. You can choose relational or denormalized format for the output fields.
When you choose
Relational
, the transformation generates the following output groups:
  • One output group for the parent element.
  • One output group for each element in which the cardinality is greater than one.
  • FaultGroup, if it is supported by the connection type you are using.
When you choose
Denormalized
, the transformation generates the following output groups:
  • Output group for the parent element. In denormalized output, the element values from the parent group repeat for each child element.
  • FaultGroup, if it is supported by the connection type you are using.
Right-click the node in the node of the response where you want to map the response to output fields. You can choose to map all descendants or only the immediate children, as shown in the following image:
The image shows the choices you have when you right-click a node in the response. You can map all descendants, map immediate children, unmap all descendants, or unmap immediate children.
0 COMMENTS
We’d like to hear from you!