Activation, Provisioning, and Deployment Changes in UCMA 3.0 Core

  • Article

Microsoft Unified Communications Managed API (UCMA) 3.0 incorporates a number of changes in deployment, activation, and provisioning that have been made since Microsoft Unified Communications Managed API (UCMA) 2.0. These changes correspond to Microsoft Lync Server 2010 planning and management changes, including the Central Management Store, Microsoft Lync Server 2010 Topology Builder, Microsoft Lync Server 2010 PowerShell command-line interface, and Microsoft Lync Server 2010 Control Panel. For more information about Lync Server 2010 Manageability changes, see New Features in Lync Server 2010.

Application Activation

Application activation is the process by which data that is needed to configure UCMA 3.0-based applications is stored for use when these applications run so that they can take advantage of Microsoft Lync Server 2010 functionalities. Most of the commonly-used configuration data exists in Active Directory, the Central Management Store, and the computer that hosts the application’s local certificate store. When applications are run, they retrieve this configuration data using the application provisioning process.

Area

UCMA 2.0

UCMA 3.0

WMI, Topology Builder, Lync Server 2010 PowerShell

Uses WMI only.

Uses Lync Server 2010 PowerShell cmdlets or Microsoft Lync Server 2010 Topology Builder.

After being activated, the application appears in Microsoft Lync Server 2010 Control Panel.

Trusted service port entries and ApplicationEndpoint contact objects

Uses Active Directory only.

Uses Active Directory and Central Management Database.

Trusted service port entries are stored in Central Management Database. ApplicationEndpoint contact objects are stored in Active Directory.

Application Provisioning

Application provisioning is the process of reading configuration data from the Central Management Store (CMS) stores, Active Directory, and the local computer certificate store. When these settings change, the application must update itself accordingly. Provisioning can be performed automatically by using the auto-provisioning in UCMA 3.0 or by using Windows Management Interface (WMI). Provisioning can also be performed manually by obtaining data through a WMI-based tool or using Windows PowerShell cmdlets and then passing the resulting data to the application. Auto provisioning is the recommended method of provisioning UCMA-based applications.

Note

An application might have additional, business-specific provisioning needs that are not covered in this documentation. The application developer is responsible for addressing those needs.

Area

UCMA 2.0

UCMA 3.0

Application auto-provisioning

Manual or WMI-based custom auto-provisioning is commonly performed.

Local Management Store replica-based auto-provisioning is the default, but applications can also be manually provisioned.

Application Deployment

Application deployment has several dimensions, including setup, load balancing, and collocation with Office Communications Server 2007/Office Communications Server 2007 R2 and Lync Server 2010.

Area

UCMA 2.0

UCMA 3.0

Load balancing

Hardware load balancing only.

DNS-based load balancing is the default. Hardware load balancing can be used.

Supported operating systems

  • The latest Microsoft Windows Server 2003 R2 (64-Bit Editions) service pack or

  • The latest Microsoft Windows Server 2008 (64-Bit Editions) service pack

  • Limited support for client operating systems: Windows Vista, Windows 7

  • 64-bit operating system versions only

  • Windows Server 2008 SP2 (or later service pack) or Windows Server 2008 R2 (latest service pack)

  • Limited support for client operating systems: Windows Vista, Windows 7

  • 64-bit operating system versions only

System requirements

  • Supported operating system version

  • .NET Framework 3.5 Service Pack 1

  • Visual C++ 2008 Redistributable Package

  • UcmaRedist.msi

  • Optional: Windows Media Format Runtime

  • OCSCore.msi

  • Speech Platform

  • Speech TTS/SR Language Packs

  • Supported operating system version

  • .NET Framework 3.5 Service Pack 1

  • UCMARuntimeSetup.exe

  • Optional: OCSCore.msi from the local copy

  • Optional: Additional Speech Language packs, if needed (can be downloaded from the Web)

Runtime

  • UCMARedist.msi (packaged with UCMA 2.0 SDK for free redistribution by an ISV)

  • ISVs must package their application with UCMARedist.msi and other components, including Microsoft Visual C++, .NET Framework 3.5 SP1, Speech Platform, Speech Language Packs, and Windows Media Format.

  • Administrators must install Office Communications Server 2007 R2 OCSCore.msi from Microsoft Office Communications Server 2007 R2 media

  • Free distribution of UCMARuntimeSetup.exe from web. No redistribution needed.

  • UCMARuntimeSetup.exe installs the runtime for both UCMA 3.0 Core and UCMA 3.0 Workflow, and also installs other used components, including Microsoft Visual C++, Speech Platform, Speech Language Packs, and Windows Media Format.

  • OCSCore is now packaged with the UCMARuntimeSetup.exe as well

Next-hop Communications Server

Office Communications Server 2007, Office Communications Server 2007 R2, Lync Server 2010

Lync Server 2010

Office Communications Server 2007 R2 for UserEndpoint and Instant Message/Presence only

In its own external pool of computers

Yes (default)

Yes (default)

Collocated with Communications Server

Yes (for example, compliance applications)

Yes (for example, compliance applications)

See Also

Concepts

Activating a UCMA 3.0 Core Trusted Application