In this release we focused on adding URL JOIN Features which may allow many multi steps scenarios in one query. Bing Ads, Amazon MWS, Google BigQuery, Amazon Athena all these supports Job style queries which needs 3 step process (Create job, keep checking status, once done read report data). We also improved compatibility with Informatica and MS Access.

Version 1.1.3.10621 [Jun 24, 2019]

New Features/Improvements

• NEW: Add option to replace placeholders in File content if you use IsMultiPart = True
• NEW: All API Drivers – Add option EnableBodyPlaceholderForMultiPart to support replacing placeholders in file content in IsMultiPart mode (E.g. replace <%access_token%> or [$token$] or [$alias.MyJoinColumn$] )
• NEW: All API Drivers – Add option OutputAsRawDocumentSingleRow (Returns __DOCUMENT__ field with entire File / Response string in one field)
• NEW: All API Drivers – Add Options to parse from any unstructured data – RawOutputExtractMode, RawOutputDataRowTemplate, RawOutputFilterExpr
• NEW: All API Drivers – Add Status Check feature for all API drivers (Keep sending request until desired value found) – Options added EnableStatusCheck, StatucCheckMaxWaitSeconds, StatucCheckIterationWaitSeconds, StatusSuccessValue, StatusFailureValue
• NEW: All API Drivers – Add support for ConnectionType in URL Join
• NEW: All API Drivers – Add Support for HMAC Authentication
• NEW: All ODBC Drivers – Add support for Parameters
• NEW: Data Gateway – Add Code Generator UI for SQL / Java
• NEW: Data Gateway – Allow to add firewall rule via UI
• NEW: Data Gateway – Better logging about connected devices
• NEW: Salesforce Driver – Add support for Select * FROM

Bug fixes

• FIX: All API Drivers – joinXX_DataConnectionType Option not supported in JOIN URL
• FIX: All API Drivers- Show meaningful error when same option used twice in WITH clause (Right now you see odd error – An item with the same key has already been added)
• FIX: Apps – Informatica – Driver may output many extra empty rows in some cases
• FIX: Apps – MS Access – Linked table throwing call fail error (due to missing support for parameters in current driver)
• FIX: Data Gateway – Certain errors not reported correctly back to caller
• FIX: Data Gateway – Enabling caching options may hang query in some case
• FIX: Data Gateway – Generic ODBC Connection Type fails with error Connection is Busy
• FIX: Data Gateway – When you use Meta option in WITH clause you may see empty rowset rather error in some cases
• FIX: Salesforce Driver – Can not load table list in Excel / Power BI
• FIX: Salesforce Driver – Failed to preview data in Power BI
• FIX: Salesforce Driver – Load ConnectionString doesnt set Username
• FIX: Salesforce Driver – Nested queries not supported – You may get syntax error
• FIX: Salesforce Driver – SSIS ODBC destination showing bad Table names in list

The post ODBC PowerPack v1.1.3 Released appeared first on ZappySys Blog.

In our previous blog post we saw how to read JSON REST API / XML SOAP in Informatica using ZappySys ODBC Drivers. Now lets look at API Write scenario. We will learn how to to POST data to API in Informatica (Insert / Update). We will use SQL Transformation to fire ODBC Driver Queries to create / update or delete records in Target System by calling Web API (i.e. REST or SOAP).

For example purpose we will use JSON API but if you are calling XML / SOAP API then use ZappySys XML Driver instead of JSON Driver.

Requirements

This article assumes that you have full filled following basic requirements.

1. Download Install ZappySys ODBC PowerPack (Drivers for JSON and REST API)
2. Install Informatica PowerCenter Client Tools (e.g. Workflow and Mapping Designers)
3. Access to a Relational database such as SQL Server (or use any of your choice e.g. Oracle, MySQL, DB2 ). If nothing available then you can use flat file target.

Video Tutorial – POST data to API in Informatica

Here is the full Video Tutorial with many API tips / tricks to show how to POST data to REST / SOAP API in Informatica PowerCenter. It also covers how to Upload File to Web API.

Getting Started

So let’s get started with basic setup on how to POST data to your API to create new records or update / delete records. In the following demo we are trying to create new Customer records by calling POST API.

For that we will use following setup.

Create ODBC Connection for API

Check this section from previous article to learn how to configure API Connection using ZappySys ODBC Driver for JSON / XML / CSV.

Create Relational Connection in Workflow Designer

Check this section from previous article to learn how to create and configure Relational Connection of ODBC Type which points to DSN (ZappySys JSON Driver).

Configure JSON connection in Informatica for REST API / JSON File connectivity – Using ZappySys JSON ODBC Driver

Prepare POST Query and generate Metadata File

