The problem occurs in an Active-Passive cluster configuration where two iProcess Engine installations share the same database but there is only one entry in the node_cluster table for the current active master node. Some customers use a script to update various tables including the node_cluster to fail-over to a second node to make it the new master node rather than have a master / slave configuring in the node_cluster table. This configuration can cause problems during an upgrade.

The first installation is upgraded performing a "Upgrade Files" and "Upgrade Schema" upgrade to upgrade both the files and database. This means the second installation will only require an "Upgrade Files" upgrade.

When the node_cluster table is updated to configure it for the second installation and an "Upgrade Files" upgrade is performed the upgrade will appear to have completed successfully but the EAI*.ear files will not have been copied to the SWDIR\libs directory or they will have been copied but not named correctly.

For example:

eaicom.ear instead of EAICOM_<ver>.ear
eaidb.ear instead of EAIDB_<ver>.ear
eaiscript.ear instead of EAISCRIPT_<ver>.ear
eaisql.ear instead of EAISQL_<ver>.ear
eai_mail.ear instead of EAI_MAIL_<ver>.ear

This results in the iProcess Engine not starting correctly.

Performing a files only upgrade can result in the EAI*.ear files not being correctly copied to the SWDIR\libs directory

Windows

The problem is cause by the method used to move to the second server/node. The iProcess Engine installer is not designed to perform this type of installation/upgrade, because it looks specifically for either a Master or Slave node to determine what type of install/upgrade to perform. The workaround for the issue is to temporarily add the second machine as a Slave Node (swadm add_server command), then run the upgrade, select "Register EAI Plugins" on the "Select Components to Configure" screen and let the installer perform the files only upgrade.

The following are steps to perform where Test01 is the current master server and has been upgraded using "Upgrade Files" and "Upgrade Schema" and Test02 is the second server/node.

1). Run the customer specific script that updates the relevant tables used to set Test01 as the master.
2). Add Test02 as a slave node using the swadm command,

swadm add_server Test02 N N Temp_server

3). Run the upgrade, select "Register EAI Plugins" on the "Select Components to Configure" screen.
4). Once the upgrade is complete check the EAI*.ear files have been copied correctly.
5). Delete the slave node,

swadm delete_server 2

6). Run the customer specific script that updates the relevant tables used to set Test02 as the master.
7). Start the iProcess Engine.