The AeroGear UnifiedPush Server is a server that allows sending push notifications to different (mobile) platforms. The initial version of the server supports Apple’s APNs, Google Cloud Messaging and Mozilla’s SimplePush.
Besides the server-side offerings, the AeroGear project supports a few platforms regarding push.
The AeroGear Android library has support for device registration with the UnifiedPush Server. In addition it also comes with a handy message listener interface to ease the work of receiving notifications within an Android app.
For iOS there is a little helper library that performs registration of the device against the UnifiedPush Server.
The AeroGear.js library has support for device registration with the UnifiedPush Server. This can be used from Apache Cordova applications or Chrome Packaged Apps as well. Besides that, AeroGear.js comes with a polyfill implementation of Mozilla's SimplePush API, which makes it easy to run SimplePush in any browser, there is no limitation to Firefox OS or the Firefox browsers.
The UnifiedPush Server requires a databases before it is able to run. The following explains how to get going with different databases.
The UnifiedPush Server requires a datasource with java:jboss/datasources/UnifiedPushDS as its JNDI name. You are free to use the Database of your choice (e.g. MariaDB or MySQL). However for your convenience we have a few command line interface scripts which helps to configure a datasource of your choice.
The H2 database is included in the JBoss AS and is pretty easy to install. First start the server:
./standalone.sh
and afterwards issue the following command:
/Path/to/JBossAS/bin/jboss-cli.sh --file=./databases/h2-database-config.cli
The above script will add the UnifiedPushDS datasource, inside of the application server (${jboss.server.data.dir}/unifiedpush).
Another option is to just copy the databases/unifiedpush-h2-ds.xml file into the deployments folder of the application server.
For using MySQL a few more steps are required.
$ mysql -u <user-name>
mysql> create database unifiedpush default character set = "UTF8" default collate = "utf8_general_ci";
mysql> create user 'unifiedpush'@'localhost' identified by 'unifiedpush';
mysql> GRANT SELECT,INSERT,UPDATE,ALTER,DELETE,CREATE,DROP ON unifiedpush.* TO 'unifiedpush'@'localhost';
The module for MySQL can be found in databases/src/main/resources/modules/com/mysql. Copy this module to JBoss AS modules directory:
cp -r databases/src/main/resources/modules/com /Path/to/JBossAS/modules/
We also need the mysql driver copied to this module:
mvn dependency:copy -Dartifact=mysql:mysql-connector-java:5.1.18 -DoutputDirectory=/Path/to/JBossAS/modules/com/mysql/jdbc/main/
Next, start your server:
./standalone.sh
Finally, run the follwing command line interface script:
/Path/to/JBossAS/bin/jboss-cli.sh --file=./databases/mysql-database-config.cli
The above script will add the mysql driver and a datasource.
If you inspect the server console output you should see the following message:
14:41:57,790 INFO [org.jboss.as.connector.subsystems.datasources] (management-handler-thread - 1) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
14:41:57,794 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/datasources/UnifiedPushDS]
For using PostgreSQL a few more steps are required.
$ psql -U <user-name>
psql> create database unifiedpush;
psql> create user unifiedpush with password 'unifiedpush';
psql> GRANT ALL PRIVILEGES ON DATABASE unifiedpush to unifiedpush;
The module for PostgreSQL can be found in databases/src/main/resources/modules/org/postgresql. Copy this module to JBoss AS modules directory:
cp -r databases/src/main/resources/modules/org /Path/to/JBossAS/modules/
We also need the PostgreSQL driver copied to this module:
mvn dependency:copy -Dartifact=org.postgresql:postgresql:9.2-1004-jdbc41 -DoutputDirectory=/Path/to/JBossAS/modules/org/postgresql/main/
Next, start your server:
./standalone.sh
Finally, run the follwing command line interface script:
/Path/to/JBossAS/bin/jboss-cli.sh --file=./databases/postgresql-database-config.cli
The above script will add the postgresql driver and a datasource.
If you inspect the server console output you should see the following message:
14:41:57,790 INFO [org.jboss.as.connector.subsystems.datasources] (management-handler-thread - 1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.2)
14:41:57,794 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/datasources/UnifiedPushDS]
Deploying the server to JBoss AS using the jboss-as-maven-plugin:
mvn package jboss-as:deploy
Note: When testing functionality with the included webapp, it may be necessary to clear the browser's local storage occasionally to get accurate testing results. This is due to the client library storing channel information for later reuse after losing a connection (via refresh, browser close, internet drop, etc.) The functionality to cleanly handle this issue is in development and will be added soon thus removing the need for manual local storage cleanup. Consult your browser's docs for help with removing items from local storage.
Once the server is running access it via http://SERVER:PORT/ag-push. Check the Administration console user guide for more information on using the console.
Besides the Administration console the server can be accessed over RESTful APIs, as explained below.
We highly recommend using the AeroGear UnifiedPush Server via https! Note: The cURL statements below are using SSLv3 (-3)
Temporarily there is a "admin:123" user. On first login, you will need to change the password.
curl -3 -v -b cookies.txt -c cookies.txt
-H "Accept: application/json" -H "Content-type: application/json"
-X POST -d '{"loginName": "admin", "password":"123"}'
https://SERVER:PORT/CONTEXT/rest/auth/login
This will return a status code of 403, then do perform the update:
curl -3 -v -b cookies.txt -c cookies.txt
-H "Accept: application/json" -H "Content-type: application/json"
-X PUT -d '{"loginName": "admin", "password":"123", "newPassword":"SOMENEWPASSWORD"}'
https://SERVER:PORT/CONTEXT/rest/auth/update
To update the initial password, you need to specify the old password and new password (newPassword). Now proceed with a login, by using the new password:
curl -3 -v -b cookies.txt -c cookies.txt
-H "Accept: application/json" -H "Content-type: application/json"
-X POST -d '{"loginName": "admin", "password":"SOMENEWPASSWORD"}'
https://SERVER:PORT/CONTEXT/rest/auth/login
Register a PushApplication, like Mobile HR:
curl -3 -v -b cookies.txt -c cookies.txt -v -H "Accept: application/json" -H "Content-type: application/json"
-X POST
-d '{"name" : "MyApp", "description" : "awesome app" }'
https://SERVER:PORT/CONTEXT/rest/applications
The response returns a pushApplicationID and a masterSecret that will be both used later on when you attempt to send a push message.
Add a PRODUCTION iOS variant (e.g. HR for iOS):
curl -3 -v -b cookies.txt -c cookies.txt
-i -H "Accept: application/json" -H "Content-type: multipart/form-data"
-F "certificate=@/Users/matzew/Desktop/MyProdCert.p12"
-F "passphrase=TopSecret"
-F "production=true" // make sure you have Production certificate and Provisioning Profile
-X POST https://SERVER:PORT/CONTEXT/rest/applications/{pushApplicationID}/iOS
Add a DEVELOPMENT iOS variant (e.g. HR for iOS):
curl -3 -v -b cookies.txt -c cookies.txt
-i -H "Accept: application/json" -H "Content-type: multipart/form-data"
-F "certificate=@/Users/matzew/Desktop/MyTestCert.p12"
-F "passphrase=TopSecret"
-F "production=false" // make sure you have Development certificate and Provisioning Profile
-X POST https://SERVER:PORT/CONTEXT/rest/applications/{pushApplicationID}/iOS
NOTE: The above is a multipart/form-data, since it is required to upload the "Apple Push certificate"!
The response returns a variantID and a secret, that will be both used later on when registering your installation through the iOS client SDK.
Add an android variant (e.g. HR for Android):
curl -3 -v -b cookies.txt -c cookies.txt
-v -H "Accept: application/json" -H "Content-type: application/json"
-X POST
-d '{"googleKey" : "IDDASDASDSA"}'
https://SERVER:PORT/CONTEXT/rest/applications/{pushApplicationID}/android
The response returns a variantID and a secret, that will be both used later on when registering your installation through the Android client SDK.
Add an simplepush variant (e.g. _HR for Browser):
curl -3 -v -b cookies.txt -c cookies.txt
-v -H "Accept: application/json" -H "Content-type: application/json"
-X POST
-d '{"name" : "My SimplePush Variant"}'
https://SERVER:PORT/CONTEXT/rest/applications/{pushApplicationID}/simplePush
The response returns a variantID and a secret, that will be both used later on when registering your installation through the UnifiedPush JS SDK.
Add a chromepackagedapp variant ( e.g. _HR for a Chrome Packaged App )
curl -3 -v -b cookies.txt -c cookies.txt
-v -H "Accept: application/json" -H "Content-type: application/json"
-X POST
-d '{
"clientId" : "CLIENT_ID",
"clientSecret" : "CLIENT_SECRET",
"refreshToken" : "REFRESH_TOKEN"
}'
https://SERVER:PORT/CONTEXT/rest/applications/{pushApplicationID}/chrome
The response returns a variantID and a secret, that will be both used later on when registering your installation through the UnifiedPush JS SDK.
iOS example for performing registration of a client:
- (void)application:(UIApplication*)application
didRegisterForRemoteNotificationsWithDeviceToken:(NSData*)deviceToken
AGDeviceRegistration *registration =
[[AGDeviceRegistration alloc] initWithServerURL:[NSURL URLWithString:@"<# URL of the running AeroGear UnifiedPush Server #>"]];
[registration registerWithClientInfo:^(id<AGClientDeviceInformation> clientInfo) {
[clientInfo setDeviceToken:deviceToken];
[clientInfo setVariantID:@"<Variant Id #>"];
[clientInfo setVariantSecret:@"<Variant Secret>"];
// --optional config--
// set some 'useful' hardware information params
UIDevice *currentDevice = [UIDevice currentDevice];
[clientInfo setOperatingSystem:[currentDevice systemName]];
[clientInfo setOsVersion:[currentDevice systemVersion]];
[clientInfo setDeviceType: [currentDevice model]];
} success:^() {
// successfully registered!
} failure:^(NSError *error) {
NSLog(@"PushEE registration Error: %@", error);
}];Check the iOS client SDK page for more information.
Android example for performing registration of a client:
// collect all 'PushRegistrar' objects:
private final Registrations registrations = new Registrations();
// Create a PushConfig for the UnifiedPush Server:
PushConfig config = new PushConfig(UNIFIED_PUSH_URL, GCM_SENDER_ID);
config.setVariantID(VARIANT_ID);
config.setSecret(SECRET);
config.setAlias(MY_ALIAS);
// create an actual 'PushRegistrar' to register with the UnifiedPush Server:
PushRegistrar registrar = registrations.push("u", config);
// register with the UnifiedPush Server:
registrar.register(getApplicationContext(), new Callback<Void>() {
...
@Override
public void onSuccess(Void ignore) {
// device metadata stored on UnifiedPush Server:
}
@Override
public void onFailure(Exception exception) {
// something went wrong
}
});JavaScript example for performing registration of a client:
//Create the UnifiedPush client object:
var client = AeroGear.UnifiedPushClient(
"myVariantID",
"myVariantSecret",
"http://SERVER:PORT/CONTEXT/rest/registry/device"
);
// assemble the metadata for the registration:
var metadata = {
deviceToken: "theDeviceToken",
alias: "some_username",
category: "email",
simplePushEndpoint: "https://some.server.com/something"
};
// perform the registration against the UnifiedPush server:
client.registerWithPushServer(metadata);JavaScript example for performing registration of a client:
//Create the UnifiedPush client object:
var client = AeroGear.UnifiedPushClient(
"myVariantID",
"myVariantSecret",
"http://SERVER:PORT/CONTEXT/rest/registry/device"
);
// assemble the metadata for the registration:
var metadata = {
deviceToken: "theDeviceToken"
};
// perform the registration against the UnifiedPush server:
client.registerWithPushServer(metadata);To send a message (version) notification, issue the following command:
curl -3 -u "{PushApplicationID}:{MasterSecret}"
-v -H "Accept: application/json" -H "Content-type: application/json"
-X POST
-d '{
"variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e", "444939cd-ae63-4ce1-96a4-de74b77e3737" ....],
"categories" : ["someCategory"],
"alias" : ["user@account.com", "jay@redhat.org", ....],
"deviceType" : ["iPad", "AndroidTablet", "web"],
"message": {"key":"value", "key2":"other value", "alert":"HELLO!"},
"simple-push": "version=123"
}'
https://SERVER:PORT/CONTEXT/rest/sender
For more details take a look at the "message format specification" and the RESTful Sender API.
Documentation for the REST APIs of the AeroGear UnifiedPush Server can be found here.