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. Working with Transformations
  3. Aggregator Transformation
  4. Custom Transformation
  5. Custom Transformation Functions
  6. Data Masking Transformation
  7. Data Masking Examples
  8. Expression Transformation
  9. External Procedure Transformation
  10. Filter Transformation
  11. HTTP Transformation
  12. Identity Resolution Transformation
  13. Java Transformation
  14. Java Transformation API Reference
  15. Java Expressions
  16. Java Transformation Example
  17. Joiner Transformation
  18. Lookup Transformation
  19. Lookup Caches
  20. Dynamic Lookup Cache
  21. Normalizer Transformation
  22. Rank Transformation
  23. Router Transformation
  24. Sequence Generator Transformation
  25. Sorter Transformation
  26. Source Qualifier Transformation
  27. SQL Transformation
  28. Using the SQL Transformation in a Mapping
  29. Stored Procedure Transformation
  30. Transaction Control Transformation
  31. Union Transformation
  32. Unstructured Data Transformation
  33. Update Strategy Transformation
  34. XML Transformations

Transformation Guide

Transformation Guide

Back Next

Configuring Groups and Ports

Configuring Groups and Ports

The ports you add to an HTTP transformation depend on the method you choose and the group. An HTTP transformation uses the following groups:
  • Output
    . Contains body data for the HTTP response. Passes responses from the HTTP server to downstream transformations or the target. By default, contains one output port, HTTPOUT. You cannot add ports to the output group. You can modify the precision for the HTTPOUT output port.
  • Input.
     Contains body data for the HTTP request. Also contains metadata the Designer uses to construct the final URL to connect to the HTTP server. To write data to an HTTP server, the input group passes body information to the HTTP server. By default, contains one input port.
  • Header
    . Contains header data for the request and response. Passes header information to the HTTP server when the Integration Service sends an HTTP request. Ports you add to the header group pass data for HTTP headers. When you add ports to the header group the Designer adds ports to the input and output groups on the Ports tab. By default, contains no ports. For all methods, you can use the header group for the HTTP request header information.
The data that passes through an HTTP transformation must be of the String datatype. String data includes any markup language common in HTTP communication, such as HTML and XML.

GET Method

Reads data from an HTTP server. To define the metadata for the HTTP request, use the input group to add input ports that the Designer uses to construct the final URL for the HTTP server.
The following table describes the groups and ports for the GET method:
Request/
Response
Group
Description
REQUEST
Input
The Designer uses the names and values of the input ports to construct the final URL.
REQUEST
Header
You can configure input and input/output ports for HTTP requests. The Designer adds ports to the input and output groups based on the ports you add to the header group:
  • Input group. Creates input ports based on input and input/output ports from the header group.
  • Output group. Creates output ports based on input/output ports from the header group.
RESPONSE
Header
You can configure output and input/output ports for HTTP responses. The Designer adds ports to the input and output groups based on the ports you add to the header group:
  • Input group. Creates input ports based on input/output ports from the header group.
  • Output group. Creates output ports based on output and input/output ports from the header group.
RESPONSE
Output
All body data for an HTTP response passes through the HTTPOUT output port.

POST Method

Writes data from multiple input ports to the HTTP server. To define the metadata for the HTTP request, use the input group for the data that defines the body of the HTTP request.
The following table describes the ports for the POST method:
Request/
Response
Group
Description
REQUEST
Input
You can add multiple ports to the input group. Body data for an HTTP request can pass through one or more input ports based on what you add to the header group.
REQUEST
Header
You can configure input and input/output ports for HTTP requests. The Designer adds ports to the input and output groups based on the ports you add to the header group:
  • Input group. Creates input ports based on input and input/output ports from the header group.
  • Output group. Creates output ports based on input/output ports from the header group.
RESPONSE
Header
You can configure output and input/output ports for HTTP responses. The Designer adds ports to the input and output groups based on the ports you add to the header group:
  • Input group. Creates input ports based on input/output ports from the header group.
  • Output group. Creates output ports based on output and input/output ports from the header group.
RESPONSE
Output
All body data for an HTTP response passes through the HTTPOUT output port.

SIMPLE POST Method

