blackberry sdk 安装

Install the BlackBerry WebWorks SDK

Before you begin:

Download the BlackBerry® WebWorks™ SDK fromhttp://www.blackberry.com/developers/tabletos/webworks. You must also download and extract theAdobe® AIR® SDK from http://www.adobe.com/go/getairsdk.

The Adobe AIR SDK is a .zip archive that you extract to a location on your computer. You will need to remember the location of the Adobe AIR SDK when you install the BlackBerry WebWorks SDK.

1.  In the folder where you downloaded the BlackBerry WebWorks SDK, double-click the installation file.
2. On the Introduction screen, click Next.
3.  On the License Agreement screen, accept or decline the terms of the license agreement and clickNext.
4. On the Choose Install Folder screen, select a location to install the BlackBerry WebWorks SDK and click Next.
5. On the Choose Adobe AIR SDK Install Folder screen, select the location where the Adobe AIRSDK is installed, and click Next.
6. On the Pre-Installation Summary screen, click Install.
7.  When the installation completes, click Done to close the installer.

 

Configure a virtual machine for the BlackBerry Tablet Simulator

Before you begin: Download and install the VMware® Player from www.vmware.com/download/player. Verify that you have 8 GB of available hard disk space or more.

Note: Do not choose the Create a New Virtual Machine option to complete this task.

1.  On the VMware Player Home screen, click Open a Virtual Machine.
2.  On the Open a Virtual Machine screen, navigate to the folder where you installed theBlackBerry® WebWorks™ SDK. The default folder is C:/Program Files/Research In Motion/BlackBerry WebWorks SDK for TabletOS <version>
3.  In the bbwp/blackberry-tablet-sdk/BlackBerryPlayBookSimulator-<version> subfolder, click theBlackBerryPlayBookSimulator.vmx file.
4. Click Open.
5.  After the simulator starts, in the Password field, type playbook.
6. Click OK.

After you finish: You should take a snapshot of the virtual machine so that you can return the virtual machine to a known stable state if necessary. To learn how to take a snapshot, view the online help inVMware Player.

To load applications in the simulator, you must obtain the IP address of the simulator. For more information about obtaining the simulator's IP address, see "Retrieving the IP address of the BlackBerry Tablet Simulator".

 

 

Configure signing for tablet applications

Before you begin: Register with RIM to receive a .csj file, the .csj PIN, and a developer company name. Visit https://www.blackberry.com/SignedKeys and complete the registration form.

After you complete the form, Research In Motion sends an email message containing a .csj file. The .csj file contains a list of signatures and your registration information.

Upgrade Instructions: The following steps are for a first-time setup. However, if you are performing aBlackBerry® Tablet OS SDK upgrade then you need to only perform step 1 -generate sigtool.p12 using the same password as you used before. Alternatively you can make a backup copy of the sigtool.p12 file and restore it to the location of the upgraded SDK after the upgrade. Note that a upgrade will delete thesigtool.p12 file.

1. From the "/bbwp/blackberry-tablet-sdk/bin" folder located in the BlackBerry WebWorks SDKinstallation folder, run the RIM key tool to generate a developer certificate:

   blackberry-keytool -genkeypair -keystore sigtool.p12 -storepass <p12 password> -dname "cn=<company name>" -alias author  

   This produces the sigtool.p12 file in the current directory where <p12 password> is a password you choose and <company name> is the company name sent to you during the signing registration process. Copy or move this file into the bbwp/bin folder of the BlackBerry WebWorks SDK.
2.  From the same "/bbwp/blackberry-tablet-sdk/bin" folder located in the BlackBerry Tablet OS SDKinstallation folder, run the .bar signing tool to set up long term keys for communication with the signing authority server:

   blackberry-signer -csksetup -cskpass <csk password>

   where <csk password> is a password you choose. This produces the barsigner.csk in the C:/Document and Settings/<name>/Local Settings/Application Data/Research In Motion folder (inWindows®) or the ~/Library/Research In Motion folder (in Mac OS).
3. From the same "/bbwp/blackberry-tablet-sdk/bin" folder located in the BlackBerry Tablet OS SDKinstallation folder, run the .bar signing tool to enroll with the signing authority server:

   blackberry-signer -register -csjpin <csj pin> -cskpass <csk password>    <filename.csj>

   where <csj pin> and <filename.csj> are the values sent by email during the signing process.

• Sign the .bar file for a BlackBerry WebWorks application

 

 

 

Running unsigned applications using a debug token

You can run unsigned applications on a BlackBerry® tablet by using a debug token. Debug tokens allow an organization to separate the process of application creation and publication. A developer can create and test an application using a debug token, then deliver the application to their supervisor or their 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

