Tools Archives | ZappySys Blog

How to migrate Postman API call to SSIS / ODBC PowerPack

ZappySys — Thu, 17 Oct 2019 16:41:23 +0000

Introduction

In the previous article, we learned how to copy settings from curl to ZappySys products, and in this article, we will continue on how to migrate Postman API call to SSIS / ODBC PowerPack. Postman is a very popular client tool to test API calls. Many API providers document how to call their API using Postman. In this article we will focus on how to use the same settings in ZappySys Products to implement API integration in SSIS or other apps like Power BI, Informatica, Excel, Tableau, SSRS… many ODBC apps.

When you are connecting to an API you may have examples of how to do that in Postman. If you know how to do it in Postman, you are one step away from making it work in SSIS PowerPack and ODBC PowerPack (JSON, XML, CSV Drivers, and other). Most of the examples will show how to do that specifically using ODBC PowerPack and JSON Driver, but since ODBC PowerPack UI is very similar to the connectors of SSIS PowerPack, it will be quite clear where to use it in SSIS PowerPack as well. In the examples where UI differs significantly, both – ODBC and SSIS PowerPack – examples will be presented.

Prerequisites

In this article we assume you meet these requirements:

When migrating Postman API call to SSIS PowerPack

Postman installed.
SSIS designer installed. Sometimes it is referred to as BIDS or SSDT (download it from Microsoft site).
Basic knowledge of SSIS package development using Microsoft SQL Server Integration Services.
ZappySys SSIS PowerPack is installed (download it).

When migrating Postman API call to to ODBC PowerPack

Postman installed.
ZappySys ODBC PowerPack installed (download it).

The Basics

This section shows how to migrate simple options such as URL, HTTP Request Method, and HTTP Headers.

How to configure the URL and HTTP Request Method

Migrate Postman API call to SSIS / ODBC (API URL setting to ODBC Driver (GET / POST) )

How to configure HTTP Headers

Migrate Postman HTTP Headers setting to ODBC Driver

Posting data

In this section, you will find how to post data in ZappySys products. You will learn how to post different formats of data, upload files and send multi-part data.

How to configure POST raw body

Migrate Postman Body / Content-Type setting to ODBC Driver

How to configure POST JSON body

Migrate Postman Body / Content-Type setting to ODBC Driver

Use this table to determine what kind of Body Content Type to configure:

Data type	Body Content Type
Text	text/plain
JSON	application/json
HTML	text/html
XML	application/xml
You don’t know the type	Default (i.e. form/x-www-form-urlencoded data)

How to configure POST form/x-www-form-urlencoded data

Migrate Postman Body (x-www-form-urlencoded) setting to ODBC Driver

How to configure multipart form POST data

Migrate Postman Multi-Part File Upload setting to ODBC Driver (Upload File)

Authentication

This section will cover all common authentication methods, starting from using API Key to OAuth 2.0.

How to authenticate using API Key in HTTP headers

Authentication – Migrate Postman API Key (via header) setting to ODBC Driver

How to authenticate using API Key as a parameter in URL

Authentication – Migrate Postman API Key (via URL query parameter) setting to ODBC Driver

How to authenticate using Bearer Token

Authentication – Migrate Postman Bearer Token setting to SSIS / ODBC Driver

How to authenticate using Basic Authentication

In ODBC PowerPack

Authentication – Migrate Postman Basic Auth setting to SSIS / ODBC Driver (Login using Userid / password)

In SSIS PowerPack

In SSIS PowerPack use the same configuration as above, just create ZS-HTTP Connection Manager using instructions below:

Authentication – Migrate Postman Basic Auth setting to SSIS JSON / XML Source (Login using Userid / password)

How to authenticate using OAuth

In ODBC PowerPack

Configure main options:
Authentication – Migrate Postman OAuth setting to SSIS / ODBC Drivers ( JSON / XML / CSV API) – Client ID / Secret / Scope / Auth and Token Url (Client Credential Grant Type, Password Grant Type, Code Authorization Grant Type)
Configure Callback/Return Url:
Authentication – Migrate Postman OAuth setting to SSIS / ODBC Drivers ( Callback / Redirect URL )

If you are using a known, public API service, you may try locating it in the OAuth Providers list, which will save you from configuring Authorization and Access Token URLs:

For simplicity and if your company policy allows it or at least for testing purposes, you can use a Default OAuth Application created by ZappySys:

