Developing Applications in the BlackBerry Development Environment

To learn more about the BlackBerry JDE, BlackBerry Java plug-in for Eclipse, or RIM BlackBerry APIs, go to the BlackBerry Java application development Web site at http://na.blackberry.com/eng/developers/javaappdev

To enable mobile devices to install applications and securely communicate in the enterprise landscape, there are different ways in which you can onboard your mobile device.

• Initializing an Application
  Before you use any of the other BlackBerry ODP APIs, you have to first initialize an application.
• Manually Registering an Application
  Manually register an application by using the user name and activation code of the application registered through the Sybase Control Center.
• Automatically Registering an Application using SSO2 Cookie
  Registering an application automatically using an SSO2 Token Cookie. This token is fetched from a ticket issuing system and verified by the server.
• Automatically Registering an Application using HTTP Authentication Provider
  Registering an application automatically using the HTTP Authentication Provider.
• Automatically Registering an Application using X.509 Certificate
  Registering an application automatically using an X.509 Certificate. This certificate is fetched from a Certificate Authority and verified by the server.
• Storing the Application Credentials Securely
  Post user registeration, if you want the user credentials to be managed by SDK, you can provide a data vault password to securely store the data.
• Checking for Registered Users
  Check if a device user is registered or not.
• Deleting Users
  Deregister an application user when you do not need the application on the device.
• Enabling Online Push
  To consume push messages, the application registers a listener object.The client SDK notifies this listener object whenever there is a push message from the server. The listener object should implement the ISDMNetListener interface.
• Getting Application End-point
  Retrieve the application end-point that corresponds to the gateway service document.
• Getting Push End-point
  Retrieve the push end-point that corresponds to the delivery address that the application uses in the subscription request for notifications.
• Data Vault API References
  The data vault is a secure storage area provided by the SUP 2.1 SDK client libraries to store sensitive data such as usernames, passwords, authentication certificates within the application. Access to the data vault is protected by two levels of passwords and unique salts.
• Clearing the Server Verification Key
  For a device to switch connection between SUP servers, this API is invoked before registering a new user. This ensures that the server public keys are removed from the SUP client SDK which enables connectivity to the new SUP Server.