Export (0) Print
Expand All

Getting Started Building a Unified Communications Managed API version 1.0 Application

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

This section describes tasks required before creating a Microsoft Unified Communications Managed API version 1.0 application. Also see Prerequisites for Unified Communications Managed API version 1.0.

When running applications on Microsoft Office Communications Server, authors may choose to use either Enterprise Edition or Standard Edition. With Enterprise Edition there may be more than one Front End Server. If more than one Front End Server is used, the application's outbound connections should be load balanced across the Front End Servers using a load balancer. Standard Edition uses a single Front End Server, so load balancing is not required.

In Microsoft Office Communications Server, identify the application computer as a trusted host. Use the Host Authorization tab on the Office Communications Server property page to configure the server to trust a connection to a specific application, and to treat traffic from the application as another server. For more information, in the Microsoft Office Communications Server 2007 Administration Guide, see "Configuring Authorized Hosts."

Unified Communications Managed API applications require the following permissions:

  • Registry read access.
  • Permission to execute unmanaged code.
  • If tracing is enabled, the application requires file write access.

Use certificates to authenticate the connection between the Office Communications Server computer and the application computer. A Unified Communications Managed API application may use either Transmission Control Protocol (TCP) or Mutual Transport Layer Security (MTLS). Use of MTLS requires a certificate to authenticate inbound and outbound connections with Office Communications Server. For more information about certificate management see Related Links (Advanced Certificate Enrollment and Management).

In Office Communications Server, use the Certificate Wizard to create certificates on the Standard Edition server or Front End Server of an Enterprise pool. For more information, in the Microsoft Office Communications Server 2007 Administration Guide see "Configuring Certificates for Servers" and "Configuring Internal and External Interfaces and Certificates for Edge Servers."

Certificates are also required on the application computer.

  • Create a certificate for the application computer that will be trusted by Office Communications Server, and import that certificate to the application host computer. This certificate must be installed at the path Console Root/Certificates(Local Computer)/Personal/Certificates.
  • Create a root certificate and install this certificate at the path Console Root/Certificates(Local Computer)/Trusted Root Certification Authorities/Certificates.

Ensure the account used for the application has read access to the certificate store and the private key.

Community Additions

ADD
Show:
© 2014 Microsoft