Patching with the patch installer

You can use the patch installer either in graphical mode, console mode or automated. The latter is reasonable for automated patching multiple systems.

Make sure that enough disk space is available

If the installer returns the message There is not enough space to perform this installation. Please free some disk space and re-run this installer…​, the environment variable IATEMPDIR can be alternatively set to a disk partition that has enough space. Execute the following commands in the UNIX command line prompt and restart the installer.

  • For Bourne shell (sh), ksh, bash and zsh:

    $ IATEMPDIR=/<free‑disk‑space‑directory>
$ export IATEMPDIR

  • For C shell (csh) and tcsh:

    $ setenv IATEMPDIR=/<free‑disk‑space‑directory>

  • For Windows

    C:\>set IATEMPDIR "c:\<free-disk-space-directory>"

Downloading the executable patch installer

Proceed as follows

  1. Download the patch installer for INUBIT 8.0 suitable for your operating system and the corresponding checksum file from the INUBIT User Portal.

    • Windows systems

      Patch Windows x64 <version> (file patchWinX64-<version>.exe)

    • Linux systems

      Patch Linux x64 <version> (file patchLinuxX64-<version>.bin)

  2. Make sure the patch installer has been downloaded correctly using the checksum file.

Executing the patch installer

Prerequisites

You have loaded the executable patch (refer to Downloading the executable patch installer).

Proceed as follows

  1. Identify the user running the Process Engine.

  2. Activate the maintenance mode.

  3. Stop all RCs on all systems connected to your process engine.

  4. Shut down the Workbench.

  5. Shut down the Process Engine.

  6. Start the patch installer without any options with the same user as the process engine.

    Examples:

    • Linux

      ./patchLinuxX64‑8.0.15.bin

    • Windows

      .\patchWinX64‑8.0.15.exe

  7. The patch installer starts, depending on the capabilities of the operating system, with a graphical user interface or on the console.

    You can also force the console mode to run by specifying the -i console option.

  8. In the selection list at the bottom of the patch installer start screen, select your preferred installation language and confirm your selection.

  9. Next choose INUBIT Components as install set.

    To patch Business Process Center, you can choose Business Process Center in the Choose Install Set dialog.

    For details how to patch the Business Process Center, refer to Patch Business Process Center (BPC).

  10. With INUBIT 8.0, AdoptOpenJDK is installed in the _jvm directory on the same level as <inubit‑installdir>.

    During the patch installation, regarding the JDK configuration, the following happens:

    • If a _jvm directory already exists, the following steps are performed:

      • An existing _jvm_backup directory is removed.

      • The existing _jvm directory is renamed to _jvm_backup.

      • A new _jvm directory is created where the latest AdoptOpenJDK version will be installed.

    • If no _jvm directory exists, a new _jvm directory is created where the latest AdoptOpenJDK version will be installed.

    • The java_home_path_setter.{sh|cmd} script is not updated during patch installation. If necessary, adjust the JAVA_HOME environment variable in this script manually to be set to the new installed _jvm directory.

  11. Follow the instructions.

    Before installing the new BPC modules, the files in the <inubit-installdir>/inubit/portal/bpc_modules/ are backed up to the <inubit‑installdir>/bpc/bpc_modules/lastversion_backup/ directory.

    These backup modules can be used if you want to roll back to previous BPC modules.

    The current BPC patch workflows are stored as BusinessProcessCenter‑workflow‑patch‑<bpcversion>.diagrams.zip file in the <inubit-installdir>/inubit/portal/bpc_modules/ directory.

    Rollback scenario

    If you want to rollback INUBIT by installing INUBIT patch installer, the respective patch version of BPC get overridden in <inubit-installdir>/inubit/portal/bpc_modules/ directory.

    Hence, the patched BPC modules get lost. Additionally, the lastversion_backup directory created during INUBIT patching is retained.

  12. Check the following log file for error messages: <inubit‑installdir>/Virtimo_Digitalization_Suite_Patch_Install_<date_time>.log

  13. If Tomcat has been updated automatically to a newer version during the patch installation, the directory containing the former Tomcat named to: <inubit‑installdir>/apache‑tomcat_backup. The new Tomcat version is installed in the directory: <inubit-installdir>/inubit/apache-tomcat.

    Tomcat configuration files under <inubit-installdir>/inubit/server/process_engine/conf retain after Tomcat update. No adjustments are required. For further information regarding the automated Tomcat update and the remaining steps, refer to Tomcat update.

  14. Check the additional patch steps required for your version jump when the INUBIT is turned off and perform these actions.

  15. Start the Process Engine.

  16. Check the additional patch steps required for your version jump when INUBIT is turned on and perform these actions.

  17. Deactivate the maintenance mode.

Automatic patch installation

Automated execution of the patch installer

JDK update

Update of the Java distribution

Tomcat update

Application server update (Apache Tomcat)

Press Esc to exit full screen
Modal image placeholder
Press Esc to exit full screen