Using the Push Notifications Service

Red Hat Managed Integration 2

For Red Hat Managed Integration 2

Red Hat Customer Content Services


This document provides instructions for using the Push Notifications service, Red Hat Managed Integration 2.


The Push Notifications service allows you to send native push notifications to different mobile operating systems.

  • Code once and push notifications to iOS and Android.
  • Push notifications to either iOS only or Android only.
  • Push notifications to different variants of a mobile app.

The service supports:

The Push Notifications service offers a unified Notification Service API to the above mentioned Push Network Services. It can be seen as a broker that distributes push messages to different 3rd party Push Networks.

  • The payload of the push notification is delivered to 3rd party Push Network providers, Google or Apple. AeroGear recommends that users do not send any sensitive personal or confidential information (for example, a social security number, financial account or transactional information) as part of any Push Notification. Users of push notifications should not have an expectation of secure transmission.
  • For analytic purposes, the service stores the content of the alert key sent to the UnifiedPush Server. The content of the alert key belongs to the metadata, which is deleted after 30 days, using a nightly job within the UnifiedPush Server.
  • You are only able to send push notifications to a real device, sending push notifications to an emulator fails.
  • Push is a signaling mechanism and is not suitable to be used as a data carrying system, for example, a chat application.

Chapter 1. Push Notifications Terminology

This section describes terminology that is associated with Push Notifications.

Push Application
A logical construct that represents an Mobile App, for example, Mobile HR.
Push Notification Message
A simple message to be sent to a Push Application.
Sender Endpoint API
A RESTful API that receives Push Notification Message requests for a PushApplication or some of its different Variants. The Server translates this request into the platform specific details and delivers the payload to the 3rd party cloud providers, which eventually might deliver the message to the physical device.
A variant of the Push Application, representing a specific mobile platform, like iOS or Android, or even more fine-grained differentiation like iPad or iPhone. There can be multiple variants for a single Push Application (for example, Mobile HR Android, Mobile HR iPad, Mobile HR iOS free or _Mobile HR iOS premium). Each supported variant type contains some platform specific properties, such as a Google API key (Android) or passphrase and certificate (Apple).
Apple Push Notification service.
Represents an actual device, registered with the UnifiedPush Server. User1 running HR Android app, while User2 runs HR iPhone premium on his phone.
Administrative User Interface
(AUI) The Unified Push Admin UI Web UI that allows you manage Push Applications and Variants, view statistics and send Push Notifications to devices.

Chapter 2. Setting Up the Push Notifications Mobile Service

2.1. Obtaining Firebase Cloud Messaging Credentials

This procedure describes how to obtain Firebase Cloud Messaging Credentials.


Before the Android application is able to receive the notifications, you must set up access to Firebase Cloud Messaging. The following credentials are necessary to set up Firebase Cloud Messaging for your app:

  • Server key
  • Sender ID
  • google-services.json file containing the credentials required to connect your app to Firebase and Google services.


  1. From the Project Settings screen, switch to the Cloud Messaging tab, where you can find the Server key and Sender ID (known in GCM as Project Number). There is also a Legacy server key but it should not be used for new projects.
  2. Download the google-services.json file as described in the Google Documentation.

2.2. Obtaining Apple Push Notification Service Credentials

This procedure describes how to enable Push Notifications for your iOS application and get the credentials required for push from Apple.


  1. Follow the official Apple guide to enable push notifications for your Xcode project.
  2. Follow the official Apple guide to generate an APNs client TLS certificate and export the client TLS identity from your Mac.


    Make sure to protect the p12 file with a password.

2.3. Creating a variant

This procedure describes how to register your app on the UnifiedPush Server


  1. Log into the Solution Explorer.
  2. Click Open Console beside Push Notification Service.
  3. If push applications already exist, they are displayed, click "Create Application" to navigate to the Welcome page. If no push applications exist, the Welcome page is displayed.
  4. Click Start Here to dismiss the Welcome Page and go to the Create Application screen
  5. Enter a name for your application and click Create App to go to the Variant screen
  6. Click Add a Variant
  7. Enter a name for your variant and select the platform that you intend to target
  8. Enter the Push Network details necessary for your push network and click Create
  9. Copy each of the various code snippets into its corresponding file in your application
  10. Build and deploy your app
  11. Click the Skip the wizard link to finish.

2.4. Setting up the Push Notifications Service SDK

This section helps you to set up the Push Notifications service SDK in your App. It describes how to set up and initialize the Push Notifications service SDK.

