Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Use of openUTM revision levels in the UTM cluster application

You can always deploy openUTM revision levels during live operation without the need to terminate the UTM cluster application. Some of the node applications can continue to run while the revision level is being installed for the remaining node applications.

To do this, the node applications must be terminated one after another and then restarted using the new revision level.

Procedure on Unix and Linux systems

On Unix and Linux systems, UTM revision levels are always installed in a directory specific to the given revision level, i.e. the files belonging to two different revision levels are stored separately and are therefore unable to overwrite each other.

For this reason you must always adjust the values of the $UTMPATH environment variables before you start an application with a new revision level. This also applies to other environment variables that are dependent on $UTMPATH, such as $PATH or $LD_LIBRARY_PATH.

Proceed as follows:

  1. Install the new revision level.

  2. Terminate the node application.

  3. Adjust the $UTMPATH environment variable to point to the new installation, i.e. adapt the start script as necessary.

  4. Create the utmwork application program again if this is necessary for using the revision level.

  5. Restart the node application.

  6. Repeat steps 1 through 5 for all other node applications of the UTM cluster application.

  7. Uninstall the old revision level if it is no longer required.

Procedure on Windows systems

On Windows systems, you can install a revision level under the same path as a previous revision level. In this event, the files of the existing version are overwritten. If this is done, installation is only possible if the UTM application has been terminated, because some of the files will otherwise be locked by the system and can therefore not be overwritten.

Note also that this old installation cannot additionally continue to be used by other UTM applications, e.g. by additional test applications.

If you install UTM revision levels in a directory specific to the given revision level, the files belonging to two different revision levels are stored separately and are therefore unable to overwrite each other.

In this event you must adjust the values of the %UTMPATH% environment variables before you start an application with a new revision level. This also applies to other environment variables that are dependent on %UTMPATH%, such as %PATH%.

Proceed as follows:

  1. Terminate the node application running the old revision level.

  2. Install the new revision level.

  3. Reboot the computer if necessary.
    This step is only necessary if the installation path has been changed, because the installation routine adjusts the %UTMPATH% environment variable in the system environment.

  4. Create the utmwork.exe application program again if this is necessary for using the revision level.

  5. Restart the node application.

  6. Repeat steps 1 through 5 for all other node applications of the UTM cluster application.

  7. Uninstall the old revision level if it is no longer required.

Notes on running the application as a service:

Proceed as follows if you have changed the installation path:

  1. Uninstall the old version of the service before starting the system.

  2. Reboot the system.

  3. Install the new version of the service in the system.