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

Scenario 3: Existing applications using broadcast/Unicast notification in their application


  1. Initialize the MFPPush client instance in your application:

    [[MFPPush sharedInstance] initialize];

  2. Implement the notification processing in the didReceiveRemoteNotification().
  3. Register the mobile device with the push notification service:

    [[MFPPush sharedInstance] registerDevice:^(WLResponse *response, NSError *error) { if(error){ NSLog(@"Failed to register"); }else{ NSLog(@"Successfullyregistered"); } }];

  4. (Optional) Un-register the mobile device from the push notification service.

    [MFPPush sharedInstance] unregisterDevice:^(WLResponse *response, NSError *error) { if(error){ NSLog(@"Failed to unregister"); }else{ NSLog(@"Successfully unregistered"); } }];

  5. Remove WLClient.Push.isPushSupported() (if used) and use:

    [[MFPPush sharedInstance] isPushSupported]

  6. Remove the following WLClient.Push API's:

    • registerEventSourceCallback()
    • WLOnReadyToSubscribeListener Implementation


Remove WL.Server.sendMessage (if used) in your adapter.

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 Configuring 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 Creating tags for push notification.
  4. We can use either of the following methods to send notifications:

Parent topic: Native iOS applications