 Detlev Poettgen
| 26 Juni 2017 15:30:05Last week IBM released a new version 9.4.0 of the IBM Verse for iOS App. IBM Verse for iOS v9.4.0 had been completely rewritten and was the first feature update since a few months. Under the hood IBM changed the way to pre-configure the app by an EMM/MDM solution. The Verse app now supports the open AppConfig Community standard to push setting like a server URL or an user name to the app. Verse for iOS supports custom managed configuration, which allows the MDM administrator to preconfigure many Verse for iOS settings. Any setting defined using the MDM takes precedence over a similar setting or policy defined at the Traveler server. Setting custom app configuration will vary by the MDM soltution you are using. All MDM providers should support the concept of Apple managed configurations using custom keys and value pairs. Now it is possible to define most of the user setting within the app and to lock some of these settings. I will post an additional bloentry in a few days, when IBM will have published the AppConfig documentation. To pre-configure Verse you will need to set in minimum these four settings: | Key | Data Type | Value (Example) | Comment | | appConfigOnly | Boolean | true (1*) | Will enable the AppConfig Settings within the app and will ignore Maas360 & MobileIron SDK | | serverType | String | onpremises | Where is your server located?
onpremises
cloud
choice (asking user) | | serverURL | String | https://mobile.comp.com/traveler | Provide the hostname or a fully qualified URL to your company's Traveler server. Only provide this value if using ‘onpremises’ as the server type. | | user | String | IggyPop | Login user id. You should be able to use placeholders depending on your MDM solution | Hint: The key names are case sensitive !!! (1*) Depending on your MDM solution you can use "true" / "false" or "1" / "0" as Boolean Values Using our own MDM solution midpoints mobile.profiler a simple pre-configuration of Verse for iOS looks like this:  Thank you at this place to Bill Wimer (IBM) and the Traveler Dev team for the AppConfig integration. Well done and I will post a few more new settings when the AppConfig documentation will be public. 15 Juni 2017 21:56:11Today IBM released a new Traveler version called 9.0.1.18 (Build: 9.0.1.18 201706131301_20). 
9.0.1.18 brings this new change: Traveler Server Run as User Starting with IBM Traveler 9.0.1.18, the run as user feature will now be enabled by default. When running as the user, the Traveler server will access the user's mail file as the user ID instead of the server ID. This feature resolves several long standing issues with accessing the user's mail file as the server ID, including: - Honor ACL controls on mail file and corporate lookup for the user.
- Prevent event notices and automated responses from being sent from the server ID.
- Prevent the server ID from being assigned as the owner of the mail profile when there is no owner defined.
Important: For run as user feature to function properly, the Traveler server must be listed as a trusted server in the user's Mail Server document. To disable run as user, set this notes.ini parameter: NTS_USER_SESSION=false
Fixlist: | APAR # | Abstract | | LO90096 | Info update continues to be ghosted on mobile device after the event is processed. | | LO91797 | Empty comments displayed on iOS native Calendar application when event processed in iNotes. | | LO91836 | Invalid this and future reschedule generated by iOS native Calendar application. | | LO91875 | Ghosted event not displayed on mobile device. | | LO91956 | Maill attachment does not sync to mobile device when contains angle brackets < and >. | | LO91997 | IBM Traveler web administrator may show iOS Verse 9.4 device as not supporting security capabilities. | | LO92010 | Better handling of special character in mail header fields. | | LO92080 | Ignore a reply message with out a valid action defined. | | LO92085 | Hard delete processed notices vs soft delete to prevent from filling up trash folder. | | LO92209 | Second meeting room may be lost if event updated from mobile device. | | LO92210 | Unable to turn off iOS Verse application password via Domino policy document setting. | | LO92257 | Two instances of a previously processed event may show on mobile device if the daylight savings rules change for the time zone. | | LO92303 | SQL Syntax error adding index TSGUDTSTAMPCREATEIDXSQL9 on DB2. |
Note: IBM Traveler 9.0.1.18 does not include a database schema update. You can download the update as usual on IBM FixCentral. An IBM Traveler 9.0.1.18 full installation package, which will be available on Passport Advantage on June 21, can be used to upgrade any previous Traveler server or to install a new environment. 3 April 2017 14:01:25Die nächste DNUG Konferenz findet vom 31.05. bis 01.06.2017 in Berlin statt!  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 gemeinsam mit Jürgen Bischof 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 Lösungen gefunden, 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 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 bis zum 10.04.2017 den Abstract einreichen:
http://dnug.de/dnug44-call-for-abstract/ 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. 21 März 2017 17:37:58Today IBM released a new Traveler version called 9.0.1.17 (Build: 9.0.1.17 201703170414_200). 
It’s a maintenance release that provides APAR fixes - no new features
Fixlist: | APAR # | Abstract | | LO90889 | Invitee status not correct on mobile device if the invitee response is received in a non-syncing folder. | | LO91550 | Multiple ghost entries possible if adding invite to event that has outstanding updates pending. | | LO91723 | User may stop recieving updates to mobile device after mail server restarted and there is no backup mail server. | | LO91733 | Subject of mail replied to/forwarded from Windows 8 device may display incorrectly. | | LO91762 | IBM Traveler server may change case of Domino domain to all lower case when sending mail. | | LO91770 | Subject of new mail sent from Windows 8 device may display incorrectly. | | LO91819 | User may not be able to sync data to mobile device when the user's mail file name contains special characters. | | LO91870 | Wipe data option may be greyed out for iOS Verse client. | Note: IBM Traveler 9.0.1.17 does not include a database schema update. You can download the update as usual on IBM FixCentral. An IBM Traveler 9.0.1.17 full installation package, which will be available on Passport Advantage on 24th March., can be used to upgrade any previous Traveler server or to install a new environment.
8 März 2017 09:27:06 As already mentioned here you will need IBM Traveler 9.0.1.16 before upgrading to Domino 9.0.1 FP8. Have in mind that when you move your Traveler HA environment to Traveler 9.0.1.16 and Domino 9.0.1 FP8 the JVM will gets upgraded to Java 8. Please check the following Technote before upgrading to FP8:
Abstract
The IBM Domino 9.0.1 FP8 release will include an upgrade to Java 8. This article details requirements for IBM Traveler servers to run Java 8.
Overview
The steps outlined below are required to run IBM Traveler on a Domino 9.0.1 FP8 or later server. It is not required to run Domino 9.0.1 FP8 or later to use the latest available IBM Traveler release.
Traveler Requirements
Java 8 support is included in IBM Traveler 9.0.1.16 and later releases. It is required to run this level or later on a Domino server running 9.0.1 FP8 or later.
JDBC Requirements
If running IBM Traveler with either DB2 or MS SQL enterprise database server, then follow these steps to ensure compatibility with Java 8.
- If using DB2 server: In order to support Java 8 you must use DB2 JDBC Driver V10.5 FP7 (4.19.49) or higher, see technote 1983724 for details. The DB2 JDBC Driver can be downloaded directly from Fix Central, see technote 1363866 for download information. Copy the db2jcc4.jar file to the \Traveler\lib directory and restart the Domino server. Be sure to remove any old copies of the DB2 JDBC driver from the system.
- If using MS SQL server: In order to support Java 8 you must use sqljdbc42.jar file from MS JDBC 4.1 or later release. Download the latest Microsoft SQL Server JDBC Driver from this site. For detailed system requirements for the SQL Server JDBC driver see this Microsoft article. Copy the sqljdbc42.jar file to the \Traveler\lib directory and restart the Domino server. Be sure to remove any old copies of the MS SQL JDBC driver from the system.
https://www-01.ibm.com/support/docview.wss?uid=swg21999188 6 März 2017 11:37:22Ich möchte an dieser Stelle gerne auf den nächsten geplanten DNUG Webcast am 14.03.2017 um 16:00 - 17:00 Uhr aufmerksam machen.  Wir haben für den DNUG Webcast zwei IBM'ler aus dem IBM Traveler und Mobile Product Team aus den USA gewinnen können. IBM's Mobile Strategy and Securing Mobile Applications No organization can ignore the fact we live in a mobile-drive world. IBM software helps organizations support the mobile, social way in which today's companies work. Come here about IBM's mobile strategy and the latests updates on mobile applications such as IBM Traveler, IBM Watson Workspace, IBM Verse, IBM Connections, and more. Also, learn about the strategic direction of mobile security, and how the IBM mobile applications can help address mobile application management and security requirements. Speakers: Paul Miller - IBM Mobile Development Director Bill Wimer - Mobile Senior Technical Staff Member Detlev Pöttgen - midpoints (Moderator) Die Anmeldung für den Webcast ist bereits über den folgenden Link möglich. (Die Inhalte sollten auf der DNUG Webseite noch heute aktualisiert werden.) http://dnug.de/event/dnug-webcast_2017-03-14/ 28 Februar 2017 09:30:28IBM released a new Traveler version 9.0.1.16 two weeks ago. This version includes a longer fixlist with important updates. Details can be found here: ibm-traveler-9.0.1.16-available.htm But as it looks like, that there is an issue, which breaks the push of new mail. I received comments on my blog post and offline feedback, that the push will break, when the mail server of the user is longer unavailable for whatever reason. A Traveler restart will fix it. The new version seems to have a bug: At night, the mail server is daily down for backup purposes. After this, the Traveler is no longer able to reconnect. The result is that no more mails are pushed. After the manual restart of the tour again everything was ok.
Is only since the new version 16. Other users report this behavior. So I would recommend to wait with your update to 9.0.1.16 until this one is fixed. Customers already updated to 9.0.1.16 and run into this issue should open a PMR. A downgrade to an older version is not a good option.
UPDATE 14.03.2017: IBM was able to reproduce the behaviour and is already pushing out a Hot Fix to customers, who opened a PMR. included Fixes in 201703012047_40_Server_Win.zip: - LO91550: INVITATION ADDING USER TO MEETING MAY INCORRECTLY GHOST OVER MORE CURRENT CHILD DOCUMENTS - LO91723: Users stop receiving mail after mail server is restarted - LO91733: Subject of mail replied to/forwarded from Windows 8 device may display incorrectly They also published an APAR Entry:
https://www-304.ibm.com/support/entdocview.wss?uid=swg1LO91723&myns=swglotus&mynp=OCSSYRPW&mync=E&cm_sp=swglotus-_-OCSSYRPW-_-E Traveler has a problem when all mail servers for a specific
user's goes down at one time and after the mail servers are
restarted users are able to synch data from the device, but no
new mails come down to the device. This was introduce in
9.0.1.16 fix pack.
The work around is to either do
- Tell Traveler Push Disable UserId and Tell Traveler Push Enable UserId for each effected user or
- Restart IBM Traveler after the mail files have been restarted. Either of these approach will resolve the issue. I suppose that IBM will update the 9.0.1.16 download package in Fix Central and Passport Advantage with a package that will contain the fix. UPDATE 21.03.2017: IBM released Traveler 9.0.1.17 today: ibm-traveler-9.0.1.17-fixing-the-issues-introduced-with-9.0.1.16.htm 15 Februar 2017 18:25:43Today IBM released a new Traveler version called 9.0.1.16 (Build: 9.0.1.16 201702130701_20). 
9.0.1.16 brings this new feature: - Support for Java 1.8. Traveler 9.0.1.16 is a pre-requisite for Traveler servers that will be upgraded to Domino 9.0.1 FP8, which we will be be released soon.
Important:
If you are running Traveler in HA Mode, you should check first the version of your used JDBC Driver. For DB2 it is recommended using a JDBC driver from IBM DB2 11.1 or later DB2 products when using Java 8. DB2 support states that this JDBC driver is backward compatible with earlier levels of DB2 server. Details regarding the DB2 JDBC Driver can be found here: http://www-01.ibm.com/support/docview.wss?uid=swg21363866
Fixlist: | APAR # | Abstract | | LO88787 | Event may not sync to mobile device if there is a replication conflict on the initial invitation document. | | LO90807 | Better documentation and behavior when syncing documents that use an unsupported document encoding. | | LO90903 | DBAccountsCheck utility may fail to recognize duplicate account for a user when the name is stored using different case. | | LO90926 | Potential issue adding primary key to database schema on a stand alone Traveler server. | | LO90987 | Event location information could be lost on a meeting that is updated from an iOS native calendar application. | | LO91052 | Traveler database schema migration may fail on MS SQL Server when upgrading from 9.0.1.0 to 9.0.1.15. | | LO91141 | Modified online meeting info may revert to original value when event is later rescheduled from mobile device. | | LO91227 | Errors may be reported on Domino console when running Traveler cleanup on a stand alone server. | | LO91272 | Subject of e-mail may get corrupted when reply/forward from a Windows 10 Pro device. | | LO91294 | Last instance of a repeating all day event may be missing from iOS native calendar application. | | LO91353 | DB2 server may select a bad query execution plan when some users have 50k+ mail documents causing high DB2 server CPU. | | LO91467 | Event may not sync to mobile device if the time zone field has unexpected characters. | | LO91468 | User with multiple devices set to different mail filters may not get expected mail filter on all devices. | | LO91485 | Unable to add additional attachments when replying or forwarding an e-mail from a Windows mobile device. | | LO91580 | Update APNS certificates, new expiration value is March 8th 2018. | | LO91585 | Support for Java 1.8 | Note: IBM Traveler 9.0.1.16 does not include a database schema update. You can download the update as usual on IBM FixCentral. An IBM Traveler 9.0.1.16 full installation package, which will be available on Passport Advantage on 24th Feb., can be used to upgrade any previous Traveler server or to install a new environment.
IMPORTANT: There is a major issue introduced in 9.0.1.16. Please read this additional Blog post issues-with-latest-traveler-version-9.0.1.16.htm
UPDATE 21.03.2017: IBM released Traveler 9.0.1.17 today: ibm-traveler-9.0.1.17-fixing-the-issues-introduced-with-9.0.1.16.htm 6 Februar 2017 14:03:25If you are still running an older IBM Traveler version as 9.0.1.15 like 9.0.1.14, you will notice since Friday that the Push Notification for IBM Verse for iOS are no longer working. You will see many error messages on the console: 06.02.2017 11:59:08 Traveler: SEVERE *system Couldn't send message after 3 retries, Message(Id=692311; Token=8C720F7F9B96D30C184445840EF0D0D925BC8C269618C7523E0B98EE9B61A03E; Payload={"aps":{"badge":14,"content-available":1,"alert":"E-Mail von test.de","sound":"v)"},"LGUID":"2068982","FLAGS":"1001","account":"1"}) Exception Thrown: javax.net.ssl.SSLException: Received fatal alert: internal_error
The reason is that the APNS certificate used for IBM Verse for iOS expired on Friday 03th Feb. 2017. The certificate is part of the Traveler installation package. And the IBM Verse APNS P12 file of Traveler 9.0.1.14 is expired. To solve it you will have two options: 1. Option: Move on to Traveler 9.0.1.15
Update your server to the latest version, but have in mind that there is still a known issue:
hotfix-via-pmr-available-for-traveler-9.0.1.15-standalone-issue.htm
2. Option: Stay on 9.0.1.14 and only change the P12 certificate files.
You can replace your existing certs and use this three files, which I copied from my Traveler 9.0.1.15 server. The certs are valid until August 12 2017.
PushAPNSAppleVerseProduction.zip
Extract the zip-file and copy the three P12-files to your Traveler server: notes_data/traveler/cfg and restart your Traveler server
You can check, if the Push Notifications are working and how long the certs are valid by executing this command:
tell traveler push cmstatus It should look like this: > tell traveler push cmstatus
06.02.2017 13:51:46 Traveler: ########## Connection Manager (Mon Feb 06 13:51:46 CET 2017) ##########
06.02.2017 13:51:46 Traveler: Description: Statistics for current connections and peak connections. List of all current connections between devices and the server.
....
06.02.2017 13:51:46 Traveler: ########## Connection SMS Sender (Mon Feb 06 13:51:46 CET 2017) ##########
06.02.2017 13:51:46 Traveler: Description: List of all pending SMS messages to be sent.
06.02.2017 13:51:46 Traveler: -- SMS-DelQ --
06.02.2017 13:51:46 Traveler: DelayQueue (Name: SMS-DelQ, Size: 0 object(s), Head: null, Current Date: Mon Feb 06 13:51:46 CET 2017)
06.02.2017 13:51:46 Traveler: obj2DqeMap (Object To DelayQueueElement Map) (0 objects sorted by dequeue time)
06.02.2017 13:51:46 Traveler: ########## Connection Notification Sender APNS (Mon Feb 06 13:51:46 CET 2017) ##########
06.02.2017 13:51:46 Traveler: Description: Details about the connections to the Apple Push Notification Service (APNS) servers.
06.02.2017 13:51:46 Traveler: No connection for To Do Development to gateway.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_APPLE_TODO_DEVELOPMENT
06.02.2017 13:51:46 Traveler: No connection for To Do Development Sandbox to gateway.sandbox.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_APPLE_TODO_DEVELOPMENT_SANDBOX
06.02.2017 13:51:46 Traveler: No connection for To Do Production to gateway.push.apple.com on port 2195, but it is enabled via NTS_PUSH_ENABLE_APNS_APPLE_TODO_PRODUCTION
06.02.2017 13:51:46 Traveler: No connection for To Do Production Sandbox to gateway.sandbox.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_APPLE_TODO_PRODUCTION_SANDBOX
06.02.2017 13:51:46 Traveler: No connection for Verse for Citrix Development to gateway.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_APPLE_VERSE_CITRIX_DEVELOPMENT
06.02.2017 13:51:46 Traveler: No connection for Verse for Citrix Development Sandbox to gateway.sandbox.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_APPLE_VERSE_CITRIX_DEVELOPMENT_SANDBOX
06.02.2017 13:51:46 Traveler: No connection for Verse for Citrix Production to gateway.push.apple.com on port 2195, but it is enabled via NTS_PUSH_ENABLE_APNS_APPLE_VERSE_CITRIX_PRODUCTION
06.02.2017 13:51:46 Traveler: No connection for Verse for Citrix Production Sandbox to gateway.sandbox.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_APPLE_VERSE_CITRIX_PRODUCTION_SANDBOX
06.02.2017 13:51:46 Traveler: No connection for Verse Development to gateway.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_APPLE_VERSE_IBM_DEVELOPMENT
06.02.2017 13:51:46 Traveler: No connection for Verse Development Sandbox to gateway.sandbox.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_APPLE_VERSE_IBM_DEVELOPMENT_SANDBOX
06.02.2017 13:51:46 Traveler: No connection for Verse Production to gateway.push.apple.com on port 2195, but it is enabled via NTS_PUSH_ENABLE_APNS_APPLE_VERSE_IBM_PRODUCTION
06.02.2017 13:51:46 Traveler: No connection for Verse Production Sandbox to gateway.sandbox.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_APPLE_VERSE_IBM_PRODUCTION_SANDBOX
06.02.2017 13:51:46 Traveler: No connection for MaaS360 Development to gateway.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_MAAS360_DEVELOPMENT
06.02.2017 13:51:46 Traveler: No connection for MaaS360 Production to gateway.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_MAAS360_PRODUCTION
06.02.2017 13:51:46 Traveler: No connection for Third Party Development to gateway.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_THIRD_PARTY_DEVELOPMENT
06.02.2017 13:51:46 Traveler: No connection for Third Party Production to gateway.push.apple.com on port 2195 because it is disabled via NTS_PUSH_ENABLE_APNS_THIRD_PARTY_PRODUCTION
06.02.2017 13:51:46 Traveler: -- Certificate Validity Dates (Mon Feb 06 13:51:46 CET 2017) --
06.02.2017 13:51:48 Traveler: D:\Programs\Domino\data\traveler\cfg\PushAPNSAppleToDoProduction.p12 is valid from Wed Jul 13 15:10:31 CEST 2016 to Sat Aug 12 15:10:31 CEST 2017.
06.02.2017 13:51:49 Traveler: D:\Programs\Domino\data\traveler\cfg\PushAPNSAppleVerseCitrixProduction.p12 is valid from Wed Jul 13 15:25:41 CEST 2016 to Sat Aug 12 15:25:41 CEST 2017.
06.02.2017 13:51:50 Traveler: D:\Programs\Domino\data\traveler\cfg\PushAPNSAppleVerseIBMProduction.p12 is valid from Wed Jul 13 15:17:45 CEST 2016 to Sat Aug 12 15:17:45 CEST 2017.
06.02.2017 13:51:50 Traveler: -- APNS-DelQ -- ...
19 Januar 2017 17:59:55Erfahren Sie alles Wichtige aus San Francisco kompakt in der von mir mitorganisierten IBM Connect Comes To You | Westfalen. 
Termin: 23.03.2017 Start / Ende: 13:30 - 18:30 Ort: Bielefeld
Kosten: kostenfrei 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, Watson Workspace, IBM Connections, IBM Notes & Domino, IBM Traveler, Anwendungsmodernisierung und Cloud in kompakter Form 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 14. OpenUserGroup | Westfalen Stammtisches. Ich würde mich auf jeden Fall freuen, Sie am 23.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: hier |
|
