Announcing the IBM Domino V10 portfolio beta program: Sign up today

Make sure to sign up and take a look to the Domino V10 beta program.

Official Post

Beta 1: We will form an initial group of beta participants, based on the submissions received and then qualify and approve for beta program enrollment. Beta 1 will begin on June 25th, 2018.

What can be tested in Beta 1:

– Domino (Windows)
– Notes client (Windows)
– Notes, Designer & Admin clients (Windows)

This beta is English-only.

Beta 2: We will extend the initial group of Beta 1 participants as we get further along in the development cycle for Domino V10, by including additional participants at the Beta 2 stage. We expect the Beta 2 phase to begin the second half of July 2018.  Submissions received up to July 15th, for those not included in the Beta 1 group, will be considered for inclusion in the Beta 2 phase.

 What can be tested in Beta 2:

– Domino (Windows and Linux)
– Notes client (Windows and Apple Mac)
– Notes, Designer & Admin clients (Windows)
– Verse on Premises (Windows and Linux)
– DominoDB NPM package for Node.js

The goal of the IBM Domino V10 Portfolio Beta Program is for the community of beta participants to conduct honest, constructive and thoughtful review and testing of the Domino V10 beta software, which includes IBM Domino V10, IBM Notes V10, IBM Sametime V10 and IBM Verse On-Premises V10.

We’re seeking people who meet the following criteria:    

– A business end user, administrator, or developer, who has prior knowledge of Domino, Notes, and Verse.
– Those who bring diverse (role/industry/geography/company size) attributes to the beta team and, thus, ensure we get the right blend of input perspectives.

IBM is looking for participants to:

– Share their use case for the beta in their company.
– Engage in a dialog about Domino V10 and provide timely feedback.
– Be constructive and professional in all written/spoken interaction with program members, IBM and HCL.
– Attend the web conferences and meetings pertaining to the beta program.
– Experience the beta in a non-production environment.
– Be open to the idea of becoming a reference for IBM Domino V10.

IBM Traveler APNS Certificate Expires on 12.08.2017

As of tomorrow, 12.08.2017, the APNS Certificate used by Traveler will expire and will not be valid anymore. For everybody who is running Traveler this is a good time to update to a newer version. The current version of IBM Notes Traveler is

You can also update the certificate files, as Detlev described in his blog post.

Why is APNS Certificate important? IBM Technical Support Video


Traveler is out and it brings one big change!

Since yesterday the new Traveler Update is out.

As usual there are a few bugfixes, but this time there is also a new feature which changes the way the users mail file is accessed.

Until now the users mail database was accessed by the Traveler server using the server ID, but starting from Traveler the “run as user” Feature will be enabled by default, which means that the users mail database will be accessed with a user ID rather than the server ID. This behavior can be disabled by using the “notes.ini” parameter “NTS_USER_SESSION=false“.

Details on what´s new.

The Traveler update can be downloaded from Fix Central.

IBM Notes Traveler Available

IBM Notes Traveler Update is available for Download.

This update covers all previous updates and beside usual fixes, this updates enables Java 1.8 Support. Which is important and makes this update a requirement before installing IBM Domino Feature Pack 8 which will come later on.

Fix List

Release Notes

Download from Fix Central

Make sure to visit Daniel Nashed´s Blog, specifically the posts about IBM Domino 9.0.1 Feature Pack 8 and Java 1.8 Support where he described the impact of the coming changes and new features in great detail.

IBM Traveler Derby Database Corruption

After an OS restart we encountered a problem with the Traveler Server, the local Derby database became corrupt, and therefore Traveler clients could not sync the enterprise data.

After starting the Traveler task the following errors were logged in the console:

[09C4:000C-0B5C] <Timestamp>   Traveler: WARNING <Username> Session ID d082448615552a82da8175a9ea5d071a309 could not be associated with any existing PS threads.

[09C4:000C-0B5C] <Timestamp>   Traveler: SEVERE  <Username>  Exception Thrown: com.lotus.sync.db.PersistenceException: java.sql.SQLSyntaxErrorException: Invalid Properties list in FROM list.  There is no index ‘IDX_GUIDNEXT_1’ on table ‘GU

[09C4:000C-0B5C] <Timestamp>   Traveler: WARNING <Username> Sync exception being treated as a backend failure. Exception Thrown: com.lotus.sync.db.PersistenceException: java.sql.SQLSyntaxErrorException: Invalid Properties list in FROM list.

Next course of action was to try to defrag the Database which solved the problem. I simply removed the Traveler task from the “notes.ini” file and started it with “Load Traveler -defrag” command. The defragmentation Process took about 10 Minutes after which the Traveler task was started and the mobile devices could sync the PIM Data without any problems.

The following article from IBM also describes a similar behavior: