Signing your application
Before you can distribute your application for use on a BlackBerry tablet, you must sign your application. The signing tool included with the BlackBerry Tablet OS SDK 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 can create and install a debug token on the device. For more information about debug tokens, see Using debug tokens.
When you sign an application, you perform the following actions:
- Request permission to sign BlackBerry Tablet OS applications by completing the BlackBerry code signing keys web form. After your request is accepted, you receive two .csj registration files by email. The RDK file allows you to configure your keystore to sign applications and the PBDT file allows you to create debug tokens. Each file arrives in a separate email with information about the purpose of the file attached.
Use the BlackBerry Tablet OS deployment setup wizard. This wizard runs when you create an Adobe ActionScript Mobile Project and guides you through the configuration process to sign your applications or test them on a BlackBerry PlayBook tablet. 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.