Deploying Sisense with custom-defined storage classes (rwxScName / rwoScName)
The Helm Provisioner allows you to deploy Sisense with RWO/RWX storage classes that were defined by you. It will be useful when deploying Sisense on the existing on-premise cluster or when you'd like to skip some specific steps during the Sisense installation (e.g. skipping FSX CSI helm chart installation because you use a different driver or need to manage it on your own)
Accessing cubes from another server
Question: How can I access all the cubes from another server, if I installed another Sisense system on another machine Solution: In order to get the cubes from another server you can follow these steps. If the computer you're working on is a computer that can VPN/connect to the internal network, if you work with your IT to obtain the IP address and connection info, you can add a connection to the ECM by doing the following: Startup the desktop ECM Go to Servers > Manage Servers 3. In the Sisense Server Console, click the green plus sign to add a server connection 4. Give the connection a descriptive name and enter the IP address of the server 5. If you have access to that server you should be able to Connect and see the connected server in your Sisense Server Console If you are not able to connect to the server, work with your IT team to see if they can open up a connection between your computer and the server, OR move on to the next optionDisabling TLS 1.0 And 1.1 In IIS
Question: Due to security considerations I want to be able to disable TLS1.0 with a view to disabling TLS1.1 Solution: Starting in Sisense 7.4, it became pretty straightforward to disable traffic on TLS 1.0 and 1.1. Setting this up involves two steps: Force traffic through TLS 1.2 on the Sisense site This can be done through the Configuration Manager on localhost:3030 (starting on Sisense 7.4) 2. Disable TLS 1.0 and 1.1 on the widows machine You can follow instructions such as these to disable TLS 1.0 and 1.1 On versions prior to Sisense 7.4 you can disable TLS 1.0 and 1.1 from the web server (step 2 above) but you will need to test extensively to ensure no loss of functionality. Starting in Sisense 7.4 is where R&D began in depth testing to remove any components that could rely on TLS 1.0 or 1.1. We have seen success with organization on Sisense 7.2 and 7.3 disabling TLS 1.0 and 1.1 on the server but again, there is not guarantee that there will not be a loss in functionality and testing by your team is needed.