Multiple Server connection on SisenseJS

Follow
Avatar
Rahat Hussain

Is there a good way to connect to and display Dashboards & widgets from multiple Sisense servers?  passing a different url to Sisense.connect() doesn't seem to work - you can only connect to one server or the other, but not both (i.e you can't display 2 dashboards that are each from different servers.

0

Comments

5 comments

Sort by Date Votes
  • Avatar
    Moti Granovsky (Edited )

    Hi Rahat,

    Unfortunately you are correct, it is not possible to connect to two Sisense servers from the same page using Sisense.js simultaneously.

    Could you perhaps share the use case that necessitates this, in case there is another possible approach?

    0
    Comment actions Permalink
  • Avatar
    Rahat Hussain

    Ah bummer!  So close and yet so far (authentication, REST API etc are all working for the multi-server solution).  The use case:  We have two Sisense servers for two separate products, the goal is to have an integrated screen where you can display dashboard/widgets from each of the servers.  So the user can create a screen with a dashboard from SisenseServer/Product A and perhaps a few dashboards/widgets from Server/Product B.

    0
    Comment actions Permalink
  • Avatar
    Moti Granovsky

    I'm not sure if this would be an appropriate solution for you, but you could have one (or both) server host all of the dashboards, while the Elasticubes (the data itself) remains on separated servers.

    Dashboards can query remote Elasticubes, as long as they are added as data sources in the Admin panel. With this approach, you could use just one Sisense.js connection, but keep your data segregated. Whether this approach is applicable depends on the reason for separating data to two servers.

    0
    Comment actions Permalink
  • Avatar
    Rahat Hussain

    Thanks for the idea - will see if that is a feasible solution. Will try a few more ideas as well and report back if there is any success so perhaps it will be useful to future developers.

    0
    Comment actions Permalink
  • Avatar
    Rahat Hussain

    Found an interesting workaround that is working for the most part - hosting the second SisenseJS in an iFrame. No ideal since it means carrying unnecessary bloat, but workable until perhaps SisenseJS allows for changing connection url. 

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post