11.2 pdrLoader

For detailed installation instructions, see Participant Data Replication Loader GUI Installer Guide or Guide to Participant Data Replication Loader.

11.2.1 Full Install

To install pdrLoader Software responsible for loading files to and from participant's local Data Interchange folders to the participant's DBMS. It can be installed in any environment supporting Java. v7.7.0 as a new implementation, select the following file from the Data Interchange A set of cooperating applications used to replicate data between AEMO's energy market systems and a participant's DBMS conforming to the MMS Data Model. software:

File

Filename

Benefit

Participant Data Replication Loader GUI Installer v7.7.0.

Participant Data Replication Loader GUI Installer for <Database> v7.7.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.

11.2.2 Upgrading from v7.6.0 to v7.7.0

A successful upgrade involves understanding the changes between the versions. See pdrLoader improvements for more information.

The v7.7.0 release has shipped with updated JDBC drivers across most database platforms. Please confirm the compatibility of the JDBC driver with your local database infrastructure.

An SSL Secure Socket Layer, a protocol for encrypting information over the internet. encrypted connection to your local database would be considered best security practice, and participants wanting to configure this should discuss signed certificates across their infrastructure with their system administrator.

Participants who do not require encrypted communications can generally apply configuration to the JDBC connection string to indicate a non-encrypted communication channel.

Refer to the OEM JDBC driver documentation for how to configure the connection string to your organisation’s requirements.

Properties file updates

The release of pdrLoader v7.7.0 introduces a number of new optional configurations in the .properties file.

For help configuring these properties, see Participant Data Replication Loader User Guide.

Property

Detail

loader_thread_check_interval

The interval (seconds) to check for failed threads. Default is 5 seconds.

loader_thread_report_interval

The interval (seconds) to report thread summary in log file. Default is 3600 seconds.

Properties file deletions

Properties made obsolete in v7.7.0.

Property

Detail

db_password_encrypted

This parameter is discontinued. Encrypted configuration is denoted by enclosing the value as follows:

${encrypted:XXX}

GUI installation process

The GUI installation process is a simple, clean way to upgrade. Alternatively, you can use the Manual Installation process below.

Follow the steps below to upgrade an existing Participant Data Replication Loader Software v7.6.0 to v7.7.0 installation:

  • If it is not already installed, install JRE 21.
  • Validate the jar file signature. From the command line prompt, run the following command:

    • jarsigner -verify "Participant Data Replication Loader GUI Installer v7.7.0.jar"

  • For more information, see https://docs.oracle.com/en/java/javase/21/docs/specs/man/jarsigner.html
  1. Install the pdrLoader v7.7.0 to the current installation folder (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.
  1. If running as a Windows service, ensure the Windows service name entered into the GUI installer matches the existing service name.

    2. This release introduces a new Windows service wrapper. If the application runs as a Windows service, select the Windows service installation option during the upgrade. The installer removes the existing Windows service and re-registers it using the new service wrapper. If this option is not selected, the legacy service wrapper remains installed and does not operate correctly with this release.

  2. Check the pdrLoader.properties file changes and re-apply any customised configurations. See Upgrading from v7.6.0 to v7.7.0.
  3. Run the pdrLoader.bat or the Windows service and check the pdr.log in the Log folder for any errors.

Manual installation process

Follow the steps below to manually upgrade an existing Participant Data Replication Loader software:

  • Backup your pdrLoader v7.6.0 installation folder.
  • Backup database tables PDR_REPORT_ROW_FILTERS and PDR_REPORT_TRANSFORMS.
  • Remove the pdrLoader v7.6.0 Windows service by running:

    • pdrServiceUninstall.bat <insert_Windows_service_name_here>.

  1. Remove all existing jar files from the Lib folder.
  1. Copy the following content from the pdrLoader v7.7.0 installation media into your Lib folder:
  2. All jar files
  3. New windows service wrapper:
  4. prun*.exe
  5. pdrServiceInstall.ini
  1. If it is not already installed, install JRE 21 and update the JRE path variable in:
  2. pdrEnvironment.bat
  3. pdrServiceInstall.bat
  1. Update the definition of_db_password to wrap the encrypted value, for example:
    db_password=uj3KvUYmchoKABGdPDggBQ==
    then becomes:
    db_password=${encrypted:uj3KvUYmchoKABGdPDggBQ==}
  1. 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 v8.0.0 properties file definition.
  2. Apply the database update scripts applicable to your database platform in the following order:
  3. <database_platform>_alter_pdr.sql
  4. populate_parser_config_metadata_delta.sql
  5. commit
  1. Install a new Windows service by running:

    2. pdrServiceInstall.bat <insert_Windows_service_name_here>.

  2. Check the database password is correctly encrypted before running the service by running the following command to avoid any password lockout:

    3. pdrConnectionTest.bat

  1. Run pdrLoader.bat or the Windows service and check the pdr.log in the Log folder for any errors. For help, see Guide to Participant Data Replication Loader.

Custom code extensions

The pdrLoader v7.7.0 release updates the code package from au.com.nemmco.* to au.com.aemo.*.

Any references to the interfaces which define those extensions must be recompiled against the interfaces in the new package. The pdrFileEventInt has also been changed from abstract class to interface in this release. Refer to the SDK folder in the installation directory for instructions and examples. Participants requiring assistance to migrate any existing plug-in configurations should log a support ticket with AEMO Australian Energy Market Operator Support Hub.

Rollback considerations

The pdrLoader v7.7.0 release updates the code package from au.com.nemmco.* to au.com.aemo.*.

Some of the references in the PDR_* management table provide mapping to various classes.

In the event that the installation needs to be reverted to v7.6.0, then the references in tables PDR_REPORT_ROW_FILTERS and PDR_REPORT_TRANSFORMS need to be reverted to the nemmco namespace.