In iMIS15 since logging into iMIS is server side you can not specify which database to login based on associated iMIS libraries. This makes it so it is easier to by mistake log into the wrong instance of a customer's setup.
When using RDS this is not done on a per user bases. This means that iMIS users accessing the Desktop to access instance A will change the default database being logged into for others.
Hmm, I started out agreeing, then thought about it and started to disagree, and now I'm just not sure.
iMIS 15.0.1 still gives you a "Set Host Location" option where you can change your datasource. If you choose a different datasource, then the server path should come from the database, right? So long as each database has the correct path to its own .NET app directory, it should work something like it always has, so long as you use separate libraries for each database.
Support for multiple environments is definitely a high priority, hosted or not. AiSP's often need to run multiple installs on one laptop. Clients want to have live and test environments accessible from the same workstation at the same time.
This points to the need for the "Multi-Net Utility" to become a standard part of iMIS. Perhaps it should be part of the Prepare Database button. It seems obvious to me that if there are multiple places that have to be in agreement to get the system to work right, then iMIS should have some built-in ability to adjust all these entries at the same time.
-- Bruce
This is now possible in iMIS 15.0.3.2005 +
This is going to have a big affect on hosted clients
For hosted clients this is going to be a big affect if you host on shared servers. Even using Citrix this will be an issue.