What's new in Traveler 14.0.0 Fix Pack 1?

Improved Version Upgrade Behaviors

Two new changes make it easier to spot problems related to upgrades. The first is that Traveler will now have a Yellow status on the console when servers in an HA pool have different Traveler versions. This will help to remind administrators that a Traveler upgrade is not complete until all Traveler servers have the same installed version. The second change is that Traveler will not run when the installed Domino version does not match the version that was present when Traveler was last installed. An error message on the console will explain whether Traveler needs to be reinstalled or upgraded. This will prevent version mismatch errors which can cause unexpected behaviors.

Support for Google FCM HTTP v1 API

Google has deprecated the legacy FCM APIs that Traveler was using for Android push notifications. Google started intermittently rejecting FCM messages sent via the legacy API in July 2024 and could reject all such messages at any time (details in KB0115437). By utilizing the FCM HTTP v1 API, all push messages will be accepted by the Google FCM servers and background syncs will work as expected.

Support for Domino versions 9.0.x and 10.0.x ended in June 2024 and will not support the new Google FCM HTTP v1 API. Customers running older (unsupported) Domino versions will not have push notifications after installing this fix pack. Background syncs will not be initiated; manual syncs will be required to get the latest data.

Updated APNS P12 files

Apple Push Notification Service (APNS) p12 certificates updated to expire in June 2025. These certificates replace the files shipped with Traveler 14.0, which expire November 14, 2024.

MS SQL Server 2022 Enterprise

HCL Traveler now supports MS SQL Server 2022 Enterprise edition.

Fixes

For fixes delivered with Traveler 14.0.0 FP1, see the release documentation support article KB0110147. and Fixes by Release support article KB0028394.