Two node upgrade process

The idea is to set up a new two node system and to keep the current two node system as a backup.

Follow the steps in order. Issue all commands using the root user account.

Perform once for the whole Ubisecure CustomerID cluster:

Back up Ubisecure Directory. See instructions from Backup and restore Ubisecure Directory - SSO.

Perform on each Ubisecure CustomerID node:

Unpack the distribution package. See instructions from Distribution package unpacking on Linux - CustomerID.
Check Java. See instructions from Java check on Linux - CustomerID.
Install WildFly. See instructions from Two node WildFly domain installation on Linux - CustomerID.

Perform once on CustomerID Master Node:

Extract the deployment template. See instructions from Deployment template extraction on Linux - CustomerID.

Copy configuration files from old master to new, and setup.

Transfer files from old master to new master.

scp /usr/local/ubisecure/customerid/application/linux.config <new_master_node_user>@<new_master_node>:/usr/local/ubisecure/customerid/application/
scp -r /usr/local/ubisecure/customerid/application/custom <new_master_node_user>@<new_master_node>:/usr/local/ubisecure/customerid/application/

Correct properties included in the linux.config file.
1. wildfly.home=/usr/local/wildfly-XX.X.X.Final
2. database.driver.file=postgresql-XX.X.X.jar

Run setup.sh.

cd /usr/local/ubisecure/customerid/application
./setup.sh

Prepare WildFly for domain configuration. See instructions from Two node WildFly prepare for domain configuration on Linux - CustomerID.
Configure WildFly on CustomerID Master Node. See instructions from Two node master WildFly configuration on Linux - CustomerID.
Configure the singleton subsystem. See instructions from Two node singleton subsystem configuration on Linux - CustomerID.

Perform on CustomerID Slave Node:

Transfer the installation folder from master node. See instructions from Two node installation folder transfer on Linux - CustomerID.
Configure WildFly on CustomerID Slave Node. See instructions from Two node slave WildFly configuration on Linux - CustomerID

Perform once for the whole Ubisecure CustomerID cluster:

Perform database schema update depending on versions.
- See Database Changes.
When upgrading from CustomerID version 5.6.x or older update CustomerID LDAP entries to facilitate REST API OAuth2 authentication. See LDAP import instructions from SSO management web applications creation on Linux - CustomerID.
- See also Configuring OAuth2 authentication for REST API.

Perform once on CustomerID Master Node:

Create JDBC data source to WildFly. See instructions from CustomerID Two Node JDBC Data Source Creation On Linux.
Create a Mail Session configuration for WildFly. See instructions from Two node mail session creation on Linux - CustomerID
Configure logging for CustomerID. See instructions from Two node logging on Linux - CustomerID
Register "customerid.home" system property to WildFly. See instructions from WildFly system property registration on Linux - CustomerID

Perform on each Ubisecure SSO node:

Upgrade PostgreSQL JDBC driver to SSO node(s). See instructions from PostgreSQL JDBC driver installation to SSO on Linux - CustomerID.
Upgrade Ubisecure CustomerID SSO Adapter to SSO node(s). See instructions from CustomerID SSO Adapter extension upgrade.

Perform on the CustomerID Master Node

Run following commands in all CustomerID nodes, to ensure files are in correct ownership and file mode.

chown -R wildfly. /usr/local/ubisecure/customerid/application/custom
chmod 644 /usr/local/ubisecure/customerid/application/custom/jndi.properties

Deploy the Worker Enterprise Archive to the WildFly domain. See instructions from Two node deploying Worker EAR on Linux - CustomerID
Deploy CustomerID Enterprise Archive to the WildFly domain. See instructions from Two node deploying CustomerID EAR on Linux - CustomerID
Configure HTTPS, See Two node CustomerID SSL on Linux - CustomerID..

Perform on each Ubisecure CustomerID node:

Configure SELinux. See instructions from SELinux configuration - CustomerID.
Restart Ubisecure CustomerID. See instructions from Restart on Linux - CustomerID.

Perform on each Ubisecure SSO node:

Restart Ubisecure SSO. See instructions from Installation related SSO restart on Linux - CustomerID.

Perform on each Ubisecure CustomerID node:

Restart Ubisecure CustomerID on Master node first, then slave node. See instructions from Restart on Linux - CustomerID.

Finalize:

Move traffic to the new two node installation.
Shutdown old two node system.
Backup and remove old two node system.

Browser not supported