Push Notifications push-notifications

Register with Amazon SNS

1. Record your Account Id. The format should be 12 digits with no spaces or dashes, that is, “123456789012”.
2. Ensure you are in the “us-east” or “eu” region, as a later step (Identity Pool Creation) requires one of those.
3. After registering, log in to the management console and select SNS (Push Notification Service). Click “Get Started” if it appears.

Create Access Key and ID

1. Click your login name on the upper right of the screen, and choose Security Credentials from the menu.
2. Click Access Keys, and in the space below, click Create New Access Key.
3. Click Show Access Key, and copy and save the Access Key ID and Secret Access Key shown. If you choose the option to download the keys, you get a csv file that contains those same values.
4. Other security-related certificates, and some other, can be managed on this page.

For organizations, which use an “AWS Sandbox” account, the steps are similar, and outlined here:

1. Click your login name on the upper right of the screen, and choose My Security Credentials from the menu.
2. Click Users in the left list of actions, and choose your user name.
3. Click the Security credentials tab.
4. From here, you see your keys and create new keys. Save the keys for later use.

Create a Topic

1. Click Create Topic and choose a topic name. Record all fields such as Topic ARN, Topic Owner, Region, Display name.
2. Click Other Topic Actions > Edit Topic Policy. Under Allow these users to subscribe to this topic, select Everyone.
3. Click Update Policy.

Create Platform Applications

1. Click Applications, then Create Platform Application. Choose a name and select a platform (APNS for iOS, GCM for Android™). Depending on the platform. other fields must be filled in:

   1. For APNS, a P12 file, a Password, a Certificate, and a Private Key must all be entered. These should have been obtained in the step Using the Apple Push Notification Service (APNS) above.
   2. For GCM, an API Key must be entered. This should have been obtained in the step Using the Google Cloud Messaging (GCM) service above.

2. Repeat the above step once for each platform that you are supporting. To be able to push to both iOS and Android™, two Platform Applications must be created.

Create an Identity Pool

1. Use Cognito to create an Identity Pool, which will store basic data of unauthenticated users. Note, only “us-east” and “eu” regions are supported by Amazon Cognito currently.
2. Give it a name, and check the box for “Enable access to unauthenticated identities”.
3. On the next page (“Your Cognito identities require access to your resources”) click Allow.
4. On the upper right of the page, click the link "Edit identity pool". The Identity Pool Id is shown. Save this text for later.
5. On the same page, choose the drop-down next to “Unauthenticated role” and ensure it has the role Cognito_<pool name>UnauthRole selected. Save your changes.

Configure Access

1. Log in to Identity and Access Management (IAM).
2. Select Roles.
3. Click the role created in the previous step, called Cognito_<yourIdentityPoolName>Unauth_Role. Record the “Role ARN” displayed.
4. Open “Inline Policies” if it is not already opened. You should see a policy there with a name like oneClick_Cognito_<yourIdentityPoolName>Unauth_Role_1234567890123.
5. Click “Edit Policy”. Replace the contents of the Policy Document with this snippet of JSON:

1. Click Apply Policy.

Register with Pushwoosh

1. Go to pushwoosh.com and create an account.

Create an API Access Token

1. On the Pushwoosh site, go to the API Access menu item to generate an API Access Token. Securely record this token.

Create an app

1. For Android™ support, you must provide your GCM API key.
2. When configuring the app, choose Cordova as the framework.
3. For iOS support you must provide the Certificate file (.cer), Push Certificate (.p12) and private key password; these should have been obtained from Apple’s APNS site. For Framework, choose Cordova.
4. Pushwoosh will generate an App Id for that app, in the form “XXXXX-XXXXX”, where each X is a hexadecimal value (0 through F).

PhoneGap Build is a service offered by PhoneGap that will build your app for you on their servers, and let you download it to your device directly. See PhoneGap Build documentation at https://build.phonegap.com/ to learn how to set up and use PhoneGap Build.

PhoneGap Command Line Interface (CLI) lets you use a rich set of PhoneGap commands on your command line to build, debug, and deploy your app. Refer to the PhoneGap developer documentation (https://docs.phonegap.com/en/edge/guide_cli_index.md.html#The%20Command-Line%20Interface) to learn how to set up and use PhoneGap CLI.

Create a notification

• In your AEM Mobile app’s dashboard, find the Push Notifications tile.
• In the menu on the upper right, choose “Create”. This button is not available until the cloud config is first set.
• In the Create Notification Wizard, enter in a title and a message, then click the “Create” button. Your notification is now ready to send immediately or later. It can be edited and the message and/or title can be changed and saved.

Send the notification

• In the Apps dashboard, find the Push Notifications tile.
• Select the notification, or click the details button on the bottom right (. . .), to show the list of notifications. This list also indicates if a notification is ready to be sent, has already been sent, or if an error occurred during sending.
• Select the checkbox for one notification (only) and click the “Send Notification” button above the list. You have one chance to “Cancel” or “Send” the notification on the dialog that appears.

Dealing with the results

• If the push notification service (Amazon SNS or Pushwoosh) receives the Send request, confirms it as valid, and sends it to the native providers (APNS and GCM) successfully, the Send dialog box closes with no message. In the notification list, the status of that notification is listed as Sent.

• If the push send fails, the dialog box shows a message indicating the problem. In the notification list, the status of that notification is listed as Error, but if the problem is rectified, the notification can be sent again. If there is an error, additional error information should appear in the server error log.

• Note that there are some platform differences between iOS and Android™ push notifications. Among them:

  • Building with CLI will start the app after it is deployed on Android™. On iOS, you have to start it manually. Because the push registration step happens at startup, Android™ apps can receive push notifications right away (because it has already started and registered), while iOS apps cannot.
  • On Android™, the OK button text is in all caps (and in any other buttons added on the in-app notification), while in iOS it is not.

Click the edit on the top-right corner of the Manage Cloud Services tile.

Select the Pushwoosh Connection. Click Next.

Enter the details of the properties and click Submit.

One you submit your configuration, the Push Notifications tile displays in the dashboard.

Click the add symbol on the top-right corner of the Push Notifications tile to open the Create Notification Wizard.

Clicking the browse icon in the link path, presents the user with the content structure of the app.

Once you select the path, click the check icon.

Enter the Text Details in the Create Notification Wizard and click Create.

Open the details by clicking the push notification that you created from the Push Notifications tile.

You can edit properties, send notifications, or delete the notification.