
BlackBerry Mobile Data System 18
Feature Description
administrators can also maintain a list of approved applications on an intranet site
where users can download them wirelessly using the BlackBerry Browser. Upgrades to
core BlackBerry device programs cannot be performed wirelessly.
To install applications wirelessly, application developers must make two files available:
o an application descriptor (.jad) file
o the .jar or compiled .cod files for the application; in the BlackBerry Browser,
the user selects the .jad file to download the application
• Desktop: System administrators can use the standalone BlackBerry Application Loader
to install and provision approved applications for users from a central location. System
administrators can provision multiple BlackBerry devices simultaneously. Users can
also use optional BlackBerry Desktop Software to install applications.
Managing
applications
System administrators can control how each application is implemented and used in the
enterprise through the BlackBerry Manager.
System administrators can control the BlackBerry device and network resources that each
custom application can access, including whether an application can
• store and access persistent storage on the BlackBerry device
• communicate with other applications (interprocess communication)
• open various types of wireless connections behind the corporate firewall, outside the
corporate firewall, or both
These application-specific policies enable system administrators to maintain corporate data
security on the BlackBerry device and on the corporate network.
System administrators can also define globally which applications users are permitted to
install. System administrators can prevent users from using third-party applications that
they have already installed on the BlackBerry device, effectively disabling the applications.
Getting started with BlackBerry MDS
Consider your wireless enterprise requirements, as well as your in-house development expertise, and choose the
appropriate application development approach.
• If you have little in-house development expertise or need to integrate a common system, consider buying a
third-party solution from an independent software vendor (ISV). Many complete solutions provide both the
BlackBerry device client and the server middleware to deploy a wireless application.
• If you need to make web-based content available or you can convert data to a web markup format, consider
using the BlackBerry Browser on the BlackBerry device. By using the browser, you avoid having to do any
custom Java development on the BlackBerry device, and you do not have to provision or manage custom
BlackBerry device applications.
• If the browser approach is insufficient, consider creating a custom Java application or BlackBerry MDS
Studio application. One of these application strategies might be an appropriate choice for several reasons:
• User interface: Your application requires additional functionality for data entry and navigation.
• Data storage: Users require access to data even when they are outside a wireless coverage area.
• Local processing: Some data processing must be performed on the BlackBerry device instead of on the
server.
• Data management: Users need to add or manage data on the BlackBerry device.
• If existing public or private web services offer functionality that you can use, consider creating a BlackBerry
MDS Studio application to make that functionality available on the BlackBerry device.
• Whatever strategy you choose, consider adding push services to your application through the connection
service. Push services are a good choice if most of the data originates on the server, and users need to know
when data is added or changed.
© 2006 Research In Motion Limited. All rights reserved.
www.blackberry.com
Komentarze do niniejszej Instrukcji