In SSIS PowerPack

In SSIS PowerPack use the same configuration as above, just create ZS-OAUTH Connection Manager using instructions below:

Authentication – Migrate Postman OAuth setting to SSIS JSON / XML Source

How to authenticate using AWS Signature

In ODBC PowerPack

Authentication – Migrate Postman AWS API call setting to SSIS / ODBC Drivers ( JSON / XML / CSV API call)

In SSIS PowerPack

In SSIS PowerPack use the same configuration as above, just create ZS-OAUTH Connection Manager using instructions below:

How to authenticate using NTLM Authentication

In ODBC PowerPack

In SSIS PowerPack

In SSIS PowerPack use the same configuration as above, just create ZS-HTTP Connection Manager using instructions below:

Conclusion

This article was quite self-explanatory, but if you have any questions or you have an authentication method that is not listed here and you don’t know how to proceed, please, contact us and we will try to help you: https://zappysys.com/support/.

The post How to migrate Postman API call to SSIS / ODBC PowerPack appeared first on ZappySys Blog.

Using Regular Expressions in SSIS

ZappySys — Wed, 07 Mar 2018 17:38:24 +0000

Introduction

In this short article, you will learn how to write Regular expressions in SSIS (i.e. Regex) and what tool to use to test them. You will also find helpful resources on how to write more sophisticated expressions and learn more about them. For demo purposes, we will use FREE SSIS Regex Parser Task to parse and extract the text using Regex.

You can use Regular expressions in several SSIS PowerPack connectors:

Writing Regular Expressions in SSIS

Based on the SSIS component you use it will include the filename in filtering options or match the text: See below Syntax to write Regex in ZappySys tools. We support additional construct {{X, Y}} at the end of Regex to control two parameters. This additional construct is useful for data extracted from matching regex. If you want to Test patterns and not worry about data extraction then no need to use last {{

Occurance_Index

Group_Index_Or_Name

}}

Syntax:

[{{Occurance_Index|*[,Group_Index_Or_Name]}}]

Where:

Occurance_Index

=Occurrence index you want to extract (X=0 means the first match) and * means all matches. Use a minus sign to get an occurrence from reverse (e.g. {{-0}} returns the last match)

Group_Index_Or_Name

=Group index/name within your search pattern (Groups are indicated by parentheses in regular expression, Y=0 means first group). If you named your group in the pattern then you can use the Group name. To use Group Name you must use the new version (the old version doesn’t support this)

How to name a group?

E.g. (\w+)@(?\w+.com)

How to use the group name in the match extract?

E.g. (\w+)@(?\w+.com){{0,domain}}

Example Input:

Let’s assume we have the following input text. We will test various Expressions.

Customer => AAA
Email => aaa@google.com
Phone => 101-222-3333
========
Customer => BBB
Email => bbb@yahoo.com
Phone => 102-222-3333
========
Customer => CCC
Email => ccc@hotmail.com
Phone => 103-222-3333
========
Customer => DDD
Email => ddd@outlook.com
Phone => 104-222-3333

Sample Regex Expressions

Expression	Description
(?s).*	Match anything including new lines. To match anything without new line just use (.*)
\w+([-+.’]\w+)@(?\w+([-.]\w+)\.\w+([-.]\w+)*)	Get first email id from text ({{0}} is omitted from end because {{0}} id default)
\w+([-+.’]\w+)@(?\w+([-.]\w+)\.\w+([-.]\w+)*){{-0}}	Get last email id from text
\w+([-+.’]\w+)@(?\w+([-.]\w+)\.\w+([-.]\w+)){{}}	Get all email addresses (separate them with new line). When you suffix Regular expression with {{*}} it will return all matches.
\w+([-+.’]\w+)@(?\w+([-.]\w+)\.\w+([-.]\w+)*){{2}}	Get third email id from text (i.e. ends with {{X}} where X is occurrence index starting from 0)
\w+([-+.’]\w+)@(?\w+([-.]\w+)\.\w+([-.]\w+)*){{0,2}}	Get first email pattern match (i.e. Index=0) and extract domain (i.e. 2nd group). Index starting from 0 for occurrence and group
(\d)-(\d)-(\d*)	Get first phone number from text (If you don’t include {{X,Y}} at the end then it will be always [0,0])
^((?!demo\|test).)*$	Match whole input text if it does not contain words like demo or test. If word found then No Match
((.\|\n)*?){{0,1}}	Extract anything between … (Include new line char i.e. \n)
(.*){{0,1}}	Extract anything between … (Exclude new line char i.e. \n)
{{0,1}}	Extract content from CData section of XML Data (This can be CSV, JSON or nested XML )
^$	Match blank string

