fighting for truth, justice, and a kick-butt lotus notes experience.

HCL Traveler 11 available incl. New Features

 30 Dezember 2019 11:56:37
Just before christmas HCL released Traveler 11.0.0 (Build 201912061918_30).

Traveler 11.0.0.0 is a feature release that includes new features and bug fixes for the Traveler server.


Traveler 11.0.0.0 can be used to install a new Traveler environment or update an existing Traveler environment running Domino 9.0.1.x, Domino 10.0.x, or Domino 11.0.x without requiring a Domino upgrade
.

(Although it is always recommended to keep Domino at the latest level.)


Database Schema


Traveler 11.0.0.0 does include a database schema update.


New Features

Support for Microsoft Exchange ActiveSync 16.x

Traveler now supports Microsoft™ Exchange ActiveSync versions 16.0 and 16.1 on Apple iOS and iPadOS devices.

This change allows for the development of features that require this version, such as the ability to sync calendar attachments.

The device controls when the devices ask the Traveler server for the supported versions and which version the device uses.
The device periodically checks and upgrades to the latest version that the device supports without user intervention.

Draft mail messages synchronized with server

Apple iOS devices now support the syncing of draft messages.

As part of Exchange ActiveSync 16.X, which Traveler now supports, the draft messages sync from the server to the device and from the device to the server.

Support for non-repeating Calendar events greater than 24 hours in duration

Traveler supported mobile clients can now create and modify non-repeating meetings and appointments that are longer than 24 hours and shorter than 6 months.

View attachments in Calendar events

When your calendar has an event that includes attachments in the event description, you can now download and open the attachments on your mobile device if your device's calendar app supports the capability.  Note that attaching or removing attachments using the device's calendar app is not supported.

Support for APNS HTTP/2

Traveler now supports HTTP/2 for communication with Apple's Apple Push Notification Service (APNS) servers.
No configuration changes are required and there is no change in behavior.  HTTP/2 support requires a minimum of Domino 9.0.1, FP8.


Fix List



TRAV-4039
Encoded addresses modified by the device causes delivery failure reports

Address encoding for Microsoft Exchange ActiveSync devices was using a format that was case sensitive, so any devices that lower case the internet address were corrupting the encoded address making it decode to incorrect addresses and cause a delivery failure report.
Traveler now utilizes a format that is not case sensitive so that it does not matter if the device changes the case because they will decode correctly when used to send mails.



TRAV-4241
Verse for iOS on Apple iOS 13 and iPadOS 13 background push messages are not causing syncs

Apple changed the push message requirements for background notifications in iOS 13 and iPadOS13. Those requirements cannot be satisfied using the legacy APNS interface that Traveler was utilizing. Traveler now uses the latest, HTTP/2 APNS interface which allows these push message requirements to be satisfied for the Verse for iOS application to receive the push messages to drive the background syncs.  Requires a minimum of Domino 9.0.1 fp8 to utilize the new HTTP/2 support.



TRAV-4199
Local replicas on the Traveler server not found

Traveler searches for local replicas on the Traveler servers for the user's mail database using the replica ID. In some cases, Traveler was not configured or able to find the replica ID on the user's primary mail server preventing Traveler from finding the local replica. Depending on whether or not a local replica was required, this could prevent syncing.



TRAV-4151
HA status shows server unreachable when servers have multiple IP addresses

If a Traveler server has multiple IP addresses, it reports its NTS_HOST_IP_ADDR as the one to which its HA peers should connect. However, connect requests coming from that Traveler server will originate from its lowest-numbered IP address, and the HA peers will reject those connect requests if they originate from the wrong IP address. So, if NTS_HOST_IP_ADDR is not set to the lowest-numbered IP address, HA status shows server unreachable. The fix causes Traveler to bind to its NTS_HOST_IP_ADDR before attempting to connect to its HA peers, so its connect requests originate from the expected IP address.  



TRAV-4184
An email has two attachments with the same name, but only one syncs to the dev

An email attachment was treated as a duplicate of another attachment on the same email because their names were the same, even though their sizes were different.

Upgrades


When upgrading Domino major versions, for example from 9.0.1 to 10.0.x or 10.0.1.x to 11.0.0.x, it is always required to run the Traveler installer after the Domino upgrade even if not changing Traveler versions to ensure the Traveler binaries match the Domino level.

Upgrades in an HA pool

Traveler 11.0 enables support for Exchange ActiveSync 16.1 by default upon install/upgrade.  When upgrading a high availability pool of servers, the upgrade should be performed on all servers in quick succession.  Running in a mixed environment (different server levels, different Exchange ActiveSync levels) for long periods of time should be avoided.

For Linux Users: Silent install when upgrading Traveler on a pre-11.0 Domino server

The installer.properties used with the silent install process defaults the install location to the new default location for Domino 11.0 (ex:  /opt/hcl/ on Linux and AIX).  If Domino is installed in a different location, the installer.properties will need to be updated to point to that location.


Details:
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0074057


Kommentare
noch keine Kommentare vorhanden
  •  
  • Hinweis zum Datenschutz und Datennutzung:
    Bitte lesen Sie unseren Hinweis zum Datenschutz bevor Sie hier einen Kommentar erstellen.
    Zur Erstellung eines Kommentar werden folgende Daten benötigt:
    - Name
    - Mailadresse
    Der Name kann auch ein Nickname/Pseudonym sein und wird hier auf diesem Blog zu Ihrem Kommentar angezeigt. Die Email-Adresse dient im Fall einer inhaltlichen Unklarheit Ihres Kommentars für persönliche Rückfragen durch mich, Detlev Pöttgen.
    Sowohl Ihr Name als auch Ihre Mailadresse werden nicht für andere Zwecke (Stichwort: Werbung) verwendet und auch nicht an Dritte übermittelt.
    Ihr Kommentar inkl. Ihrer übermittelten Kontaktdaten kann jederzeit auf Ihren Wunsch hin wieder gelöscht werden. Senden Sie in diesem Fall bitte eine Mail an blog(a)poettgen(punkt)eu

  • Note on data protection and data usage:
    Please read our Notes on Data Protection before posting a comment here.
    The following data is required to create a comment:
    - Name
    - Mail address
    The name can also be a nickname/pseudonym and will be displayed here on this blog with your comment. The email address will be used for personal questions by me, Detlev Pöttgen, in the event that the content of your comment is unclear.
    Neither your name nor your e-mail address will be used for any other purposes (like advertising) and will not be passed on to third parties.
    Your comment including your transmitted contact data can be deleted at any time on your request. In this case please send an email to blog(a)poettgen(dot)eu

Archive