For up-to-date product documentation, see the IBM MobileFirst Foundation Developer Center.

Scenario 2: Existing applications using multiple event sources in their application

Applications using multiple event sources requires segmentation of users based on subscriptions.

Client

This maps to tags which segments the users/devices based on topic of interest. To migrate this, this model can be converted to tag-based notification.

1. Initialize the MFPPush client instance in your application and in the success callback register the callback method that should receive the notification.

   MFPPush.initialize(function(successResponse){
   					MFPPush.registerNotificationsCallback(notificationReceived);              					}, 
   					function(failureResponse){
   						alert("Failed to initialize”);
   					}
   		);

2. Implement the notification callback method.

   var notificationReceived = function(message) {
   		    alert(JSON.stringify(message));
   	};

3. Register the mobile device with the push notification service.

   MFPPush.registerDevice(function(successResponse) {
   					alert("Successfully registered");
   				    },
   				  function(failureResponse) {
   					alert("Failed to register");
   				    }
   				);

4. (Optional) Unregister the mobile device from the push notification service.

   MFPPush.unregisterDevice(function(successResponse) {
   					alert("Successfully unregistered");
   				    },
   				  function(failureResponse) {
   					alert("Failed to unregister");
   				    }
   				);

5. Remove WL.Client.Push.isPushSupported() (if used) and use.

   MFPPush.isPushSupported (function(successResponse) {
   					alert(successResponse);
   				    },
   				  function(failureResponse) {
   					alert("Failed to get the push suport status");
   				    }
   				);

6. Remove the following WL.Client.Push APIs since there will be no event source to subscribe to and register notification callbacks.
   1. registerEventSourceCallback()
   2. subscribe()
   3. unsubscribe()
   4. isSubscribed()
   5. onReadyToSubscribe()
7. Subscribe to tags.

   var tags = ['sample-tag1','sample-tag2'] 
          MFPPush.subscribe(tags, function(successResponse) {
   					alert("Successfully subscribed");
   				    },
   				  function(failureResponse) {
   					alert("Failed to subscribe");
   				    }
   				);

8. (Optional) Unsubscribe from tags.

   MFPPush.unsubscribe(tags, function(successResponse) {
   					alert("Successfully unsubscribed");
   				    },
   				  function(failureResponse) {
   					alert("Failed to unsubscribe");
   				    }
   				);

Server

Remove the following WL.Server APIs (if used) in your adapter:

• notifyAllDevices()
• notifyDevice()
• notifyDeviceSubscription()
• createEventSource()

Complete the following steps for every application that was using the same event source:

1. Set up the credentials by using the MobileFirst Operations Console. See Configure push notification settings.

   We can also set up the credentials by using Update GCM settings (PUT) REST API, for Android applications or Update APNs settings (PUT) REST API, for iOS applications.

2. Add the scope push.mobileclient in Scope Elements Mapping.
3. Create tags to enable Push notifications to be sent to subscribers. See Create tags for push notification.
4. We can use either of the following methods to send notifications:
   • The MobileFirst Operations Console. See Sending push notifications to subscribers.
   • The Push Message (POST) REST API with userId/deviceId.

Parent topic: Hybrid applications