10-15-2009 10:27 AM
10-15-2009 03:45 PM
If definitely sounds like we're mixing up some of the jargon. Let's see if we can clear things up a bit.
There are three main ways to get applications wirelessly to the devices. Software configurations from the BES, using the MDS Integration Service or hosting the installation package on an internal server.
These explanations will be overly simplified so feel free to ask questions and I will answer what I can.
Software configurations are not too bad. They basically involve obtaining a package of COD/ALX files (Try Google Maps for example) which can then be added to a software configuration. The software configuration is then applied to a user and the applications are deployed. In all this, you can apply application control policies that set various permissions on the application (what APIs and data it can access) as well as the disposition (determining whether or not the application is required, optional, or disallowed).
Using the MDS Integration Service (or MDS-IS) you can set up a repository of applications where, using the BlackBerry MDS runtime, users can choose to download and install the applications. I personally don't have too much experience on this side of things. Luckily, we have an entire section of the forums dedicated to it.
Lastly, you also have the option of hosting the app (say, on an internal web server) as a JAD file. This file can then be navigated to by the users and downloaded/installed.
Let's clarify how you are trying to push the app, then we can look into what you are pushing.