Currently if you acces the web interface just by server name (e.g.
http://localhost) you will always be redirected to the default tenant or sub pages of the default tenant (e.g. download client).
This is fine for singe tenant systems but not for multi tenant systems.
Change this behavior for multi tenants systems to:
The user will be presented with a landing page where you can pick the tenant you want to go to (if you acces the web interface just by server name without adding the tenant).
Add an option so you can set "your own default tenant" for redirection (e.g. you want the application to always redirect to tenant "xy" instead of tenant "default").
Add a functionality so you can have different URLs go to different tenants directly, e.g.: User opens "http://tenant1.local" in the browser and is redirected to the login page for tenant1, user opens "http://tenant2.local" in the browser and is redirected to the login page for tenant2, and so on ...
In our demo ARIS environment I customize the login and logout pages to cover partly your requirement. Those login/logout pages offer links to all available tenants and some more links to offer support for the users.
Here are two examples of customizing the login page in C:\SoftwareAG\ARIS10.0\server\bin\work\work_copernicus_m\base\webapps\ROOT\WEB-INF\config\global\views\error401.xml (and error403.xml), and the logout page in C:\SoftwareAG\ARIS10.0\server\bin\work\work_copernicus_m\base\webapps\ROOT\WEB-INF\config\global\templates\logout.html.
Of course, such post-installation customizing won't survive the next ARIS update. But they help a lot with "lost users" who can't get where they want to go but are always thrown back to the /#default/home page.