More Regular Expression Examples

Input Text	Regex	Matched text	Comment
	id=”([^”]*)”{{0,1}}	123	This expression shows how to extract group value (i.e. {{0,1}} – first match and 2nd group ). It extracts text between double quotes using [^”]* pattern , match anything until double quote is found. {{0,1}} syntax is ZappySys specific so it may not work with other Regex engines.
123	([^<]*)<\/data>{{0,1}}	123	This expression shows how to extract group value (i.e. {{0,1}} – first match and 2nd group ). It extracts text between double quotes using [^<]* pattern , match anything until < is found. {{0,1}} syntax is ZappySys specific so it may not work with other Regex engines.
File_20180930_source.txt	File	File	Will match text/filename that has “File” keyword in it.
File_20180930_SOURCE.dat File_20180930_source.dat	source\|SOURCE	SOURCE and source	Will match text/filenames that contain either “source” or “SOURCE” keyword.
File_20180930_source.txt	File.+source	File_20180930_source	Will match text/filename that contains keyword that starts with “File” and ends with “source”. Basically, you can use this pattern if you want to match two keywords in the text that appear in particular order.
File_20180930_source.txt File_20180830_source.dat	\.txt$\|\.dat$	.txt and .dat	Will match text/all filenames that end with “.txt” or “.dat”.
File_20180930_source.txt file_20190102_source.txt	^(F\|f)ile_\d{8}	File_20180930 file_20190102	Will match text/filename that starts with “File_” or “file_” and then followed by 8 digits.
File_20180930_source.txt File_20190101_none.txt	(.+)_(.+)_(.+){{0,2}}	20180930	Will match text that has three groups of text strings, separated by “_”. Non-Regex {{0,2}} notation will bring back second group (index “2”) of first match (index “0”).
File_20180930_source.txt File_20190101_none.txt	(.+)_(.+)_(.+){{1,2}}	20190101	Will match text that has three groups of text strings, separated by “_”. Non-Regex {{1,2}} notation will bring back second group (index “2”) of second match (index “1”).
File_20180930_source.txt File_20190101_none.txt	(.+)_(.+)_(.+){{*,2}}	20180930 20190101	Will match text that has three groups of text strings, separated by “_”. Non-Regex {{,2}} notation will bring back second group (index “2”) of all matches (index “”). Returned matches are separated by \r\n
	]+src=”([^”>]+)”{{*,1}}	/img-1.png /img-2.png /img-3.png	Will return image URLs from HTML content. We used {{*,1}} means it will pull all occurrences and for each match it will extract first group (which is just src attribute value).
null	^((?!null\b).)*$		Returns blank if null word found (match all except null)
black white	^((?!red\|blue\|orange).)*$	black white	Returns full string as is if any of those 3 words (i.e. red, blue, orange) not found anywhere in the string
black white red	^((?!red\|blue\|orange).)*$		Returns blank if any of those 3 words (i.e. red, blue, orange) found anywhere in the string

Regex Examples (Using SSIS Regular Expression Parser Task)

Here is an example how Regex

(.+)_(.+)_(.+){{1,2}}

works in Regular Expression Parser Task (FREE):

Using Regular Expressions in SSIS Regex Parser Task (Extract Groups)

Using Groups / Occurrence Index

Some tasks like SSIS Regex Parser Task (FREE) supports extracting value from specific occurrence and specific part of matched pattern using special syntax at the end of your pattern (see below).

Your Regex Pattern Here{{OccuranceIndex,GroupIndex}}

Where :
OccuranceIndex is 0 based (0=extract first occurrence)
GroupIndex is 0 based (0=extract first matching group from pattern. First group is always entire text. )

See above screenshot in previous section for example.

Tools

The best tool we’ve found to write and test Regex is Regex Hero (will require IE with Silverlight if you want to use it online, in the browser):

Another great site for Regex testing is https://regex101.com (Works in any browser unlike previous one)

and few more sites as below

http://www.regexr.com/
http://www.regexlib.com/
http://www.regular-expressions.info/

Resources

