Issue all the commands using the root user account.

Stopping Ubisecure CustomerID Services

Ubisecure CustomerID services can be stopped by using the following command: 

/etc/init.d/customerid stop

Make sure no changes are made to the database during following steps.

Set Up the Derby-to-PostgreSQL Migration Tool

Extract the migration tool package cid-database-migration-package-x.x.x-linux.tar.gz to /usr/local/ubisecure/migration-tool. 

cd /usr/local/ubisecure
mkdir migration-tool
cd migration-tool
tar -xzvf ~/customerid/cid-database-migration-package-x.x.x-linux.tar.gz

Checking Java

See Java check on Linux - CustomerID.

Use the Migration-Tool to Export Data from Derby DB

Environment variables used by the migration-tool:

Use the following lines as an example how to setup your own environment variables from the command line. Edit values to match your own environment. 

export DERBY_HOME=/usr/local/ubisecure/customerid/db-derby
export DERBY_CONNECTION_URL="jdbc:derby://localhost:1527/eidm2db;territory=fi_FI;collation=TERRITORY_BASED:PRIMARY"
export DERBY_PASSWORD='secretDerbyPassword'
export MIGRATION_JAR_FILE=cid-database-migration-x.x.x.jar

Run DerbyExportWithCopy functionality of the migration-tool to export data from the existing Derby DB: 

cd /usr/local/ubisecure/migration-tool
$JRE_HOME/bin/java -Dderby.system.home=$DERBY_HOME -cp ./lib/derbyclient-10.11.1.1.jar:cid-database-migration-x.x.x.jar com.ubisecure.customerid.database.migration.DerbyExportWithCopy

The DerbyExportWithCopy functionality of the migration-tool will create .sql scripts into export-results-batch subfolder that can be used to import existing data to PostgreSQL. It may take a while to perform this, depending on how much data is stored in Derby database. If the tool discovers pre-existing sql files in this folder with the same name as what it is going to write, it will interrupt its work and exit. So, if you have to fix something and re-run the command, you will have to ensure that the export-results folder is empty before you do so.

Backing up Ubisecure CustomerID

See instructions from Backup and restore - CustomerID.

Backing up Ubisecure Directory (OpenLDAP)

See instructions from Backup and restore Ubisecure Directory - SSO.

Uninstalling and Deleting the Old Installation

The Ubisecure CustomerID services and related user account must be deleted before proceeding with the update by running:

/etc/init.d/customerid-db stop
cd /usr/local/ubisecure/customerid/application
chmod o+x config/unix/uninstall.sh
./config/unix/uninstall.sh

Rename old installation folder:

cd /usr/local/ubisecure
mv /usr/local/ubisecure/customerid /usr/local/ubisecure/customerid-old

Unpacking the New Distribution Package

See Distribution package unpacking on Linux - CustomerID

Installing WildFly

If you have an existing WildFly installation, you need to uninstall it and install the one included in the distribution package.
For instructions installing (and uninstalling) WildFly see WildFly installation on Linux - CustomerID.

Extract the deployment template

Extract the archive cid-deployment-template-x.x.x-linux.tar.gz: 

cd /usr/local/ubisecure
tar xzvf ~/customerid/cid-deployment-template-x.x.x-linux.tar.gz

Importing configuration settings from the old installation

In order to resume the service after the upgrade, it is necessary to copy some configuration settings from the previous installation. These settings are contained in the file customerid/application/linux.config.
In the new installation the linux.config file is located further down the similar path in the subfolder config and must first be copied to the application folder.
The values must be copied carefully as the configuration options may have changed. You should copy only those values that have the same keys on both old and new linux.config files.

Refer to page Setup template on Linux - CustomerID for more information about the new configuration options.

Running setup script

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

Configuring WildFly

See CustomerID WildFly Configuration On Linux.

Preparing a database for Ubisecure CustomerID

See CustomerID PostgreSQL Preparation On Linux.

Create JDBC Data Source To WildFly

See JDBC data source creation on Linux - CustomerID.

Modify Directory Service for Ubisecure CustomerID Internal Database

You should already have a directory service for Ubisecure CustomerID internal database. However that service points to the old Derby database. It needs to be modified so that it points to the PostgreSQL database. See further instructions from SQL directory service creation on Linux - CustomerID concerning the correct values.

Use the migration-tool to import the data to PostgreSQL

You have to create an empty PostgreSQL database and the CustomerID database user before import.

Environment variables used by the import-tool:

Use the following lines as an example how to setup your own environment variables from the command line. Edit values to match your environment.

export PGUSER=customerid_user
export PGPASSWORD=secretPostgresqlPassword
export PGCLIENTENCODING=UTF8
export PGHOST=localhost
export PGPORT=5432
export PG_CONNECTION_URL=jdbc:postgresql://$PGHOST:$PGPORT/customeriddb
export MIGRATION_JAR_FILE=cid-database-migration-x.x.x.jar

Create tables to the PostgreSQL DB:

psql -d customeriddb -U $PGUSER -f ./scripts/cid_create_postgresql.sql

Initialize the DB with internal data used by the CustomerID:

psql -d customeriddb -U $PGUSER -f ./scripts/cid_init.sql

Import previously exported Derby DB data to the PostgreSQL DB:

for f in ./export-results-batch/*.sql; do (psql -d customeriddb -U $PGUSER -f $f;) done

Use the following command if you need to drop database tables before a new attempt (for example after correction of the data):

psql -d customeriddb -U $PGUSER -f ./scripts/cid_drop.sql

Validating the data

When the data has been imported, run DataCleanup functionality of the migration-tool to make sure that the data has been imported properly.

$JRE_HOME/bin/java -cp .:./lib/postgresql-9.4.1210.jar:cid-database-migration-x.x.x.jar com.ubisecure.customerid.database.migration.DataCleanup

This functionality will write errors in a log file called CLEANUPRESULTS.txt. If there were errors in the data import it is possible to repair them manually using an SQL client to connect to PostgreSQL. How to repair depends on the nature of the error and in this case you may have to consult Ubisecure support.
When all errors have been fixed, you should run DataCleanup functionality of the migration-tool again and check the log file if the data is consistent.

Creating constraints and indexes

When the data has been validated, execute the following commands to create indexes and constraints to the tables.

psql -d customeriddb -U $PGUSER -f ./scripts/cid_create_postgresql_sso_views_and_functions.sql
psql -d customeriddb -U $PGUSER -f ./scripts/cid_create_postgresql_constraints.sql

Restoring the Local Customizations

Restore the old custom folder with the following commands:

cp -a /usr/local/ubisecure/customerid-old/application/custom /usr/local/ubisecure
/customerid/application/
chown -R wildfly:wildfly /usr/local/ubisecure/customerid
chmod -R o-xrw /usr/local/ubisecure/customerid

Deploying Ubisecure CustomerID

Ubisecure CustomerID uses WildFly as a J2EE Container. This chapter describes how to deploy the cid-ear-x.x.x.ear and cid-worker-ear- x.x.x .ear enterprise archives (EARs).
Deploy the Ubisecure CustomerID application to WildFly using the deploy-ear.sh command. When invoking the command, you must supply the path to the ear file, like in the example below:

cd /usr/local/ubisecure/customerid/tools
./deploy-ear.sh ~/customerid/cid-ear-x.x.x.ear
./deploy-ear.sh ~/customerid/cid-worker-ear-x.x.x.ear

SELinux configuration

Configure SELinux

If a reverse proxy is used in SELinux:

/usr/sbin/setsebool httpd_can_network_connect 1

Ubisecure CustomerID SSO Adapter Upgrade

See SSO adapter upgrade on Linux - CustomerID