Client-side apps

You need to be registered to test your client-side push app. Fill out the BlackBerry Push Service Evaluation Form.

When your application is approved, you receive an email that confirms your registration details and provides the following information:

Account Administration Portal

• Portal URL: https://cpadmin.pushapi.eval.blackberry.com/mss/CP_login
• Portal Username: <your email address>
• Portal Password

Server Configuration Details

• Application ID
• Push Password
• Content Provider ID (CPID)
• Account Expiration Date
• Push URL: https://cp<your CPID>.pushapi.eval.blackberry.com

Client Configuration Details

• Application ID
• Push Registration URL: http://cp<your CPID>.pushapi.eval.blackberry.com
• Push Port

The Application ID is the same for your server-side and client-side apps. You can ignore the Push Port because it is not required for BlackBerry 10 push apps.

You can add a plugin from the command line or using the SDK web tool. With either method, the plugin gets copied to your project's plugins folder and the required <feature> element gets added to your app's config.xml file. The next time you build your app, the contents of the plugin are packaged together with your other app resources.

To add the plugins from the command line:

1. Open a command prompt in your app's project folder.
2. Run the following commands:

   webworks plugin add com.blackberry.push
   webworks plugin add com.blackberry.invoked

To add the plugins using the SDK web tool:

1. With your project open in the SDK web tool, in the navigation panel, click Plugins.
2. In the Plugin Name or URL field, type com.blackberry.push and then click Add plugin.
3. Repeat the previous step for the com.blackberry.invoked plugin.

1. Add an entry for the invoke events that your app receives for push messages.

   <!-- config.xml -->
   <!-- Need to put an invoke entry here for push.   
        The ID here must match the invokeTargetId that is passed
        to blackberry.push.PushService.create. 
   -->     
    <rim:invoke-target id="sample.pushreceiver.invoke.push">       
    <type>APPLICATION</type>       
    <filter>        
      <action>bb.action.PUSH</action>
      <mime-type>application/vnd.push</mime-type>       
    </filter>     
    </rim:invoke-target>

   Note the value for the invoke-target id. This value must match the invokeTargetID that's passed into the call to the PushService.create() function. For more information about the invokeTargetID and PushService.create(), see Creating a Push Service object.

   The action tag is set to bb.action.PUSH. This value indicates that the invocation relates specifically to push messages. The event listener in the sample app also uses this value to check that the invoke event is a push message. For more information about the event listener and the push invoke event, see Receiving a push message.

2. To allow your app to be opened from BlackBerry Hub notifications, add the following statements.

   <!-- config.xml -->
   <!-- Have an invoke entry here for when a user taps a
        notification in the BlackBerry Hub. This will cause 
        the app to open. 
   -->   
    <rim:invoke-target id="sample.pushcapture.invoke.open">
    <type>app</type>
    <filter>
      <action>bb.action.OPEN</action>
      <mime-type>text/plain</mime-type>
    </filter>
    </rim:invoke-target>

   The action tag is set to bb.action.OPEN. This value indicates that the invocation relates to an open invoke event. In the sample app, an open invoke event occurs when a user taps a notification for a push message in the BlackBerry Hub. The event listener in the sample app also uses this value to check that the invoke event is an open invoke event. For more information about the event listener and the open invoke event, see Handling notifications in the BlackBerry Hub.