I have to send & receive messages between R and Azure Service Bus. This is possible with Python, Java, .Net but there is no help for R script. As I'm limited to use only R to achieve this, is there any resource/documentation available to refer.
According to this documentation, Currently, R programming doesn't support the Azure Service bus service. As of now Data Science Virtual Machine, ML Services on HDInsight, Azure Databricks, Azure Machine Learning, Azure Batch and Azure SQL Managed Instance are the only Azure services that are compatible with R programming.
Related
I'm looking for option to connect to and query the "Model"/Database of Azure Analysis Services(AAS)/Power BI. I've found multiple options for connecting AAS to .Net Core, but nothing for Power BI. Can I use any of the following connection types to connect to Power BI? And if so which flavor? Power BI Pro, Power BI Premium, Power BI Embedded?
I can connect to Azure Analysis Services using the following:
ADOMD <- This is my preferred connection method.
AMO
MSOLAP
REST API with Bearer token
I'm not looking to embed my report in a .Net Core application. I'm looking to actually query different models so everyone is reporting off the same data.
I don't want to shell out for AAS if I can do this with Power BI Pro!
As a short answer, I would say you can most likely do what you are asking with data sets hosted within a Power BI Premium instance or by users with a Premium per user (PPU) license.
My reasoning is simple. Access to the XMLA endpoint is only available for datasets hosted within Power BI Premium. Microsoft describes that in a bit more detail here within the Power BI documentation. Power BI Embedded (in a round about way) also ends up requiring Power BI Premium, so I believe this would be the same case for Power BI Embedded.
As a reminder on why the XMLA endpoint matters, Power BI Premium encapsulates an AAS instance (with some limitations). Per Microsoft (from here):
XMLA is the same communication protocol used by the Microsoft Analysis Services engine, which under the hood, runs Power BI's semantic modeling, governance, lifecycle, and data management.
So XMLA endpoint is required in order to allow connectivity to the AAS instance behind Power BI.
To answer your question regarding the different connection methods:
ADOMD/AMO
Microsoft provides a client library for .NET Framework and .NET Core for both ADOMD and AMO which should be able to connect to the XMLA endpoint of Power BI. You can browse those and the information available from Microsoft on those here. There are several open-source tools out there (recommended by Microsoft) that make use of these libraries. So if you are looking for examples, look in to Tabular Editor 2 or DAX Studio.
MSOLAP
Per Microsoft (in same link about client libraries):
Analysis Services OLE DB Provider (MSOLAP) is the native client library for Analysis Services database connections. It's used indirectly by both ADOMD.NET and AMO, delegating connection requests to the data provider. You can also call the OLE DB Provider directly from application code.
So unless you have some very specific needs regarding MSOLAP, I would probably rely on the Microsoft's AMO/ADOMD client libraries.
REST API
Assuming we are talking about the actual Power BI REST API (like this link) then, it depends. There are certain functionalities that the API exposes that might have been your use case for wanting to use a direct connection to the XMLA endpoint. For example, it does allow you to execute DAX queries or initiate dataset refreshes (all with its limitations). So I would advise you to review the API's documentation. It seems to be a good tool so far, and my guess is that it will only expand.
I did some researches and video to figure out how to connect EEG devices which is Emotiv Insight in real-time to Microsoft Azure Machine Learning Studio.
I thought any ways to do it, perhaps I need to connect to other services before connecting to Azure studio.
My aim is making an app taken brainwave and use Azure studio to analyze it. Finally, data is saved to firebase and response to my app.
However, I am stucking to find a way to connect my EEG data to Azure. It is appreciated for anyone can help me.
Emotive use a service, running on the cortex process. You need a websocket to talk with it. Additionaly all communication to and from the service is using JSon objects. Then you need to transport that into Azure
Apologies if this is a broad question...just wanted to if any has an idea with regards the comparison of SQL Service Broker Vs Windows Workflow Foundation for Workflow development.
R,
These are two different technologies to solve different problems. One deals with messaging between multiple applications, and the other deals with modeling of business processes.
SQL Service Broker is a messaging paradigm that is provided in SQL Server between two or more applications. It provides the ability to have multiple applications communicate with each other by placing messages on queues, and SQL Server would take care of delivering messages to other applications asynchronously.
Windows Workflow Foundation provides the ability to define business processes in either a flow-chart or state-machine fashion.
We are using mainframe application and from mainframe we write lots of messages to MQ to send to downstream. We are planning to migrate from MQ to Solace on mainframe. Is it possible? Solace supports mainframe applications?
How can we put messages to solace from mainframe batch and online(IMS transactions)?
Thanks,
Praveen.
Solace does not support mainframe applications directly but Solace can be easily integrated with IBM DataPower appliances which can interface with mainframe applications. The DataPower appliance can handle the transformation requirement of the service and the Solace appliance can handle the messaging portion to provide quick and efficient message delivery downstream.
The 'Solace Integration with IBM Datapower' integration guide, available on the Solace Developer Portal, has more information on this:
http://dev.solacesystems.com/integration-guides/ibm-datapower/
You may also be able to use Solace's REST interface, depending on your Mainframe application. Solace's REST interface allows communication using standard POST HTTP requests.
There are also guides for Solace's REST interface available on the Solace Developer Portal:
http://dev.solacesystems.com/docs/open-apis-protocols-docs/
Old thread, but Mainframe is a long lasting tech.
Solace now provide an open-source bridge for IBM MQ Bridge, so MainFrame<->IBM MQ<->Solace is possible.
Datapower integration using JMS to connect to Solace is still possible.
Solace REST Messaging API is still possible.
And finally OpenLegacy can help here :
https://www.openlegacy.com/
Is it possible to scale out SignalR using Windows Server Service Bus?
I found sample of doing it with Redis, and I know there are libraries in GitHub for SQL Server (although I couldn't find a working sample for that), but I would like to implement it using the new on-premises Service Bus.
Any ideas / references?
Thanks!
In theory yes. The current stable versions support the Azure Service Bus, the latest source includes a rework of the scaleout providers such that even if it doesn't work out of the box (as the two service bus solutions are designed to have API parity) it should be straightforward to implement.
The service bus scaleout is enabled using its DependencyResolverExtensions class.