• Article

Communicator Mobile for Java

Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

Microsoft Office Communicator Mobile for Java is a new enterprise messaging client built on the Java Platform Micro Edition. When it is deployed together with Office Communications Server 2007 R2, Communicator Mobile for Java enables mobile phones that can run Java applications to function as unified communications endpoints, providing instant messaging (IM) and presence to create a familiar experience for users of Microsoft Office Communicator. Mobile devices enable users to extend the reach of Office Communications Server 2007 R2. This topic describes the prerequisites, the required server components, and the deployment process for Communicator Mobile for Java.

Mobile Device Software Requirements

The following are prerequisites for installing the Communicator Mobile for Java client.

  • Nokia S60

  • Nokia S40

  • Motorola RAZR V3xx

Each of the mobile phones must also meet the following prerequisites:

  • Capable of running Java applications greater than 512 KB, and with a heap size of 2 MB.

  • Mobile Information Device Profile 2.0 (MIDP 2.0).

  • Connected Limited Device Configuration 1.1 (CLDC 1.1).

  • Screen resolution:

    240x320 for Nokia S40 and Motorola RAZR V3xx phones.

    240X 320 or 320x240 for Nokia S60 phones.

  • Data-connection-enabled (GPRS, Edge, or 3G connection) mobile device. Subscription to an unlimited data plan on the mobile device is recommended, because the client and server will be exchanging messages even when they are in an idle state.

For details about the specific mobile phones supported for Communicator Mobile for Java, see Supported Clients in the Supported Topologies and Infrastructure Requirements documentation.

Required Server Components

The following list describes the Office Communications Server components that are required to implement Office Communicator Mobile for Java:

  • Office Communications Server 2007 R2. Communicator Mobile for Java requires a deployment of Office Communications Server 2007 R2.

  • Communicator Web Access server. The Communicator Web Access server is a critical server deployment requirement for Communicator Mobile for Java. Communicator Mobile for Java uses the Communicator Web Access server to connect client devices to the Office Communications Server 2007 R2 environment, and the Communicator Web Access server acts as a gateway to the various Office Communications Server functions.

  • Voice mail configuration. The Communicator Mobile for Java user account must be configured with an Exchange mailbox, and it must be enabled for Enterprise Voice.

  • Reverse proxy deployment. A reverse proxy is typically used in front of Web servers, and it presents a single interface to clients. It is also used to balance the load on a Web server farm. Communicator Mobile for Java connects to Communicator Web Access server through the reverse proxy.

  • Exchange Client Access server. The Client Access server role supports the Microsoft Outlook Web Access and Microsoft Exchange ActiveSync client applications and the Post Office Protocol version 3 (POP3) and Internet Message Access Protocol version 4rev1 (IMAP4) protocols. The Client Access server role accepts connections to your Exchange 2007 server from a variety of different clients, including mobile devices. The Client Access server role is required in every Exchange Server 2007 organization.

  • Exchange Unified Messaging deployment. Microsoft Exchange Server Unified Messaging (UM) integrates with Office Communications Server 2007 R2 to offer voice mail functionality.

Deployment Process

The deployment process for Communicator Mobile for Java is described in the following table.

Table 1. Communicator Mobile for Java Deployment Process

Phase Steps Permissions Documentation

Verify that prerequisites and dependencies are met.

Verify that the needed services are installed:

  1. Verify that the Communicator Web Access server and other server components are deployed.

  2. Ensure that the feature phone is a supported model and that it meets Java software requirements.

Administrator

Supported Clients and the previous information in this section.

Deploy the Communicator Mobile component

  1. Configure the site for downloading self-signed certificates.

  2. Set up the Communicator Mobile for Java deployment site

  3. Prepare for installation of Communicator Mobile for Java.

Administrator

Setting up the Communicator Mobile for Java Download Site

Configuring a Site for Downloading Self-Signed Certificates

Preparing for Installation of Communicator Mobile for Java
topics in Deploying Communicator Mobile for Java in the Client Planning and Deployment documentation

Install Communicator Mobile for Java on the phone.

  1. Install client software on the phone.

  2. Configure client software on the phone.

Administrator

Installing Communicator Mobile for Java Client Software in Deploying Communicator Mobile for Java

Complete post-setup tasks.

  1. Configure client settings.

  2. Use the client.

Administrator

Configuring and Using the Communicator Mobile for Java Client in Deploying Communicator Mobile for Java