Configuring Push Notifications for Mobile

Enable notifications to be sent to mobile users about Connections events.

Before you begin

Important: The following ports must be open on each node in the cluster where the Mobile application is installed:
Android
Port 443 (HTTPS only)
iOS
Ports 2195 and 2196

About this task

The Push Notifications service sends information from the Connections server to a user's mobile device when the following events occur:
  • The user is invited to join a community.
  • The user is invited to join a person's network.
  • A task is assigned to the user.
  • A comment is added to content that the user owns.
  • A synced file is modified on the server and updated on the user's mobile device.

To enable and configure Push Notifications, complete the following steps:

Procedure

  1. Check out the mobile-config.xml file for editing. For more information about checking out the file, see the Changing Mobile configuration property values topic.
  2. Open the mobile-config.xml file in a text editor.
  3. To enable Push Notifications, specify true for the Push enabled property.
  4. Specify values for the remaining Push Notifications properties, based on the requirements of your organization. For more information, see the section about Push Notifications properties in the Mobile configuration properties topic.
  5. Save and check in the mobile-config.xml file.

What to do next

If your deployment uses IBM Tivoli Access Manager, you must add the /mobileAdmin context root to the WebSEAL junction. The Push Notifications log on the Connections server uses mobile administration support for registering devices, and therefore the mobile administration API must be accessible to devices through the WebSEAL junction. The default setting for the context root is /mobileAdmin.