4. The BlackBerry Collaboration Service checks the BlackBerry Configuration Database to find out if the maximum number
of sessions has been reached, and performs one of the following actions:
• If the maximum number of sessions has been reached and a timeout limit is set, the BlackBerry Collaboration
Service logs out any instant messaging sessions on BlackBerry devices that are out of coverage, and any instant
messaging sessions that are no longer sending status messages to the BlackBerry Collaboration Service.
• If there are no idle sessions, the BlackBerry Collaboration Service sends a "Server Busy" status message to the
BlackBerry device and rejects the login request.
• If the maximum number of sessions is not set and the number of sessions equals the total number that the HTTP
persistent connection supports, the BlackBerry Collaboration Service sends a "Failed" status message to the
BlackBerry device and rejects the login request.
5. The BlackBerry Collaboration Service checks the BlackBerry Configuration Database to verify that the user has
permission to use the collaboration client, and tries to authenticate the user using Integrated Windows® Authentication;
if the authentication is not successful, the BlackBerry Collaboration Service tries a forms-based login process instead.
The BlackBerry Collaboration Service sends a login request in JSON, a lightweight data-interchange format, to the
Microsoft® Office Communicator Web Access server.
The BlackBerry Collaboration Service opens the connection using HTTPS over port 443. The administrator can also
configure the connection to use HTTP, the transport protocol that the AJAX service uses, or a custom port number.
6. The Microsoft Office Communicator Web Access server formats the request using a Microsoft API and sends the request
to the Microsoft® Office Live Communications Server over an MTLS connection.
7. The Microsoft Office Live Communications Server accepts the request, processes the login information, and sends the
acceptance to the Microsoft Office Communicator Web Access server.
8. The Microsoft Office Communicator Web Access server sends the acceptance to the BlackBerry Collaboration Service.
9. The BlackBerry Collaboration Service sends the acceptance, in encrypted and compressed format, through the
BlackBerry Dispatcher to the BlackBerry device, and creates a cache of the connectivity information to maintain the
new instant messaging session.
10. The collaboration client on the BlackBerry device starts the session using an open GET request over the HTTPS persistent
connection.
The BlackBerry Collaboration Service receives server-initiated events from the Microsoft Office Communicator Web Access
server using an HTTP GET or HTTPS GET request, and sends these events to the collaboration client over this session. The
BlackBerry Collaboration Service sends events that the BlackBerry device initiates to the Microsoft Office Communicator
Web Access server using an HTTP POST or HTTPS POST request.
Feature and Technical Overview
Instant messaging process flows
47
Comentarios a estos manuales