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

HCL Traveler v11.0.2 released including MySQL support for Traveler HA Pools

Detlev Poettgen  November 18 2020 12:46:44 PM
Traveler 11.0.2 with Build Level 11.0.2.0 Build 202010261910_30 includes fixes for the Traveler server and two new features.

The big news: Traveler 11.0.2 will support MySQL for building Traveler HA Pools (Cluster) as one more option besides IBM DB2 or Microsoft SQL Server.

New Features:


Support for MySQL
Traveler 11.0.2 supports MySQL database for Traveler High Availability mode. MySQL versions 8.0.20 and higher of MySQL Community, Standard, and Enterprise editions are supported.  Traveler servers configured to use MySQL must be running Domino 11.0.0 or higher.

Support of Room Reservations with EAS 16.x Apple Calendar

Traveler 11.0.2 supports updating Room reservations for meetings modified from the Apple calendar.
The Apple device must be using the Microsoft Exchange ActiveSync 16.0 or later protocol (EAS 16.x).
Rescheduling or cancelling a meeting from the device will now reschedule or cancel a related room reservation in the Domino Rooms and Resources Database.
See 'Apple Limitations and restrictions' for support limitations

Updated APNS Certificates
Traveler 11.0.2 includes updated APNS Certificates that replace the certificates shipped with Traveler 11.0.1.  These new certificates expire November 7, 2021.


Database Schema
Traveler 11.0.2 does not include a database schema update, but a new Database Index:

This index was added to prevent duplicate entries in the ts_field_name table.
On the first Traveler startup on 11.0.2 a table repair action will be run to fix and remove duplicate entries if they exist and then add the index. 
However, if you manage your schema manually, you will need to do the following process to add the index:

        1        Run the VerifyIndexes.sql script
        2        If the index IDX_TS_FIELD_NAME_FN fails to be applied because of UNIQUE constraint errors, start traveler to have the table repair action run.
        3        Stop Domino and run the VerifyIndexes.sql again

Included Fixes


KB0082616
Server may exhaust Java memory in environments starved of memory

KB0084142
Apple native Mail app unable to send mails if the user does not have an internet address

KB0084445
HCL Traveler server might end abnormally with Out Of Memory conditions ghosting unprocessed many multi-instance meeting notices for a repeating meeting

KB0084375        
Attachments missing when syncing MIME email that is not multipart

KB0084048        
Error at writing MIME stream, Output Buffer Overflow when NTS_MIME_STREAM_FROM_DEVICE=true

https://support.hcltechsw.com/csm?id=kb_article_view&sys_kb_id=2459a5261b3b9c98beab64e6ec4bcba6


Kommentare

1Christian  11/18/2020 8:15:28 PM  HCL Traveler v11.0.2 released including MySQL support for Traveler HA Pools

Wo kann man dieses Fixup finden und runterladen?

Es ist niergendwo auffindbar!

  •  
  • 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

Treffpunkte

Archive