While the BlackBerry platform is relatively easily deployed, enterprises with more stringent security concerns or those required to meet recent regulations such as Sarbanes-Oxeley must take steps to assure their BlackBerry implementation is consistent with these needs.
Research In Motion provides a comprehensive set of IT policies to control the general aspects of the device. However, the BlackBerry is increasingly being used as a platform to solve business problems. As such, companies are deploying both third-party and internally developed applications to their BlackBerry devices. This hack will discuss the application of IT policies in custom applications.
There are two primary use cases for IT policies in BlackBerry solutions:
Provide configuration data, which can change in the future, to all devices in the enterprise.
Hide application complexity from users.
Many wireless applications depend on server resources. These server resources may be specified by a DNS name, URL, or IP address. How does a BlackBerry administrator or BlackBerry application designer allow configuration data such as this to be easily deployed to all devices and for this data to be updated? It would be possible to include a configuration file in the deployment of an application that contains important metadata. However, what happens six months later when this data must change? IT policies provide a simple way for the BES administrator to update configuration ...