I'm currently testing iMIS 15 in a development environment and need to move the database, not the application, from one SQL Server to another. Is it possible to modify the database connection string on the iMIS 15 server? And if so, how? I already tried modifying the ODBC data sources, and grep'd through the entire iMIS 15 program tree looking for the server name, so it must be encoded somewhere... Is there a tool I can use to reset it?
Thanks,
Bret
If you wanted to make the changes manually without the tool, you would have to modify the config files on the application server:
C:\Program Files\ASI\iMIS15\Net\web.config
Note: This may be encrypted in here so in that case you would have to change it in the IIS virtual directory properies.
For IIS 5 and 6: Right click iMIS15 virtual directory under websites and go to properties. Click on ASP.NET tab->Edit Configuration...->Change the connection string in the General tab.
Then look at all the config files under "C:\Program Files\ASI\iMIS15\Net\bin", open them in notepad and change the server name in the connection string.
The ODBC connection is created by iMIS automatically the first time you login to iMIS. So changing it in here won't do anything if the server details are incorrect.
If you are creating a second instance of iMIS, then you should use the multi-instance tool and follow those instructions. It will make all the config changes for you, but also creates the windows services and runs some updates to the database.
Thanks for the comments. The multi-instance tool did manage to do what I needed, but not without removing the services and indexing catalog first. It looks like using the IIS Manager to modify the connection string in the ASP.NET configuration would have done it. I'll remember that for next time.
Changing SQL servers should be OK with this, but changin web servers would not be so simple.
The web.config file is encrypted using a key stored only on the web server where it is located. If the file is copied to another server, you will be unable to decrypt the connection string. This is actually the exact why the encryption was added.
You have two options:
* Read up on the instructions for manually decrypting and encrypting web.config. Decrypt before copying, re-encrypt on the new server.
* Read up on how to identify which key is used to encrypt the web.config and copy it to another server.
--
Bruce Wilson
Director, Technical Services
RSM McGladrey, Inc.
The newer versions of the multi-instance tool allow you to preserve the Services and Indexing catalog. There is an optional checkbox on the right side of the tool that allows for these to be preserved (as in cases with applying patches to multiple instances). Using this checkbox prevents the tool from trying to create the Services and Indexing catalog based on the database name.
-K
Kevin Blouin - enSYNC Corp.
Use the multi-instance tool
Use the multi-instance tool to reconfigure the existing site. Depending on which version of 15 you are on, there are different tools. With 15.1.2, the tool is provided in the application. Prior to that, you will need to get the tool from the main ASI website, under the support community >> downloads >> NET folder.
You will not need to go through all the steps for a relocation, just run the tool and fill out the form information, matching your existing application URL to the new SQL Server/db.
-K
Kevin Blouin - enSYNC Corp.