Before you can call POST API in Informatica Mapping, you need to generate Metadata file using ODBC Data Source UI. Metadata file creation is important to avoid double calls (One for Metadata and One for Getting Data). When you dont Supply Metadata file to ZappySys Driver then it will try to call API twice (First time read 300 rows to guess datatypes / response columns and then call API again to read all remaining rows from response).

Its OK to allow two reads for the same request if its GET request (Read scenario) but its not OK if you are creating a New records because same request is sent twice and you may end up creating duplicate records.

Obtaining metadata is simple using Query Preview UI.

1. Go to ODBC Data Source and setup properties on Driver UI (e.g. URL, Connection, Filter, Headers etc)
2. Once everything is configured go to Preview Tab and click Preview Button to see data.
3. Once Data is returned as per your need you can click on Save Metadata. Copy SQL Query for later use.
   

   Generate Metadata File for REST API POST Operation using ZappySys API Driver (JSON / XML)

Create Informatica Mapping to POST data to REST API / SOAP Web Service

Once Metadata File is we can proceed to Informatica Mapping designer. For making instructions simple we will skip few details (e.g. Importing Source  /Target Definitions). Refer to Previous article to read instructions in depth.

Created Now lets look at how to read data from relational source (E.g. SQL Server, Oracle) and send data to REST API (Call POST API).

1. Drag Source into Mapping Designer
2. Drag Expression Transform  into Mapping Designer and drop desired columns on Expression Transform as Pass through Columns.
3. Create one additional Output Port for API URL as below (You may not need this if API URL is not Dynamic. Skipping URL or any other setting in ODBC SQL Query will use DSN Settings you configured in previous section)
4. Drag SQL Transform and select following Option (Mode = Query, Connection Type =ODBC)
   

   Create new SQL Transform for API Call (POST Data to API using Informatica and ZappySys ODBC Driver)