Regular Expressions cheat-sheet to hang on the wall

Regular Expressions quick reference

The post Using Regular Expressions in SSIS appeared first on ZappySys Blog.

Tutorial – How to use Fiddler to analyze HTTP Web Requests (Tips)

ZappySys — Tue, 26 Jul 2016 21:47:54 +0000

Introduction

Fiddler is one the most popular tool to inspect your Http Traffic. This tool helps you to test REST API / SOAP Web requests very easily. If you are using SSIS PowerPack or REST API ODBC Drivers you will find this post really useful to debug various REST API integration issues.

When you run Fiddler on your system, it acts as a tiny Web Proxy that sits between your client application and the webserver. Fiddler only starts capturing traffic when you running it. By default, it runs on the local machine (127.0.0.1) Port 8888. You can change the default port from Tools > Options.

How to download Fiddler (it’s FREE)

You can download Fiddler Classic using this link for FREE (If that link doesn’t work then try this one)

Make sure that you have Downloaded the Fiddler Classic and not a Fiddler Everywhere. Both products might have same features listed in this article but screenshots and steps listed in this article is about Fiddler Classic.

Fiddler is a third party Telerik’s tool used to log, inspect, and alter HTTP and HTTPS traffic between a computer and a web server or servers.
It is not our product, this article is just to show you how you can analyze the API Request and Response call made from our Tasks/Components/Drivers.

How to start/stop Fiddler two ways – Capture HTTP(s) Traffic

After you install Fiddler, Go to Start Menu >Search for Fiddler

Launch Fiddler exe and it will start capturing HTTP traffic (For HTTPS URL see next section).

Run fiddler to start capturing web requests/responses made by various client applications on your system (e.g. Curl, Chrome, Internet Explorer). To start/stop capture go to File > Check/Uncheck [Capture Traffic] option.

By default when you run Fiddler it behaves like the default proxy server on your system. However, not all web requests appear in fiddler unless the client application using a system Default Proxy.

Start / Stop Fiddler Capture

How to capture HTTPS traffic in Fiddler

By default Fiddler doesn’t show the content of Web requests made to HTTPS Url (Secure site) because it’s encrypted. Perform the following steps if you want to see HTTPS Traffic.

Launch Fiddler
Go to Tools > Telerik Fiddler Options > HTTPS > Check [Decrypt Https Traffic Option]
Fiddler Option – Decrypt HTTPS Traffic
Once prompted Accept certificate generated by Fiddler

How to filter traffic for specific Domain or URL (contains)

If you see lots of unwanted log entries after you enable Capturing then try following setting to Include / Clude certain log entries from the Capture making it easier to analyze.

Go to Filters Tab
Check Show only if URL contains. Type any words you like to check in URL. e.g. zappysys.com will include only those URL which has “zappysys.com” anywhere in the Full URL. You can add multiple included by adding space after words
If you like to exclude some URLs then check Hide if URL contains option and enter string like previous step

How to view Web Request and Response in Fiddler

Once your web requests appear on the left side panel. Simply double click on the request entry to view. On your right side, you will see two panels.

Top Panel – Request View
Bottom Panel – Response View

Here is an example of seeing API calls generated by aws command line requests/response in Fiddler.

Capture AWS Command line (CLI) request using Fiddler

How to Test API using Fiddler (Call REST API for without Postman)

Fiddler comes with another cool feature just like Postman so you can test your API call. Basically, there will be a time when you like to edit your request and test with different data (e.g. URL / Body or Headers). If that’s the case you can directly go to Composer Tab or Replay existing request right Right Click.

How to replay existing request / edit / send new request

To reply to the existing request

Test Web Requests in Fiddler Composer – Replay existing REST API requests or send new one (Edit Header, Body, URL)

How to view and format JSON / XML data in Fiddler

By default Fiddler will show you JSON / XML Tab if request body or response data in that format (see JSON / XML tabs on top and bottom panels). But what if you like to see in Raw Text but in Syntax Highlighted / formatted way?

Format Fiddler Request / Response (XML or JSON). View text with Syntax Highlighting

How to use fiddler Converters (e.g. Base64 / URL encode – decode)

There will be a time when you like to encode / decode strings appearing in web requests. Fiddler has another very handy feature call Send to Text Wizard. This option appears in most right click Menu in Raw / Syntax View / Headers view and other places.

Encode / Decode / Convert Text in Fiddler (e.g. Base64, URL Encode)

