Route tenants to different servers
Scenario: I have a domain mydomain.com. I have several Sisense tenants. (So, users access Sisense at mydomain.com/tenant1, mydomain.com/tenant2, and mydomain.com/tenant3.) Challenge: I want tenant1 and tenant2 to be hosted on a Sisense server in CountryA, and tenant3 to be hosted on a Sisense server in CountryB. I found three viable solutions. Solution 1: Different domain: Change my url to be countrya.mydomain.com and countryb.mydomain.com. Solution 2: Proxy: In Sisense config, set a proxy. "https://mydomain.com/countrya/" on the CountryA system tenant and "https://mydomain.com/countryb/" on the CountryB system tenant. In mydomain.com's routing configuration, set rules routing /countrya/* to CountryA's server and /countryb/* to CountryB's server. Solution 3: Cookie: Three steps: 3.1. In mydomain.com's routing configuration, route mydomain.com/tenant1 to server A, route mydomain.com/tenant2 to server A, and route mydomain.com/tenant3 to server B. 3.2. Make a file MyPlugin.js with the line document.cookie = "MyCookieName=CountryA; path=/; max-age=86400". Deploy per the Sisense plugin instructions. 3.3. In mydomain.com's routing configuration, set rules for "If MyCookieName=CountryA, route to the server A. If MyCookieName=CountryB, route to server B." Explanation of Solution 3: If you do just step 3.1 without 3.2 and 3.3, the user will be able to open mydomain.com/tenant1 and log in. But many Sisense features cause the user's browser to make requests to the system tenant mydomain.com. Those fail because your routing configuration doesn't know which server to send mydomain.com to. To solve that, when the user opens mydomain.com/tenant1, we give them the cookie stating which server to use, and then we check that cookie when they later make requests against the system tenant.Proxy requires full URL if using multi-tenancy
Bugfix: In Sisense settings, you can set a "Web Proxy". E.g. if you want to use "mydomain.com/Path/To/Sisense" instead of "mydomain.com". In the proxy setting, you can enter either (a) "/Path/To/Sisense" or (b) "https://mydomain.com/Path/To/Sisense". When you use multi-tenancy, (a) doesn't work for tenants, only (b) works. Please make (a) work. (Specifically: When I open (a), it redirects to /app/account/mydomain.com/Path/To/Sisense/app/mydomain.com/Path/To/Sisense) (This came out of a tech support case 00830131.)Separate proxy per tenant
Feature request: You can set a proxy URL for a Sisense server. I'd like to set a separate proxy for the system tenant. That will help me with routing in an environment where there are multiple Sisense servers. Better still would be if I could set a separate proxy for each tenant. Then I can customise their URLs independently of the tenant name.Multi-server multi-tenant
Summary: Feature request: Make it so users on Sisense tenants never make requests to the system tenant. Scenario: I have a domain mydomain.com. I have several Sisense tenants. I want tenant1 and tenant2 to be hosted on a Sisense server in CountryA, and tenant3 to be hosted on a Sisense server in CountryB. I described solutions here: Route tenants to different servers | Sisense Community Feature request: I needed the solutions because many Sisense features cause the user's browser to make requests to the system tenant. One type of request was websockets, and there may be others. I would like Sisense to make these requests against the user tenant instead of the system tenant. The user tenant could query the system tenant internally, or the user tenant could answer the request itself. Purpose: A) To configure a multi-tenant multi-server environment, the only thing I need to do is route each mydomain.com/tenantname to the appropriate server. B) I can firewall the system tenant.Multitenantcy are very unusable
Hi, Related about multitenants, we are unable to: - Execute Custom Code in an EC inside a Tenant - Acces the file system from an EC in a tenant so refer with BloX to assets is a nightmare (image icons etc.). - GIT - Look&Feel And more There are other kind of limitations that makes the multi tenancy a nightmare. If you are going to continue providing this feature to customers, we expect to add functions you make it usable to end user. Best
Feature to export all datamodels from UI
We propose adding a valuable feature to our dashboard UI: the ability to export a comprehensive list of all data models, including both Elasticubes and live models. This enhancement is essential for efficiently monitoring model changes before and after Sisense upgrades. Presently, this process involves manual actions like taking screenshots or exporting a text file using 'si' commands, but it lacks the capability to export live models and essential metadata such as data model type, owner, last modification date, last publication date, activity, and size. By introducing export functionality in formats like CSV, users will be equipped to easily track and compare models, quickly identifying any discrepancies or replacements. This improvement will significantly streamline model management and ensure seamless transitions during upgrades.
Allow for Usage Analytics within self-contained multitenancy
At the moment, the usage analytics functionality is only available for the system tenant. You can monitor activity across all tenants from there. However, this means that you cannot share usage analytics data with designers within the self-contained tenant.
