Configuring B2D in Sisense

This section describes how to configure the Sisense environment with the properties defined above. Configurations are applied globally (for all cubes) via CLI commands.

1. Create two yaml files, for Storage and Connections, to be used to update the Sisense environment configurations:
    Storage yaml holds the intermediate storage details

   ActionScript

   - storageType: AMAZON_S3
      accessKey: the access key if needed for authentication.
      secretKey: the secret key if needed for authentication.
      bucketName: the staging bucket name
      bucketRegion: the bucket region

    Connections yaml holds the CDWH details

   ActionScript

   connections:  
   - connectionString: host_string:port
      user: the user name
      password: the password for the user above
      role: which role related to the user (required only for Snowflake connections)
      database: database name
      permissions: what permissions granted to the role defined (e.g writer)
      buildDestination: destination (e.g redshift)
   

   
   See Yaml File Examples.
2. Once the files are ready, place the files or create them in this location: /opt/sisense/storage/ (a common method is to create them using vim commands or to use a freeware FTP tool)
3. SSH to the designated environment to configure the Storage and Connections in Sisense 
   1. Run CLI command “si storage create -path [/opt/sisense/storage/FILE_NAME.yaml]” command to configure the Storage in SIsense using the file we created for that purpose
      1. Example: “si storage create -path /opt/sisense/storage/[b2dstorage.yaml]”
   2. Run CLI command “si connections create -path [/opt/sisense/storage/FILE_NAME.yaml]” command to configure the Connections in SIsense using the file we created for that purpose
      1. Example: “si connections create -path /opt/sisense/storage/[b2dstorage.yaml]”
4. To enable B2D in Sisense, select the Admin tab.
5. From the navigation menu on the left side of the window, select Feature Management.
6. Toggle ON the Build Destination switch.
   

• B2D is done through cloud storage. So, for a given destination database, you must set up and configure the required storage and the destination database. 
• Snowflake and Redshift DB destinations are built through Amazon S3.

Yaml File Examples

connections:

  - connectionString: jdbc:snowflake://sisense.aws.com/?warehouse=EXWH&role=WRITER
    user: WRITER
    password: expassword
    role: WRITER
    database: EXDB
    permissions: writer
    buildDestination: snowflake

  - connectionString: jdbc:snowflake://sisense.aws.com/?warehouse=EXWH&role=VIEWER
    user: VIEWER
    password: expassword
    role: WRITER
    database: EXDB
    permissions: viewer
    buildDestination: snowflake
    
  - connectionString: sisense.redshift.com
    user: exadmin
    password: expassword
    database: exdb
    permissions: writer
    buildDestination: redshift

  - connectionString: sisense.redshift.com
    user: exadmin
    password: expassword
    database: exdb
    permissions: viewer
    buildDestination: redshift

  storage:
  - storageType: AMAZON_S3
    accessKey: exampleaccesskey
    secretKey: examplesecretkey
    iamRole: exampleIAMrole
    bucketName: examplebucketname
    bucketRegion: example-region