Feature and Technical Overview
BlackBerry Enterprise Server for Microsoft Exchange
Version: 4.1 | Service Pack: 6
SWDT305802-456536-0708052501-001
Contents |
|
|
1 |
New in this release............................................................................................................................................................. |
5 |
2 BlackBerry Enterprise Server architecture.................................................................................................................... |
9 |
|
|
Architecture: BlackBerry Enterprise Server............................................................................................................................. |
9 |
|
Architecture: BlackBerry Enterprise Server remote components........................................................................................ |
13 |
3 BlackBerry Enterprise Server components and features............................................................................................ |
17 |
|
|
BlackBerry messaging and collaboration services................................................................................................................. |
17 |
|
BlackBerry Messaging Agent................................................................................................................................................ |
17 |
|
BlackBerry Collaboration Service......................................................................................................................................... |
19 |
|
BlackBerry Synchronization Service..................................................................................................................................... |
22 |
|
BlackBerry Attachment Service............................................................................................................................................. |
23 |
|
BlackBerry MDS........................................................................................................................................................................... |
24 |
|
BlackBerry Applications......................................................................................................................................................... |
26 |
|
Types of BlackBerry Applications.......................................................................................................................................... |
26 |
|
BlackBerry MDS Connection Service................................................................................................................................... |
27 |
|
BlackBerry MDS Integration Service.................................................................................................................................... |
29 |
|
BlackBerry device management................................................................................................................................................ |
30 |
|
Wireless implementation of BlackBerry devices................................................................................................................. |
30 |
|
Centralized maintenance of BlackBerry devices................................................................................................................ |
31 |
|
Controlling third-party applications on BlackBerry devices............................................................................................ |
31 |
|
BlackBerry Enterprise Solution security................................................................................................................................... |
32 |
|
Master encryption keys.......................................................................................................................................................... |
33 |
|
Standard message encryption............................................................................................................................................... |
33 |
|
Options for extending messaging security......................................................................................................................... |
34 |
|
Options for encrypting stored data...................................................................................................................................... |
35 |
|
Controlling BlackBerry device access to the BlackBerry Enterprise Server................................................................... |
36 |
|
Management of BlackBerry device security over the wireless network using IT administration commands........... |
37 |
|
BlackBerry Policy Service........................................................................................................................................................... |
37 |
|
BlackBerry Configuration Panel................................................................................................................................................ |
39 |
4 BlackBerry Enterprise Server process flows.................................................................................................................. |
41 |
|
|
Messaging process flows............................................................................................................................................................ |
41 |
|
Process flow: Sending a message to a BlackBerry device................................................................................................. |
41 |
Process flow: Sending a message from a BlackBerry device............................................................................................ |
42 |
Process flow: Sending a message that contains an attachment from a BlackBerry device........................................ |
42 |
Process flow: Searching an organization's address book on a BlackBerry device........................................................ |
44 |
Instant messaging process flows.............................................................................................................................................. |
45 |
Process flow: Starting an instant messaging session using the BlackBerry Client for use with Microsoft Office |
|
Live Communications Server 2005 (Windows Messenger)............................................................................................... |
45 |
Process flow: Starting an instant messaging session using the BlackBerry Client for use with Microsoft Office |
|
Live Communications Server 2005 (Microsoft Office Communicator)........................................................................... |
46 |
Process flow: Starting an instant messaging session using the BlackBerry Client for use with Microsoft Office |
|
Communications Server 2007............................................................................................................................................... |
48 |
Process flow: Starting an instant messaging session using the BlackBerry Client for IBM Lotus Sametime........... |
49 |
Process flow: Starting an instant messaging session using the BlackBerry Client for Novell GroupWise Messenger |
|
.................................................................................................................................................................................................... |
51 |
Process flow: Sending a file to a contact using the BlackBerry Client for IBM Lotus Sametime................................ |
52 |
Message attachment process flows.......................................................................................................................................... |
53 |
Process flow: Viewing a message attachment.................................................................................................................... |
53 |
Process flow: Viewing an attachment through a link........................................................................................................ |
55 |
Organizer data process flows.................................................................................................................................................... |
55 |
Process flow: Synchronizing organizer data for the first time on a BlackBerry device................................................ |
56 |
Process flow: Synchronizing subsequent changes to organizer data............................................................................. |
57 |
Process flow: Adding a contact picture on a BlackBerry device...................................................................................... |
58 |
Mobile data process flows.......................................................................................................................................................... |
59 |
Process flow: Requesting BlackBerry Browser content on a BlackBerry device............................................................ |
59 |
Process flow: Requesting BlackBerry Browser content while access control is turned on for the BlackBerry MDS |
|
Connection Service................................................................................................................................................................. |
60 |
Process flow: Requesting BlackBerry Browser content with two-factor authentication turned on........................... |
61 |
Process flow: Pushing application content to a BlackBerry device................................................................................. |
62 |
Process flow: Requesting BlackBerry MDS Runtime Applications from a BlackBerry device..................................... |
63 |
BlackBerry device management process flows....................................................................................................................... |
64 |
Process flow: Activating the BlackBerry device over the wireless network................................................................... |
64 |
Process flow: Resending an IT policy to the BlackBerry device manually...................................................................... |
65 |
Process flow: Authenticating the data on a BlackBerry device without connecting to the BlackBerry Infrastructure |
|
.................................................................................................................................................................................................... |
65 |
Process flow: Sending an application to a BlackBerry device over the wireless network............................................ |
66 |
5 |
Glossary................................................................................................................................................................................ |
67 |
6 |
Legal notice.......................................................................................................................................................................... |
71 |
Feature and Technical Overview |
New in this release |
New in this release |
1 |
|
|
|
|
|
Feature |
Description |
|
|
|
|
Rich-content email messages |
BlackBerry® Enterprise Server version 4.1 SP6 supports HTML and rich-content |
|
|
email messages for BlackBerry devices that are running BlackBerry® Device |
|
|
Software version 4.5 or later. By default, this feature is turned on. |
|
|
For more information about the impact of supporting HTML email messages and |
|
|
rich-content email messages on CPU resources, visit www.blackberry.com/go/ |
|
|
serverdocs to see the Impact of supporting HTML and RTF email messages |
|
|
document. |
|
|
The BlackBerry Enterprise Server and its components support HTML email |
|
|
messages in a Japanese environment when the following options are selected in |
|
|
the regional and language settings of the computer: Install files for complex |
|
|
script and right-to-left languages, and Install files for East Asian languages. |
|
Changes to the BlackBerry |
BlackBerry Enterprise Server version 4.1 SP6 contains changes to the BlackBerry |
|
Configuration Database schema |
Configuration Database schema. The changes occur in the upgrade file that is |
|
|
named UpgradeV20080410.sql. |
|
Support for Microsoft® Office |
The BlackBerry Collaboration Service supports Microsoft Office Communications |
|
Communications Server 2007 |
Server 2007. BlackBerry Enterprise Server version 4.1 SP6 supports a new |
|
|
collaboration client for use with this instant messaging server: the BlackBerry® |
|
|
Client for use with Microsoft® Office Communications Server 2007. |
|
Support for IBM® Lotus® Sametime® |
The BlackBerry Collaboration Service supports IBM Lotus Sametime version 8.0. |
|
version 8.0 |
|
|
New names for the BlackBerry |
The collaboration client that was previously named BlackBerry® Instant |
|
collaboration clients |
Messaging for Microsoft® Office Live Communications Server 2005 is now |
|
|
named the BlackBerry® Client for use with Microsoft® Office Live |
|
|
Communications Server 2005. |
|
|
The collaboration client that was previously named BlackBerry® Instant |
|
|
Messaging for IBM® Lotus® Sametime® is now named the BlackBerry® Client |
|
|
for IBM® Lotus® Sametime®. |
|
|
|
5
Feature and Technical Overview |
New in this release |
Feature |
Description |
|
|
|
The collaboration client that was previously named BlackBerry® Instant |
|
Messaging for Novell® GroupWise® Messenger is now named the BlackBerry® |
|
Client for Novell® GroupWise® Messenger. |
Control RIM value-added applications |
You can use new and existing IT policy rules to control RIM value-added |
|
applications. For more information about new IT policy rules, see the Policy |
|
Reference Guide. |
Improved reconciliation of |
BlackBerry Enterprise Server versions 4.1 and later support the reconciliation of |
permanently deleted messages |
permanently deleted messages from Microsoft® Outlook®. If users permanently |
|
delete messages in Microsoft Outlook (using SHIFT+DELETE) or archive |
|
messages in personal folders, the messages are deleted from the users' |
|
BlackBerry devices. BlackBerry Enterprise Server version 4.1 SP6 includes |
|
improvements for the reconciliation of permanently deleted messages. |
|
This feature uses a message state database that is stored in the memory of the |
|
BlackBerry Messaging Agent. The message state database is used to associate |
|
messages on your organization's messaging server with messages on the |
|
BlackBerry devices of users in your organization. In previous releases of the |
|
BlackBerry Enterprise Server, the size of the message state database determined |
|
how many permanently deleted messages could be reconciled for each user. |
|
In BlackBerry Enterprise Server version 4.1 SP6, the BlackBerry Messaging Agent |
|
uses recurring message scans to detect permanently deleted messages on the |
|
messaging server and delete them from the users' BlackBerry devices. The size |
|
of the message state database no longer limits how many permanently deleted |
|
messages the BlackBerry Messaging Agent can reconcile for each user. |
|
By default, on the BlackBerry Enterprise Server, reconciliation for permanently |
|
deleted messages is turned off. You can turn on this feature using the BlackBerry |
|
Manager. |
|
When reconciliation for permanently deleted messages is turned on, the |
|
BlackBerry Messaging Agent uses approximately 64 x N bytes of additional |
|
memory for each user on the computer that hosts the BlackBerry Messaging |
|
Agent, where N represents the number of records in the message state database. |
|
|
6
Feature and Technical Overview |
New in this release |
Feature
New naming conventions for the BlackBerry® Mobile Data System and related software
Description
For example, if an organization's environment has 2000 users and 100 records in the message state database, the computer that hosts the BlackBerry Messaging Agent uses 12.2 MB of additional memory.
The component of the BlackBerry Enterprise Server that was previously named the BlackBerry MDS Services is now named the BlackBerry MDS Integration Service. The term BlackBerry MDS Services now refers collectively to the BlackBerry MDS Integration Service and the BlackBerry MDS Connection Service.
BlackBerry® MDS Studio Applications are now named BlackBerry® MDS Runtime Applications. Java® applications that are developed for and used on BlackBerry devices are now named BlackBerry Java Applications. Browser applications that are developed for and used on BlackBerry devices are now named BlackBerry® Browser Applications. The term BlackBerry Applications refers collectively to BlackBerry MDS Runtime Applications, BlackBerry Java Applications, and BlackBerry Browser Applications.
The BlackBerry Manager UI and the BlackBerry Enterprise Server documentation reflect these new naming conventions.
7
Feature and Technical Overview |
BlackBerry Enterprise Server architecture |
BlackBerry Enterprise Server architecture |
2 |
The BlackBerry® Enterprise Server consists of various components that are designed to perform the following actions:
•provide productivity tools and data from an organization's applications to its BlackBerry device users
•monitor other BlackBerry Enterprise Server components
•process, route, compress, and encrypt data
•communicate with the wireless network
9
Feature and Technical Overview |
Architecture: BlackBerry Enterprise Server |
Component |
Description |
|
|
BlackBerry Attachment Service |
The BlackBerry Attachment Service converts supported message attachments |
|
into a format that users can view on their BlackBerry devices. |
BlackBerry Collaboration Service |
The BlackBerry Collaboration Service provides a connection between your |
|
organization's instant messaging server and the enterprise instant messaging |
|
application on BlackBerry devices. |
|
|
10
Feature and Technical Overview |
Architecture: BlackBerry Enterprise Server |
Component |
Description |
|
|
|
|
BlackBerry Configuration Database |
The BlackBerry Configuration Database is a relational database that contains |
|
|
configuration data that BlackBerry Enterprise Server components use. The |
|
|
BlackBerry Configuration Database includes the following data: |
|
|
• |
details about the connection from the BlackBerry Enterprise Server to the |
|
|
wireless network |
|
• |
user list |
|
• |
address mappings between PINs and email addresses for BlackBerry MDS |
|
|
Connection Service push features |
|
• |
read-only copy of each master encryption key |
BlackBerry Controller |
The BlackBerry Controller monitors the BlackBerry Enterprise Server |
|
|
components and restarts them if they stop responding. |
|
BlackBerry Dispatcher |
The BlackBerry Dispatcher compresses and encrypts all of the data that is sent |
|
|
to and from BlackBerry devices. It sends the data through the BlackBerry Router, |
|
|
to and from the wireless network. |
|
BlackBerry Manager |
The BlackBerry Manager connects to the BlackBerry Configuration Database. |
|
|
You can use the BlackBerry Manager to manage the BlackBerry Domain, |
|
|
including user accounts and device administration. The BlackBerry Domain |
|
|
consists of a single BlackBerry Configuration Database and all the BlackBerry |
|
|
Enterprise Server instances that use it. |
|
BlackBerry MDS Connection Service |
The BlackBerry MDS Connection Service enables users to access web content, |
|
|
the Internet, or your organization's intranet, and also enables applications on |
|
|
BlackBerry devices to connect to your organization's application or content |
|
|
servers for application data and updates. |
|
BlackBerry MDS Integration Service |
The BlackBerry MDS Integration Service provides application-level integration |
|
|
for BlackBerry® MDS Runtime Applications on BlackBerry devices. You can use |
|
|
the BlackBerry MDS Integration Service to install BlackBerry MDS Runtime |
|
|
Applications that are stored in the BlackBerry MDS Application Repository on |
|
|
BlackBerry devices. You can also use it to manage, update, and remove |
|
|
BlackBerry MDS Runtime Applications. |
|
BlackBerry MDS Application |
The BlackBerry MDS Application Repository stores BlackBerry MDS Runtime |
|
Repository |
Applications that your organization's developers can create and publish using |
|
|
the BlackBerry® MDS Studio or the BlackBerry® Plug-in for Microsoft® Visual |
|
|
|
|
11
Feature and Technical Overview |
Architecture: BlackBerry Enterprise Server |
Component |
Description |
|
|
|
Studio® developer tools. You can use the BlackBerry Manager to manage the |
|
BlackBerry MDS Runtime Applications that are stored in the BlackBerry MDS |
|
Application Repository. |
BlackBerry Messaging Agent |
The BlackBerry Messaging Agent connects to your organization's messaging |
|
server to provide messaging services, calendar management, address lookups, |
|
attachment viewing, attachment downloading, and encryption key generation. |
|
The BlackBerry Messaging Agent also acts as a gateway for the BlackBerry |
|
Synchronization Service to access organizer data on the messaging server. The |
|
BlackBerry Messaging Agent synchronizes configuration data between the |
|
BlackBerry Configuration Database and user mailboxes. |
BlackBerry Policy Service |
The BlackBerry Policy Service performs administration services over the wireless |
|
network. It sends IT policies and IT administration commands and provisions |
|
service books. IT policies and IT administration commands define BlackBerry |
|
device security, settings for synchronizing data over the wireless network, and |
|
other configuration settings on BlackBerry devices. The BlackBerry Policy Service |
|
also sends service books to configure feature and component settings on |
|
BlackBerry devices. |
BlackBerry Router |
The BlackBerry Router connects to the wireless network to send data to and from |
|
BlackBerry devices. It also sends data within your organization's network to |
|
BlackBerry devices that are connected to computers with the BlackBerry® Device |
|
Manager. |
BlackBerry Synchronization Service |
The BlackBerry Synchronization Service synchronizes organizer data between |
|
BlackBerry devices and the messaging server over the wireless network. |
organization's application or content |
The organization's application or content server provides push applications and |
server |
intranet content for the BlackBerry MDS Services. |
instant messaging server |
The instant messaging server stores instant messaging accounts. |
messaging server |
The messaging server stores email accounts. |
user's computer with the BlackBerry |
The user's computer with the BlackBerry Device Manager enables users to |
Device Manager |
connect their BlackBerry devices to their computers using a serial or USB |
|
connection. The BlackBerry Enterprise Server and BlackBerry devices use this |
|
connection to send data between them. |
|
|
12
Feature and Technical Overview |
Architecture: BlackBerry Enterprise Server remote components |
Component |
Description |
|
|
|
Data traffic from BlackBerry devices bypasses the wireless network while |
|
BlackBerry devices are connected to users' computers. The BlackBerry Device |
|
Manager connects to the BlackBerry Router, which sends data directly to |
|
BlackBerry devices. |
|
Users can install the BlackBerry Device Manager separately from the |
|
BlackBerry® Desktop Manager or with it as part of the full BlackBerry® Desktop |
|
Software installation. The BlackBerry Device Manager is an optional component, |
|
but it is required to support a bypass connection to the BlackBerry Router. |
|
|
Architecture: BlackBerry Enterprise Server remote components
You can install all BlackBerry® Enterprise Server components on one computer, or you can install certain components on separate computers. Different components impact system resources differently. You can choose to install only one remote component on each computer in your organization's environment.
Sample architecture with a remote BlackBerry Collaboration Service
13
Feature and Technical Overview |
Architecture: BlackBerry Enterprise Server remote components |
Sample architecture with a remote BlackBerry MDS Connection Service
14
Feature and Technical Overview |
Architecture: BlackBerry Enterprise Server remote components |
Sample architecture with a remote BlackBerry MDS Integration Service
Component |
Description |
|
|
BlackBerry Manager |
A remote BlackBerry Manager enables you to manage the BlackBerry Domain |
|
from their computers. |
BlackBerry Attachment Service |
A remote BlackBerry Attachment Service can support multiple BlackBerry |
|
Enterprise Server instances. |
|
The BlackBerry Attachment Service can use increased system resources when it |
|
processes concurrent conversion requests. You can install the BlackBerry |
|
Attachment Service on a remote computer to increase the number of concurrent |
|
conversions without impacting message delivery. |
BlackBerry Collaboration Service |
A remote BlackBerry Collaboration Service can support multiple BlackBerry |
|
Enterprise Server instances. |
|
The BlackBerry Collaboration Service uses a persistent socket connection for |
|
each instant messaging session. You can install the BlackBerry Collaboration |
|
Service on a remote computer to maximize the number of available sockets. |
|
|
15
Feature and Technical Overview |
Architecture: BlackBerry Enterprise Server remote components |
Component |
Description |
|
|
|
You can install only one type of BlackBerry Collaboration Service (for example, |
|
IBM® Lotus® Sametime®), and users can use only one type of enterprise instant |
|
messaging application on their BlackBerry devices. |
BlackBerry MDS Connection Service |
A remote BlackBerry MDS Connection Service can support multiple BlackBerry |
|
Enterprise Server instances. |
|
The BlackBerry MDS Connection Service can use increased system resources |
|
when it processes content requests. You can install the BlackBerry MDS |
|
Connection Service on a remote computer to minimize the impact on message |
|
and data delivery. |
BlackBerry MDS Integration Service |
A remote instance of the BlackBerry MDS Integration Service can support |
|
multiple BlackBerry Enterprise Server instances and one BlackBerry MDS |
|
Application Repository. |
|
The BlackBerry MDS Integration Service can use increased system resources |
|
when processing content requests. You can install a BlackBerry MDS Integration |
|
Service on a remote computer to minimize the impact on message delivery. |
BlackBerry MDS Application |
A remote BlackBerry MDS Application Repository can support one instance of |
Repository |
the BlackBerry MDS Integration Service. You must install the BlackBerry MDS |
|
Application Repository on the same database server as the BlackBerry |
|
Configuration Database. |
BlackBerry Router |
A remote BlackBerry Router can support multiple BlackBerry Enterprise Server |
|
instances. |
|
The BlackBerry Router does not use many system resources, but it is a critical |
|
connection point for the BlackBerry® Enterprise Solution. You can install multiple |
|
standby instances of the BlackBerry Router as failover locations in the event that |
|
the active BlackBerry Router is unavailable. |
BlackBerry Configuration Database |
A remote BlackBerry Configuration Database can support multiple BlackBerry |
|
Enterprise Server instances, which creates a BlackBerry Domain. |
|
|
16
Feature and Technical Overview |
BlackBerry Enterprise Server components and features |
BlackBerry Enterprise Server components and features |
3 |
The BlackBerry® messaging and collaboration services provide a wireless extension of an organization's messaging environment. These services include the BlackBerry Messaging Agent, the BlackBerry Collaboration Service, the BlackBerry Synchronization Service, and the BlackBerry Attachment Service.
BlackBerry Messaging Agent
The BlackBerry® Messaging Agent connects to an organization's messaging server and provides messaging services, calendar management, address lookups, attachment viewing, attachment downloading, and encryption key generation. The BlackBerry Messaging Agent also acts as a gateway for the BlackBerry Synchronization Service to access organizer data on the messaging server. The BlackBerry Messaging Agent synchronizes configuration data between the BlackBerry Configuration Database and user mailboxes.
The BlackBerry Messaging Agent integrates with existing email accounts in your organization. The BlackBerry Messaging Agent redirects messages from users’ email applications to their BlackBerry devices automatically. If users configure identical signatures on their BlackBerry devices and in their email accounts, recipients cannot distinguish between the messages sent from BlackBerry devices and those sent from email applications.
When users move or delete messages or mark messages as read or unread on their BlackBerry devices or in their email applications, the BlackBerry Messaging Agent reconciles these changes over the wireless network between their BlackBerry devices and the email applications. By default, both BlackBerry devices and the BlackBerry® Enterprise Server reconcile email messages over the wireless network.
Wireless messaging features
BlackBerry® device users can use many of the same messaging features that are available in the email applications on their computers.
Feature |
Description |
|
|
email reconciliation |
The BlackBerry® Enterprise Server reconciles the status of messages between |
|
users' BlackBerry devices and their email applications. If users delete, archive, |
|
or move messages to personal folders in their email applications, the messages |
|
are deleted from the message list on the users' BlackBerry devices. If users mark |
|
messages as read or unread in their email applications, the messages appear |
|
with the same status on their BlackBerry devices. |
|
|
17
Feature and Technical Overview |
BlackBerry messaging and collaboration services |
Feature |
Description |
|
|
|
|
|
Administrators can turn off wireless email reconciliation. |
|
email message filters |
Users and BlackBerry Enterprise Server administrators can create and change |
|
|
email message filters. Email message filters determine the actions that the |
|
|
BlackBerry Enterprise Server takes if incoming messages match specific criteria: |
|
|
forward, forward with priority, or do not forward to BlackBerry devices. For |
|
|
example, users can create email message filters to forward messages from |
|
|
specific senders to their BlackBerry devices with high priority. |
|
message forwarding |
Users can turn off message forwarding to their BlackBerry devices, for example, |
|
|
if they are outside of a wireless coverage area. Administrators can also turn off |
|
|
message forwarding to users' BlackBerry devices. |
|
signature |
Users can add a signature to all of the messages that they send from their |
|
|
BlackBerry devices. Administrators can add a signature and disclaimers to all of |
|
|
the messages that the members of a user group send or a specific user sends. |
|
out-of-office reply |
Users can set and change their out-of-office replies using their BlackBerry |
|
|
devices. |
|
contact lookup |
Users can search for a contact’s first name, last name, or both in their |
|
|
organization's directory. The BlackBerry Enterprise Server returns results for up |
|
|
to 20 of the closest matches. |
|
contact list updates |
When users select contacts from the contact lookup results, they can add the |
|
|
contacts to the contact lists on their BlackBerry devices. |
|
custom fields in the contact list |
If your organization maintains custom fields in users’ personal contact lists, you |
|
|
can map these fields to corresponding fields that appear in the contact list on |
|
|
BlackBerry devices. Users can use these custom fields to search for contacts on |
|
|
their BlackBerry devices. |
|
attachments |
Users can send messages that contain attachments from their BlackBerry |
|
|
devices. The BlackBerry Attachment Service does not convert these messages; |
|
|
they are processed by the BlackBerry Messaging Agent only. Attachments must |
|
|
meet the following requirements: |
|
|
• |
If a user sends one attachment in a message, the file size of the attachment |
|
|
cannot exceed 3 MB. |
|
• |
If a user sends multiple attachments in a message, the total file size of the |
|
|
attachments cannot exceed 5 MB. |
|
|
|
18
Feature and Technical Overview |
BlackBerry messaging and collaboration services |
Feature |
Description |
|
|
|
|
|
• |
If an attachment exceeds 64 KB, the BlackBerry device sends the |
|
|
attachment in multiple data packets. |
|
Users can send messages with attachments only from supported BlackBerry |
|
|
devices that run BlackBerry® Device Software version 4.2 or later. If you want to |
|
|
manage the system resources that the BlackBerry Messaging Agent uses to |
|
|
upload and send attachments, you can limit the size of attachments or prevent |
|
|
users from attaching files to messages. For example, if too many users are |
|
|
sending large attachments, such as pictures or video, you might want to limit the |
|
|
size of supported attachments or turn off support for message attachments. |
|
downloading attachments |
Users with BlackBerry Device Software version 4.5 or later can download |
|
|
attachments in any native format to their BlackBerry devices. Users can open |
|
|
and make changes to native file formats using an appropriate third-party |
|
|
application on their BlackBerry devices. Depending on the file format, users |
|
|
might be able to open files using the media application on their BlackBerry |
|
|
devices. |
|
|
To manage network resources in your organization's environment, you can |
|
|
change the maximum file size of attachments that users can download to their |
|
|
BlackBerry devices. |
|
save sent messages |
Users can configure their BlackBerry devices to save copies of messages that |
|
|
they send from their BlackBerry devices in the sent items folder in their email |
|
|
applications. |
|
|
|
|
BlackBerry Collaboration Service
The BlackBerry® Collaboration Service provides a connection between an organization's instant messaging server and the collaboration client on BlackBerry devices. The BlackBerry Collaboration Service integrates with existing instant messaging applications. The BlackBerry® Enterprise Server supports the following collaboration clients:
•BlackBerry® Client for use with Microsoft® Office Live Communications Server 2005
•BlackBerry® Client for use with Microsoft® Office Communications Server 2007
•BlackBerry® Client for IBM® Lotus® Sametime®
•BlackBerry® Client for Novell® GroupWise® Messenger
The BlackBerry Collaboration Service sends messages between the organization's instant messaging server, the BlackBerry Enterprise Server, and BlackBerry devices using public APIs, protocols that are defined by IBM, Microsoft, and Novell, and a Research In Motion proprietary protocol.
19
Feature and Technical Overview |
BlackBerry messaging and collaboration services |
Instant messaging features
Using the collaboration clients on their BlackBerry® devices, users can use many of the same features that are available in the instant messaging applications on their computers.
Feature |
Description |
|
|
session management |
You can specify the number of simultaneous instant messaging sessions that the |
|
BlackBerry Collaboration Service supports. You can also specify a timeout |
|
threshold, after which the BlackBerry Collaboration Service ends inactive |
|
sessions automatically and permits new sessions to start. |
|
You can control whether users of certain versions of the BlackBerry® Client for |
|
IBM® Lotus® Sametime® or the BlackBerry® Client for Novell® GroupWise® |
|
Messenger can see an icon on their BlackBerry devices when contacts in their |
|
contact lists are using the same collaboration clients. By default, the icon |
|
appears. |
conversations with multiple contacts |
Users can start and manage conversations with multiple instant messaging |
|
contacts on their BlackBerry devices. |
availability status |
Users can change their availability status while they are logged in to their |
|
collaboration clients. For example, users can set their availability status to away |
|
or busy. |
presence updates |
Using the latest version of the collaboration clients, users can set their |
|
availability status to display as away if they do not use their BlackBerry devices |
|
for a specified period of time. |
presence level |
Using the latest version of the BlackBerry® Client for use with Microsoft® Office |
|
Communications Server 2007, users can set the presence level of contacts in |
|
their contact lists. Each presence level consists of rules that determine how a |
|
contact can interact with a user through the instant messaging application. For |
|
example, users can assign the Personal presence level to their contacts. |
contact pictures |
Using the latest version of the collaboration clients, users can add pictures to |
|
the contacts in their contact lists. The pictures that users add using the |
|
collaboration clients on their BlackBerry devices are not synchronized with the |
|
instant messaging applications on users' computers. |
|
|
20
Feature and Technical Overview |
BlackBerry messaging and collaboration services |
Feature |
Description |
|
|
synchronized contact lists |
The instant messaging contact lists on users' BlackBerry devices are |
|
synchronized with the contact lists in their organization's instant messaging |
|
application. |
contact alerts |
Users can request alerts when specific contacts become available. |
file transfer |
Using the latest version of the BlackBerry Client for IBM Lotus Sametime, users |
|
can send files to contacts in their contact lists. Recipients can view supported |
|
file formats on their BlackBerry devices. |
link instant messaging contacts to the |
Using the latest version of the collaboration clients, users can link instant |
BlackBerry contact list |
messaging contacts to existing contact list entries on their BlackBerry devices, |
|
or they can create new contact list entries for instant messaging contacts and |
|
populate them with information from their organization's messaging server. |
send email messages from contact list |
Using the latest version of the collaboration clients on their BlackBerry devices, |
|
users can send email messages to contacts directly from their contact lists. |
call contacts |
Using the latest version of the collaboration clients on their BlackBerry devices, |
|
users can call instant messaging contacts directly from their contact lists. After |
|
a user starts an instant messaging conversation with a contact, the user can |
|
make a call to that contact from the conversation window. Phone numbers for |
|
contacts are retrieved from the messaging server or from the BlackBerry contact |
|
list if the user is linked to an existing contact list entry. |
email conversation history |
Using the latest version of the collaboration clients, users who are participating |
|
in an instant messaging conversation can send the history of the conversation |
|
as an email message to the participants of the conversation and to additional |
|
contacts from their BlackBerry contact lists. |
embedded links |
Users can click phone numbers in instant messages to make calls and they can |
|
click links in instant messages to view web pages. |
public groups |
Using the latest version of the BlackBerry Client for IBM Lotus Sametime, users |
|
can add public groups to their instant messaging contact lists. |
location information |
Using the latest version of the BlackBerry Client for IBM Lotus Sametime or the |
|
BlackBerry Client for use with Microsoft Office Communications Server 2007, |
|
users can set their current location to display in their contact information. For |
|
example, users can set their current location to "In the office." This feature is not |
|
available if your organization's environment uses IBM Lotus Sametime version |
|
6.5.1. |
|
|
21