Amazon MWS Connector for Azure Data Factory (SSIS)Amazon MWS (Marketplace Web Service) Connector can be used to integrated web service API that helps Amazon sellers to programmatically exchange data on listings, orders, payments, reports, and more. In this article you will learn how to quickly and efficiently integrate Amazon MWS data in Azure Data Factory (SSIS) without coding. We will use high-performance Amazon MWS Connector to easily connect to Amazon MWS and then access the data inside Azure Data Factory (SSIS). Let's follow the steps below to see how we can accomplish that! Amazon's MWS (Marketplace Web Service) is being deprecated and replaced by the newer AWS Selling Partner API (SP-API). For a more robust and secure integration, we recommend using our AWS Selling Partner (SP-API) Connector. As Amazon is phasing out MWS functionality and eventually plans to fully deprecate it.
Amazon MWS Connector for Azure Data Factory (SSIS) is based on ZappySys API Connector Framework which is a part of SSIS PowerPack. It is a collection of high-performance SSIS connectors that enable you to integrate data with virtually any data provider supported by SSIS, including SQL Server. SSIS PowerPack supports various file formats, sources and destinations, including REST/SOAP API, SFTP/FTP, storage services, and plain files, to mention a few (if you are new to SSIS and SSIS PowerPack, find out more on how to use them). |
Connect to Amazon MWS in other apps
|
Create SSIS package
First of all, create an SSIS package, which will connect to Amazon MWS in SSIS. Once you do that, you are one step closer to deploying and running it in Azure-SSIS integration runtime in Azure Data Factory (ADF). Then simply proceed to the next step - creating and configuring Azure Blob Storage Container.
Prepare custom setup files for Azure-SSIS runtime
Now it's time to start preparing custom setup files for Azure-SSIS runtime. During Azure-SSIS runtime creation you can instruct ADF to perform a custom setup on a VM (Azure-SSIS node); i.e. to run the custom installer, copy files, execute PowerShell scripts, etc. In that case, your custom setup files are downloaded and run in the Azure-SSIS node (a VM) when you start the runtime. In this section we will prepare custom setup files so that you can run SSIS packages with SSIS PowerPack connectors inside in Azure-SSIS runtime.
Trial Users
Use the step below if you are a Trial User, when you did not purchase a license key. Proceed with these steps:
-
Download ~/Views/IntegrationHub/ContentBlocks/Links/SSIS-PowerPack/DownloadTrial.cshtmlSSIS PowerPack trial installer.
Make sure you don't rename the installer and keep it named as SSISPowerPackSetup_64bit_Trial.msi.
- Create a text file and name it main.cmd (make it all lowercase, very important).
-
Copy and paste this script into it and save it:
set DIR=%CUSTOM_SETUP_SCRIPT_LOG_DIR% echo Calling Step 1 : %TIME% >> "%DIR%\steps_log.txt" dir /s /b > "%DIR%\file_list.txt" echo Calling Step 2 : %TIME% >> "%DIR%\steps_log.txt" ::Install SSIS PowerPack msiexec /i "SSISPowerPackSetup_64bit_Trial.msi" ADDLOCAL=ALL /q /L*V "%DIR%\powerpack_trial_install_log.txt" echo Calling Step 3 : %TIME% >> "%DIR%\steps_log.txt" dir "C:\Program Files\Microsoft SQL Server\*Zappy*.*" /s /b >> "%DIR%\installed_files.txt" dir "C:\Program Files (x86)\Microsoft SQL Server\*Zappy*.*" /s /b >> "%DIR%\installed_files.txt" echo DONE : %TIME% >> "%DIR%\steps_log.txt" echo complete
This is the entry-point script that is executed when Azure-SSIS runtime is started. - At last! You are ready to upload these two files — main.cmd & SSISPowerPackSetup_64bit_Trial.msi — into your Azure Blob Storage container's folder, which we will do in the Upload custom setup files to Azure Blob Storage container step.
Paid Customers
Use the steps below if you are a Paid Customer, when you purchased a license. Proceed with these steps:
-
Download SSIS PowerPack paid installer.
Make sure you don't rename the installer and keep it named as SSISPowerPackSetup_64bit.msi.
- Have your SSIS PowerPack license key handy, we will need it in the below script.
- Create a text file and name it main.cmd (make it all lowercase, very important).
- Copy and paste the below script into it.
- Paste your license key by replacing parameter's
--register
argument with your real license key. -
Finally, save main.cmd:
set DIR=%CUSTOM_SETUP_SCRIPT_LOG_DIR% echo Calling Step 1 : %TIME% >> "%DIR%\steps_log.txt" dir /s /b > "%DIR%\file_list.txt" echo Calling Step 2 : %TIME% >> "%DIR%\steps_log.txt" ::Install SSIS PowerPack msiexec /i "SSISPowerPackSetup_64bit.msi" ADDLOCAL=ALL /q /L*V "%DIR%\powerpack_install_log.txt" echo Calling Step 3 : %TIME% >> "%DIR%\steps_log.txt" ::Activate PowerPack license (Optional) "C:\Program Files (x86)\ZappySys\SSIS PowerPack (64 bit)\LicenseManager.exe" -p SSISPowerPack --register "lgGAAO0-----REPLACE-WITH-YOUR-LICENSE-KEY-----czM=" --logfile "%DIR%\powerpack_register_log.txt" ::Show System Info echo Calling Step 4 : %TIME% >> "%DIR%\steps_log.txt" "C:\Program Files (x86)\ZappySys\SSIS PowerPack (64 bit)\LicenseManager.exe" -i -l "%DIR%\sysinfo_log.txt" echo Calling Step 5 : %TIME% >> "%DIR%\steps_log.txt" dir "C:\Program Files\Microsoft SQL Server\*Zappy*.*" /s /b >> "%DIR%\installed_files.txt" dir "C:\Program Files (x86)\Microsoft SQL Server\*Zappy*.*" /s /b >> "%DIR%\installed_files.txt" echo DONE : %TIME% >> "%DIR%\steps_log.txt" echo complete
This is the entry-point script that is executed when Azure-SSIS runtime is started. - At last! You are ready to upload these two files — main.cmd & SSISPowerPackSetup_64bit.msi — into your Azure Blob Storage container's folder, which we will do in the Upload custom setup files to Azure Blob Storage container step.
Upload custom setup files to Azure Blob Storage container
Within Azure Blob Storage container we will store custom setup files we prepared in the previous step so that Azure-SSIS can use them in custom setup process. Just perform these very simple, but very important steps:
-
Create Azure Blob Storage container, if you haven't done it already
Make sure you create and use Azure Blob Storage container instead of Azure Data Lake Storage folder. Azure Data Lake Storage won't allow creating an SAS URI for the container, which is a crucial step in the process.
-
Find Blob Containers node, right-click on it and hit Create Blob Container option:
-
Upload the two custom setup files — main.cmd & the MSI installer — into your Azure Blob Storage container's folder:
- It was easy, wasn't it? It's time we create an SAS URI in the next step.
Create SAS URI for Azure Blob Container
Once you have custom setup files prepared, it's time we generate an SAS URI. This SAS URI will be used by a new Azure-SSIS runtime to install SSIS PowerPack inside the runtime's node, a VM. Let's proceed together by performing the steps below:
- Install and launch Azure Storage Explorer.
-
Right-click on the Storage Accounts node and then hit Connect to Azure storage... menu item:
- Proceed by right-clicking on that container node and select Get Shared Access Signature... option.
-
Next, set the Expiry time field to a date far in the future.
If you restart Azure-SSIS runtime and your SAS URI is expired by that time, it will not start.
-
Select Read, Create, Write, and List permissions:
We also recommend to add Delete permission too to support future functionality.
-
Copy SAS URL to the clipboard and save it for the next step:
You can also generate and copy SAS URL from within Azure Portal itself:
Create Azure-SSIS integration runtime
Once you have the SAS URL we obtained in the previous step, we are ready to move on to create an Azure-SSIS runtime in Azure Data Factory:
- Firstly, perform the steps described in Create an Azure-SSIS integration runtime article in Azure Data Factory reference.
-
In Advanced settings page section, configure Custom setup container SAS URI you obtained in the previous step:
-
And you are done! That was quick! You can see your Azure-SSIS runtime up and running:
The custom setup script is executed only once — at the time an Azure-SSIS runtime is started.
It is also executed if you stop and start Azure-SSIS runtime again.
Deploy SSIS package in Visual Studio
We are ready to deploy the SSIS package to Azure-SSIS runtime. Once you do that, proceed to the next step for the grand finale!
Execute SSIS package in SQL Server Management Studio (SSMS)
After all hard work, we are ready to execute SSIS package in SQL Server Management Studio (SSMS):
- Connect to the SQL Server which is linked to your Azure-SSIS runtime and contains SSISDB database.
-
Navigate to Integration Services Catalog » Your Folder » Your Project » Your Package, right-click on it, and hit Execute...:
-
To view the status of the past execution, navigate to
Integration Services Catalog » Your Folder » Your Project » Your Package, right-click on it, and select Reports » Standard Reports » All Executions menu item:
Scenarios
Moving SSIS PowerPack license to another Azure-SSIS runtime
If you are a Paid Customer, there will be a time when you no longer use Azure-SSIS runtime or you need to use your license on a different ADF instance. To transfer a license from one Azure-SSIS runtime to another, perform these steps:
-
Copy & paste this script into main.cmd we used in the previous step:
set DIR=%CUSTOM_SETUP_SCRIPT_LOG_DIR% echo Calling Step 1 : %TIME% >> "%DIR%\steps_log.txt" dir /s /b > "%DIR%\file_list.txt" echo Calling Step 2 : %TIME% >> "%DIR%\steps_log.txt" ::Install SSIS PowerPack msiexec /i "SSISPowerPackSetup_64bit.msi" ADDLOCAL=ALL /q /L*V "%DIR%\powerpack_install_log.txt" echo Calling Step 3 : %TIME% >> "%DIR%\steps_log.txt" ::De-Activate same license "C:\Program Files (x86)\ZappySys\SSIS PowerPack (64 bit)\LicenseManager.exe" -p SSISPowerPack --unregister --logfile "%DIR%\powerpack_un_register_log.txt" ::Show System Info echo Calling Step 4 : %TIME% >> "%DIR%\steps_log.txt" "C:\Program Files (x86)\ZappySys\SSIS PowerPack (64 bit)\LicenseManager.exe" -i -l "%DIR%\sysinfo_log.txt" echo Calling Step 5 : %TIME% >> "%DIR%\steps_log.txt" dir "C:\Program Files\Microsoft SQL Server\*Zappy*.*" /s /b >> "%DIR%\installed_files.txt" dir "C:\Program Files (x86)\Microsoft SQL Server\*Zappy*.*" /s /b >> "%DIR%\installed_files.txt" echo DONE : %TIME% >> "%DIR%\steps_log.txt" echo complete
- Start Azure-SSIS runtime.
This will unregister your license on the original Azure-SSIS runtime.
- Stop Azure-SSIS runtime to deallocate resources in Azure.
- Now you are free to activate it on another Azure-SSIS runtime.
Actions supported by Amazon MWS Connector
Amazon MWS Connector supports following actions for REST API integration:
Get CSV Report By ID - Cached Copy (Previously Generated)
Description
Not available.
Parameters
You can provide the following parameters to this action:
-
ReportId
-
Version
Input Fields
You can provide the following fields to this action:
-
N/A
Output Fields
The following fields are returned after calling this action:
-
N/A
Visit documentation for more information.
Get FlatFile Report (Live)
Description
Returns data from FlatFile Reports (TSV - Tab Seperated Values) listed here http://docs.developer.amazonservices.com/en_US/reports/Reports_ReportType.html. Depending which Report you choose, it can take upto 30 minutes to generate report. To get data from previously generated report, you can use [Get CSV Report By ID - Cached Copy] endpoint to fetch data by GeneratedReportId.
Parameters
You can provide the following parameters to this action:
-
ReportType
-
StartDate
-
EndDate
-
ReportOptions
-
Version
-
MarketplaceIdList
Input Fields
You can provide the following fields to this action:
-
N/A
Output Fields
The following fields are returned after calling this action:
-
N/A
Visit documentation for more information.
Get Report Count
Description
Returns a count of the reports, created in the previous 90 days, with a status of _DONE_ and that are available for download.
Parameters
You can provide the following parameters to this action:
-
AmazonOrderId
-
ReportTypeList
-
Acknowledged
-
AvailableFromDate
-
AvailableToDate
-
Version
Input Fields
You can provide the following fields to this action:
-
N/A
Output Fields
The following fields are returned after calling this action:
-
N/A
Visit documentation for more information.
Get Report List (Successful Only)
Description
Returns a list of reports that were created in the previous 90 days.
Parameters
You can provide the following parameters to this action:
-
ReportTypeList
-
Acknowledged
-
AvailableFromDate
-
AvailableToDate
Input Fields
You can provide the following fields to this action:
-
N/A
Output Fields
The following fields are returned after calling this action:
-
ReportId
-
ReportType
-
Acknowledged
-
ReportRequestId
-
AvailableDate
Visit documentation for more information.
Get Report Requests
Description
Returns a list of report requests that you can use to get the ReportRequestId for a report.
Parameters
You can provide the following parameters to this action:
-
Version
-
ReportTypeList
-
MaxCount
-
ReportStatus
-
RequestedFromDate
-
RequestedToDate
-
ReportRequestId
Input Fields
You can provide the following fields to this action:
-
N/A
Output Fields
The following fields are returned after calling this action:
-
ReportRequestId
-
ReportType
-
Acknowledged
-
GeneratedReportId
-
StartDate
-
EndDate
-
ReportProcessingStatus
-
SubmittedDate
-
StartedProcessingDate
-
CompletedDate
Visit documentation for more information.
Get XML Report (Live)
Description
Returns data from XML Reports listed here http://docs.developer.amazonservices.com/en_US/reports/Reports_ReportType.html.
Parameters
You can provide the following parameters to this action:
-
ReportType
-
StartDate
-
EndDate
-
ReportOptions
-
Version
-
MarketplaceIdList
Input Fields
You can provide the following fields to this action:
-
N/A
Output Fields
The following fields are returned after calling this action:
-
N/A
Visit documentation for more information.
Get XML Report By ID - Cached Copy (Previously Generated)
Description
Not available.
Parameters
You can provide the following parameters to this action:
-
ReportId
-
Version
Input Fields
You can provide the following fields to this action:
-
N/A
Output Fields
The following fields are returned after calling this action:
-
N/A
Visit documentation for more information.
Orders: Get Single Order Information
Description
The GetOrder operation returns an order for each AmazonOrderId that you specify, up to a maximum of 50. The GetOrder operation includes order information for each order returned, including PurchaseDate, OrderStatus, FulfillmentChannel, and LastUpdateDate.
Parameters
You can provide the following parameters to this action:
-
AmazonOrderIdList
-
Version
Input Fields
You can provide the following fields to this action:
-
N/A
Output Fields
The following fields are returned after calling this action:
-
AmazonOrderId
-
PurchaseDate
-
LatestShipDate
-
OrderType
-
BuyerEmail
-
LastUpdateDate
-
IsReplacementOrder
-
NumberOfItemsShipped
-
ShipServiceLevel
-
OrderStatus
-
SalesChannel
-
IsBusinessOrder
-
NumberOfItemsUnshipped
-
PaymentMethodDetails_PaymentMethodDetail
-
IsGlobalExpressEnabled
-
IsSoldByAB
-
BuyerName
-
IsPremiumOrder
-
OrderTotal_Amount
-
OrderTotal_CurrencyCode
-
EarliestShipDate
-
MarketplaceId
-
FulfillmentChannel
-
PaymentMethod
-
ShippingAddress_City
-
ShippingAddress_PostalCode
-
ShippingAddress_isAddressSharingConfidential
-
ShippingAddress_StateOrRegion
-
ShippingAddress_CountryCode
-
ShippingAddress_Name
-
ShippingAddress_AddressLine1
-
IsPrime
-
SellerOrderId
-
ShipmentServiceLevelCategory
Visit documentation for more information.
Orders: Read Order Items
Description
The ListOrderItems operation returns order item information for an AmazonOrderId that you specify. The order item information includes Title, ASIN, SellerSKU, ItemPrice, ShippingPrice, as well as tax and promotion information.
Parameters
You can provide the following parameters to this action:
-
AmazonOrderId
-
Version
Input Fields
You can provide the following fields to this action:
-
N/A
Output Fields
The following fields are returned after calling this action:
-
TaxCollection_ResponsibleParty
-
TaxCollection_Model
-
QuantityOrdered
-
Title
-
PromotionDiscount_Amount
-
PromotionDiscount_CurrencyCode
-
IsGift
-
ASIN
-
SellerSKU
-
OrderItemId
-
IsTransparency
-
ProductInfo_NumberOfItems
-
QuantityShipped
-
ItemPrice_Amount
-
ItemPrice_CurrencyCode
-
ItemTax_Amount
-
ItemTax_CurrencyCode
-
PromotionDiscountTax_Amount
-
PromotionDiscountTax_CurrencyCode
Visit documentation for more information.
Orders: Read Orders
Description
The ListOrders operation returns a list of orders created or updated during a time frame that you specify. You define that time frame using the CreatedAfter parameter or the LastUpdatedAfter parameter. You must use one of these parameters, but not both. You can also apply a range of filtering criteria to narrow the list of orders that is returned. The ListOrders operation includes order information for each order returned, including AmazonOrderId, OrderStatus, FulfillmentChannel, and LastUpdateDate.
Parameters
You can provide the following parameters to this action:
-
MarketplaceIdList
-
CreatedAfter
-
CreatedBefore
-
LastUpdatedAfter
-
LastUpdatedBefore
-
OrderStatus
-
FulfillmentChannel
-
PaymentMethod
-
BuyerEmail
-
SellerOrderId
-
EasyShipShipmentStatus
-
Version
Input Fields
You can provide the following fields to this action:
-
N/A
Output Fields
The following fields are returned after calling this action:
-
AmazonOrderId
-
OrderTotal_Amount
-
OrderTotal_CurrencyCode
-
BuyerName
-
OrderStatus
-
OrderType
-
PurchaseDate
-
LatestShipDate
-
PaymentMethod
-
ShippingAddress_City
-
ShippingAddress_PostalCode
-
ShippingAddress_isAddressSharingConfidential
-
ShippingAddress_StateOrRegion
-
ShippingAddress_CountryCode
-
ShippingAddress_Name
-
ShippingAddress_AddressLine1
-
ShippingAddress_AddressLine2
-
ShippingAddress_County
-
LastUpdateDate
-
IsReplacementOrder
-
NumberOfItemsShipped
-
ShipServiceLevel
-
SalesChannel
-
IsBusinessOrder
-
NumberOfItemsUnshipped
-
PaymentMethodDetails_PaymentMethodDetail
-
IsGlobalExpressEnabled
-
IsSoldByAB
-
IsPremiumOrder
-
EarliestShipDate
-
MarketplaceId
-
FulfillmentChannel
-
IsPrime
-
SellerOrderId
-
ShipmentServiceLevelCategory
-
BuyerEmail
Visit documentation for more information.
Make Generic API Request
Description
This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL.
Parameters
You can provide the following parameters to this action:
-
Url
-
Body
-
IsMultiPart
-
Filter
-
Headers
Input Fields
You can provide the following fields to this action:
-
N/A
Output Fields
The following fields are returned after calling this action:
-
N/A
Visit documentation for more information.
Make Generic API Request (Bulk Write)
Description
This is a generic endpoint for bulk write purpose. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL.
Parameters
You can provide the following parameters to this action:
-
Url
-
IsMultiPart
-
Filter
-
Headers
Input Fields
You can provide the following fields to this action:
-
N/A
Output Fields
The following fields are returned after calling this action:
-
N/A
Visit documentation for more information.
Conclusion
In this article we showed you how to connect to Amazon MWS in Azure Data Factory (SSIS) and integrate data without any coding, saving you time and effort.
We encourage you to download Amazon MWS Connector for Azure Data Factory (SSIS) and see how easy it is to use it for yourself or your team.
If you have any questions, feel free to contact ZappySys support team. You can also open a live chat immediately by clicking on the chat icon below.
Download Amazon MWS Connector for Azure Data Factory (SSIS) Documentation