Moving OpenInsight and Universal Driver To A New Server [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Moving OpenInsight and Universal Driver To A New Server ======

==== Created at 20 FEB 2024 10:00am ====

As older versions of MS Windows servers are retired or taken off of support, users of Revelation-based products may find that they need to migrate their applications to a newer platform. This document describes how to move both the OpenInsight and Universal Driver (Linear Hash server) products from an existing installed server to a new system.  While moving an OpenInsight installation to a new server is relatively straightforward, there are several steps that you will need to follow.

As always, please ensure you have a good backup of your OpenInsight system before proceeding.

==== Step 1: Ensure All Users Have Exited The System ====

This includes turning off any "automated" users, such as the Engine Server service.  To use the Windows Services dialog to stop the Engine Server service, go to the "search" bar, and type in "Services":

{{kb:kb_articles:kb1092_1.png}}

Look for the "OEngine Server" service - if it's there, and running, right-click on it and choose "Stop":

{{kb:kb_articles:kb1092_1a.png}}

==== Step 2: Turn Off The Current Universal Driver ====

Using the Windows Services application, look for the "Linear Hash Service" and stop it.  Go to the "search" bar, and type in "Services":

{{kb:kb_articles:kb1092_1.png}}

Right-click on the Linear Hash service, and choose "Stop":

{{kb:kb_articles:kb1092_2.png}}


==== Step 3: Copy the OpenInsight Folder(s) and Universal Driver Folder ====

These are both often found under C:\RevSoft.  Note that you may have other data folders installed elsewhere on the server; you will need to copy them as well, to the same relative location on the new server.  If you get errors that some files are "locked", you may need to reboot the old server before copying.

After the copy, right-click and choose "Properties" on the various folders, and ensure that any "Read-Only" permissions are removed (unless you have them set intentionally).

Using Regedit, "export" the registry subtrees for OpenInsight products. Go to the "search" bar and type in "Regedit":

{{kb:kb_articles:kb1092_3.png}}

These will be found in HKEY_LOCAL_MACHINE\Software\Revsoft\ for 64-bit products like UD5.x, OI 10.x, and OECGI4, or HKEY_LOCAL_MACHINE\WOW6432Node\Revsoft for 32-bit products like UD 4.x, OI 9.x, and OECGI3:

{{kb:kb_articles:kb1092_4.png}}

Export the settings for the Universal Driver and OECGI3/OECGI4:

{{kb:kb_articles:kb1092_5.png}}

==== Step 4: Install the Universal Driver On The New Server ====

After copying over the exported registry subtree(s) from the old server, you can right-click and choose to install them in the registry of the new server.

Open up a DOS cmd prompt as "Administrator" - using the Windows "search", type in "cmd":

{{kb:kb_articles:kb1092_8.png}}

When found, right-click on the command and choose "Run as Administrator":

{{kb:kb_articles:kb1092_9.png}}

Use the "cd" command to change to the Universal Driver folder on the new server, and type in:

     <ud exe name> install

The name of the exe will vary depending on the version of the Universal Driver - for UD 5.x, use "revlhsrvc.exe", for UD 4.7 use "lh47srvc.exe", for UD 4.5 use "lhsrvc45.exe", etc.:

{{kb:kb_articles:kb1092_6.png}}

After running the "install" command, you can check the services on the new server and you should find the Linear Hash service is installed and running.

If you are running the Universal Driver using TCP/IP, you may need to make sure the UD port is "opened" in any software or hardware firewall.  The port is usually 777 (for UD 4.x) or 1777 (for UD 5.x).

If you are using a Universal Driver Manager, be sure to copy the shortcut from the old server to the new server, updating the "target" and "start in" properties of the shortcut if needed.  Also be sure to update any REVPARAM in the UD folder, or the UD Manager subfolder, to point to the new server.

==== Step 5: Install the OpenInsight On The New Server ====

In the OpenInsight folder, locate and run the "clientsetup.exe".  Note that if you choose to install the .Net 2 components, you must ensure that the .Net 3.5 framework is installed:

{{kb:kb_articles:kb1092_7.png}}

([[kb:kb_articles:kb1090|please see this document for instructions on enabling/installing the .net 2.0 framework]]).

Locate and edit, using Notepad or another Windows editor, the REVPARAM file in your OpenInsight folder, and in any subfolders or data folders, so that the ServerName parameter is now pointing to the new server.

Verify that OpenInsight can start on the new server.

If you were previously running the OpenInsight Engine Server, you will need to install the Java Runtime Edition (JRE) (unless you are using OpenInsight 10.2+ with the included JRE), and then re-install the Engine Server service by double-clicking on the "installservice.bat" (OI10.x) or "installApp-nt.bat" (OI9.x) file found in the OESERVER folder.   NOTE: do NOT right-click/run as administrator the .bat file.

If you were previously using a Web Server (IIS or Apache) on the old server, you will need to recreate your "virtual directory(s)" on the new server, and enable CGI access to OECGI3.EXE or OECGI4.EXE.

==== Step 6: Set Up Users ====

If the users have a shortcut on their desktop, make sure it points to the new server location.

From each user's desktop, find and run the clientsetup.exe file in the server's OpenInsight folder.  Note that if you choose to install the .Net 2 components, you must ensure that the .Net 3.5 framework is installed:

{{kb:kb_articles:kb1092_7.png}}

([[kb:kb_articles:kb1090|please see this document for instructions on enabling/installing the .net 2.0 framework]]).


==== Step 7: Final Cleanup ====

If you have mapped drives on the old server you will want to make the same mappings point to the same folders on the new server.

If you have hard coded UNC paths inside your application then you will need to change these to point to the new server.