Starting up and Testing the INUBIT Software

After migrating, only those workflows are active that have already been active in the source system. Since the maintenance mode has been activated workflows are not resumed immediately. Only if all tests have been successfully completed, deactivate the maintenance mode in the end to resume all workflows as scheduled.

Proceed as follows

Start the INUBIT Process Engine on the node on which you have executed the migration script.
Configure the portal server.
Deploy the portlet archive.
Configure the process user server.

Test the workflows and system connections.

When migrating from INUBIT 6.1 with JDBC 4.0 driver

If you are using column name aliases in database queries, the result set of the Database Connector will now always return these aliases as labels for the columns.

Therefore, in the modules following a Database Connector, ensure that the column name aliases are used instead of the column names. If you have used parameters to return column name alias instead of the column name in the database URL or in the connection parameters of Database Connectors then remove them.

Check the logging and monitoring information.
Test the portal functionalities.
In the workbench, deactivate maintenance mode using Administration > General Settings> Administration > Server > Maintenance mode.