A debug token must be created by an individual or organization that has permission to sign BlackBerry® Tablet OS applications. To request permission to sign applications, complete the web form athttps://www.blackberry.com/SignedKeys. After your request is approved, you receive two CSJ registration files by email. One file allows you to configure your computer 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.

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 you create to developers to install on those tablets, or install them yourself. You are limited to a total of 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 apps that rely on that token to run.

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

Create a debug token from the command line

You can find blackberry-debugtokenrequest in the bin subfolder where you installed the BlackBerry® Tablet OS SDK. The first time you create a debug token on your computer, you must register the CSJ registration file for creating debug tokens. To create a debug token, you must have the CSK password that you specified when you configured your computer to sign applications, and the PIN you typed on the web form to request permission to sign applications.

Before you begin: Configure your computer to sign applications. For more information about configuring your computer to sign applications, see Configure application signing from the command line.

1.  To create a debug token for the first time, register your CSJ registration file for debug tokens and provide the following values for the blackberry-debugtokenrequest tool.

   blackberry-debugtokenrequest -register -cskpass <your csk password>    -csjpin <your CSJ PIN> <path to your CSJ registration file>

2.  Create a debug token for your device. Provide the following values for the command line options:

   Option

   Value

   cskpass

   The password you defined when you configured your computer to sign applications

   keystore

   The developer certificate you created when you configured your computer to sign applications (a file that ends in .p12)

   storepass

   The password you defined when you created your developer certificate

   deviceId

   The PIN of the BlackBerry® tablet on which you want to install this debug token. Prefix each PIN with 0x. For example, if you PIN is 100ABCD, then enter 0x100ABCD as the parameter value.

   For more information about finding the PIN of a tablet, seeRetrieve the PIN of a BlackBerry tablet.

   debug_token_file_name.bar

   The file name of the debug token you want to create. The debug token file must end with .bar. If you specify the name of an existing file, the blackberry-debugtokenrequest tool deletes the file before the tool creates the debug token.

   If you specify a path that does not include a file name, theblackberry-debugtokenrequest tool deletes the directory you specify and does not create a debug token.

   blackberry-debugtokenrequest -cskpass <csk password> -keystore <.p12 file>     -storepass <keystore password> -deviceId 0x<PIN tablet 1>     -deviceId 0x<PIN tablet 2> -deviceId 0x<PIN tablet n> <debug_token_file_name.bar>

You can now distribute or install the debug token you created.

Install a debug token from the command line

Before you begin:

Retrieve the IP address of your BlackBerry® tablet. For more information about retrieving the IP address of your tablet, see Retrieving the IP address of the BlackBerry tablet

1. Open the BlackBerry tablet options. In the upper-right corner of the Home screen on yourBlackBerry tablet, press the gear icon. 
2. In the list of options, press Security.
3. In the list of security options, press Development Mode.
4. Press Upload Debug Token.
5. At a command prompt, enter the following command:

   blackberry-deploy -installDebugToken <path to debug token> -device <IP address of tablet>     -password <tablet password>

The tablet is now ready to accept unsigned applications. For more information about configuring your application for use on a tablet with a debug token, see "Configuring your application for use with a debug token from the command line".

Configure your application for use with a debug token from the command line

The BlackBerry® Tablet OS allows you to run unsigned applications on a BlackBerry® tablet that has a debug token installed. To load an unsigned application you must configure the application's author andauthorId properties match those of specified by the debug token.

1. At the command prompt, type the following and record the information in the Package-Author andPackage-Author-Id fields. You can find the the blackberry-airpackager in the bbwp/blackberry-tablet-sdk/bin folder in yourBlackBerry® WebWorks™ SDK installation.

   blackberry-airpackager -listManifest <path to debug token>

2. In your blackberry-tablet.xml file, create or modify the author and authorId values. Type the information that you recorded from the output of the blackberry-airpackager command in step 1.
3. Save your blackberry-tablet.xml file.

You can now load your application on a tablet without signing it.

Sample blackberry-tablet.xml file

<qnx>    <icon>        <image>my_icon.png</image>    </icon>    <author>My Company</author>    <authorId>gYAAgIqK0RLL5u4I9NanyxBUuCI</authorId>    <category>core.games</category>    <splashscreen>img/spalsh_landscape.jpg:img/splash_portrait.jpg</splashscreen>    <action>use_camera</action>    <action>read_geolocation</action>    <action>play_audio</action>    <buildId>349</buildId>    <platformVersion>1.0.0.0</platformVersion></qnx>