11 April 2016 09:40:42
After upgrading your Domino Server to 9.0.1 FP5 IF1 you may notice more or less often an error on the console:
New SSL session data length of 103 bytes is larger than the
current size of 100 bytes.
IBM published an APAR Request about this issue a few days ago:
Since 9.0.1Fp5IF1, the defaults SSL SESSION SIZE is causing the
following warning to be thrown more often.
New SSL session data length of 103 bytes is larger than the
current size of 100 bytes.
Default size may be to small for generall SSL and is causing
Set SSL_SESSION_SIZE ini to a high value hence extending the
To get rid of this messages set SSL_SESSION_SIZE in your notes.ini to 1024 bytes for example:
Link to the APAR Request:
6 April 2016 17:16:04
It is no longer mandatory for administrators to manually perform tell traveler security delete
to remove the device security administration data from IBM Traveler after a device has been deleted or reset. Starting with version 22.214.171.124, IBM Traveler will automatically quarantine deleted devices and move them into the deleted state
. These deleted devices will not be seen in the "Devices" view, however they will continue to be seen in the "Devices Security" view for up to 30 days. IBM Traveler keeps deleted device security data for the 30 day period in order to
- Publish device security data to the IBM Traveler Web Administration Console so that Administrators can take further action on those deleted devices
- Allow IBM Traveler Administration REST API consumers query for a list of all deleted devices.
- Allow sufficient time for any security actions taken against the device to complete.
If there is no device activity for 30 days, the corresponding device security data will be automatically removed. This means any security action previously completed or still pending against the device will be lost. However, if a deleted or reset device happens to connect and/or sync with IBM Traveler within the 30 day window, it will be moved to an active state and will resurface in the "Devices" view.
, is available to customize the 30 day period for security data removal.
If an administrator wants the security data to be immediately removed during device deletion, they can assign a value of 0 to this ini
setting. This forces IBM Traveler to remove both the device and its security data when tell traveler delete
or tell traveler reset
is performed. Any previous security (such as approval, deny, or wipe) actions taken against the device will be immediately lost. In environments where NTS_ADMIN_CLEANUP_TIMEOUT = 0
has been set, we recommend not to delete a device immediately after a security action has been issued. Instead, wait for the server and/or device to complete the action before deleting the device. For example, if a device or application wipe has been issued and the device is deleted immediately following that wipe, even before the device acknowledges the wipe, the wipe action will be lost from IBM Traveler. Note:
There is still no explicit indication available on the IBM Traveler Administration UI to highlight devices in the deleted state. If a device is deleted, it will not appear in the "Devices" view.
Can be found here: http://www.ibm.com/support/knowledgecenter/?lang=en#!/SSYRPW_9.0.1/tellcommandreference.dita
15 März 2016 21:09:25
Today IBM released a new Traveler version called 126.96.36.199 (Build: 201603081019_20).
|APAR # ||Abstract |
|LO87777 ||Ghosted view of rescheduled event may be missing a previous information update. |
|LO87835 ||Warning messaged displayed on server when a user tries to update an event they are not the chair for from iOS 9.x native calendar. |
|LO87837 ||Calendar event with DBCS characters in description may sync slowly to IBM Verse mobile client. |
|LO87872 ||Sent By may be incorrect when sending mail from IBM Verse mobile and a delegate created the draft message. |
|LO87916 ||IBM Verse on iOS may show wrong unread count if the user has multiple devices using different e-mail filter ranges. |
|LO87975 ||Parent calendar document with update conflict will not sync to mobile device. |
|LO88010 ||Schema may not be upgraded when using DB2 on AIX in Traveler HA environment. |
|LO88053 ||Ghosted view of new invitation may remain on mobile device after decline from the Notes client. |
|LO88065 ||Out of Memory (OOM) error when sending e-mail from mobile device and the recipient list contains an invalid address. |
|LO88121 ||Signed e-mail sent from IBM Verse or IBM Companion may use incorrect signing certificate. |
|LO88142 ||Out of Memory (OOM) error when running standalone (Derby) to Enterprise DB migration. |
|LO88163 ||Add, then remove, then re-add invitee to a repeating event and the event will not be ghosted on the invitee's mobile device as expected. |
|LO88164 ||Reschedule then canceled event may still appear ghosted on iOS 8.x Apple device when using the native calendar application. |
|LO88166 ||Cancel all instances of repeating event and the event may still appear ghosted on an iOS 8.x Apple device when using the native calendar application. |
|LO88203 ||IBM Traveler server crash due to very long log message. |
|LO88209 ||DBAccountsCheck may not show or repair duplicate account if the user is the last one in the list. |
|LO88214 ||OrderLatch timeout errors in the IBM Traveler server logs. |
|LO88244 ||Reschedule all after cancel one instance of repeating event and the recipient may still see the cancelled event ghosted on an iOS device when using the native calendar application. |
|LO88245 ||Ghosted view of repeating event may show incorrect content if the event was first updated then rescheduled. |
|LO88246 ||Accept notice may be sent from mobile device when processing a cancellation for the event. |
|LO88247 ||Ghosted view of event may not be correct after invitee is removed then re-added to an event. |
|LO88319 ||Update APNS certificates for use with IBM Verse client for Citrix enabled Apple devices.|
You can download the update as usual on
14 März 2016 22:24:17
Die nächste DNUG Konferenz findet vom 01. bis 02.06.2016
Wer sich als Referent aktiv einbringen möchte, hat hierzu die Chance einen Abstract einzureichen.
Die einzelnen Tracks werden durch die einzelnen DNUG-Fachgruppen organisiert.
Ich selbst bin Mitverantwortlich für die DNUG-Fachgruppe Mobile und würde mich über Abstract zu Mobile-Themen freuen.
Was mir hierbei am Herzen liegt:
Die DNUG ist eine User Group und lebt vom Austausch, der Diskussion und dem Networking untereinander. Daher würde ich mich freuen, wenn nicht nur die üblichen bekannten Sprecher Abstracts einreichen, sondern auch neue Gesichter sich motiviert fühlen, sich einzubringen.
Jeder hat bestimmte Herausforderungen oder Aufgaben bei sich im Unternehmen gemeistert und die sich im Alltag bewährt haben.
Warum diese nicht teilen und im Rahmen eines DNUG Vortrags vorstellen? Andere stehen in der Regel vor den gleichen Herausforderungen - die DNUG ist die Plattform diese Erfahrungen untereinander auszutauschen.
Wenn jemand also zu Mobile-Themen (IBM Notes Traveler, Enterprise Mobile Device & Application Management, interessante Mobile Inhouse Projekte, Best Practices, ...) einen Vortrag halten oder an einer Diskussionsrunde teilnehmen möchte, kann sich gerne bei mir melden oder einfach Online den Abstract einreichen:
Wer selbst keinen Vortrag halten will oder kann, aber gerne ein Thema behandelt sehen möchte, kann mir gerne auch einfach einen Themenvorschlag per Mail schicken oder hier einen Kommentar hinterlassen. Ich würde dann schauen, ob wir hierzu einen Referenten in der Community finden.
19 Februar 2016 09:44:09
Erfahren Sie alles Wichtige aus Orlando kompakt in der von mir mitorganisierten IBM Connect Comes To You | Westfalen
Start / Ende: 12:30 - 18:00
Ort: Bielefeld -
Hotel Bielefelder Hof
(direkt gegenüber dem Hauptbahnhof)
Für die Veranstaltung konnten wir als Referenten original Sprecher und Teilnehmer der Connect gewinnen, die ungefiltert Ihre Erfahrungen und Eindrücke schildern und gemeinsam mit Ihnen die aktuellen Themen diskutieren.
Wir stellen die wichtigsten News und interessanten Themen rund um IBM Verse, Project Toscana, IBM Connections, IBM Notes & Domino,IBM Notes Traveler, Mobile, Development und Cloud kompakt in fünf Sessions vor.
Die Teilnahme an der Veranstaltung an sich ist kostenfrei und wird durch Sponsoren getragen.
Keine Angst - es handelt sich bei der Veranstaltung ausdrücklich um keine Produktvertriebsveranstaltung, sondern Fokus ist die Vorstellung und gemeinsame Diskussion der News von der diesjährigen IBM Connect.
Die Veranstaltung ist ins Leben gerufen worden von der OpenUserGroup | Westfalen und wird von mir organisiert.
Nach Abschluss der offiziellen Veranstaltung besteht die Möglichkeit zum gemeinsamen Essen im üblichen Rahmen des 12. OpenUserGroup | Westfalen Stammtisches.
Ich würde mich auf jeden Fall freuen, Sie am 03.03. auf der IBM Connect Comes To You | Westfalen begrüßen zu dürfen.
Details, Agenda und Anmeldung zur IBM Connect Comes To You | Westfalen:
3 Februar 2016 17:01:43
Two weeks ago IBM released a new Version of
IBM Notes Traveler 188.8.131.52..
When you upgrade to 184.108.40.206, Traveler will perform a new check, if doubled account records exists in a specific table of the Derby / Enterprise database. The account records must be unique. But in the past there could be a second record been created under certain circumstances.
You will get more or less of these messages after starting the Traveler server:
"CN=Frank Demo/OU=West/O=Foo has 2 account IDs when there should be only one account ID. You may need to reset CN=Frank Demo/OU=West/O=Foo 2 times.
30 out of 831 users had multiple account IDs and may need to be reset multiple times"
To get this fixed you need to run the new DBAccountsCheck Command:
Starting with 220.127.116.11, the Traveler server has been updated to solve it, but also will create a unique index on the account table to prevent any future possibility of this problem from happening. However, the unique property can not be applied while the account table has non-unique data (i.e., users with multiple accounts). Follow these steps to ensure that no user has multiple accounts.
1) Run DbAccountsCheck command in show mode to determine if the problem exists.
tell traveler DbAccountsCheck show *
2) If any users are reported with this issue then the account table constraint has not yet been added to the account table. To remove the multiple accounts run a reset * command for the user once for each account. I.E. if the user has two accounts run the reset * command for the user twice. The DbAccountsCheck tell command has a repair option to simplify this operation.
tell traveler DbAccountsCheck repair
In repair mode it is advisable to run in small batches and during off peak hours to ensure no performance impact on the system. In general batches of 50 or 100 users at a time should pose little impact to the overall system performance.
tell traveler DbAccountsCheck repair 50
3) Once all users with multiple accounts are cleared up the unique constraint should automatically be added to the account table. To verify run the DbAccountsCheck show option again
Because the repair option will enforce an reset * command, have in mind, that the specific users will get an initial sync for their devices. So running the command in small batches will make sense.
We had to run the DbAccountCheck Command on most of the systems, we already upgraded to 18.104.22.168.
26 Januar 2016 16:03:59
IBM introduced with IBM Notes Traveler 22.214.171.124 a new tool to get better control of the defragmentation of the used relational state database (Derby in Standalone / DB2 or MS SQL in HA).
Before 126.96.36.199 the periodic defragmentation could be configured by using the notes.ini setting NTS_DEFRAG_INTERVAL_DAYS. This INI-setting is no longer used by Traveler and 188.8.131.52 will show you a warning:
Since 184.108.40.206 you need to configure scheduled defragmentation by using the new DBMAINT-Command:
To check the current config and status:
tell traveler dbmaint show
To enable periodic defragmentation you will have to enable and configure it using this commands:
tell traveler dbmaint set interval 30
tell traveler dbmaint set auto on
From the Traveler documentation:
Running defragmentation on a scheduled basis (220.127.116.11 and later)
To perform defragmentation on a scheduled basis, perform the following procedure:
1 Use the tell command DBMaint set interval in order to set the interval to a number greater than 0. For example, to set an interval of 30 days, enter into the console:tell traveler dbmaint set interval 30
2 Use the tell command DBMaint set auto on to turn on automatic defragmentation.
3 To force a defragmentation, enter the command tell traveler dbmaint run. This sets NTS_DEFRAG_ONCE to 1 and the Derby database will be defragmented the next time the IBM Traveler server restarts.
Running defragmentation on a scheduled basis (18.104.22.168 to 22.214.171.124)
To run defragmentation on a scheduled basis with IBM Traveler server 126.96.36.199 to 188.8.131.52, perform the following procedure:
1 Add NTS_DEFRAG_INTERVAL_DAYS to the notes.ini file. For example, to set an interval of 30 days add: NTS_DEFRAG_INTERVAL_DAYS=30
2 Restart the IBM Traveler server. From that point on, if the IBM Traveler server is restarted and it has been 30 days since the last defragmentation, then the defrag operation will run.
3 To force a defragmentation, simply delete the parameter NTS_LAST_DEFRAG from the notes.ini file and restart the server.
If NTS_DEFRAG_INTERVAL_DAYS is set and there is no last defragmentation timestamp, then the server will perform a defragmentation and reset the NTS_LAST_DEFRAG timestamp.
|DBMaint Run ||Immediately performs online maintenance. If the server is standalone, then it will configure maintenance to run on restart. |
|DBMaint Show ||Displays various database maintenance scheduling information. |
|DBMaint Fragmentation ||Recommends database maintenance based on fragmentation levels. |
|DBMaint Set Interval days ||Sets the interval of days in which automatic database maintenance will perform. |
|DBMaint Set Time hh:mm ||Sets the time in 24-hour format in which automatic database maintenance will perform. |
|DBMaint Set Day monday-sunday/off ||Sets the day of the week on which the first scheduled automatic maintenance will start. Set this to Off if you want the first scheduled maintenance to be based off of the last maintenance time. |
|DBMaint Set Threshold on/off ||Configures automatic database maintenance to check fragmentation levels before execution. |
|DBMaint Set Auto on/off ||Enables automatic database maintenance. Re-enablement will reschedule maintenance if either the time or interval have changed. |
|DBMaint Set Indexes number ||Configures the number of fragmented indexes for the fragmentation threshold. |
|DBMaint Set Ownership ||Configures ownership of database maintenance to the executing server. This server will be the only server that can perform automatic database maintenance. |
|DBMaint Set Percent 0-100 ||Only applicable for SQL Server. Configures the fragmentation percentage of indexes for the fragmentation threshold. |
|DBMaint Set Functions 1-4 ||Only applicable for DB2. Configures the number of functions that are used to determine if an index is fragmented for the fragmentation threshold.|
18 Januar 2016 21:06:25
Yesterday IBM released a new version of the IBM Connections App for iOS.
The new app version now includes support for iOS Managed App Configurations!
We as midpoints had been in talks with IBM for a while regarding the possibility to manage the iOS IBM ICS mobile Apps (Verse, Companion, ToDo, Connections and Connections Chat aka Sametime) by using Apple Managed App Configurations. The Connections App was the last missing app. Mission completed :-)
Example Managed App Configurations:
com.ibm.mobile.connections.serverName.1="My personal Account"
The complete list of support MDM App Configurations can be found here:
IBM Knowledge Center - MDM app configuration
Details about Managed App Configurations can be found in my blog post from Nov. 2015:
Our EMM solution mobile.profiler supports Managed App Configurations since iOS 7 and can be used to preconfigure the iOS IBM ICS Apps.
16 Januar 2016 13:50:41
Yesterday IBM released a new Traveler version called 184.108.40.206 (Build: 201601150235_20).
IBM Traveler 220.127.116.11 is now available for download from Fix Central. A full installation package will be available for download from Passport Advantage by January 27th.
Due to the potential issue described in the following technote, Traveler 18.104.22.168 is recommended as the minimum 9.x server version to upgrade to from 8.5.3.x
Two scenarios where multiple accounts for users could be created on an IBM Traveler server HA pool (technote 1974741).
A few weeks ago I ran into this issue while ungrading form 8.5.3 UP2 IF 8 to 22.214.171.124 at customer site, too. Great that it is fixed now.
The new version contains a longer list of fixes and two new features:
- Calendar Ghosting (which was added in 126.96.36.199) is enabled by default for IBM Verse clients starting in release 188.8.131.52
- New Tell command named "DbAccountsCheck".
For details on this command, including why it was introduced, as well as its syntax and expected output, refer to Two scenarios where multiple accounts for users could be created on an IBM Traveler server HA pool (technote 1974741).
|APAR # ||Abstract |
|LO86162 ||E-mail sent to recipient with nested quotes and a comma may result in delivery failure. |
|LO86465 ||Delegated repeating event may not sync to delegates mobile device. |
|LO86501 ||Attendee removed then added back to event, event may be missing from mobile device. |
|LO86630 ||Link to Companion application missing in encrypted e-mail when syncing to Maas360 Secure Mail Client. |
|LO86680 ||Notice comments appear in preview but not body of notice when viewed in IBM Verse application on Android devices. |
|LO86682 ||Event update from iOS 9 Native Calendar application may change the time zone of the event. |
|LO86700 ||Startup on Linux may create bogus directory ./data/IBM_TECHNICAL_SUPPORT in data directory. |
|LO86787 ||Unable to set JDBC connection URL greater than 256 characters. |
|LO86807 ||Folder create on mobile device may not sync to other mobile devices for same user. |
|LO86831 ||Rapid multiple updates to calendar event from Apple device may not process all updates. |
|LO86871 ||Traveler server may run defrag more then desired on stand-alone environment when interval set to value larger than 24 days. |
|LO86932 ||Domino server version detection may fail during install if system temp directory contains special characters. |
|LO87022 ||Traveler server crash when syncing large Mime format document that is missing plain text content. |
|LO87112 ||Font may grow on Apple device when viewing e-mail with multiple in-line replies. |
|LO87123 ||Add capability to expand groups at the Traveler server level for FYI/BCC fields. |
|LO87238 ||Ghosted reschedule of a repeating event may show incorrect time if previously declined one of the even instances. |
|LO87241 ||Declined invitation moved to Inbox could cause a sync loop. |
|LO87243 ||Recognize correctly Windows 10 Tablets and Windows Mobile 10 Phones. |
|LO87286 ||StringIndexOutOfBoundsException displayed in Console. |
|LO87309 ||Event syncs to iOS native Calendar application then later disappears. |
|LO87331 ||Max attachment size in Domino Policy document may not apply to assigned user due to case mismatch. |
|LO87335 ||Traveler Web Administration app may not display a small number of users. |
|LO87414 ||Out Of Memory error running standalone to HA Migration with large number of users. |
|LO87442 ||User may receive new account ID and resync all devices when upgrading an HA environment from IBM Traveler 184.108.40.206 to 220.127.116.11. |
|LO87602 ||Forwarded event from BlackBerry device has event chair set in Reply-To field instead of sender. |
|LO87603 ||Calendar document copy to mail file succeeds even if exception thrown by Domino API causing server to retry copy. |
|LO87609 ||Notes doc links do not work when viewed on some mobile devices. |
|LO87612 ||E-mail may be missing body in unrecognized character set is specified. |
|LO87613 ||E-mail may be missing body if Mime format document is missing plain text content. |
|LO87614 ||Add additional tell commands to repair duplicate account IDs and missing items for a user. |
|LO87623 ||Add unique index t account table to prevent single user from having multiple account IDs. |
|LO87660 ||Updated APNS Certificates for IBM Verse Application.|
You can download the update as usual on
14 Januar 2016 20:48:43
Apple released a new beta of the Apple Configurator v2.2 and iOS 9.3.
The Beta includes a new restriction, that will allow you to hide Apple system apps like Watch, Stocks, Tips, News, Passbook ....
To be able to use the new restriction the device must be Supervised!
Create a configuration profile in Apple Configurator 2.2 Beta with a restrictions payload set to “Do not allow some apps” under “Restrict App Usage” in the Apps section of the Restrictions. Add the necessary bundle IDs like com.apple.tips, com.apple.stocks, then plug in your device and apply the profile. The icons will simply disappear from the home screen…
Here are some of the Bundle IDs for iOS’ default apps:
com.apple.stocks – Stocks
com.apple.tips – Tips
com.apple.videos – Videos
com.apple.mobilemail – Native Email Client
com.apple.mobilenotes – Notes
com.apple.reminders – Reminders
com.apple.calculator – Calculator
com.apple.Maps – Maps
com.apple.Music – Music
com.apple.Passbook – Wallet
com.apple.Health – Health
com.apple.mobilephone – Phone
com.apple.MobileStore – iTunes Store
com.apple.MobileSMS – Messages
com.apple.VoiceMemos – Voice Memos
com.apple.weather – Weather
com.apple.podcasts – Podcasts
com.apple.gamecenter – Game Center
com.apple.Bridge – Watch
com.apple.mobileme.fmf1 – Find Friends
com.apple.iBooks – iBooks
com.apple.mobileme.fmip1 – Find iPhone
com.apple.mobiletimer – Clock
com.apple.mobileslideshow – Photos
com.apple.Preferences – Settings
com.apple.Camera – Camera
com.apple.facetime – FaceTime
com.apple.MobileAddressBook – Contacts
com.apple.news – News
At the moment it is Beta, but I hope Apple will ship and add it to the MDM restrictions, too.