After the extraction process is finished, you will have a set of files that comprise your upgrade! These files can be easily incorporated into your system using a stored procedure called RDKInstall. There are two ways to run RDKInstall.
It can be run on a System Editor Exec line, or
The application developer could have designed code to run it and attached this code to a menu choice or a button. This is recommended for production applications.
Assuming the deployed application does not have such a button, the System Editor will be used to perform the upgrade. Follow these steps to start the runtime version of the System Editor and perform the upgrade.
Launch OpenInsight.
Shell out to a DOS prompt
Change to the OpenInsight runtime application directory (make sure the directory you are in is the directory of the deployed application you want to upgrade).
Assuming the application is called EXAMPLES and the user name is called EXAMPLES, type:
DWB /AP=RDKTUT /UN=RDKTUT
You should now be in the System Editor in runtime mode. Many of the System Editor’s features are unavailable in the runtime. Upgrading an application, however, is available in the runtime version.
Copy the upgrade package you created in the previous topic to a directory (C:\UPGRADE, in this example). In the Exec line of the system editor, enter:
RDKInstall 'C:\UPGRADE'
This should apply the upgrade to the production copy. Quit the System Editor.
You can use this method to:
Copy new entities into an application (such as forms, tables, images, etc.)
Update any old entities with newer versions of themselves
When designing upgrades, it’s important to note that the end-user must have some way of having his deployed application find the upgrade package, whether it be in a floppy disk, a zip disk, unzipped into a hard disk directory, or any other location. It is important for the application developer to account for that. Naturally, it’s also important to program upgrade functionality into applications to ease the upgrade process for end users.
