When developing rules for an application, one of the following two common upgrade scenarios may occur, which requires manipulation of the database backup:
Application Upgrade Scenario #1:
BPM Events server is running an application that requires replacing. In other words, we want to install a new application that ignores everything from the previous version. The procedure to follow is:
1. Change your application rules.
2. Unload the application.
3. Load the application.
Application Upgrade Scenario #2:
BPM Events is currently running an application that we want to update. But we do not want to lose the current application objects, for example, the current infopads state. Let us assume the update is restricted to some rule change (that is, no change in infopad definition or in any other object) declared in a module. It is then possible to only replace the rules of the module without losing the current state of the running application.
Note: This dynamic upgrade procedure is NOT appropriate for changing infopad definitions. It should only be used for minor changes affecting the rules part of a module. These new rules should be consistent with the previous state of the application objects (infopads, stored events), as saved in the database between shutdown and restart.
