Will WKC running on-premise leverage StoredIQ for data connectors or does it leverage connectors in IGC?
WKC running on-premises support the same connectors as those available in WKC as a public Saas in IBM Cloud.
You can find the full list of supported connectors for WKC on-prem here.
Related
I need to connect to IBM WebSphere MQ using BizTalk 2016.
Can this be done using out of the box MQSeries Adapter? Do we need anything else to get this working (For example IBM Websphere MQ client) or only out of the box MQSeries Adapter is enough?
I have read some document that we have to install the Adapter for WebSphere MQ which ships with HIS. Why do we need this?
If this can be achieved with both out of the box MQSeries Adapter and Adapter for WebSphere MQ which ships with HIS then what's the advantage or disadvantage of one with others.
IBM MQSeries product has been discontinued by IBM. MQSeries adapter in BizTalk is meant for MQSeries specifically. If you are looking to connect to IBM MQ recent versions, you need to install HIS. This gives you MQSC adapter and support for latest MQ version. With latest HIS, you have option to use IBM MQ client or Microsoft Client (built into HIS) to connect to IBM MQ.
IBM MQ, WebSphere MQ, and MQSeries product READMEs
Looking for documentation on our overall networking for WKC on Cloud in order to feel confident in its viability & security. Want to know all connectivity and networking options for WKC.
The recommended way is to use the IBM Cloud Secure Gateway service. WKC has direct support for it.
Here are the docs
for creating a connection.
Here are the docs
for configuring a secure gateway service.
Here are the docs
for all connections available out of the box in WKC.
We have existing Web application which has following layers
Web Layer (Asp.Net MVC ) Sql Server 2012 SAP ETL services: ETL
jobs pulling the data from different datasource to sql server
We have QA,STAGE,Production environment for the application.
We are planning to migrate the application to AZURE PAAS.For Web layer there is no issue's in migrating to PAAS.
For DB Layer we have used microsoft migration steps using visual studio there is no issues at data base design level.
the only concern moving DB to PAAS is SAP ETL service and application jobs which is dumping millions of data to database. Not sure about how many DTU's it will consume.
Just need help to decide for the above scenario is it good to move DB to PAAS or have Sql server VM ?
Thanks
I think it will be best for you to make some tests and base your decision on the results. For example, create an Azure Sql Server (Standard S0) and see how that performs. A great benefit of the PaaS offering, as you probably know, is that many aspects are handled for you automatically - upgrades, you can easily switch to another performance level, DB backups and restored, etc.
There is a very good article which can give you some additional pointers on how you can evaluate the pros/cons in your situation - Choose a cloud SQL Server option: Azure SQL (PaaS) Database or SQL Server on Azure VMs (IaaS)
I would personally choose the PaaS option. I have used Azure Sql Server for a long time and I never want to go back to configuring and supporting my own SQL server.
I am beginer in learning IBM DataPower so please let me know why it is used and
where it is used and what is the purpose that we use it.
Thank you.
IBM Datapower is called an appliance because it is purpose built with an OS of its own. The datapower appliance is usually located in the DMZ layer where an organization communicates with the other 3rd party vendor. Datapower has the ability to transform messages as well and the inbuilt security feature makes it a stronghold to secure the DMZ layer. It can connect using many protocols such as MQ, HTTP, HTTPS, JMS, SFTP, FTP, IMS , AS2, AS3 etc as well. It is also used to host APIs and SOAP web services. In short it is used for integrating with application outside of the organization layer.
I hear HTTP endpoints are being deprecated in SQL Server. What takes its place in future?
Deprecated in favor of Windows Communication Foundation. So basically you would write and host WCF services in .NET which will directly talk to the SQL database and then consume those services from client applications.