Google Cloud Messaging for IBM Traveler for Android clients

IBM Traveler server can use Google Cloud Messaging (GCM) for real time push notifications to keep your Mail, Calendar, Contact and To Do data on your IBM Traveler for Android clients up to date.

Using GCM can greatly improve the battery life of Android devices using IBM Traveler, as IBM Traveler no longer needs to stay constantly connected through HTTP to the IBM Traveler server for push notifications. If you currently use the HTTP option for the Real-time sync type, then the existing IBM Traveler for Android application (version or later) will automatically start using GCM once it detects that the server supports this capability and the device is logged into a Google account.

If you have chosen SMS or periodic sync as your sync type, you can use GCM by selecting Real-time as the sync type, and then choosing GCM as the Real-time option.

The IBM Traveler server will attempt to communicate with the Google Cloud Messaging service using the host on port 443. Make sure that any internal firewalls between the IBM Traveler servers and this external host allow this connection. To verify that this connection is working, connect an IBM Traveler for Android client from a device that is also logged in with a Google account. The IBM Traveler server will not attempt to contact GCM until it has a reason to do so.

On the Traveler server, run the command:
tell traveler push cmstatus
In the output, check for a section that looks similar to this:
Traveler: ########## Connection Notification Sender GCM (Wed Feb 04 06:50:43 EST 2015) ##########
Traveler: Description: Details about the connections to the Google Cloud Messaging (GCM).
Traveler: Connection to Google Cloud Messaging is active

If this connection is not showing active, check your NTSErrors*.log files for connection issues with the host