Is the Data Speed Accelerator a requirement for MSAS?

Good morning,
I’d like to know if the Data Speed Accelerator is an unavoidable requirement for the use of flexmonster with MSAS. We have a web application that connects to MSAS Olap cubes via the old Microsoft Office Web Components, which we are looking a sustitute for. Flexmonster seems to fullfill the functionalities of OWC and a lot more, but we do not want to install anything on the MSAS server.
So, can I connect to the MSAS cubes from the client web-app without the Data Speed Accelerator? If so, is there a big hit in performance when not using it?

5 answers

Ian Sadovy Flexmonster June 14, 2018

Hello Javier,
Thank you for the question.
Data Speed Accelerator is not mandatory to connect to MSAS. We also support connection via XMLA protocol.
But still, it needs some configuration on the MSAS server. Actually, any third-party web pivot will require XMLA, because it is the only way to establish HTTP connection with MSAS server.
As for the performance, you can compare it on our samples:

Also, here are some advantages of Accelerator:

  • it’s easy to install and configure
  • it has preconfigured CORS, GZIP and caching

Please let me know if you have further questions.

Javier G. June 14, 2018

Hello Ian,
Thank you for your answer, glad to hear it is not mandatory.
Actually, I just tested the connection with my data via XMLA and it seems to work fine. I’ll keep testing flexmonster to see if it fits my needs 🙂

Ian Sadovy Flexmonster June 14, 2018

Glad to hear that XMLA works for you.
Feel free to ask in case of any other questions.

Javier G. 7 days ago

Hello again,
Continuing with this topic…
In our current SSAS configuration we have some OLAP cubes accesible by everyone and also some cubes only accesible by certain roles that we have defined on the SSAS server. So, in our SSAS server’s IIS we have a Virtual Directory with Anonymus Authentication enabled (for the cubes that every user can see) and another Virtual Directory with Basic Authentication enabled. The front end users from our webpage will then have a local user created on the SSAS Server that is member of a group that has role assigned on the SSAS.
With our current XMLA configuration with Office Web Components, when a front-end user wants to see the data of those cubes, we use the ConnectionString tag on the XMLA to log him on the server, with something like this: 

<x:ConnectionString>Provider=MSOLAP.4;Persist Security Info=True;User ID=machine\some_username;Password=some_password;Initial Catalog=our_catalog;Data Source=http://our_url_to_role_specific_msmdpump.dll;Extended Properties=&quot;Client Cache Size=25;Large Level Threshold=10&quot;;Auto Synch Period=10000</x:ConnectionString>

with, as you can see, the user/password settings on the XML. 
Now, onto my question, is there a way to do this with flexmonster, and is it possible without the Data Accelerator?
I can connect to the msmdpump.dll that has the basic authentication enabled but the browser will always ask for the credentials, and I’d like to do it automatically, so our front-end users don’t have to type their credentials on their browser (actually they don’t even know they have those credentials, it’s just something we do internally to configure the data a specific user can access to).
I tried using the API connectTo() method with the dataSourceInfo parameter with no luck, also tried to use the getXMLADataSources(proxyUrl, ‘onDataSourceLoaded’,’username’,’password’) method with the username and password as parameters just to get the data sources but it keeps asking for the credentials as if the parameters are being ignored.
Any other options?
Thanks for your help.

Dmytro Zvazhii Flexmonster 6 days ago

Hello Javier,
Thank you for your question. One of the reasons we designed Data Accelerator is to avoid the necessity of running the authentication from the client side. The browser rejects headers which are necessary to perform the authentication process. It is a restriction of the javascript, therefore it is not possible to run cube’s authentication from the client side. However, some of our clients that decided using XMLA approach send the credentials using customData property. They use such approach to overcome the client side restrictions. Here is the example of how to send customData Also, this article about using roles with analysis services may be useful for you:!roles
Please let us know if you have any other question.

Please login or Register to Submit Answer