Versions Compared

Old Version 1

changes.mady.by.user SRP Support

Saved on

compared with

New Version 2

changes.mady.by.user Corby Nagel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Launch OpenInsight.

  2. Shell out to a DOS prompt

  3. 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).

  4. Assuming the application is called EXAMPLES and the user name is called EXAMPLES, type: 

    Code Block
     DWB /AP=RDKTUT /UN=RDKTUT

...

  2. 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.
  3. 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:
...
  1.  Code Block
     RDKInstall 'C:\UPGRADE'
...
  2. This should apply the upgrade to the production copy.  Quit the System Editor.
...
  • Copy new entities into an application (such as forms, tables, images, etc.)
  • Update any old entities with newer versions of themselvesthemselves 
 Info
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.