Overview

This manual guides you through the process of migrating from an older INUBIT installation to the latest INUBIT 8.0 version. Before migrating to the latest INUBIT 8.0 version, first patch your current INUBIT installation to the latest supported patch level of your minor release, for example for INUBIT 7.2.x patch to INUBIT 7.2.0.59 and for INUBIT 7.3.x patch to INUBIT 7.3.0.44. Afterward, you can migrate to the next supported INUBIT version or to the latest INUBIT 8.0 version.

You have to obey all intermediate steps.

Migration matrix

Your current INUBIT version Possible INUBIT target version

<= 7.0.x

7.1.x

7.1.x

7.2.x / 7.3.x

7.2.x

7.3.x / 7.4.x / 8.0.x

7.3.x

7.4.x / 8.0.x

7.4.x

8.0.x

Recommendation for migrating from INUBIT 7.1.x to INUBIT 8.0.x: First patch your INUBIT 7.1.x installation to INUBIT 7.1.0.63, and then migrate to INUBIT 7.3.0.44. Backup your INUBIT 7.3. installation and then migrate to the latest INUBIT 8.0 version.

Migrating an INUBIT installation under JBoss to INUBIT 8.0 is not supported anymore. Switch to the Apache Tomcat application server.

As of INUBIT 7.4.0.43, an AdoptOpenJDK is delivered, and it is installed in the _jvm folder below <inubit‑installdir>. AdoptOpenJDK is used automatically by default. Alternatively, you can use another supported JDK (refer to Software Requirements). In this case, you have to set the JAVA_HOME environment variables accordingly, refer to Setting the JAVA_HOME Environment Variable.

Data migration process

The migration runs largely automatically using a script (refer to Executing the Migration Script).

The following section describes which data are migrated automatically by this script and which data you need to migrate manually as well as the settings you need to configure manually in the destination system.

Additional manual steps are required, for example, to install the database drivers and to configure the application server. Refer to Installing Database Driver on Destination System and refer to Migrating External Settings.

Before migrating larger amounts of data using an Oracle database, set AUTOEXTEND for the undo tablespace.

To migrate the data, the following steps are performed:

  1. Backup of the source system’s data

  2. Optionally: Migrating EDI ID lists manually (refer to EDI Migration)

  3. Restoring the source system’s data on the destination system

The following data are saved automatically for the migration

  • External libraries in the directory <inubit‑installdir>/server/lib/ext (contains, among other things, plug- ins and third party libraries)

  • System libraries (directory <inubit‑installdir>/server/lib/system, contains, among other things, database driver required for executing workflows)

  • Configurations files

    • ibis_config.xml

      Features and properties that become obsolete in the new version are omitted. For each property that is not migrated, an "info" entry is added to the migration log file.

    • plugin.xml

    • profile.xml

    • tool_profiles.xml

    • Application profiles (directory app)

  • EDI (rules, qualifier, schemas)

    To migrate EDI IDs, manual steps are necessary (refer to EDI Migration).

  • Monitoring database

  • Tasks and task lists

    • Delegated tasks, if delegation happened on INUBIT 7.4.0.47 and onwards

  • Tags

  • user-specific Repository data

  • Process Id range (process_id.xml)

The following data are NOT saved automatically

  • Toolset and Workbench settings as well as Toolset and Workbench reports

  • Database driver for the Monitoring database and the Repository database

  • Point In Time Recovery archive

  • Start script of the application server

  • Repository directory Global (including EDI rules)

  • Delegated tasks if delegation happened before INUBIT 7.4.0.47

  • Portal server

  • ExtJS directory extensions

  • Portal folder <inubit‑installdir>/server/ibis_root/conf/portal (because of possible incompatibilities with the installed Liferay version)

  • Configuration files

    • logsDBConfig.xml

    • taskDBConfig.xml

    • repository.xml

    • ibis_deploy.xml

    • systemdiagram_config.xml

    • partnermanagement_config.xml

      The configuration files ibis_deploy.xml, systemdiagram_config.xml, and partnermanagement_config.xml must be configured using the INUBIT Workbench (Configuration> Deployment, Configuration > System Diagrams, Configuration > Partner management).

  • INUBIT libraries: ibis.jar, ibis_tools.jar

  • Tomcat log files (directory <inubit‑installdir>/server/process_engine/logs)

  • Tutorial Users

Prior to restoring the data, all existing data (users, processes, repository, logs, etc.) will be removed from the destination system.

Updating Your License

To start the Process Engine on the destination system, you need a new license suitable for the version you want to migrate to. You apply for a license key at the support of Virtimo AG support@virtimo.de.

Refer to requesting a License Key.

Incompatibilities

Along with the numerous improvements and innovations of the INUBIT software, there are a few incompatibilities that are only relevant in particular use cases. Find the complete list of incompatibilities in the readme‑EN.txt file in the INUBIT installation folder or here.

Announcements of Discontinuation

Find the complete list of discontinuations in the readme‑EN.txt file in the INUBIT installation folder or here.

Support

If you have questions concerning the migration, please contact the support of Virtimo AG:

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