BlackBerry Enterprise Instant Messaging is not functional with Microsoft Office Communications Server 2007 R2

Article ID: KB17757

Type: Support Content

Last Modified: 12-14-2011

 

Product(s) Affected:

  • BlackBerry Enterprise Server for Microsoft Exchange
  • BlackBerry Enterprise Server for IBM Domino
CollapseEnvironment
  • BlackBerry® Enterprise Server 4.1 SP6 to 5.0. SP2
  • Microsoft® Office Communications Server 2007 R2
  • Microsoft® Office Communications Server 2007
  • Microsoft® Office Communicator Web Access 2007
  • SDR271303
  • DT 333394
CollapseOverview

Microsoft® Office Communications Server 2007 R2 (OCS) is not functional with BlackBerry® Collaboration Services 4.1 SP6, SP7 and 5.0, SP1 and SP2.

  1. The web address to make Communicator Web Access (CWA) requests to the CWA server has changed. Using the currently documented web address generates an HTTP 500 Internal Server Error on the CWA Server.
  2. Names spaces are generated in cwaEvents and cwaResponses Extensible Markup Language (XML) top nodes, violating the previous schema. As a result, no Java® Architecture for XML Binding (JAXB) parsing can occur.
  3. Phone oriented data in CWA XML has changed.
  4. Chatting will function, but a single chat window appears as a multi-chat window on the BlackBerry® Client for use with Microsoft® Office Communications Server 2007 because the logged in BlackBerry smartphone user is interpreted as a different participant.

    Note: If planning to install Microsoft Office Communications Server 2007 R2, the unsupported AJAX API impacts the BlackBerry Enterprise Server for Microsoft Exchange for instant messaging implementation against Microsoft Office Communications Server. Once Microsoft Office Communications Server 2007 R2 is installed, the BlackBerry Enterprise Server will not be able to integrate with your instant messaging environment.

    Instant messaging with Microsoft Office Communications Server 2007 R2 is compatible with the BlackBerry Collaboration Service and the BlackBerry Client for use with Microsoft Office Communications Server 2007 only if the workaround described in the Workaround section of this article is implemented.

CollapseCause

In Microsoft Office Communications Server 2007 R2, the Asynchronous JavaScript® and XML (AJAX) Application Programming Interface (API) is no longer supported by Microsoft. The Unified Communications (UC) AJAX SDK that is available through the Microsoft Office Communicator Web Access 2007 server will not be re-released by Microsoft in Microsoft Office Communicator Web Access 2007 R2 or in future releases.

CollapseResolution
Upgrade the BlackBerry® Enterprise Server to 5.0 SP3
CollapseWorkaround

Research In Motion, in conjunction with Microsoft, has documented a workaround that must be implemented to allow BlackBerry smartphone users to continue using the enterprise instant messaging application.

If updating the Microsoft Office Communications Server 2007 to R2, it is required that the Microsoft Office Communicator Web Access 2007 servers remain at R1 for continued communication with the BlackBerry Enterprise Servers.

For more information on the removal of AJAX API support, search the Microsoft support web site for knowledge base article 969336 or "How to set up a Communicator Web Access 2007 server in a Communications Server 2007 R2 topology to support UC AJAX applications".


Prerequisites

  1. Configure two servers in the same domain as follows:
    • On Server 1, install Windows® Server 2003 R2 32-bit edition
    • On Server 2, install Windows Server 2003 R2 64-bit edition
  2. Verify that you have an existing Mutual Transport Layer Security (MTLS) certificate, or create a new MTLS certificate.

Note: It is required to install Microsoft Office Communicator Web Access 2007 in the domain before you install Microsoft Office Communications Server 2007 R2. If the installation of Microsoft Office Communications Server 2007 R2 is done first, the installation of Microsoft Office Communicator Web Access 2007 will fail.

Tasks - Server 1

Complete the following steps on Server 1:

  1. Using the deployment wizard in Microsoft Office Communications Server 2007, configure Microsoft® Active Directory®.
  2. Using the deployment wizard in Microsoft Office Communicator Web Access 2007, use the MTLS certificate to install, create, and activate a virtual Microsoft Office Communicator Web Access 2007 server.

    Note: The requirement in the deployment wizard that states that you must have already installed and deployed Microsoft Office Communications Server 2007 can be ignored.

  3. Type the following web address in your browser to access Microsoft Office Communicator Web Access 2007:

    http://<server1>:81/

    where <server1> is the computer name of Server 1.

    Note: If the error message Error 401: Unauthorized Access displays, your browser might be sending an Internet authentication header field that the web server cannot accept. In this case, perform the following actions:

  4. On Server 2 or from the domain controller, click Start > Run.
  5. Type dsa.msc .
  6. Using Microsoft Active Directory, add the existing CWAService user name to the RTCUniversalServerAdmins user group.
  7. On server 1  click Start > Administrative Tools.
  8. In Computer Management, restart the World Wide Web Publishing Service.
  9. Retry step 3.

Tasks - Server 2

Complete the following steps on Server 2:

  1. Using the deployment wizard in Microsoft Office Communications Server 2007 R2, configure Microsoft Active Directory.
  2. Install Microsoft Office Communications Server 2007 R2.

    Note: Warnings related to log components or a failure to start services can be ignored only if the Monitoring Agent in Microsoft Office Communications Server 2007 R2 fails to start.

  3. In the directory where you installed setupse.exe or setupee.exe, from the setup subdirectory, run admintools.msi. The Communications tab for users is accessible in both Microsoft Active Directory and the Microsoft Office Communications Server 2007 console.
  4. In Microsoft Active Directory, create SIP user IDs that are enabled for Microsoft Office Communications Server 2007 R2.
  5. Install Microsoft Office Communicator 2007 R2.
  6. Using a SIP user ID, connect to Microsoft Office Communications Server 2007 R2.
  7. Using the Microsoft Office Communications Server 2007 console open the Front End Server Properties. On the General tab, add TCP port 5060 to connections.
  8. On Server 1 type the following web address in your browser to access the virtual Microsoft Office Communicator Web Access 2007 server:

    http://<server1>:81/

    Where <server1> is above, enter the computer name of server 1.

  9. Sign in with a SIP ID.

Post-requisite: It is also an option to install Microsoft Office Communicator 2007 or Microsoft Office Communicator 2007 R2 on Server 1 to verify connectivity and sign-in functionality.

Disclaimer

By downloading, accessing or otherwise using the Knowledge Base documents you agree:

   (a) that the terms of use for the documents found at www.blackberry.com/legal/knowledgebase apply to your use or reference to these documents; and

   (b) not to copy, distribute, disclose or reproduce, in full or in part any of the documents without the express written consent of RIM.


Visit the BlackBerry Technical Solution Center at www.blackberry.com/btsc.