Using debug tokens

You can run an unsigned application on a
BlackBerry
PlayBook tablet by using a debug token. Debug tokens allow you to
separate the process of application creation and publication. You can create
and test an application using a debug token, then deliver the application to a
supervisor or a client for signing and publication.

When you run an unsigned application using a debug token, you can avoid:

Changing the version number
of your application

Accessing the Internet

Exporting a release build of
your application

If you have permission to sign
BlackBerry Tablet
OS applications, you can create a debug token. To request
permission to sign applications, you must complete the web form at
BlackBerry code signing keys. After your request is
approved, 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.

After you receive your CSJ registration files, you can configure your
computer to create debug tokens.

When you create a debug token, you specify the PIN for each tablet on
which the token can be used. You can distribute the debug tokens that you
create to developers who can install them on the specified tablets, or you can
install the debug tokens yourself. You are limited to 100 tablet PINs across
all of your debug tokens that are currently active. If you create debug tokens
that address 100 PINs, you must wait for some of your debug tokens to expire
before you create more.

Debug tokens are valid for 30 days. When a debug token expires, the
BlackBerry Tablet
OS no longer allows unsigned applications that rely on that token
to run.

When a developer is ready to install an unsigned application on a
tablet, they must configure the application to use the same
author and
authorID values that are defined in the debug token.