How to add Request Start Time, Overall Elapsed Time Columns in Fiddler

It’s really useful to see how much time each request is taking. For that, you can try the below steps in Fiddler Classic

Right-click on any Header Column
Select “Customize Columns”
Choose “Session Timers“
Choose Overall_Elaspsed and ClientConnectedTime from the dropdown

How to see request start time, overall elapsed time in Fiddler

How to edit and execute the processed requests in Fiddler

If you want to re-execute existing requests in Fiddler with different parameters then try the below steps

Select request from the left-hand side panel (or may be bottom side)
Press “E” and you will see a panel like below
Edit your request (i.e. URL, Header or Body)
Click on Run to Complete

Edit, Execute Processed Requests in Fiddler

How to enable AutoResponder – Fake Response (Rule based)

If you want to test some API calls for testing purposes, then you can use the AutoResponder feature of Fiddler. It allows you to match URL pattern and send response text from a local file. Here is how to enable Fake Response (Rule-based Auto Response)

Select URL from the log (Optional) – If you skip this step then in step#3 you will have to enter URL manually.
Go to AutoResponder Tab
Click Add Rule (if you didn’t select Log entry then Rule editor will have blank URL)
Enter / Change URL Rule in the Rule editor if needed. By default it uses EXACT match rule. Click here to learn more about more rules
Enter a file path where you have saved Fake Response you like to serve if URL rule.

Examples:

Exact URL match:

EXACT:HTTP://abc.com/api/v3/projects/123/milestones

Pattern URL match:

method:GET regex:(.*)/api/v3/projects/([\w\d-])+/milestones(.*)

Fiddler AutoResponder (Test Fake Response from local file – Rule match based on URL Pattern)

How to diff Fiddler requests

Sometimes you like to see difference between two requests. Fiddler comes with very handy feature. Just select two requests and click Diff Option in Right click menu. For diff to work make sure you install some diff utilities like KDiff3 or WinMerge.

Compare requests in Fiddler / Reissue same request with changes (Composer Tab)

How to show SSIS PowerPack requests in Fiddler

In most cases SSIS PowerPack requests will apperar in Fiddler without any extra configurations. However in some cases applications like SSIS PowerPack cannot detect it as System Default Proxy automatically. In that case try to enable Proxy settings in HTTP Connection or OAuth Connection. If you are not using connection manager then some Components like JSON Source offers its own Proxy tab so just check Enable Proxy.

By default Fiddler register itself as Default Web Proxy on port 8888 (i.e.

http://127.0.0.1:8888

)

Using Proxy Settings in SSIS PowerPack

View HTTP Request in Fiddler

To inspect HTTP Web Request using Fiddler perform following steps.

Click on the web request entry on left pane
Click on the Inspector Tab > Click Raw from top panel

View HTTP Response in Fiddler

To inspect HTTP Web Response using Fiddler perform following steps.

Click on the web request entry on left pane
Click on the Inspector Tab > Click Raw from bottom panel
You can also click on JSON or XML Tab if your want to see response coming in specific format

HTTTP Multipart POST – File Upload Example – Check Fiddler Request

View compressed (i.e. gzip, deflate) Response in Fiddler raw view

When response is compressed then by default you wont be able to see it in Raw tab. When response is compressed you may see header like below in response headers. You can also click on

Content-Encoding: gzip

To view compressed response in fiddler perform following steps.

Click on the web request entry on left pane
Click on the Inspector Tab > Click Transformer tab from bottom panel
Click on transformer tab and select No compression option and then click Raw tab

View uncompressed data in Fiddler (GZip, Deflate Encoding)

How to view Formatted JSON / XML

If you have JSON or XML response and you like to view formatted documents then you can go to Syntax View in the Response Panel and right-click and format

How to format Fiddler Request / Response (JSON/XML document)

Using Fiddler Text Wizard Tools (Encode / Decode – Hex, HTML, URL, Base64)

If you would like to perform some conversions like the one below, then you can use the TextWizard tool found in Fiddler. It’s very handy. Simply right click and click on Send to TextWizard option (found in most tabs / screens)

Base64 Encode / Decode
HTML Encode / Decode
URL Encode / Decode
Hex Encode / Decode
and more…

Launching Fiddler TextWizard from Right click menu

Fiddler Send To TextWizard Menu

Launching Fiddler TextWizard from Toolbar

