To deploy applications on a blackberry device a series of steps are required. It involves, configuring your system for app signing, emulator set up, config file positioning and debug token handling.
Following steps describes the complete process in detail:
Step 1 –
The very first need is to configure your computer to sign applications. For this, you need a set a signing key files. To get these keys, you need to fill a form. The link to the form is – bit.ly/U9eD2h
After filling the form, the signing key files are sent to your email address(as mentioned in the form filling process).
You will receive three mails –
- Order confirmation mail
Mail contents: Order Confirmation-Blackberry Tablet Code Signing Key : Order Number 346XX50
It could take up to 2 hours to fully process your order.
- Two mails carrying signing keys files
client-RDK-205XXX2.csj – This is the file that you use to sign your apps and publish to the BlackBerry World storefront
client-PBDT-205XXX1.csj – This file is used to generate a debug token that you can use to test your app on a device.
Note – While filling the form, you need to fill an important field “csj pin”. Make a note of this entry as you will need this while signing your apps. (Your PIN protects against usage of your Code Signing Keys by unauthorized parties, so keep it safe.)
Step 2 –
Next step will be to develop your developer’s certificate. It is done by registering yourself with RIM Signing Authority using your .csj registration file for application signing. The following command will be used –
blackberry-signer -register -csjpin <csj pin> -storepass <KeystorePassword> <client-RDK-xxxxxx.csj file> <client-PBDT-xx.csj file>
In my case, I used the command will following real time entries –
C:\Program Files\Research In Motion\BlackBerry 10 WebWorks SDK 18.104.22.168\dependencies\tools\bin>blackberry-signer -register -csjpin mypin123 -storepass mypin123 “E:\BB Key\client-RDK-2053372.csj” “E:\BB Key\client-PBDT-2053371.csj”
As you can see, I need to move to Blackberry 10 WebWorks SDK folder and later its bin folder.
Also, I need to pass the two .csj file paths to the registration command.
Output of the command –
Info: Developer certificate created in C:\Users\Sumit\AppData\Local\Research In
Info: Successfully registered with server.
Info: Successfully registered with server.
Step 3 –
The next step is to get ready with Ripple extension.
The Ripple emulator is an extension to the Google Chrome browser. It allows you to quickly see how your application looks and functions on multiple mobile devices and platforms, while using BlackBerry WebWorks and PhoneGap APIs in a quick, browser-like environment.
To download Ripple you can use this link bit.ly/ZDncAH
– Download the Ripple emulator and drag and drop it in google chrome’s extensions window.
– Enable the ripple emulator and access your project from chrome.
Step 4 –
The next step is to package your application. You can do it in two ways, using Blackberry 10 webworks sdk or using ripple emulator tool.
I used Ripple Emulator Tool for packaging my application.
Click on ‘Settings…’ button from under Build option in Ripple panel will make following window appear to you. Fill this window with correct enteries and Click on “Package” or “Package and Sign”.
Below figures depicts various settings to be done in ripple for packaging.
In the settings window enter the path to sdk and application. For my application I entered following –
– Sdk Path – C:\Program Files\Research In Motion\BlackBerry 10 WebWorks SDK 22.214.171.124
– App Path – C:\Users\Sumit\Desktop\Demo App\apps\Demo\blackberry10\native\www
– Archive name – Required filled. Give any name here
– O/p folder path – O/p path. Required – e:\Demo Folder\device\ArchDemo.bar
– Sigining pswd – Developers pin
– Target – Set it to device
– IP – BB10 device IP address (Required for launch)
– Device pswd – BB10 device pswd (Required for launch)
Step 5 –
Next step is deploying your application to Blackberry device. To do this, you first need to create a debug token. Then install that debug token into the device. And then deploy and launch your application in the device. Following are the real time commands that I used –
- Create debug token :
C:\Program Files\Research In Motion\BlackBerry 10 WebWorks SDK 126.96.36.199\dependencies\tools\bin>”c:\Program Files\\Research In Motion\BlackBerry 10 WebWorks SDK 188.8.131.52\dependencies\tools\bin\blackberry-debugtokenrequest” -storepass mypin123 -devicepin 1AC1C1F1 e:\DemoFolder\device\debTokFN.bar
Info: Debug token created.
- Install debug token :
C:\Program Files\Research In Motion\BlackBerry 10 WebWorks SDK 184.108.40.206\dependencies\tools\bin>blackberry-deploy -installDebugToken e:\DemoFolder\device\debTokFN.bar -device 172.16.1.177 -password password
Info: Sending request: Install Debug Token
Info: Action: Install Debug Token
Info: File size: 2349
Package your application with this debug token – generalized command for Windows OS –
bbwp C:\myapp\myarchive.zip -d -o C:\myapp\output
- Install and launch application :
C:\Program Files\Research In Motion\BlackBerry 10 WebWorks SDK 220.127.116.11\dependencies\tools\bin>blackberry-deploy -installApp -launchApp -password devpswd -device 1X2.XX.1.XXX -package e:\Demo Folder\device\ ArchDemo.bar
Info: Sending request: Install and Launch
Info: Action: Install and Launch
Info: File size: 3051133
Info: Installing Demo.gYABgNHJ_-bPRo1CrtbHMSkEmng…
Info: Processing 3051133 bytes
Info: Progress 35%…
Info: Progress 65%…
Info: Progress 90%…
Info: Progress 100%…
Note :- Debug tokens are valid for 30 days only. If you use an expired debug token, the BlackBerry 10 OS will not allow that application to install.