11.3 pdrMonitor

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

11.3.1 Full Install

To install pdrMonitor v1.4.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 Monitor GUI Installer v1.4.0	Participant Data Replication Monitor GUI Installer for <Database> v1.4.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.3.2 Upgrading from v1.3.0 to v1.4.0

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

The release of pdrMonitor v1.4.0 introduces new configurations in the XML eXtensible Mark-up Language. configuration file

Properties file updates

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

Property	Detail
/Database/DbPassword	Encrypted passwords are represented as ${encypted:XXX} where XXX is the encrypted password.
/WebServer/Provider	The web server provider. Supported values are: au.com.aemo.Common.Web.JDK.WebServerJDK Supports http/1.1 and https/1.1 (default) au.com.aemo.Common.Web.Jetty.WebServerJetty Supports http/1.1 and https/1.1 au.com.aemo.Common.Web.Jetty.WebServerJettyHttp2 Supports https/2 with fall back to https/1.1 Modern browsers do not support http/2 (plain text). Note: https/2 requires a much larger number of threads due to the parallel nature of the protocol. Refer NoThreads configuration parameter.
/Authentication/AuthorisationProvider	The provider changes from: au.com.nemmco.Pdr.Monitor.Security.pdrMonitorAuthorisationProvider to au.com.aemo.Pdr.Monitor.Security.pdrMonitorAuthorisationProvider
/ThreadStatusCheckInterval	The interval (seconds) to check for failed threads. Default is 5 seconds.
/ThreadStatusReportingInterval	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.

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 Monitor Software v1.3.0 to v1.4.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 Monitor GUI Installer v1.4.0.jar"

• For more information, see https://docs.oracle.com/en/java/javase/21/docs/specs/man/jarsigner.html

3. Install the pdrMonitor v1.4.0 to the current installation folder (for example, C:\Pdr\Monitor).

• The current installation is backed up to a folder alongside the current installation with a timestamp appended to the folder name.

4. If running as a Windows service, ensure the Windows service name entered into the GUI installer matches the existing service name.

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.

5. Check the pdrMonitor.xml file changes and re-apply any customised configurations. See configuration files updates and deletions.
6. Run the pdrMonitor.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 Monitor software:

• Backup your pdrMonitor v1.3.0 installation folder.
• Remove the pdrMonitor v1.3.0 Windows service by running:

pdrServiceUninstall.bat <insert_Windows_service_name_here>.

3. Remove all existing jar files from the Lib folder.

4. Copy the following content from the pdrMonitor v1.4.0 installation media into your Lib folder:
5. All jar files
6. New windows service wrapper:
7. prun*.exe
8. pdrServiceInstall.ini

5. Run the following command, after unzipping the command line prompt in the Lib folder:

jarsigner -verify "AppPdrMonitor.jar"

6. Update script pdrEnvironment.* and align CLASSPATH environment variable definition to match the v1.4.0 definition.
7. Copy the following content from the pdrMonitor v1.4.0 installation media into your Website folder:
8. All folders under Website

8. If it is not already installed, install JRE 21 and update the JRE path variable in:
9. pdrEnvironment.bat
10. pdrServiceInstall.bat

9. Adjust configuration of the following elements in pdrMonitor.xml:
10. /Database/DbPassword
    Wrap the existing encrypted password as follows:
11. ${encrypted:XXX}

10. Apply the database update scripts applicable to your database platform in the following order:
11. <database_platform>_alter_pdr Participant Data Replication.sql
12. populate_parser_config_metadata_delta.sql
13. commit

11. Install a new Windows service by running:

pdrServiceInstall.bat <insert_Windows_service_name_here>.

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

pdrConnectionTest.bat

13. Run pdrMonitor.bat or the Windows service and check the pdr.log in the Log folder for any errors.

14. Test upgrade by loging to pdrMonitor Web url as Admin. If login cannot be completed using previous password, try resetting password using pdrMonitorPasswordReset.bat. Restart pdrMonitor service.
15. API keys defined within pdrMonitor source connections to pdrBatcher and pdrLoader need to match with respective keys defined within pdrBatcher and pdrLoader (pdr_key.properties). If these are changed during pdrBatcher/pdrLoader upgrades, please align the values and re-test pdrMonitor.