Reconciliation rules: BlackBerry Java Applications
Scenario |
Rule |
---|---|
Multiple software configurations are assigned to a user account or the groups the user belongs to. Multiple BlackBerry Java Applications are contained in each software configuration. |
The BlackBerry Java Applications in each software configuration are installed on the BlackBerry device. If the BlackBerry Device Software does not support a specific BlackBerry Java Application, the application is not installed on the BlackBerry device. |
Multiple software configurations that contain different versions of the same BlackBerry Java Application are assigned to a user account or the groups the user belongs to. |
When different versions of an application exist in the software configurations that are assigned to a user account, the latest version of the application that is supported by the BlackBerry Device Software is installed on the BlackBerry device. For example, if a software configuration with version 1.0 of an application is assigned to a user account, and another software configuration with version 2.0 of the application is assigned to a user account, version 2.0 of the application is installed on the BlackBerry device. The version of a BlackBerry Java Application that is in a software configuration that is assigned to a user account takes precedence over the version of a BlackBerry Java Application that is in a software configuration that is assigned to a group. For example, if version 1.0 of an application is in a software configuration that is assigned to a user account, and version 2.0 of an application is in a software configuration that is assigned to a group that the user belongs to, version 1.0 of the application is installed on the BlackBerry device. |
Multiple software configurations that contain the same BlackBerry Java Application are assigned to a user account or the groups the user belongs to. The disposition of the BlackBerry Java Application (required, optional, or disallowed) is different in each software configuration. The deployment method (wired or over the wireless network) for the application is different in each software configuration. |
The disposition specified for an application in a software configuration that is assigned to a user account takes precedence over the disposition of the same application in any software configuration that is assigned to a group. If the application has different dispositions in multiple software configurations that are assigned at the same level (either to the user account or groups), the required disposition takes precedence over the optional disposition, and the optional disposition takes precedence over the disallowed disposition. The BlackBerry Administration Service resolves the deployment method after resolving the disposition of an application. The deployment method specified for an application in a software configuration that is assigned to a user account takes precedence over the deployment method for the same application in any software configuration that is assigned to a group. The wireless setting takes precedence over the wired setting. |
One or more software configurations that include BlackBerry Java Applications are assigned to a user account or the groups the user belongs to, but a limited amount of available memory remains on the BlackBerry device. |
The BlackBerry Administration Service checks the amount of available memory on the BlackBerry device after resolving application conflicts (for example, resolving conflicting disposition and deployment settings) and before installing a BlackBerry Java Application. If there is not enough memory available on the BlackBerry device to support the application, the application is not installed. Depending on the amount of available memory, applications are installed in the following order:
|
A software configuration is assigned to a user account and it contains a BlackBerry Java Application that has a dependency on another BlackBerry Java Application. |
If a BlackBerry Java Application in a software configuration has a dependency on another application, and the other application is not included in a software configuration that is assigned to the user account or a group that the user belongs to, the application is not installed on the BlackBerry device. If a BlackBerry Java Application in a software configuration has a dependency on another application, and the dependent application is included in a software configuration that is assigned to the user account or a group the user belongs to, the dependent application is installed first. If the dependent application is installed successfully, the application with the dependency is then installed. |
A software configuration is assigned to a user account and it contains a BlackBerry Java Application that has a dependency on another BlackBerry Java Application. The dependent application is not supported on the BlackBerry device. |
If a dependent application is not supported by the BlackBerry device or was not installed successfully on the BlackBerry device, the application with the dependency is not installed on the user's BlackBerry device. |
Multiple BlackBerry Java Applications have a circular dependency (for example, application A is dependent on application B, application B is dependent on application C, and application C is dependent on application A) and are included in the same application bundle. The application bundle is added to the application repository. The applications are added to a software configuration and assigned to a user account or a group the user belongs to. |
If multiple BlackBerry Java Applications are included in the same application bundle and have a circular dependency, the applications are not installed on the BlackBerry device. If multiple applications have a circular dependency, they can only be installed if they exist in separate application bundles and are installed using wired deployment. |