Saturday 2 March 2013

HTTP Transformation/How to use http transformation in informatics

HTTP Transformation Overview


Transformation type:

Passive

Connected

Why we need this T/R?

The HTTP transformation enables you to connect to an HTTP server to use its services and applications. When you run a session with an HTTP transformation, the Integration Service connects to the HTTP server and issues a request to retrieve data from or update data on the HTTP server, depending on how you configure the transformation:

¨ Read data from an HTTP server. When the Integration Service reads data from an HTTP server, it retrieves the data from the HTTP server and passes the data to the target or a downstream transformation in the mapping. For example, you can connect to an HTTP server to read current inventory data, perform calculations on the data during the PowerCenter session, and pass the data to the target.

¨ Update data on the HTTP server. When the Integration Service writes to an HTTP server, it posts data to the HTTP server and passes HTTP server responses to the target or a downstream transformation in the mapping.

For example, you can post data providing scheduling information from upstream transformations to the HTTP server during a session.

The Integration Service passes data from upstream transformations or the source to the HTTP transformation,

reads a URL configured in the HTTP transformation or application connection, and sends an HTTP request to the HTTP server to either read or update data.

Requests contain header information and may contain body information. The header contains information such as authentication parameters, commands to activate programs or web services residing on the HTTP server, and other information that applies to the entire HTTP request. The body contains the data the Integration Service sends to the HTTP server.

When the Integration Service sends a request to read data, the HTTP server sends back an HTTP response with the requested data. The Integration Service sends the requested data to downstream transformations or the target.



When the Integration Service sends a request to update data, the HTTP server writes the data it receives and sends back an HTTP response that the update succeeded. The HTTP transformation considers response codes 200 and 202 as a success. It considers all other response codes as failures. The session log displays an error when an HTTP server passes a response code that is considered a failure to the HTTP transformation. The Integration Service then sends the HTTP response to downstream transformations or the target.

You can configure the HTTP transformation for the headers of HTTP responses. HTTP response body data
passes through the HTTPOUT output port.

Authentication

The HTTP transformation uses the following forms of authentication:

¨ Basic. Based on a non-encrypted user name and password.

¨ Digest. Based on an encrypted user name and password.

¨ NTLM. Based on encrypted user name, password, and domain.

Connecting to the HTTP Server

When you configure an HTTP transformation, you can configure the URL for the connection. You can also create an HTTP connection object in the Workflow Manager. Configure an HTTP application connection in the following

circumstances:

¨ The HTTP server requires authentication.

¨ You want to configure the connection timeout.

¨ You want to override the base URL in the HTTP transformation.

Creating an HTTP Transformation

You create HTTP transformations in the Transformation Developer or in the Mapping Designer. An HTTP

transformation has the following tabs:

¨ Transformation. Configure the name and description for the transformation.

¨ Ports. View input and output ports for the transformation. You cannot add or edit ports on the Ports tab. The

Designer creates ports on the Ports tab when you add ports to the header group on the HTTP tab.

¨ Properties. Configure properties for the HTTP transformation on the Properties tab.

¨ HTTP. Configure the method, ports, and URL on the HTTP tab.

To create an HTTP transformation:

1. In the Transformation Developer or Mapping Designer, click Transformation > Create.

2. Select HTTP transformation.

3. Enter a name for the transformation.

4. Click Create.

The HTTP transformation displays in the workspace.

5. Click Done.

6. Configure the tabs in the transformation.



Configuring the Properties Tab

The HTTP transformation is built using the Custom transformation. Some Custom transformation properties do not apply to the HTTP transformation or are not configurable.

the same data between the session and the recovery, the recovery process can result in corrupted data.

Configuring the HTTP Tab


On the HTTP tab, you can configure the transformation to read data from the HTTP server or write data to the HTTP server. Configure the following information on the HTTP tab:

¨ Select the method. Select GET, POST, or SIMPLE POST method based on whether you want to read data from or write data to an HTTP server.

Configuring the Properties Tab 159

¨ Configure groups and ports. Manage HTTP request/response body and header details by configuring input

and output ports. You can also configure port names with special characters.

¨ Configure a base URL. Configure the base URL for the HTTP server you want to connect to.

GET method: Use the input group to add input ports that the Designer uses to construct the final URL for the HTTP server.

¨ POST or SIMPLE POST method. Use the input group for the data that defines the body of the HTTP request.

For all methods, use the header group for the HTTP request header information.




Informatica Data Explorer 8.x/9.0.x Versus Informatica Data Explorer 9.1


Informatica Data Explorer 8.x/9.0.x Versus Informatica Data Explorer 9.1

Upgrading from Informatica Data Explorer 8.x to Informatica Data Quality 9.0.1 is more than just a product upgrade—it’s a complete data quality overhaul.
Informatica Data Quality extends your existing Informatica Data Explorer capabilities to deliver pervasive data quality to all stakeholders and all data domains for all projects and all business applications—on premise or in the cloud—using a single, unified platform.
Features/CapabilitiesInformatica Data Explorer Standard Edition 8.x/9.0.xInformatica Data Explorer 9.1.x
Column profiling
Validation of join conditions
Export value frequency results to reference tables;
Export the profiling results to CSV
Ability to profile flat files, relational sources
Support for third party reporting tools to access the profiling results
Ability to profile mainframe sources
Rules
Unified IDE/IDQ User Interface
Unified IDE/IDQ repository & metadata
Web based client for business users (Analyst)
Ability to profile the output of DQ rules
Ability to join sources and profile results (without database views)
Mid stream profiling
Easy to build & share scorecards; Includes trending;
Ability to profile SAP or Unstructured data sources
UNICODE enabled
64 bit application
Easy to build & share scorecards; Includes trending
LDAP authentication
Column level comments
Primary Key Analysis and Validation
Foreign Key Analysis and Validation
Filtering of data upon drilldown or profiling
Tags
Comparative Profiling
Generate mapping from profile
Iterative Custom Drilldown
Reuse profile across data sources