API to pull EC cube build schedule informaiton

Comments

8 comments

  • Avatar
    Moti Granovsky

    Hi Wojciech,

    I moved your post to the REST API forum as it relates to a feature request for our REST API.

    There is a way for you to extract the build schedule from existing Elasticubes today, via the .ecube file (the file created by the windows-based Elasticube Manager application). That file can be converted to XML using the PSM.exe Shell and in the resulting XML you will find an element called <Cloud.ScheduleSyncInfo> which contains information about the build schedule, if it was set for the Elasticube.

    As Sisense transitions to a web-based Elasticube Manager interface, a (much more convenient) REST API to allow not just the retrieval but also modification of build schedules will become available in one of the upcoming releases.

    0
    Comment actions Permalink
  • Avatar
    Wojciech Obiedzinski

    Hi Moti,

    THanks for the instructions. I will try PSM shell. Should be easy enough to iterate through all the ecube files to get schedule.

    Yes, control over EC build schedule with REST API is much needed. I hope we can see it soon with one of coming releases or new web interface which will show all schedules in one place.

     

    Thanks,

    Wojtek

    0
    Comment actions Permalink
  • Avatar
    Wojciech Obiedzinski

    Hi Moti,

    I checked today few ecube files as advised.

    from 3 files I checked:

    - 1 had schedule information incorrect - not matching current schedule settings

    - 1 had schedule information correct

    - 1 didn't have schedule information - schedule section had no schedule details

    Any ideas?

    Thanks,

    Wojtek

     

    0
    Comment actions Permalink
  • Avatar
    Moti Granovsky

    Hi Wojtek,

    I forgot to mention this - but there are two "stages" in which .ecube files can be. When you are designing your data model in the Elasticube Manager application, you can save the current model as an .ecube file anywhere on your PC, and then open it to continue working.

    However, once you build your Elasticube, the outcome of the build is a folder that contains both the Elasticube data and the model (.ecube file) that is actually running on Elasticube Server. Thus, when you set your schedule via the Elasticube Manager before building - the same schedule information will be copied over to the "operational" Elasticube, but once you change the schedule (via the Sisense Server Console, or by editing the active cube in ECM) that change is applied only on the .ecube file that is being actively run at the time, and is not reflected in any prior copies of the .ecube file you may have stored along the way.

    You can find the "operational" .ecube file in this path:

    C:\ProgramData\Sisense\PrismServer\ElastiCubeData\Sample Healthcare\ElastiCube.ecube

    Of course replacing "Sample Healthcare" with the name of your Elasticube.

    This will actually allow you to easily write a script that traverses each folder under "ElastiCubeData", opens the .ecube file within (as they are all identically named) and extracts the schedule information.

    If you're still seeing inconsistency between the schedule information in these files and what's displayed in the server console, I suggest opening a support ticket as that would deviate from intended behavior.

    Hope this helps!

    0
    Comment actions Permalink
  • Avatar
    Wojciech Obiedzinski

    Hi Moti,

    Thanks, I have found the other ecube files. And data there looks good.

    One more question about this:

    I was thinking of importing ecube files to another server for processing.

    Does PSM shell require any license or can I just install it on another server?

    THanks,

    Wojtek

     

     

    0
    Comment actions Permalink
  • Avatar
    Moti Granovsky

    Hi Wojtek,

    Glad I could be of assistance!

    Hopefully I understood your question correctly: The PSM.exe shell is only a shell - it does not do the Elasticube processing (build) itself, but rather it is a command-line interface for interacting with the Elasticube Management Service - that service is responsible for managing builds and queries. Therefor, simply copying the shell to another machine will not move the actual processing load to that machine; For that (a multi-node deployment) licensing changes are usually required, which you can discuss with your CSM.

    0
    Comment actions Permalink
  • Avatar
    Wojciech Obiedzinski

    Yes, just want to use PSM shell on diffrent machine to convert ecube files to xml.

    I will check with my CSM.

    You were great help. Thank you.

     

     

    0
    Comment actions Permalink
  • Avatar
    Roopa Raghavan

    Is there a way to do this without using PSM shell? We have our servers hosted in the cloud and don't have access to CLI. What other way can i get build schedules of all cubes in an environment?

     

     

    0
    Comment actions Permalink

Please sign in to leave a comment.