Session Management and Creation- Real-time Reporting Round II

(8 posts) (2 voices)
  1. nsepetys, Member

    Hello myDBR Support,

    How are things going? After going through a short period of tackling other priorities we have been able to return to implementing the task we set out to do earlier- real-time reporting/charting. As you guys have provided a lot of assistance (see our conversation here for reference) we have been able to successfully implement this and to create an environment for monitoring the reporting activity and experience of the users from a reporting dashboard. A big thank you for helping us achieve this!

    The next phase is to release this real-time functionality to other reports on the server (our network admin team is really excited about this). We have, however, run into some limitations. The primary limitation seems to be due to the inability to make and receive multiple requests simultaneously in the same session. The dashboard (mentioned above) provides a view that appears to be making and receiving multiple requests and give the impression that there is true multi-tasking going on with refreshing each of the 3 embedded subreports, but in truth it's just a careful balance of the ajax call timing and continuous checks of the queue for those calls.

    What I am hoping to potentially get your help on is managing sessions for the end-user. I can easily create new sessions (using a chrome plugin) to navigate and continue using myDBR without the one dashboard holding up anything I'm trying to do in myDBR- the end users mostly will not be looking to do this. Is there a way to create and potentially manage sessions within the myDBR framework?

    Preferably I'd like any real-time report to be in its own session. The most I'd expect is 3 sessions per active user. Thanks for taking the time to read this and thanks in advance for any ideas you guys may have.

    - Noah

  2. myDBR Team, Key Master

    what is the setting you have in the "Use embedded charts" in Environmental variables? Can you try to set it on and see if it makes any difference?

    myDBR Team

  3. nsepetys, Member

    While the reporting dashboard doesn't use embedded charts (just tables) I have gone ahead an enabled that option in the environment settings. What is going on behind the scenes when I check that? Is there something that should allow the framework to handle the multi-tasking roadblock I'm coming across?

  4. myDBR Team, Key Master

    when the setting is disabled, the possible chart images in the report are using normal IMG tags with reference to the image where the SRC of the image is a 'https://xxx' URL. As the image needs to be stored somewhere (either to temp disk or to a session), myDBR uses session for this. As the reporst are fully dynamic, myDBR will have to wait until the report is executed until it can release the session.

    If the setting is enabled, myDBR uses data URIs (stores the image to the IMG SRC tag, "data:image/svg+xml") and therefore does not need to write to the session when the report is executed. This allows for myDBR to close the session much earlier thus allowing other reports to use the session.

    This should help you with the concurrent requests, let us know if it did / did not.
    myDBR Team

  5. nsepetys, Member

    It seems it is working somehow even though no charts are used. So that is a notable improvement!

    The most active embedded report checks running processes and returns just one table. When I check the option to use embedded charts I now can see processes, that are running and associated with the other embedded reports (in the same reporting dashboard) even though they both do not have any charts either. So I'm baffled as to how the sessions are managing to close much earlier when I don't see any image storage being necessary for any of the embedded reports. If you have any explanation I'd like to know. Regardless, thanks for your assistance.

  6. myDBR Team, Key Master

    As myDBR reports are fully dynamic, myDBR has to process the whole report before it can be sure that it can close the session (a report could contain a chart which needs the session if so decided in the settings).

    If you use the embedded charts setting (regardless of if you actually use charts), myDBR knows for certain that the session can be closed earlier. Hence the improvement.

    For simplicity's sake, the recommended setting for the embedded chart-option is that it is on.
    myDBR Team

  7. nsepetys, Member

    Got it.

    Is there any reason it should be disabled? Are there certain features that would be at a disadvantage with the embedded charts option enabled?

  8. myDBR Team, Key Master

    No disadvantages (some older mobile browsers might be marginally slower with large number of charts). Just keep it on.

    myDBR Team


You must log in to post.