Two node JDBC data source creation on Windows - CustomerID
Ubisecure CustomerID uses a JDBC data source to access the database, thus one needs to be created to the WildFly domain before the Ubisecure CustomerID application can be deployed. There is a script in the distribution package's tools folder for this purpose: config-wildfly-domain-datasource.cmd. Note that the win32.config file must have been configured and setup.cmd must have been run successfully and WildFly must be running before the create-datasource.cmd script can be run successfully.
The script will also connect to the Master and Slave nodes and check that the data source can contact the database.
cd /D %PROGRAMFILES%\ubisecure\customerid\tools config-wildfly-domain-datasource.cmd
In case you need to make modifications to Data Source definitions at a later point of time, following scripts are provided:
config-wildfly-domain-datasource.remove.cmd
This script will remove the datasource definition, but leaves the driver deployment intact. When the data source has been removed, the script will also reload (restart) the master and customerid-slave nodes. If you have added nodes to the WildFly domain, you may have to restart them as well.
config-wildfly-domain-datasource-update.cmd
This script will remove the current data source definition and reconfigure a new one based on configuration parsed from win32.config with the setup.cmd script. The script will restart the master and customerid-slave nodes during this process. If you have added more nodes to the WildFly domain, you may have to restart them as well.
config-wildfly-domain-datasource-test.cmd
This script will connect to the master and customerid-slave nodes and run a test to see if the data source is operational on each node.
This web page (including any attachments) may contain confidential, proprietary, or privileged information – not for disclosure without authorization from Ubisecure Inc. Copyright © 2022. All Rights Reserved.