Implementation Instructions
For detailed installation instructions, see Participant Data Replication Loader GUI Installer Guide or Guide to Participant Data Replication Loader.
Full Install
To install pdrLoader v7.5.0 as a new implementation, you can choose one of the following files from the Data Interchange Software:
|
File |
File name |
Benefit |
|---|---|---|
|
Participant Data Replication Loader GUI Installer for <Database> v7.5.0.zip |
Requires the minimum data entry for localisation All implementation steps are automatic A manual installation is possible by exiting the installer and using a text editor to set the configuration properties |
Upgrading from pdrLoader v7.4.n to v7.5.0
A successful upgrade involves understanding the changes between the versions. See Improvements.
The v7.5.0 release has shipped with updated JDBC drivers across all database platforms, Microsoft have changed the configuration in their SQL Server JDBC driver to default to use SSL encrypted connections to the database.
An SSL encrypted connection would be considered best security practice, and participants wanting to configure this should discuss signed certificates across their infrastructure with their system administrator and refer to the OEM JDBC driver documentation for how to configure the connection string.
Participants who do not require encrypted communications can revert the configuration to previous Microsoft JDBC driver releases by configuring the connection string as follows:
db_url=jdbc:sqlserver://<host>:1433;databaseName=<db_name>;encrypt=false;selectMethod=cursor;sendStringParametersAsUnicode=false
Properties file updates
The release of pdrLoader v7.5.0 introduces a number of new optional configurations in the .properties file.
For help configuring the application properties, see Guide to Participant Data Replication Loader.
|
Property |
Detail |
|---|---|
|
${xxx} where xxx is the variable name, e.g.b base_dir=c:/pdr/
data_dir=${base_dir}/data
will result in data_dir being resolved to c:/pdr/data |
|
|
${env:xxx} where xxx is the environment variable name, e.g. participant_identifier=${env:ParticipantId}
will result in participant_identifier property being set to the value of the environment variable ParticipantId Environment variables are only resolved at the time of application startup. |
|
|
${sys:xxx} where xxx is the system variable name There are a range of system variables preconfigured in the JRE Additional system variables can be passed in on the command line using -D option, e.g. java -Dvar_name=var_value ......
will result in a system variable "var_name" set to "var_value". This can be referenced in the properties file as follows: my_variable=${sys:var_name} |
|
|
The comma delimited list of active threads. Replaces file_load_threads |
|
|
The logic to apply to file inclusion and exclusion masks. Valid values are: EXCLUSIVE: include mask (if defined) is evaluated first
exclude mask is only evaluated where there is not a match on include mask
AND: both include and exclude masks must be satisfied
Default value is EXCLUSIVE |
Properties file deletions
Properties made obsolete in v7.5.0.
|
Property |
Detail |
|---|---|
|
Is replaced by file_load_threads_active |
GUI installation process
The GUI installation process is a simple, clean way to upgrade. Alternatively, you can use the Implementation Instructions.
- If not already available, install JRE 11.
- Install the pdrLoader v7.5.0 to the current installation directory (for example, C:\Pdr\Loader). The current installation is backed up to a folder alongside the current installation with a timestamp appended to the folder name.
- If running as a window service, then ensure that the windows service name entered into the GUI installer matches the existing service name.
- Check the pdrLoader.properties file changes and re-apply any customised configurations. See Implementation Instructions.
- Run the pdrLoader.bat or the Windows service and check the pdr.log in the Log directory for any errors.
Manual installation process
The generic steps are:
- Backup your v7.4.n pdrLoader installation folders.
- Remove the pdrLoader v7.5.0 Windows service by running:
- Remove all existing jar files from the Lib folder
- Copy the following content from the pdrLoader v7.5.0 installation media into your Lib folder
- All jar files
- New scripts:
- pdrConnectionTest.*
- pdrLoaderDataExport.*
- Update script pdrEnvironment.* and align CLASSPATH environment variable definition to match the v7.5.0 definition
- If not already, install JRE 11 and update the JRE path variable in:
- pdrEnvironment.bat
- pdrServiceInstall.bat
- WinRun4J.ini files
- Replace property file_load_threads with new property file_load_threads_active, e.g.
file_load_threads=3
would be replaced with
file_load_threads_active=1,2,3
- Consider aligning your pdrLoader.properties to the standard configuration file unless you have specific customisation requirements. For participants with customisation requirements, it is recommended that these customisations be merged into a standard v7.5.0 properties file definition
- Apply the database update scripts applicable to your database platform in the following order:
- <database_platform>_alter_pdr.sql
- populate_parser_config_metadata_delta.sql
- commit
- Install a new Windows service by running:
pdrServiceInstall.bat <insert_Windows_service_name_here>.
- Check the database password is correctly encrypted before running the service by running the following command to avoid any password lockout:
- Run pdrLoader.bat or the Windows service and check the pdr.log in the Log directory for any errors. For help, see Guide to Participant Data Replication Loader.