Upgrading customer sites from OI 3.5 -] 3.6 (None Specified)
At 23 APR 1998 01:16:49PM Alex Cruise Eloquent wrote:
We'll be needing the international character support in OI 3.6 Real Soon Now, so would like to upgrade several of our customers from 3.5 to 3.6 as cleanly as possible. I have a few questions about this process:
1) Can RDK Upgrade/Module images produced on an OI 3.6 development system be applied to an OI 3.5 runtime system?
2a) Is there any way to COMBINE the RTI 3.5-]3.6 upgrade (which we need in order to upgrade multi-user OENGINE.EXE's) with an in-house upgrade procedure using InstallShield, which we need to install Splaver's OIPI/OIWAM at client sites? We'd like to make the 3.5-3.6 transition as smooth as possible, ideally a "one-button" operation.
2b) Is it possible to run the OI 3.5-]3.6 upgrade as part of a standard RDKInstall() upgrade/module update?
thanks,
acruise@istar.ca
[url=http://www.eloquent-systems.com/]Eloquent Systems Inc.
At 23 APR 1998 02:22PM Cameron Purdy wrote:
Alex,
I could spend a long time on these issues, but I will try to answer them in brief here.
1) Can RDK Upgrade/Module images produced on an OI 3.6 development system be applied to an OI 3.5 runtime system?
Yes. There are only a few differences between them, and it should not pose a problem.
2a) Is there any way to COMBINE the RTI 3.5-]3.6 upgrade (which we need in order to upgrade multi-user OENGINE.EXE's) with an in-house upgrade procedure using InstallShield, which we need to install Splaver's OIPI/OIWAM at client sites? We'd like to make the 3.5-3.6 transition as smooth as possible, ideally a "one-button" operation.
Yes. First, install the original product exactly as it was shipped to your customers; this is the "orig" image. Second, get your product exactly as you would like to ship it; this is the "new" image. Split the upgrade task into three parts:
1. Upgrade the engine
2. Upgrade the OS files (i.e. not .lk/.ov)
3. Upgrade the LH records
The engine part you will need some InstallShield help (from us or from a customer who has already done it). We plan to white-paperize this task.
The OS file part is easy … use WinDif or some other directory compare utility to compare the "orig" image vs. the "new" image. Copy those files that have changed into the InstallShield "image" directory (which it builds the .z out of).
The LH file part is easy … with the right tools. I'll paste some code in here. As is. Remember, this is just one way to do it … don't take this as gospel but rather as some ideas to work from. (They worked for me … Darren and I wrote these routines to build the OI 2.5 upgrade.)
This one gets run first. It sucks every record out of an entire volume. For example, 'REVBOOT'.
This is run after using the above to make an image of "orig" and "new". It creates the first-pass "SYSUPGRADE" information.
This creates the semi-finalized "SYSUPGRADE".
This is just a brute-force utility for table compares.
2b) Is it possible to run the OI 3.5-]3.6 upgrade as part of a standard RDKInstall() upgrade/module update?
No, but vice-versa.
Let me know if this gets you started on the right foot … there is a lot we can do to help you in this area, but we'll need to know which path you are taking. We have done everything from building combined/customized upgrades (you wouldn't like the price tag!) to having customers bring their apps here.
Best wishes,
Cameron Purdy
info@revelation.com