iMIS Database Upgrade
If your organization is going to be upgrading it's iMIS database, the good news is that no code changes are needed in Informz to accommodate the upgrade. You can focus on all the iMIS technical details and Informz will continue to work from the same integration code base.
However, it's a good idea to contact Higher Logic prior to any major iMIS or network changes. This lets Informz do some extra monitoring to ensure that your iMIS-Informz connection remains up and running.
- Notify Higher Logic (preferably two to three weeks in advance) of the upcoming change.
- Check with your IT team to verify that the following information has remained the same:
- IP Address
- Database name
- Port #
- If you are using an IPSEC tunnel, have available the following information for Higher Logic.
- Hosting provider or self-hosted
- Name, email, and phone number of the client-side Network Engineer configuring the tunnel
- External IP address
- Internal IP address of the SQL Server that hosts the iMIS database
This may be an internal LAN IP address or an external IP address that you are NATing to the SQL Server.
- Phase 1 Authentication – IKE Proposal
- Phase 2 Encryption
Database Things To Do
Verify that the Informz user:
- Exists on the database (Databases > [database name] >Security > Users).
- Exists at the SQL Server level (Security > Logins).
- Is listed as DB_OWNER on [database name].
NOTE: Do not connect to a named instance (e.g., SQL03\[database]).
If the above-listed conditions are met, try to log into your SQL Server with the Informz username and password and be sure to select the SQL Server (not the local server) from the Server Name field. If the login fails, you should see a message detailing why.
iMIS Database on a New Server
Informz can help make your database server move a seamless transition. Follow these steps to make sure the bridge connection between Informz and your database stays up.
Preparing your iMIS Database for the Server Move
First, verify whether any of the following information on the old server will be different on the new server.
- IP Address
- Database name
- Port #
Second, review your login information. A common occurrence when an iMIS database is moved to a different server is the Informz login not moved over. This will cause the iMIS bridge connection to break. You will need to recreate the Informz login in the SQL server. You can work with your database admin to make sure this login is created.
Third, keep Higher Logic in the loop. If you know of a planned server move, let Higher Logic know in advance. Higher Logic can work with the software operations team to ensure everything is ready in Informz.
Your iMIS Database on the New Server
If your iMIS database has been moved to a new server, there is a good chance that you will get a connection error. When the database is moved, the Informz login, originally created at the system level, is NOT automatically moved to the new server. The system-level login is the Informz connection point, so if it is absent or incorrectly set up, the bridge connection will fail.
NOTE: You may find an Informz login at the database level as well. This should be available, but is different than the server-level login.
If your iMIS database has been moved to a new server, run the following steps in SQL Server Management Studio (SSMS) to make sure that your “informz” database user can connect.
- Verify that the Informz user is listed in both of the following security folders:
- One at the iMIS database level (Security > Users)
- One at the server level (Security > Logins)
If the Informz user is missing in either or both of these, create it there with public access to the new iMIS database. (There may be an error when it is recreated. This is generally resolved by refreshing.)
- Execute this ms stored procedure to ‘unorphan’ the Informz user:
EXEC sp_change_users_login 'Update_One', 'informz', 'informz'
NOTE: Do not copy the above command; copy-and-paste might add extraneous hidden characters.
You will know the problem has been fixed if you are able to log into SSMS as the Informz user.
IPsec Tunnel and iMIS IQA
While the steps above are helpful in making the server move seamless, keep in mind that there are a few more steps involved when your database also has an IPsec tunnel or iMIS IQA. Contact Higher Logic if you think you have either of these two features. IPsec tunnels may take a few days to configure, so plan accordingly in your project management plan.