To install the Universal Driver 5, Revelation Software provides a temporary installation key for use during the installation process. This is different from previous versions of the Universal Driver where a static serial number was needed during installation. While the Universal Driver 5 installation key’s expiration date is sufficient for most projects (and can be extended upon request) you may find yourself in the situation of having an expired installation key after hours but need to migrate to a new server. While installing from the setup file is the preferred installation method you can manually copy the Universal Driver 5 to a new server following these steps.
On the Old Server
- Copy the c:\Revsoft\Universal Driver 5.1 directory to the new server at the same location.
- Open RegEdit.exe
- Export the registry branch to a file:
HKEY_LOCAL_MACHINE\SOFTWARE\RevSoft\Revelation Universal Driver\5.1
- Copy the exported registry file to the new server.
On the New Server
- Merge the exported registry file into the registry.
- Open RegEdit.exe and set the IP address of the new server in the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\RevSoft\Revelation Universal Driver\5.1\ServerName
- Open the file “C:\Revsoft\Universal Driver 5.1\Revparam” in notepad.
- Change the ServerName parameter to the IP or DNS name of the new server and save the file.
- Open a command prompt as administrator and change to the C:\Revsoft\Universal Driver 5.1 directory.
- Run the command to install the LinearHash service:
- Create a desktop shortcut named UD Manager to:
“C:\Revsoft\Universal Driver 5.1\UD_Manager\OINSIGHT.exe” /AP=SYSPROG /UN=SYSPROG
Tip: Be sure to set the Start in folder to “C:\Revsoft\Universal Driver 5.1\UD_Manager”
You may now launch the newly created UD Manager shortcut to verify the LinearHash service was installed and is functioning.
If the Univeral Driver manager is functioning and showing the correct server information you may begin copying your application to a new server. Be sure to change the revparam file in your application to ensure it points to the correct server. The ServerName parameter in your application’s revparam file should match the value in C:\Revsoft\Universal Driver 5.1\Revparam.
The standard multi-user deployment practice for OpenInsight involves executing OINSIGHT.exe across the network from a shared network folder. By default Windows distrusts network folder locations that haven’t been previously trusted and can’t be detected as part of the local intranet. This results in Windows displaying the Open File – Security Warning before launching the program.
In this article we’ll cover 3 methods to prevent the Open File – Security Warning by configuring Windows to trust the shared OpenInsight network location.
The rule of thumb when it comes to the Universal Driver’s LinearHash service and server performance is to have enough free physical RAM available on the server to fit all the commonly accessed OpenInsight database files (the LK and OV files managed by the LinearHash service) into memory. This article walks through the problems associated when requests for commonly accessed LinearHash files exceed the amount of available server memory.
This is a continuation of our series focusing on the performance difference of the Universal Driver 5 and 4.7. In what is likely to be the last article in the series, we resume testing the number of simultaneous clients and the rate in which they are able to read records from the Linear Hash service. Please note, however, that these tests were performed with UD 18.104.22.168. Since then, Revelation Software has released two more patches. The latest patch addresses some rather significant performance issues which were identified in the wild. Given that our tests are synthetic, we do not expect the following results to vary much. Therefore we opted not to retest our results in the latest release. Continue reading
The previous articles in this blog series focused on the performance differences between the UD 5 and 4.7 by running tests directly on the server where the Linear Hash service was installed. This essentially limited our tests to single client loops that didn’t have the latency introduced by the network.
In this article the tests will focus on running OpenInsight across the network in parallel from 5 servers running multiple copies of the test program.
In this blog series, the UD 5 Performance Part 1 article focused on benchmarks between the UD 4.7 and UD 5.0 using a simple read / modify / write loop running directly on the server. This article continues the same series of testing by including record locking in the test loop to compare the impact of locking between both Universal Drivers. Details about the test setup and testing environment are included in part 1, and since this is a continuation we will not review the details in this part.
Since writing part 1, Revelation Software also released an article on UD 5 and UD 4.7 Benchmarks. Their benchmarks compared the overall test time where as our series is more focused on throughput (records read/written per second). Two key differences between the Revelation tests and the testing methodology in our series is the Revelation Software benchmarks include locking and wrote new records into a new table. This series does not write any new records but instead modifies only existing records.
There is a lot of excitement around the release of the Universal Driver 5.0 and it’s new features. This article will be the first of several that analyzes the performance and operation of the new product against the current Universal Driver 4.7.
Manufacturer benchmarks are a black art with comparisons done to test the product under the best possible circumstances to highlight product superiority. The benchmark test in this article is independent of the manufacturer and designed not to introduce un-needed complexity or variables. Default options are selected whenever possible during setup and the test is run directly on the server.