A Firebase account.
An APNs service.


  1. Import the libraries
  2. Install cordova-plugin-aerogear-push:

    $ cordova plugin add @aerogear/cordova-plugin-aerogear-push
  3. Install the Unified Push Server package needed for device registration:

    $ npm install --save @aerogear/push

Chapter 3. Registering device on Push Notifications Service

To receive native push notifications from a Push Network, for example APNs or FCM, the mobile device is identified with a unique device-token assigned by that Push Network. This device-token is passed, by the operating system, to the mobile application. Refer to the operating system and Push Network documentation for further details.

Every time a user launches a mobile app, that app receives the device-token, from a platform-specific method (or callback). Since the Push Network may assign a new token to a device, AeroGear recommends that the app registers the device-token with the UnifiedPush Server each time.

The required metadata for an Installation:

  • deviceToken: _Identifies the device/user-agent within its Push Network.
  • variantID: The ID of the variant, where the client belongs to
  • variantSecret: Password of the actual variant

The AeroGear UnifiedPush Server is able to store some user-specific metadata as well:

  • deviceType: The device type of the device or the user agent.
  • operatingSystem: The name of the underlying Operating System.
  • osVersion: The version of the used Operating System.
  • alias: Application specific alias to identify users with the system. For instance an email address or a username.
  • categories: Used to apply one or more "tags".

The device-token needs to be registered with the UnifiedPush Server, to indicate there is a new Installation for a Variant. This registration is performed by calling an endpoint of the server.

import { PushRegistration } from "@aerogear/push";

new PushRegistration(app.config).register().then(() => {
    // Registration with UPS successful, you can now send push notifications from the UPS UI
}).catch(err => {
    // Error on device registration

Optionally, you can pass the parameters below to the register method

  alias: 'some-alias',
  categories: ['one', 'or', 'more', 'categories'],
  timeout: 5000 // in milliseconds

Chapter 4. Sending a Push Notification using the Unified Push Admin UI

The Unified Push Admin UI allows you to send Push Notifications.


  • Make sure the Push Notifications service is provisioned.
  • Select a route in OpenShift.
  • Login with your OpenShift credentials.

On first login you need to provide the OpenShift OAuth service permissions to read your user account.

Admin UI
  1. Open the Unified Push Admin UI in a browser.
  2. Select the target application from the home page and click Send Notification To This App.

    Send a Push
  3. When the Send Push dialog displays, enter text in the Message form.

    Enter the payload
  4. Click Send Push Notification to send the message to the target application.
Java API
  1. Add unifiedpush-java-client as a dependency to your project.

  2. Send the message to the target application.

    final PushSender sender = DefaultPushSender
            .withRootServerURL("<pushServerURL e.g http(s)//host:port/context>")
            .pushApplicationId("<pushApplicationId e.g. 1234456-234320>")
            .masterSecret("<masterSecret e.g. 1234456-234320>")
    final UnifiedMessage unifiedMessage = UnifiedMessage
            .alert("Hello from Java Sender API!")
    sender.send(unifiedMessage, () -> {
        //do cool stuff
Node.js API
  1. Add unifiedpush-node-sender as a dependency to your project.

    npm i unifiedpush-node-sender
  2. Send the message to the target application.

    const agSender = require('unifiedpush-node-sender');
    const settings = {
      url: "<pushServerURL e.g http(s)//host:port/context>",
      applicationId: "<pushApplicationId e.g. 1234456-234320>",
      masterSecret: "<masterSecret e.g. 1234456-234320>"
    const message = {
      alert: "Hello from the Node.js Sender API!"
    const options = {
      config: {
        ttl: 3600
    agSender(settings).then((client) => {
      client.sender.send(message, options).then((response) => {
        console.log('success', response);
      }).catch((error) => {
        console.log('error', error);
  1. Send the message to the target application.

    curl -u "<pushApplicationId>:<masterSecret>"  \
       -v -H "Accept: application/json" -H "Content-type: application/json"  \
       -X POST  -d \
         "message": {
          "alert": "Hello from the curl HTTP Sender!",
          "sound": "default"
       }'  \

The 3rd party Push Network is responsible for delivering the Push Notification to the target application.

Chapter 5. Handling Incoming Push Notifications

This section describes how to handle incoming push notifications in your foregrounded application.


Push notifications that arrive when the application is in the background are always handled by the OS.


  1. Add the following code to your app:

    import { PushRegistration } from "@aerogear/push";
    PushRegistration.onMessageReceived((notification: any) => {
      console.log('Received a push notification', notification);
  2. Build and run your app.

Legal Notice

Copyright © 2020 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.