Admin Tips: The New Jobs Feature and ID Enterprise Activation Issues
This month we have two informative admin tips. The first explains why you should use the new Jobs feature introduced in BlackBerry® Enterprise Server v5.0. The second tip explains how to identify and troubleshoot enterprise activation issues.
TIP 1: A JOB WELL DONE: WHY USE THE NEW JOBS FEATURE
When there are several requests being made of the BlackBerry Enterprise Server, you'll appreciate the work the new Jobs feature does to keep everything running smoothly. Jobs were introduced in BlackBerry Enterprise Server v5.0 and are an important feature of the BlackBerry® Administration Service.
As the new interface is a web-based system, there needed to be a way to manage simultaneous requests. This is where Jobs come in to play. Jobs are a grouping of commands that need to be executed. When an administrator issues a command it is sent to the BlackBerry Administration Service where it is grouped with other commands that also need to be executed. If the command has already been issued from another administrator it is either ignored or updated depending on the situation.
The following commands will use the job scheduler:
- IT Policy
- Applications Push
- Native application settings
Why use jobs?
By default, jobs are only executed every 15 minutes. That means that any device-side distributions may take up to 15 minutes before they are sent to the device. This can lead to people thinking something is wrong when it is not.
Application Push/Settings, OTASL, and IT Policy all fall under this category; however the following commands are still executed immediately and do not use the Job system:
- Resend Service Books
- Resend IT Policy
In order to not overwhelm the SQL server and other BlackBerry services there needs to be a controlled method in place to manage the jobs. This is done by Throttling and Scheduling, terms that go hand-in-hand with Jobs. Many administrators will know these terms from the BlackBerry Enterprise Server v4.1 days, so we'll start there in explaining Throttling and Scheduling and share what you can do with these features now thanks to the BlackBerry Administration Service.
- Throttling is a way to help control the amount of work to do on the system. BlackBerry Administration Service lets you control the throttle from the system and individual Job level. From the system level you can control the maximum amount of tasks that can be performed at any given time. You can also get more granular and control it from the individual job level itself.
- Scheduling takes place before the Job is even created, based on your schedule settings, provided reconciliation takes place. During the reconciliation, the BlackBerry Administration Service will also look for other tasks already queued for work—and make sure the latest settings are always the ones being applied. This is done to avoid changes being applied in the wrong order. Once the specified scheduling conditions have been met a job will be created. From the BlackBerry Administration Service interface it is also possible to manage the jobs directly, which allows you to modify or change their schedule. You can change the schedule to run based on your organizational needs.
See the increased level of control administrators now have when using Throttling and Scheduling?
TIP 2: IDENTIFYING AND TROUBLESHOOTING ENTERPRISE ACTIVATION ISSUES
Here is an excellent troubleshooting guide if you are getting errors during the enterprise activation process: