Guides

Drive 6.0.1

A new version of Drive is being released on 31st December 2023.

This purpose of this release is to support all instances of Autopay with one version of Drive.

Enhancements

Single Drive version

To reduce the number of versions to maintain, Drive has been updated to support all instances of Autopay.

Service creation at install

During the installation of Drive, the windows service will now be created at this time. Users will no longer be required to run the Windows Service bat file separately.

To complete the configuration, users must run the Windows CMD program with elevated administrator permissions, change the directory (cd) to the drive install path, and run Drive.bat - - c.

Cloning and supporting multiple instances of Drive

Drive still supports multiple instances to be run at the same time but we have made this easier for users to clone the existing installation and set up the windows service at the same time.

From the main installation of Drive, users can run the clone-drive.bat file, choose a location to clone, and set a new service name for the specific instance.

Sleep interval

To support customers with continuous disablement of Drive where the service encounters an error, we have updated Drive to make use of the current sleep functionality.

Currently Drive will enter a sleep cycle when it encounters a backend 503 error (when Autopay Online Plus is offline during maintenance). We have updated Drive to also utilize this functionality when encountering 502 backend errors.

Based on user configuration, Drive will enter a sleep cycle, reactivate and re-attempt to authenticate with Autopay Online Plus. If no connection can be established, Drive will repeat now repeat this cycle until authentication can be established with the service.

DigiCert certificates

To enhance security, Drive now uses the latest G2 intermediary DigiCert certificates.

Open JDK

Drive has been updated to use OpenJDK version 1.21.

Removal of older libraries

To improve performance we have removed the following unused libraries:

  • NSSM - modernizing this process by replacing the existing wrapper and incorporating service installation as an integral part of the MSI execution.
  • Log4j - unused log4j libraries have been removed from drive.jar.