Page tree
Skip to end of metadata
Go to start of metadata

Last reviewed: 2019-03-26

Issue all the commands using the root user account.

Stopping Ubisecure CustomerID services

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

systemctl stop wildfly.service

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

Checking Java

See Java check on Linux - CustomerID .

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

Remove the old files before unpacking the new ones to the installation folder. You can delete the old installation by using the following commands: 

cd /usr/local/ubisecure
rm -rf /usr/local/ubisecure/customerid

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 and which are defined by you and not the installation package.

Running setup script

NOTE: If you have made configuration changes to any of the linux.config parameters after previously running the setup.sh, ensure that these changes are included in the new linux.config file. For example, if you have changed the REST credentials in eidm2.properties file, make sure the same values are now present in the linux.config file.

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

Configuring WildFly

See CustomerID WildFly Configuration On Linux .

Setting up customerid.home System Property for WildFly

Setting up Audit and Diagnostic logging

Setting up a Mail Session

See WildFly configuration on Linux - CustomerID .

Preparing a database for Ubisecure CustomerID

See Database changes.

Creating the JDBC Data Source to WildFly

Ubisecure CustomerID uses a JDBC data source to access the database, thus one needs to be created to WildFly before the Ubisecure CustomerID application can be deployed. There is a script in the distribution package's tools folder for this purpose: create-datasource.sh. Note that the linux.config file must have been configured and setup.sh must have been run successfully and WildFly must be running before the create-datasource.sh script can be run successfully. 

cd /usr/local/ubisecure/customerid/tools
./create-datasource.sh

Restoring the Local Customizations

NOTE: Before replacing the custom folder, make sure there are no new additions in the configuration files. If there are, update your old customizations to support new configurations before replacing the files. The page CustomerID Configuration Changes In Versions lists all changes you need to do between different versions. Using that document as a guide delete all removed keys, add new ones if needed and replace all changed keys.


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


UPGRADE IS NOW COMPLETE! Log in with your credentials.

  • No labels