A simplified version of the POST method. Writes data from one input port as a single block of data to the HTTP server. To define the metadata for the HTTP request, use the input group for the data that defines the body of the HTTP request.
The following table describes the ports for the SIMPLE POST method:
Request /Response
Group
Description
REQUEST
Input
You can add one input port. Body data for an HTTP request can pass through one input port.
REQUEST
Header
You can configure input and input/output ports for HTTP requests. The Designer adds ports to the input and output groups based on the ports you add to the header group:
  • Input group. Creates input ports based on input and input/output ports from the header group.
  • Output group. Creates output ports based on input/output ports from the header group.
RESPONSE
Header
You can configure output and input/output ports for HTTP responses. The Designer adds ports to the input and output groups based on the ports you add to the header group:
  • Input group. Creates input ports based on input/output ports from the header group.
  • Output group. Creates output ports based on output and input/output ports from the header group.
RESPONSE
Output
All body data for an HTTP response passes through the HTTPOUT output port.

SIMPLE PATCH Method

Updates partial data from one input port as a patch to the resource. Writes data from one input port as a complete or partial block of data to the HTTP server. To define the metadata for the HTTP request, use the input group for the data that defines the body of the HTTP request.
The following table describes the ports for the SIMPLE PATCH method:
Request /Response
Group
Description
REQUEST
Input
You can add one input port. Body data for an HTTP request can pass through one input port.
REQUEST
Header
You can configure input and input/output ports for HTTP requests. The Designer adds ports to the input and output groups based on the ports you add to the header group:
  • Input group. Creates input ports based on input and input/output ports from the header group.
  • Output group. Creates output ports based on input/output ports from the header group.
RESPONSE
Header
You can configure output and input/output ports for HTTP responses. The Designer adds ports to the input and output groups based on the ports you add to the header group:
  • Input group. Creates input ports based on input/output ports from the header group.
  • Output group. Creates output ports based on output and input/output ports from the header group.
RESPONSE
Output
All body data for an HTTP response passes through the HTTPOUT output port.

SIMPLE PUT Method

Replaces or writes a resource. Writes data from one input port as a single block of data to the HTTP server.
If the data does not exist, the SIMPLE PUT method posts the data. If the data does exist, the SIMPLE PUT method updates data from one input port as a single block of data to the HTTP server.
To define the metadata for the HTTP request, use the input group for the data that defines the body of the HTTP request.
The following table describes the ports for the SIMPLE PUT method:
Request /Response
Group
Description
REQUEST
Input
You can add one input port. Body data for an HTTP request can pass through one input port.
REQUEST
Header
You can configure input and input/output ports for HTTP requests. The Designer adds ports to the input and output groups based on the ports you add to the header group:
  • Input group. Creates input ports based on input and input/output ports from the header group.
  • Output group. Creates output ports based on input/output ports from the header group.
RESPONSE
Header
You can configure output and input/output ports for HTTP responses. The Designer adds ports to the input and output groups based on the ports you add to the header group:
  • Input group. Creates input ports based on input/output ports from the header group.
  • Output group. Creates output ports based on output and input/output ports from the header group.
RESPONSE
Output
All body data for an HTTP response passes through the HTTPOUT output port.

SIMPLE DELETE Method

Deletes a resource from the HTTP server. If the request body is required, SIMPLE DELETE deletes data from an input port as a single block of data to the HTTP server. To define the metadata for the HTTP request, use the input group to add input ports that the Designer uses to construct the final URL for the HTTP server.
The following table describes the ports for the SIMPLE DELETE method:
Request/
Response
Group
Description
REQUEST
Input
The Designer uses the names and values of the input ports to construct the final URL.
REQUEST
Header
You can configure input and input/output ports for HTTP requests. The Designer adds ports to the input and output groups based on the ports you add to the header group:
  • Input group. Creates input ports based on input and input/output ports from the header group.
  • Output group. Creates output ports based on input/output ports from the header group.
RESPONSE
Header
You can configure output and input/output ports for HTTP responses. The Designer adds ports to the input and output groups based on the ports you add to the header group:
  • Input group. Creates input ports based on input/output ports from the header group.
  • Output group. Creates output ports based on output and input/output ports from the header group.
RESPONSE
Output
All body data for an HTTP response passes through the HTTPOUT output port.
0 COMMENTS
We’d like to hear from you!