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.

...

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

Perform on each Ubisecure CustomerID node:

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

Perform once on CustomerID Master Node:

1. Extract the deployment template. See instructions from Deployment template extraction on Linux - CustomerID.
2. Copy configuration files from old master to new, and setup.
   

   1. Transfer files from old master to new master.

      Code Block
      language text
      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/

   2. 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

   3. Run setup.sh.

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

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

Perform on CustomerID Slave Node:

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

Perform on PostgreSQL

1. Perform database schema update depending on versions.

   • See Database Changes.

...

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

Perform on each Ubisecure SSO node:

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

...

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

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

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

Perform on each Ubisecure CustomerID node:

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

Perform on each Ubisecure SSO node:

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

Perform on each Ubisecure CustomerID node:

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

Finalize:

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