Update Manager service

With the Update Manager Service you can update:

• The OSGi runtime
• The JVM running the OSGi framework
• The underlying operating system

Registering bundle

This service is registered by the System bundle.

Update Manager properties

Details on the Update Manager system properties are provided in the Setup guide.

Preliminaries

Before Updating your Framework take into account:

• OSGi / and JVM updates require the flowing file structure to work:
  • <sdk_dir>/osgi
  • <sdk_dir>/update_storage
  • <sdk_dir>/new_update_image
  • <sdk_dir>/mbsa
• The <sdk_dir> should be writable and have enough space to hold old OSGi image + storage + new OSGi image + new storage.
• If the storage is moved anywhere outside <sdk_dir>/osgi, it cant automatically recover in case of rollback.
• Do not put the com.prosyst.mbs.util.validator.jar in boot.ini .
• The expected flow of the Update Procedure is:
  • Use backup manager to export client bundle's data.
  • Force the OSGi update. The new image will start with clean storage.
  • In validation the Backup Manager will restore the previous configurations. The FW will be restarted one more time in normal mode.

The Update Manager Service is activated if the system property mbs.updatemanager is set to true and the OSGi runtime is started from the mBSA. The service is registered under the com.prosyst.mbs.framework.updatemanager.UpdateManager interface and can be configured through the mbs.um.storage and mbs.um.osUpdate system properties.

For more information on mBSA Watchdog configuration go to "Watchdog Config" section of the mBSA setup guide.

Initiating an image update

Update images are taken from a specific directory. After you prepare the image, place it in the specified location on the same level as the "jvm", "mbsa" and "osgi" folders - e.g. [osgi_update_location] in the base directory ([install path]) as shown in the following Figure.

Figure 1. Tree for the mBSA-framework with separated mbsa/osgi directories.

In order to start an update, call the updateImage method of the Update Manager service. The method requires two arguments:

• A map containing the update parameters - For update of the framework and the JVM, the map must contain the location of the new image to be extracted. If the location is not specified, the Update Manager looks for an image into a default one - e.g. [install path]/default directory.
• The image type for update.

The call of the updateImage method results only in framework restart.

The following basic steps are performed for a successful OSGI image update:

1. When an OSGi update is initiated from the mBSA, the Update Manager checks if image location (e.g. osgi_new) is provided and switches to an update mode.

   If an error occurs – the original image is kept.

2. After the OSGi runtime is replaced, it is started by the mBSA in validation mode. The Update Manager waits while the self validation of the runtime is completed. If no errors occur, the new OSGi runtime image is committed.

   If an error occurs from the new image – the original one is restored.

3. The mBSA restarts the new runtime again, but in non-validation mode.

The update of the JVM image is basically performed in the same manner as the OSGi image update. Updating the JVM of a target device does not mean automatically update of the OSGi. You can either update the OSGi or the JVM images, but not both at the same time.