Fiddler TextWizard UI

How to compare requests / re-execute

Sometimes you want to compare two requests and find the difference. Here is how you can compare requests and re-execute same request or edit it.

Compare requests in Fiddler / Reissue same request with changes (Composer Tab)

How to show web request of Curl in Fiddler

By default some application such as Curl doesn’t use system default Proxy. That means if you running Fiddler and trying to analyze requests made from Curl command line then it wont show up. Its easy to tell curl that which proxy server to use. Just use -x command line option with proxy server IP and Port (e.g. Default Fiddler IP and port … 127.0.0.1:8888 )

curl.exe -v -x 127.0.0.1:8888 https://google.com

How to show SoapUI requests in Fiddler

If you are using an application like SoapUI then also it may not use Fiddler as default web proxy. to show your SoapUI web requests in Fiddler try following options

Configure Proxy Settings in SoapUI

How to show aws command line requests in Fiddler

If you are using aws command line application and want to show requests in Fiddler then add –no-verify-ssl like below. This way you can capture RAW API requests and use it like this in SSIS.

aws lambda invoke --function-name HelloWorld c:\temp\outputfile.txt --no-verify-ssl --payload file://c://test/customer.json

How to show Windows Service requests in Fiddler (Local System Account)

By default if Fiddler launched as Admin it will capture most of requests by various apps. But if your like to capture Web requests which are issued by windows service such as ZappySys Data Gateway then you might have to do little extra work (Assuming Service is not setup Run As Your account). By default many service Run under “Local System” account

Here is how to capture those requests which are issued by service account.

Go to Folder where Service Exe is located (If you are unsure simply right click on Service > Properties and check path)
Create new file in the same folder where Service Exe is located. File name must be .exe.config
Enter following XML text in your config file and save
```
  
    
      
    
  
```
Restart Service and check Fiddler now see requests are captured

Capture Windows Service Web Requests in Fiddler (App Config method)

REST API integration using ODBC in BI Apps (e.g. Power BI, Excel, Informatica, Access, C#…)

If you want to consume API data in SQL Server (without ETL) or Live API consumption in Tools like Power BI, Excel, Tableau, SSRS, Talend, Informatica then use ODBC PowerPack from here. See below table for each use case.

ZappySys ODBC Drivers built using ODBC standard which is widely adopted by industry for a long time. Which mean the majority of BI Tools / Database Engines / ETL Tools already there will support native / 3rd party ODBC Drivers. Below is the small list of most popular tools / programming languages our Drivers support. If your tool / programming language doesn't appear in the below list, which means we have not documented use case but as long as your tool supports ODBC Standard, our drivers should work fine.

BI / Reporting Tools Integration	ETL Tools Integration	Programming Languages Integration
Microsoft Power BI Tableau SSRS (SQL Reporting Services) QlikView /Qlik Sense MicroStrategy Google Sheet Microsoft Excel Microsoft Access Oracle OBIEE Many more (not in this list).....	Informatica PowerCenter (Windows) Informatica Cloud SSIS (SQL Integration Services) SQL Server Talend Data Studio Pentaho Kettle Oracle OBIEE Many more (not in this list).....	Visual Studio C# C++ JAVA Python PHP PowerShell T-SQL (Using Linked Server)

Remove Fiddler Root Certificate (Uninstall / Untrust)

The Fiddler certificate is unique per machine / user, so you do not have to worry about someone else reusing it to intercept traffic, but still, for some reason, if you would like to uninstall the Fiddler root certificate (installed when you checked the Decrypt option), then perform the following steps.

Goto Tools > Options > HTTPS
Uncheck the Decrypt option first if it’s checked
Click on Actions > Remove interception Certificates

How to remove Fiddler Root Certificate

Coding-Free REST API integration using ODBC Drivers (For many Reporting / ETL Tools)

If you ever need to read /write data from REST API without writing a single line of code, check these ODBC Drivers / API Connectors.

ODBC PowerPack is a collection of high-performance drag and drop ODBC / API Drivers for various Modern / Legacy data sources. Connect data in Reporting / ETL Tools / Programming Languages.

Coding-Free REST API integration in SSIS (Microsoft ETL Tool)

If you use SSIS as your primary etl tool and you have API integration usecase then check this product.

The post Tutorial – How to use Fiddler to analyze HTTP Web Requests (Tips) appeared first on ZappySys Blog.