5. Now connect input columns from Expression Transform to SQL Transformation. These input columns will be used as parameters in API POST Body and SQL Query WITH Clause to craft JSON / XML API request.
6. Now double click on SQL Transform and go to SQL Ports Tab
7. Click somewhere in the Output Columns Group and Add desired columns (Tip: Add same number of columns you define in the Metadata File in Previous section. For Demo purpose you can remove some columns from Metadata file so you have only hadful columns to deal with. When you remove columns from Metadata File make sure JSON is Valid. Many times user forget to remove last comma)
8. Once you define Input and Output columns for your SQL Transform you can Edit SQL Query button and configure your SQL Query as below. In below example query we have supplied URL,  Body, HTTP Headers. Also notice that Body JSON is crafted by using Input Columns from Upstream. We used only CustomerID as an example but in real words you may add many more in your JSON Body.
   
   For Old Version of PowerCenter- V8.5 or lower:  It’s important to Pass URL via Substitution else you may get error (http://abc.com is output as http:/abc.com – only one slash)Here is a sample Query for SQL Transform (Added String Substitutions) 
   Few things to notice:
   – Output Ports defined in SQL Transform must match order and column names of SQL query. Best thing is to avoid SELECT * FROM and use explicit column names like below. If you already took care column orders in Metadata file then you can use * to shorten your SQL statement.
   – Slash (i.e. \ ) is treated as escape character so replace slash with double slash anywhere in SQL text(e.g. c:\temp\meta.txt should be replaced with c:\\temp\\meta.txt).
   – If you use ? in URL (e.g. http://myapi/?id=111) then replace ? with \?  because ? has special meaning in SQL Transform SQL Text.  ? is used in Parameter Binding (e.g. ?my_input_port?) .
   – You may use Format Specifiers

   <<~P_URL~,FUN_JSONENC>>

     if you want to encode special characters in your data (e.g. Tabs, Double quotes, New lines). Check this link
   – Avoid using string specifier before back slash (e.g. c:\\data\\~FileName~ ). because \~ cause issue with escape sequence triggered by \ . To solve this issue Use Expression Transform before SQL Transform to build Dynamic Path or other type of string.
   

   SELECT url,origin FROM $
   WITH
   (
     META='c:\\temp\\meta.txt'
    ,METHOD='POST'
    ,HEADER='Content-Type:text/plain||x-hdr1:AAA'
    ,SRC='~P_URL~'
    ,BODY='
    {
       "ID": "~P_CustomerID~",
       "Link": "<<~P_URL~,FUN_JSONENC>>",
       "Notes": "Line1\\r\\nLine2"
    }'
   )

   

   Configure Informatica SQL Transform to call ODBC SQL Queries – JSON /XML API POST Data (Create / Update Records)

9. In the above Screenshot Notice Following items in SQL Query.
   1. We have specified META property (Use the same Metadata File we generated   in the previous section. Meta Property can take direct file path, meta name (settings stored in DSN) or supply direct JSON for Metadata. Notice we escaped \ with \\
      

      META='[ {"Name": "MyCol1", "Type": "String", "Length": 100}, {"Name": "MyCol2", "Type": "String", "Length": 100} ...... ]'
      -- OR --
      META='c:\\meta\\my_post_query_metadata.txt'
      -- OR --
      META='MyMetaName'

   2. Second thing you will Notice that in the Body we have used String Substitution in SRC and BODY.  If your URL is not Dynamic and you like to use setting defined in DSN then omit SRC attribute from WITH clause. Substitution must start and end with tild (~). For example Input column P_URL can be used as ~P_URL~ and at runtime it will be replaced. Make sure to escape  single quote with double quote (We replaced ‘ with ” in Sam”s) in Input Parameter Values else SQL Query will fail. You can use Expression Transform to escape data if needed using REPLACE function.  We also replaced \r\n with \\r\\n
      

      SRC='~P_URL~'

      and
      

      BODY='
       {
          "ID": "~P_CustomerID~",
          "Notes": "Line1\\r\\nLine2, Sam''s Club"
       }'

10. Now connect your SQL Transformation output Ports to Target (e.g. Flat File Target or Relational Target)
11. Create new Workflow and Session using this Mapping
12. Go to Session properties and on the Mapping Tab make sure to change COnnection Type for SQL Transformation to Relational Connection.
    

    Configure Session Mapping Properties – Set ODBC COnnection Type for SQL Transform to call API requests

13. In our example we changed Target to File Writer but you can save SQL Transform output to some relational table too.
14. Now you can execute Workflow and check your session log for any error. You can also debug web requests in Fiddler (Must be installed on Server where actual Job is running).
    

    Monitor Session Execution in Informatica – Debug Web API requests using Fiddler

Upload File to API (Read Body from Local File)

Now let’s look at scenario to POST Body content from File (i.e. Upload File to API). Below simple query will Upload file content to API server (POST request where Body is coming from file)

SELECT url,origin FROM $
WITH
(
  META='c:\\temp\\meta.txt'
 ,METHOD='POST'
 ,HEADER='Content-Type:text/plain||x-hdr1:AAA'
 ,SRC='~P_URL~'
 ,BODY='@~P_FilePath~'
 ,IsMultiPart='True'
)

Notice how we have used IsMultiPart = ‘True’  and used @ before FilePath in Body. Our File Path is coming from String Substitution (i.e. Input Port  ~P_FilePath~)

Debugging REST / SOAP API using Fiddler

Check this article on how to debug REST / SOAP API calls using fiddler. You can also enable Log to Debug Mode on Advanced Tab of ODBC DSN UI.

Conclusion

In this post we saw how to call API POST requests in Informatica and send data from relational system to Web API (Create / Update / Delete Records using JSON / XML API calls). You can explore many other API related scenarios using ZappySys ODBC Drives for JSON / XML / CSV. Click here to try ZappySys ODBC Drivers for FREE and check out how easy it is to read / write JSON / XML API in Informatica or any other ODBC Compliant Apps (e.g Power BI, SSIS, Qlik).

The post POST data to API in Informatica using SQL Transformation appeared first on ZappySys Blog.

JSON / REST API is becoming more and more popular each day as everyone embrace cloud-centric services. This article is primarily focused on Informatica users who want to do XML SOAP/ JSON / REST API Integration in Informatica. However many tips and techniques described in this article will help you to understand how to integrate XML SOAP / JSON / REST API in other ETL / Reporting apps such as Tableau, Power BI, SSRS, Talend, Excel and many more.

After going through this article you will learn how to Read JSON in Informatica and understand the concept of JSON / REST API. We will go through many screenshots and step-by-step examples to demonstrate  JSON File or REST API integration in Informatica PowerCenter.

XML / JSON can come from a local file or REST API service (internal or public) so we will include both examples in this article (i.e. Read JSON files in Informatica,  Import REST API in Informatica). So let’s get started. Next article will focus on how to write data to API in Informatica (POST / PUT data)

Requirements

This article assumes that you have full filled following basic requirements.

1. Download Install ZappySys ODBC PowerPack (Drivers for JSON and REST API)
2. Install Informatica PowerCenter Client Tools (e.g. Workflow and Mapping Designers)
3. Access to a Relational database such as SQL Server (or use any of your choice e.g. Oracle, MySQL, DB2 ). If nothing available then you can use flat file target.

How to Import JSON data using Informatica (Read JSON Files or REST API)

Before we dive deep to learn how to load JSON data in Informatica (JSON to SQL Table), Here the summary of high-level steps you need to perform to import JSON Files or REST API in Informatica.

1. Download and Install ZappySys JSON ODBC Driver (for JSON Files and REST API)
2. Create ODBC DSN using ZappySys JSON driver for your API Service (You can override most of the DSN settings via SQL Query at runtime)
3. Create Relational > ODBC Connection in Informatica Workflow designer (Point to JSON DSN we created in the previous step)
4. Import JSON Source Definition in the Informatica Mapping Designer > Sources Tab
5. Import Target Table Definition in the Informatica Mapping Designer > Targets Tab
6. Create source to target mapping in Mappings tab
7. Save mapping (name m_API_to_SQL_Load )
8. Create Session using the mapping we created in the previous step
9. Save Workflow and execute to load JSON data into SQL Table. Verify your data and log.
   

   Loading JSON data to SQL Table in Informatica (Import REST API or JSON Files)

Video Tutorial – Read JSON in Informatica (Load JSON to SQL Table)

By watching following ~5 min video can learn steps listed in this article to load JSON API data into SQL Server Table using ZappySys JSON Driver. You can go though full article to learn many useful details not covered in this video.

Getting Started – Import JSON to SQL Server in Informatica

Now let’s get started. For example purpose, we will read data from OData JSON based REST API service and load data into SQL Server Table using Informatica Workflow.

Create ODBC DSN using ZappySys JSON Driver

The first step to read from JSON File or REST API Service in Informatica is to create ODBC DSN.

1. Search for ODBC in your start menu and open ODBC Data Sources (64bit). You can also find same under ZappySys > ODBC PowerPack > ODBC Data Sources (64bit)
2. When ODBC UI shows up, Go to System tab.
3. Click on Add
4. Select ZappySys JSON Driver from the list and click Finish.
   

   Create New DSN for JSON File or REST API – Use ZappySys JSON Driver

5. When Configuration UI enter the following URL for Data source. You can also enter JSON File path here too but for this example, we will use OData REST API (JSON Format). Click Test to confirm its working. This API doesn’t use any credentials but in the real world, you may have credentials (e.g. OAuth creds using Key / Secret or Basic Auth using UserID / Password). Below URL is default URL for your DSN. You can always override URL and other settings from SQL Query using WITH Clause (see examples)
   

   https://services.odata.org/V3/Northwind/Northwind.svc/Invoices?$format=json

   

   Configure ODBC DSN for JSON Data

6. Optionally one more setting you can change is Under Other settings >>>  Date data type set option to Convert to DateTime (Timezone lost). If you don’t do this then OrderDate field or any other Date Field will be detected as nstring in Informatica. Later in this section, we will show you how to convert nstring to DateTime using Expression Transform (TO_DATE function).
7. Now switch to Preview Tab and try some sample queries to learn more about API driver. For example, you can try some with simple queries like below. For more advanced queries read this help file.Read from root level (include all attributes)
   

   select * from $

   Read from an array (value tag)
   

   select * from value
   --OR--
   select * from $ WITH (Filter='$.value[*]')

   Override URL (Supply different URL than entered in ODBC DSN UI)
   

   SELECT * FROM $
   WITH (SRC='https://api.hubapi.com/contacts/v1/lists/all/contacts/all?hapikey=demo&count=20', 
   Filter='$.contacts[*]')

8. Click on View Examples to check other example queries
   

   ODBC JSON Driver Query Preview – Informatica JSON Query Examples (Read REST API or JSON Files)

9. Click OK to save your DSN Properties.
10. Click OK to close ODBC Data SOurces UI.

Create Connection in Informatica Workflow Designer

Once you create DSN using JSON Driver our next step is to define a connection for JSON source in Informatica PowerCenter Workflow designer.

1. Open Workflow designer [W] icon
2. Goto Connections > Relational
   

   Create a new connection for JSON in Informatica

3. Click New and select ODBC
   

   Select ODBC connection type in Informatica (Using ZappySys JSON ODBC DSN)

4. Now on the ODBC connection setup enter connection name, some fake userid / password (this is a required field but its ignored by JSON Driver)
5. In the Connection String field enter the exact same name of DSN (Open ODBC Data Sources UI to confirm)
   

   Configure JSON connection in Informatica for REST API
   / JSON File connectivity – Using ZappySys JSON ODBC Driver

6. Click OK to close the connection properties.

That’s it. Now we ready to move to next step (define source and target in Mapping Designer).

Import JSON Source Definition in Informatica Mapping Designer

Now let’s look at steps to import JSON source table definition.

1. Open Informatica Mapping Designer (Click [D] icon)
2. Click on Source Icon to switch to Sources designer
3. From the top menu > Click on Sources > Import from Database …
   

   Import JSON Source definition in Informatica Mapping Designer (JSON file or REST API)

4. Select ODBC data source from the dropdown (Find out DSN we created earlier to use as JSON Source)
5. Click Connect button to get a list of tables. Any array node is listed as a table. Also, you will see array node with parent columns (e.g. value_with_parent). You may get some warning like below but they are harmless so just ignore by clicking OK.
   
   DLL name entry missing from C:\Informatica\PowerCenter8.6.1\client\bin\powrmart.ini Section = ODBCDLL Entry = ZappySys JSON Driver
   —————————————————-
   Using EXTODBC.DLL to support ZappySys JSON Driver. For native support of ZappySys JSON Driver make an entry in the .ini file.
   

   Select JSON Source Table in Informatica Mapping Designer (JSON file or REST API)

6. Select Table you wish to get (You can filter rows by custom SQL query. We will see later in this article how to do)
7. Optionally once table structure is imported you can rename it
   

   Rename imported table definition in Informatica Source Designer

8. That’s it, we are now ready to perform similar steps to import Target table structure in the next section.

Import SQL Server Target Definition in Informatica Mapping Designer

Now let’s look at steps to import Target table definition (very similar to the previous section, the only difference is this time we will select DSN which points to SQL Server or any other Target Server). For example purpose, we will use following table structure as our SQL Server Table. If its missing you can create one.

CREATE TABLE [dbo].[Tbl_Invoices](
	[ShipName] [nvarchar](40) NULL,
	[ShipAddress] [nvarchar](60) NULL,
	[ShipCity] [nvarchar](15) NULL,
	[ShipRegion] [nvarchar](15) NULL,
	[ShipPostalCode] [nvarchar](10) NULL,
	[ShipCountry] [nvarchar](15) NULL,
	[CustomerID] [nchar](5) NULL,
	[CustomerName] [nvarchar](40) NULL,
	[Address] [nvarchar](60) NULL,
	[City] [nvarchar](15) NULL,
	[Region] [nvarchar](15) NULL,
	[PostalCode] [nvarchar](10) NULL,
	[Country] [nvarchar](15) NULL,
	[Salesperson] [nvarchar](31) NULL,
	[OrderID] [int] NULL,
	[OrderDate] [datetime] NULL,
	[RequiredDate] [datetime] NULL,
	[ShippedDate] [datetime] NULL,
	[ShipperName] [nvarchar](40) NULL,
	[ProductID] [int] NULL,
	[ProductName] [nvarchar](40) NULL,
	[UnitPrice] [money] NULL,
	[Quantity] [smallint] NULL,
	[Discount] [real] NULL,
	[ExtendedPrice] [money] NULL,
	[Freight] [money] NULL
)

Now lets look at steps to import target table definition in Informatica mapping designer.

1. In the Mapping Designer, Click on Target Icon to switch to Target designer
2. From the top menu > Click on Targets > Import from Database …
3. Select DSN for your Target server (if DSN doesn’t exist then create one by opening ODBC Sources just like we created one for JSON API source (see the previous section about creating DSN).
   

   Import target Table Definition in informatica

4. Enter your userid , password and Schema name and click Connect to see tables
5. Select Table name to and click OK import definition.
   

   Import Target SQL Table Definition in Informatica – Select table from the list

Create Source to Target Mapping in Informatica (Import JSON to SQL Server)

Once you have imported source and target table definition, we can create mapping and transformation to load data from JSON to SQL Table.

1. First open Mapping Designer (Click [D] icon)
2. Drag JSON Source from sources folder
3. Drag SQL Table from Targets folder
4. Map desired columns from Source to target
   

   Define Source to Target mapping for JSON to SQL Table load in Informatica

5. For certain columns you may have to do datatype conversion. For example to convert OrderDate form nstring to DataTime you have to use Expression Transform like below and map it to target. In below example, our JSON has date format (e.g. 2018-01-31 12:00:00 AM ). To import this to DateTime field in SQL server we need to convert it using TO_DATE function. Use double quotes around T to make this format working.
   

   TO_DATE(OrderDate,'YYYY-MM-DD H12:MI:SS AM')
   
   --For ISO use below way
   TO_DATE(OrderDate,'YYYY-MM-DD"T"HH24:MI:SS')

   

   Informatica JSON to SQL Table Mapping – Datatype conversion (nstring to datetime)

6. Once you done with mapping save your mapping and name it (i.e. m_Api_To_SQL)
7. Now lets move to next section to create workflow.

Create Workflow and Session in Informatica

Now the final step is to create a new workflow. Perform following steps to create workflow which with a session task to import JSON data into SQL table.

1. Open workflow designer by click [W] icon.
2. Launch new workflow creation wizard by click Workflow top menu >  Wizard
   name your workflow (e.g. wf_Api_Tp_Sql_Table_Import)
   

   Creating Informatica Workflow – Wizard UI (Import JSON data to SQL Table)

3. Finish the wizard and double-click the Session to edit some default properties.
4. First change Error settings so we fail session on error (By default its always green)
   

   Fail Informatica Session on error (JSON to SQL Load)

5. Select JSON connection for Source
   

   Select JSON Source Connection in Informatica – JSON File / REST API Load to SQL Table

6. Change default Source query if needed. You can pass parameters to this query to make it dynamic.
   

   Modify JSON Source SQL query – Pass parameters, change URL, set filter etc

7. Select Target connection of SQL Target Table
   

   Select SQL Target Connection in Informatica – JSON File / REST API Load to SQL Table

8. Save workflow
9. That’s it. We ready to run our first workflow to load JSON data to SQL.

Execute Workflow and Validate Log in Informatica

Now once you are done with your workflow, execute it to see the log.

Loading JSON data to SQL Table in Informatica (Import REST API or JSON Files)

Import JSON Files in Informatica (Single or multiple)

So far we have seen an example of loading JSON REST API in Informatica but loading JSON files are pretty much same process. Rather than URL, you have to specify JSON file path as Data source.

ZappySys JSON Driver is capable of reading from JSON file, REST API, and embedded JSON string.

Reading JSON data from single File Informatica

select * from $ (SRC=’c:\data\customer_2015.json’, Filter=’$.rows[*]’)

Reading JSON data from multiple Files in Informatica

select * from $ (SRC=’c:\data\customer_*.json’, Filter=’$.rows[*]’)

Reading JSON data from embedded string

SELECT * FROM $ 
WITH 
(
Filter='$.rows[*]',
DATA='
{          
  rows : [
        {id:1, name: "AAA"}, 
        {id:2, name: "BBB"}, 
        {id:3, name: "CCC"}
  ]
}'
)

Import XML Files in Informatica

Reading from XML files or API can be done using the same way as previous sections except you have to use ZappySys XML Driver. Read help file here to see examples.

POST data to REST API in Informatica

There will be a time when you like to send Source data to REST API or SOAP Web Service. You can use below Query for example. For detailed explanation on how to POST data in Informatica check this article.

SELECT * FROM $
WITH 
(METHOD='POST' 
,HEADER='Content-Type:text/plain || x-hdr1:AAA'
,SRC='http://httpbin.org/post'
,BODY='{ data of body goes here }'
)

Video Tutorial – How to POST data to REST API in Informatica

Here is detailed step by step video on REST API POST in informatica PowerCenter

Upload file to REST API in Informatica

Above example was POST data to API URL but what if your Request Body is large and you have saved that to file? Well here is the way to get your request body from a file (Use @ symbol before path and add IsMultiPart=’True’). Refer to this post to learn more about Raw Upload and Multi-Part Upload

SELECT * FROM $
WITH 
(METHOD='POST' 
,HEADER='Content-Type:text/plain || x-hdr1:AAA'
,SRC='http://httpbin.org/post'
,BODY='@c:\files\dump.xml'
,IsMultiPart='True'
)

Calling XML SOAP Web Service in Informatica

So far we have looked at examples to consume data using JSON driver. Now lets look at an example, to call XML SOAP Web Service in Informatica.

To call SOAP API you need to know Request XML Body Structure. If you are not sure how to create SOAP Request body then no worries. Check this article to learn how to generate SOAP Request body using the Free tool SoapUI. Basically, you have to use SoapUI to generate Request XML and after that, you can replace parameters as needed in the generated body.

What is SOAP Web Service?

If you are new to SOAP Web Service sometimes referred as XML Web Service then please read some concept about SOAP Web service standard from this link There are two important aspects in SOAP Web service.

1. Getting WSDL file or URL
2. Knowing exact Web Service URL

What is WSDL

In very simple term WSDL (often pronounced as whiz-dull) is nothing but a document which describes Service metadata (e.g. Functions you can call, Request parameters, response structure etc). Some service simply give you WSDL as xml file you can download on local machine and then analyze or sometimes you may get direct URL (e.g. http://api.mycompany.com/hr-soap-service/?wsdl )

Example SQL Query for SOAP API call using ZappySys XML Driver

Here is an example SQL query you can write to call SOAP API. If you not sure about many details then check next few sections on how to use XML Driver User Interface to build desired SQL query to POST data to XML SOAP Web Service without any coding.

SELECT * FROM $
WITH(
	 Src='http://www.holidaywebservice.com/HolidayService_v2/HolidayService2.asmx'
	,DataConnectionType='HTTP'
	,CredentialType='Basic' --OR SoapWss
	,SoapWssPasswordType='PasswordText'
	,UserName='myuser'
	,Password='pass$$w123'
	,Filter='$.soap:Envelope.soap:Body.GetHolidaysAvailableResponse.GetHolidaysAvailableResult.HolidayCode[*]'
	,ElementsToTreatAsArray='HolidayCode'	
	,RequestMethod='POST'	
	,Header='Content-Type: text/xml;charset=UTF-8 || SOAPAction: "http://www.holidaywebservice.com/HolidayService_v2/GetHolidaysAvailable"'
	,RequestData='
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:hol="http://www.holidaywebservice.com/HolidayService_v2/">
   <soapenv:Header/>
   <soapenv:Body>
      <hol:GetHolidaysAvailable>
         <!--type: Country - enumeration: [Canada,GreatBritain,IrelandNorthern,IrelandRepublicOf,Scotland,UnitedStates]-->
         <hol:countryCode>UnitedStates</hol:countryCode>
      </hol:GetHolidaysAvailable>
   </soapenv:Body>
</soapenv:Envelope>'
)

Now let's look at steps to create SQL query to call SOAP API. Later we will see how to generate code for your desired programming language (e.g. C# or SQL Server)

Video Tutorial - Introduction to SOAP Web Service and SoapUI tool

Before we dive into details about calling SOAP API using ZappySys XML Driver, lets first understand what is SOAP API and how to create SOAP requests using SoapUI tool. You will learn more about this process in the later section. The video contains some fragment about using SOAP API in SSIS but just ignore that part because we will be calling Soap API using ZappySys ODBC Driver rather than SSIS Components.  

Using SoapUI to test SOAP API call / Create Request Body XML

Assuming you have downloaded and installed SoapUI from here, now we are ready to use WSDL for your SOAP Web Service Calls. If you do not have WSDL file or URL handy then contact your API provider (sometimes you just have to add ?wsdl at the end of your Service URL to get WSDL so try that. Example: http://mycompany/myservice?wsdl ). If you don't know what is WSDL then in short, WSDL is Web service Description Language (i.e. XML file which describes your SOAP Service). WSDL helps to craft SOAP API request Body for ZappySys XML Driver. So Let's get started.

1. Open SoapUI and click SOAP button to create new SOAP Project
2. Enter WSDL URL or File Path of WSDLFor example WSDL for our sample service can be accessed via this URL

   http://www.dneonline.com/calculator.asmx?wsdl

   
   Create new SOAP API Project in SoapUI tool for SOAP API Testing
3. Once WSDL is loaded you will see possible operations you can call for your SOAP Web Service.
4. If your web service requires credentials then you have to configure it. There are two common credential types for public services (SOAP WSS or BASIC )
   1. To use SOAP WSS Credentials select request node and enter UserId, Password, and WSS-PasswordType (PasswordText or PasswordHash)
      
      Configure SOAP WSS Credentials for SoapUI (SOAP API Testing Tool)
   2. To use BASIC Auth Credentials select request node and double-click it. At the bottom click on Auth (Basic) and From Authorization dropdown click Add New and Select Basic.
      Configure Basic Authorization for SoapUI (SOAP API Testing Tool)
5. Now you can test your request first Double-click on the request node to open request editor.
6. Change necessary parameters, remove optional or unwanted parameters. If you want to regenerate request you can click on Recreate default request toolbar icon.
   Create SOAP Request XML (With Optional Parameters)
7. Once your SOAP Request XML is ready, Click the Play button in the toolbar to execute SOAP API Request and Response will appear in Right side panel. Test SOAP API using SoapUI Tool (Change Default XML Body / Parameters, Execute and See Response)

Create DSN using ZappySys XML Driver to call SOAP API

Once you have tested your SOAP API in SoapUI tool, we are ready to use ZappySys XML driver to call SOAP API in your preferred BI tool or Programming language.

1. First open ODBC Data Sources (search ODBC in your start menu or go under ZappySys > ODBC PowerPack > ODBC 64 bit)
2. Goto System DSN Tab (or User DSN which is not used by Service account)
3. Click Add and Select ZappySys XML Driver ZappySys ODBC Driver for XML / SOAP API
4. Configure API URL, Request Method and Request Body as below ZappySys XML Driver - Calling SOAP API - Configure URL, Method, Body
5. (This step is Optional) If your SOAP API requires credentials then Select Connection Type to HTTP and configure as below.
   ZappySys XML Driver - Configure SOAP WSS Credentials or Basic Authorization (Userid, Password)
6. Configure-Request Headers as below (You can get it from Request > Raw tab from SoapUI after you test the request by clicking the Play button) Configure SOAP API Request Headers - ZappySys XML Driver
7. Once credentials entered you can select Filter to extract data from the desired node. Make sure to select array node (see special icon) or select the node which contains all necessary columns if you don't have array node. Select Filter - Extract data from nested XML / SOAP API Response (Denormalize Hierarchy)
8. If prompted select yes to treat selected node as Array (This is helpful when you expect one or more record for selected node) Treat selected node as XML Array Option for SOAP API Response XML

Preview SOAP API Response / Generate SQL Code for SOAP API Call

Once you configure settings for XML Driver now you can preview data or generate example code for desired language (e.g. C#, Python, Java, SQL Server). Go to Preview tab and you will see default query generated based on settings you entered in previous sections. Attributes listed in WITH clause are optional. If you omit attribute in WITH clause it will use it from Properties tab.

Preview Data

Preview SOAP API Response in ZappySys XML Driver

Generate Code Option

Generate Example Code for ZappySys Driver

REST API Pagination in Informatica

SELECT * FROM $
WITH(
SRC=@'https://zappysys.com/downloads/files/test/pagination_nextlink_inarray_1.json'
,NextUrlAttributeOrExpr = '$.nextlink'  --keep reading until this attribute is missing. If attribute name contains dot then use brackets like this $.['my.attr.name']
)

SELECT * FROM $
WITH (
SRC=@'https://zappysys.com/downloads/files/test/page-xml.aspx?page=1&mode=DetectBasedOnResponseStatusCode'
,PagingMode='ByUrlParameter'
,PagingByUrlAttributeName='page'
,PagingByUrlEndStrategy='DetectBasedOnResponseStatusCode'
,PagingByUrlCheckResponseStatusCode=401
,IncrementBy=1
)

SELECT * FROM $
WITH (
SRC=@'https://zappysys.com/downloads/files/test/cust-<%page%>.xml'
,PagingMode='ByUrlPath'
,PagingByUrlAttributeName='<%page%>'
,PagingByUrlEndStrategy='DetectBasedOnRecordCount'
,IncrementBy=1
)

SELECT * FROM $
LIMIT 25
WITH(
	 Src='https://wordpress.org/news/wp-json/wp/v2/categories?per_page=10'
	,PagingMode='ByResponseHeaderRfc5988'
	,WaitTimeMs='200' --//wait 200 ms after each request
)

Error Handling in REST API

Sometimes errors occur... they just do and there is nothing you can do! Or can you? Actually, in ODBC PowerPack you can handle them in two ways.

METHOD 1 - Using Error Handling Options

When to use?

You may want to use them when your source is a resource located on the Internet; e.g. a file on a website, a file on an FTP server or just a plain API HTTP response. By default, when a remote server returns an error, data retrieval is stopped, an error is raised and no data is given back to you. This might not be always desirable.

Scenario 1

Imagine a scenario, that there is a web server which each day at 12 AM releases a new JSON file with that day's date as filename, e.g. http://www.some-server.com/data/2018-06-20.json. And, of course, you want to download it and use it daily in your Power BI report. But you have a problem: Power BI report data sources are refreshed each hour and you may get HTTP 404 status code (no file was found) when a file is not released yet. Which consequentially means other data sources won't be updated as well and you will see old and cached data on the report. That's where you could use Continue on any error or Continue when Url is invalid or missing (404 Errors) to avoid an error being raised and let other data sources to be updated.

Scenario 2

Another scenario is when you expect a web server to raise some kind of HTTP error when accessing a URL. You don't want ODBC Data Source to raise an error but instead, you want to get response data. That's where you can use Continue on any error or alike together with  Get response data on error to continue on an error and get the data:

METHOD 2 - Using Connection [Retry Settings]

Another scenario you may run into is a buggy web server. You ask it to give you some file or data and it, like a snotty kid, just doesn't give it to you! You have to ask twice or thrice before it does its job. If that's the case, you have to retry HTTP requests using Connection:

Performance consideration for REST API

Coming soon…

Security consideration for REST API

If you need to authenticate or authorize your user to access a web resource, you will need to use one of the Connections:

• HTTP
• OAuth

HTTP Connection

Use HTTP Connection for simple Windows, Basic, NTLM or Kerberos authentication. Just fill in a username and a password and you are good to go!

You can also use HTTP Connection for more sophisticated authentication like:

• SOAP WSS (when accessing a SOAP WebService)
• Static Token / API Key (when need to pass an API key in HTTP header)
• Dynamic Token (same as Static Token method except that each time you need to log in and retrieve a fresh API key)
• JWT Token (As per RFC 7519)

OAuth

If you are trying to access REST API resource, it is a huge chance, you will need to use OAuth Connection. Read this article to understand how OAuth authentication and authorization works and how to use it (article originally was written for SSIS PowerPack, but the concepts and UI stay the same): 
https://zappysys.com/blog/rest-api-authentication-with-oauth-2-0-using-ssis/

Conclusion

Consuming data from JSON files or REST API in Informatica can be challenging but not to worry anymore. Using ZappySys JSON Driver you get most innovative JSON processing engine which not only processes/denormalizes nested JSON but also gives you 100+ Options to cover almost any API processing scenario. You can use this driver to consume data in any ODBC compliant app (i.e. Tableau, Power BI, Excel) and Programming Languages (i.e. C#, Java, Python, PHP). Click here to Download a FREE trial of ZappySys ODBC PowerPack and learn how to perform JSON / API integration in Informatica without any coding.

Keywords

how to import json file in informatica | how to read json file in informatica powercenter | how to test json from informatica | how to use jsaon file as source in informatica power center | how to use json in informatica 10 | informatica how to import data from rest api | informatica jtx to import json file (use of java transformation) | informatica plugin for restful api using json | informatica power center and json support | informatica read json files | informatica rest api | informatica rest api connector | json parser import informatica

The post Read JSON in Informatica – Import REST API / SOAP / JSON File appeared first on ZappySys Blog.