Automating ElastiCube Deployment
The following instructions describe a common scenario for deploying ElastiCubes in a new environment where .ecube files have been imported into a production environment and the data source connections need to be updated.
Editing .ecube Files
Using the Sisense Shell, or Sisense PSM, it is easy to edit the database connection attributes. This set of APIs allows you to edit Elasticube parameters via a command line interface. The most commonly used command in a dev-to-prod scenario redirects .ecube build queries to a production database. Below is an example where “myecube.ecube” is redirected from a development database called “tracking” to a production database called “trackingX”.
psm ecube edit connection database ecube="c:\users\myuser\documents\mycube.ecube" server="10.0.0.1" database="tracking" newserver="localhost" newdatabase="trackingX" newusername="mynewuser" newpassword="newpassword"
The server and database parameters contain the details of the previous database and the newserver and newdatabase parameters should contain the location and name of your updated data source on the production server.
Building ElastiCubes with the PSM
The build can also be initiated on the production server through the Sisense interface or through the PSM. The following example code builds the Elasticube on the production server with the PSM:
- Full Build, Local Server: psm ecube build name="<elasticube name>" mode=restart serverAddress=localhost
- Accumulative Build, Remote Server: psm ecube build name="<elasticube name>" mode=full serverAddress=192.168.1.134