The SMS notification option inside Verse for Android will be removed with Verse release 10.0.4:
So if you use this option try to switch the devices to another notification option.
Tag Archives: traveler
Traveler DB2 DDL Scripts may fail to execute due to malformed copyright header
Last week during the Domino V11 JAM in Vienna an extremely nice friend from IBM Austria told me that the delivered DB2 scripts are buggy.
You can read about the issue and download the correct DB2 scripts here:
IBM Notes Traveler 9.0.1.21 available
Yesterday IBM release the new release of IBM Notes Traveler including the following fixes:
IBM Traveler 9.0.1.21 includes a database schema update for MS SQL Server deployments. It is only necessary to run verifyIndexes.sql to update the schema to latest level. Otherwise no action is required unless upgrading from a version prior to 9.0.1.16. If you use auto schema updates (default behavior) there is no action required.
The upgrade is available on IBM Fix Central.
Performance problems on Apache Reverse Proxy
Yesterday I had massive performance troubles after going online with an Apache Reverse Proxy running on CentOS 6.9 for IBM Notes Traveler.
The customer has about 1.250 users and approx. 1.650 devices.
After some investigation and a great site, where the performance parameters are described very good:
( https://www.linode.com/docs/web-servers/apache-tips-and-tricks/tuning-your-apache-server )
I figured out, that the default configuration of the HTTP server was causing this issues, because the settings are much too low/high for this amount of devices. I did some modifications in the httpd.conf and now it´s working fine – feel free to use them:
#
# Timeout: The number of seconds before receives and sends time out.
#
# Default Value: Timeout 60
New Value: Timeout 10
#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to “Off” to deactivate.
#
# Default Value: KeepAlive Off
New Value: KeepAlive On
#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
# Default Value: MaxKeepAliveRequests 100
New Value: MaxKeepAliveRequests 50
#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
# Default Value: KeepAliveTimeout 15
New Value: KeepAliveTimeout 5
# prefork MPM
# Default Value: StartServers 8
New Value: StartServers 1000
# Default Value: MinSpareServers 5
New Value: MinSpareServers 1000
# Default Value: MaxSpareServers 20
New Value: MaxSpareServers 1000
# Default Value: ServerLimit 500
New Value: ServerLimit 1000
New Value: MaxClients 1000
# Default Value: MaxRequestsPerChild 400
New Value: MaxRequestsPerChild 4000
# worker MPM
# Default Value: StartServers 4
New Value: StartServers 8
# Default Value: MaxClients 500
New Value: MaxClients 1000
# Default Value: MinSpareThreads 25
New Value: MinSpareThreads 100
# Default Value: MaxSpareThreads 75
New Value: MaxSpareThreads 750
New Value: ThreadsPerChild 25
# Default Value: MaxRequestsPerChild 0
New Value: MaxRequestsPerChild 0
# Enabled HTTP Compression
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/xml
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/rss+xml
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/x-javascript
If you also need the configuration flie for the Traveler site with the load balancing configuration, feel free to contact me…
Resolve synchronisation issues after upgrade to IBM Notes Traveler 9.0.1.18
IBM Notes Traveler 9.0.1.18 has the new feature to access the users mail server with the same rights as the user. But if you forget to add the IBM Notes Traveler server to the field “Trusted Servers” in the server document of the Mail Server, you receive the following errors:
An exception occurred when opening database /user.nsf using user shortname CN=John Doe /O=IBM in order to retrieve changed documents. Exception information: Throw: TASK_PROFILE_OPEN_DB
*** Content Adapter Exception *** ERROR 23 (ERR_DATABASE_ERROR) — Debug Info ————: Database cannot be opened with status of 0x17eb. Server=database=mail/user.nsf
INFO Mntr-0a78[Master]John Doe dna.cpp.jniDoesDatabaseExist#8427 Internal Error: Debug Data: Could not open Database=’mail/jdoe.nsf’ on server=’ PathName=” for user ‘CN=John Doe /O=IBM’. Error(17eb)=You are not listed as a trusted server
You can easily get rid of those errors either by:
- disable the new feature by setting the following NOTES.INI entry on the IBM Notes Traveler Server
- NTS_USER_SESSION=false
- Add the IBM Notes Traveler Server to the “Trusted Servers” field of the Mail Server in the second tab “Security”
Moving Android devices from unsecure to secure communication with IBM Notes Traveler
IBM released a very smart way to switch Android devices to HTTPS communication with IBM Notes Traveler servers:
Problem
Your IBM Verse for Android applications connect to your on-premises IBM Traveler server using an unencrypted HTTP connection instead of an encrypted HTTPS connection. Since the IBM Traveler server can use unencrypted HTTP connections immediately without any additional setup, some installations may have skipped the HTTPS setup procedures prior to deploying Verse for Android to users. To ensure that all your communications are encrypted, first enable HTTPS either on your IBM Traveler server or on an edge proxy. Then ensure the IBM Verse for Android app begins using the encrypted connection without requiring any manual intervention from your users.
Resolving the problem
This feature requires the following components at the specified minimum version levels:
· IBM Traveler server, version 9.0.1.15 (or later)
· IBM Verse for Android app, version 9.5.0.0 (or later)
If all the IBM Verse for Android apps have not yet upgraded to the required minimum level prior to the completion of these steps, then it is recommended you keep HTTP port 80 enabled until you can ensure all apps have been upgraded. It is not required that all users upgrade at the same time.
1. Enable your IBM Traveler server to use HTTPS. Typically, this will be the Domino server that hosts your Traveler server, but it could also be an edge proxy. If this is a Domino server, Domino 9.0.1 fp5 or later is recommended. See the following for more information on this task:
Also reference the article Securing connections for IBM Traveler mobile applications for the latest updates on security requirements for IBM Traveler servers and mobile apps.
2. Update the “External Server URL” field on the Traveler server to change the current server URL to start with “https://” instead of “http://”. This can be done either through the current configuration document, by updating notes.ini, or by using the domino console. For more information, see:
3. Before forcing all IBM Verse for Android apps to use the new URL, test the HTTPS connection to ensure that it works properly. The first test is to ensure that the HTTPS port is working properly and routing to the IBM Traveler server. You can use a web browser to easily validate this. Open a browser page, connect to your Traveler Server External URL, and login using an ID. For example, if your Traveler server External URL is https://traveler.example.com/traveler, use a web browser to connect to that page and validate that you do not see any errors.
4. Test the setup with a few devices that are connected to your IBM Traveler server using the HTTP connection. To do this, issue these commands at the domino console:
tell traveler policy setdevice tsExternalURLEnforced=1
tell traveler push flagsadd serviceability configGet
Where and are the device ID and user you are testing.You can obtain the of a user that has previously connected to the Traveler server using the command:
tell traveler show
5. Sync the test devices to ensure that the sync is working properly. From within the Verse for Android app, open Settings > Server and validate that the field called Use Secure Protocol is checked.
NOTE: Ensure that everything syncs normally and shows as secure. If you push an incorrect server URL to the mobile app, the only way to recover is to remove and reinstall the Verse app on the device.
6. After you have verified that the External Server URL is correct and your migrated device can sync, set the IBM Traveler server to enforce this property for all devices by entering the following command into the Domino server console:
set config NTS_EXTERNAL_URL_ENFORCED=true
This command migrates the rest of your IBM Verse for Android apps (that meet the minimum level) to use your secure server URL.
7. Restart the IBM Traveler server to have the settings take effect.
8. Once all your IBM Verse for Android apps have been updated, you can disable the HTTP port on your Domino server, assuming it is not required for other applications that are using the same server.
IBM Notes Traveler is syncing only one time
During this week we found a strange issue regarding a Traveler sync. This would especially be for german speaking colleagues:
If the name of a mail database contains special characters like “ä”, “ö”, “ü” or “ß”, you will be able to do a primesync with your device, but we saw, that no more changes or new mails will be synched to the device.
Our solution:
– Create a replica of the mail database without a special character
– Stop the router task
– Modify the person document
– Modify the settings in the location document of the Notes Client
– Start the router task
– Do a “te traveler security delete device-id username” on the Notes Traveler Server
– Reconfigure the Traveler Client on the device
– Ready
After those steps all synchronisation tasks were working fine. This should be fixed in Traveler 8.5.2, but happened this week with 9.0.1.8
