how to create elasticube using api

Comments

6 comments

  • Avatar
    Moti Granovsky

    Hi Helmi, 

    I've moved this post to the REST API forum as creating Datamodels (aka Elasticubes) is an operation available via the REST API.

    At the moment, REST API for creating Datamodels is only available on Sisense for Linux, starting from version L8.0.2. This capability should become available on the Windows version as well later this year.

    To get started with using the Datamodels API, here are some helpful resources:

    If you are using Sisense for Windows and still need to automate the creation of Elasticubes, there are some possible approaches to do so that aren't via REST. However, those can be somewhat more complex and if this is your use case I would suggest bringing this up with Sisense support as a ticket, to make sure you get the help you need.

    0
    Comment actions Permalink
  • Avatar
    Helmi Sfia (Edited )

    thank you mr Moti 

    i need to automate the creation of Elasticubes

    so im thinking about copy the schema of my existing elasticube without data 

    "C:\ProgramData\Sisense\PrismServer\ElastiCubeData\<your elasticube name>\ElastiCube.ecube"

    but i have to do that with script shell to make it run automatically 

    tahn i need to get my data from my DW using ip adress of user and put it in my elasticube

     

    do you have any idea about that 

    0
    Comment actions Permalink
  • Avatar
    Moti Granovsky

    So as I understand, you are indeed using Sisense for Windows.

    In this case, I think you got the right idea - take a template schema as an `.ecube` file, make a copy of it, then modify it to set the correct connection attributes for that specific copy and build it.

    To edit the schema, you will need to decode it to XML, make your changes and then encode it back to `.ecube` and run the build. All of these operations are done via the Sisense Shell (PSM.exe)

    0
    Comment actions Permalink
  • Avatar
    Paul Furman

    Thank you, Moti Granovsky.

    This is a tedious and ridiculous process for a mature product, in my opinion.  Needless to say, it also violates security protocols, as XML file will contain passwords in plain text format.

     

    1
    Comment actions Permalink
  • Avatar
    Moti Granovsky

    Hi Paul,

    The schema file does not start out as a plaintext XML - it has to be decoded first, edited as XML then encoded again - thus the plaintext stage is temporary and local, but of course it is the developer's responsibility to make sure the plaintext XML is deleted from the local filesystem after use.

    As mentioned above in my first comment to this thread, Sisense has a very strong suite of REST APIs for creating and modifying Datamodel schemas, but these endpoints are currently only available on the Sisense Linux version - which is intended for the same large scale use-cases where schema automation is often needed. However, these APIs will definitely be added to the Windows version as well further down the line, deprecating the legacy XML/CLI based approach.

    0
    Comment actions Permalink
  • Avatar
    Paul Furman

    Thank you, Moti Granovsky

     

    Yes, I've learned earlier today that these APIs are only available in Linux, which is promising, but not helpful at the moment :)

     

    I've also learned that there are some undocumented APIs that can unblock automation and deployment, but I haven't found them yet.  I guess, there is a reason they are undocumented :)

    1
    Comment actions Permalink

Please sign in to leave a comment.