RIM BlackBerry Enterprise Server
The BlackBerry Enterprise Solution is a complete wireless platform to extend the benefits of your messaging and collaboration environment and other tools to your mobile professionals. The BlackBerry Enterprise Solution provides push-based access to email, calendar, contacts, tasks, and notes. The product also includes instant messaging, web-based applications, services and enterprise applications.
Known versions
BMC Discovery supports the following versions of the BlackBerry Enterprise Solution:
- 4.1
- 4.0
- 3.6
Software pattern summary
The following table gives an overview of the pattern characteristics:
Product component | OS type | Versioning | Pattern depth |
---|---|---|---|
EnterpriseServer | Windows | Package | Footprint |
BlackBerryRouter | None | ||
BlackBerryDispatcher |
Platforms supported by the pattern
The pattern discovers RIM BlackBerry Enterprise components on the Windows system.
Identification
To run a discovery of the product, the pattern must be triggered. This section describes conditions under which the pattern can be triggered.
Software instance triggers
The following tables give details about the pattern triggers:
EnterpriseServer
Trigger node | Attribute | Condition | Argument |
---|---|---|---|
DiscoveredProcess | cmd | matches | regex'(?i)\bblackberryserver\.exe$' |
or | |||
regex'(?i)\bblackberrycontroller\.exe$' |
BlackBerryRouter
Trigger node | Attribute | Condition | Argument |
---|---|---|---|
DiscoveredProcess | cmd | matches | regex'(?i)\bblackberryrouter\.exe$' |
BlackBerryDispatcher
Trigger node | Attribute | Condition | Argument |
---|---|---|---|
DiscoveredProcess | cmd | matches | regex'(?i)\bblackberrydispatcher\.exe$' |
Simple identification mappings
The following components/processes are identified by using the simple identity mappings that map the product's known processes:
Name | Command |
---|---|
RIM BlackBerry Enterprise Administrator Alert Service | regex'(?i)\bBESAlert\.exe$' |
RIM BlackBerry Enterprise Attachment Service Conversion Monitor | regex'(?i)\bBBAttachServer\.exe$' |
RIM BlackBerry Enterprise Attachment Service File Format Converter | regex'(?i)\bBBConvert\.exe$' |
RIM BlackBerry Enterprise Dispatcher Service | regex'(?i)\bblackberrydispatcher\.exe$' |
RIM BlackBerry Enterprise Server Controller | regex'(?i)\bblackberrycontroller\.exe$' |
RIM BlackBerry Enterprise Agent | regex'(?i)\bblackberryagent\.exe$' |
RIM BlackBerry Enterprise Server | regex'(?i)\bblackberryserver\.exe$' |
RIM BlackBerry Enterprise Mobile Data Service | regex'(?i)\bbmds\.exe$' |
RIM BlackBerry Enterprise Router | regex'(?i)\bblackberryrouter\.exe$' |
RIM BlackBerry Enterprise Sync Server | regex'(?i)\bblackberrysyncserver\.exe$' |
RIM BlackBerry Enterprise Calendar Helper Application | regex'(?i)\bcalhelper\.exe$' |
RIM BlackBerry Enterprise Database Consistency Check | regex'(?i)\bdbconsistency\.exe$' |
RIM BlackBerry Enterprise User Administration Service | regex'(?i)\bbbuseradminservice\.exe$' |
Versioning
The pattern attempts to obtain the version information by using the package querying method.
Package versioning
Foundation executes a search for the installed packages and tries to match them against one of the following regular expressions:
- ^BlackBerry Enterprise Server$
- ^BlackBerry Enterprise Server for
When the pattern finds a match, it extracts the version for RIM BlackBerry Enterprise Server from the package information.
Software pattern model
If the pattern discovers a SoftwareInstance of the BlackBerry Enterprise Solution, it defines its architecture in the form of the application model.
The EnterpriseServer pattern is created with the RIM BlackBerry Enterprise Server (blackberryserver.exe) or RIM BlackBerry Enterprise Server Controller (blackberrycontroller.exe) processes as its trigger process.
The BlackBerryRouter pattern is created with the RIM BlackBerry Enterprise Router (blackberryrouter.exe) process as its trigger process.
The BlackBerryDispatcher pattern is created with the RIM BlackBerry Enterprise Dispatcher Service (blackberrydispatcher.exe) process as its trigger process.
SI depth
All three patterns create a footprint Software Instance whose key is based on type and host.
Relationship creation
This pattern performs a search for all the processes running on the host, and then checks each process's command line against a set of regular expressions as listed below:
- (?i)\bbmds\.exe$
- (?i)\bbbuseradminservice\.exe$
- (?i)\bBESAlert\.exe$
- (?i)\bblackberrysyncserver\.exe$
- (?i)\bBBAttachServer\.exe$
- (?i)\bBBConvert\.exe$
- (?i)\bcalhelper\.exe$
All of the processes that match one of these regular expressions are then associated as a related process to the Software Instance. The pattern performs a search for all of the children processes that are spawned by the bosk_init process, and then relates them to the Software Instance.
Differences from 6.x approach
There are no major differences.