Table of Contents

Search

  1. Preface
  2. Introduction to Transformations
  3. Transformation Ports
  4. Transformation Caches
  5. Address Validator Transformation
  6. Aggregator Transformation
  7. Association Transformation
  8. Bad Record Exception Transformation
  9. Case Converter Transformation
  10. Classifier Transformation
  11. Comparison Transformation
  12. Consolidation Transformation
  13. Data Masking Transformation
  14. Data Processor Transformation
  15. Decision Transformation
  16. Duplicate Record Exception Transformation
  17. Expression Transformation
  18. Filter Transformation
  19. Hierarchical to Relational Transformation
  20. Java Transformation
  21. Java Transformation API Reference
  22. Java Expressions
  23. Joiner Transformation
  24. Key Generator Transformation
  25. Labeler Transformation
  26. Lookup Transformation
  27. Lookup Caches
  28. Dynamic Lookup Cache
  29. Macro Transformation
  30. Match Transformation
  31. Match Transformations in Field Analysis
  32. Match Transformations in Identity Analysis
  33. Normalizer Transformation
  34. Merge Transformation
  35. Parser Transformation
  36. Python Transformation
  37. Rank Transformation
  38. Read Transformation
  39. Relational to Hierarchical Transformation
  40. REST Web Service Consumer Transformation
  41. Router Transformation
  42. Sequence Generator Transformation
  43. Sorter Transformation
  44. SQL Transformation
  45. Standardizer Transformation
  46. Union Transformation
  47. Update Strategy Transformation
  48. Web Service Consumer Transformation
  49. Parsing Web Service SOAP Messages
  50. Generating Web Service SOAP Messages
  51. Weighted Average Transformation
  52. Window Transformation
  53. Write Transformation
  54. Appendix A: Transformation Delimiters

Developer Transformation Guide

Developer Transformation Guide

Resource Identification

Resource Identification

To identify the resource in an HTTP request, the Data Integration Service appends values in specific input ports to the base URL. You define the base URL in the HTTP connection or in the transformation properties. Use URL or argument ports to identify a particular resource.
Use URL ports when the web service identifies a resource through a unique string of characters.
For example, the HypoStores REST web service identifies parts by the part number through the following URL:
http://www.HypoStores.com/products/ProductDetails/<Part_No>
To identify a part, define the following transformation details:
  1. Set the base URL to the following URL:
    http://www.HypoStores.com/products/ProductDetails
  2. Define a URL port, and pass the part number to the transformation through the URL port.
If the mapping passes part number 500 to the URL port, the Data Integration Service uses the following URL in the request message:
http://www.HypoStores.com/products/ProductDetails/500
Use argument ports when the web service identifies the location of a resource through arguments.
For example, you want to pass a part number to the HypoStores REST web service through the "Part_No" argument.
To identify a part, define the following transformation details:
  1. Set the base URL to the following URL:
    http://www.HypoStores.com/products/ProductDetails
  2. Create an argument port with argument name "Part_No," and pass the part number to the transformation through the argument port.
If the mapping passes part number 600 to the argument port, the Data Integration Service uses the following URL in the request message:
http://www.HypoStores.com/products/ProductDetails?Part_No=600
Create multiple argument ports to define multiple arguments. The Data Integration Service separates each argument with an ampersand character (&).
For example, you want to retrieve employee details from a REST web service and pass the employee first name and last name through the "First_Name" and "Last_Name" arguments. Create argument ports with the argument names "First_Name" and "Last_Name." If the mapping passes the name "John Smith" to the transformation, the Data Integration Service uses a URL like the following in the request message:
http://www.HypoStores.com/employees/EmpDetails?First_Name=John&Last_Name=Smith
If you do not specify a URL or an argument port, the Data Integration Service uses the base URL from the transformation properties or HTTP connection to identify the resource. The base URL in the HTTP connection overrides the base URL in the transformation.

0 COMMENTS

We’d like to hear from you!