Before you can distribute your application for use on a BlackBerry PlayBook tablet, you must sign it. The signing tool included with the BlackBerry Native SDK for Tablet OS adds cryptographic hash values to your application package (.bar file) during the signing process. The hash files help verify the authorship of your application to users and the BlackBerry Tablet OS.
If you want to test your application on a device without signing it, you must create and install a debug token on the device. For more information about debug tokens, see Configure your environment for development and deployment in the Getting Started Guide, and Create a debug token from the command line.
The following steps describe the application signing process. There are two phases in the signing process. In the first phase, you configure your computer to sign applications. You should need to configure your computer only once. To configure your computer:
- Request permission to sign BlackBerry Tablet OS applications by completing the web form at http://developer.blackberry.com/native/signingkey . After your application is accepted, you receive two CSJ registration files by email. One file allows you to configure your keystore to sign applications; the other file allows you to create debug tokens. Each file arrives in a separate email with information about the purpose of the file attached.
- Complete the BlackBerry Tablet OS deployment setup wizard. This wizard runs when you create a new project for your application, and guides you through the configuration process to sign your applications or test them on a device. If necessary, you can manually configure your environment for application signing.
- Sign your application by requesting a .bar file signature from the RIM Signing Authority. You must increment the version number of your application each time you sign it.
After you sign your application, you can publish it to the BlackBerry App World storefront.