Before you install Integration Broker, you must prepare your Windows system.

About this task

The following operating systems are supported for Integration Broker.

  • Windows Server 2008 R2

  • Windows Server 2012

  • Windows Server 2012 R2

Prerequisites

  • Determine how you will deploy Integration Broker.

    Consider the following questions.

    • Will you use multiple Integration Broker instances?

      Multiple instances are useful for both high-availability and load-balancing purposes.

      • If you use multiple Integration Broker instances, a preferred practice is to install one Integration Broker instance for each Windows Server instance.

      • If your deployment distributes heavy traffic, a preferred practice is to use at least one Integration Broker instance to sync with VMware Identity Manager and at least one Integration Broker instance to provide SSO.

    • If so, will you use load balancers?

      If your deployment uses multiple Integration Broker instances for high-availability or load-balancing purposes, consider installing them behind one or more load balancers.

  • Verify that Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 are installed with the latest updates. To check for updates, select Control Panel > Windows Update.

  • Install .NET Framework 3.5. When you install .NET, it installs version 3.5 as a feature. If you are using Windows Server 2008 R2, ensure that you select WCF Activation. If you are using Windows Server 2012 or 2012 R2, ensure that you select HTTP Activation.

  • Download and install Microsoft Visual J#® 2.0 Redistributable Package - Second Edition. Depending on your operating system, you might need to download either the 32-bit or 64-bit version of Microsoft Visual J#.

  • Configure IIS 7 or 7.5 for Windows Server 2008 R2, IIS 8 for Windows Server 2012, or IIS 8.5 for Windows Server 2012 R2.

    Note:

    If you are installing IIS 7, install it in 6.0 Management Compatibility Mode. You must also install the Management Tools if this is your only IIS 7 instance.

  • For Windows Server 2012 or 2012 R2, select the following features, roles, and role services. You select these in Server Manager, using the Add Roles and Features wizard.

    Features

    • .NET Framework 3.5 Features

      • .NET Framework 3.5 (includes .NET 2.0 and 3.0)

      • HTTP Activation

    • IIS Hostable Web Core

    • Windows Process Activation Service

    • WinRM IIS Extension

    • WoW64 Support

    For example:

    Features


    Roles

    • Application Server

    • Web Server (IIS)

    • File Server

    For example:

    server roles


    Role Services

    Application Server Role Services

    • .NET Framework 4.5

    • COM+ Network Access

    • Web Server (IIS) Support

    • Windows Process Activation Service Support

      • HTTP Activation

    Web Server Role (IIS) Role Services

    • Web Server

      • Common HTTP Features

        • Default Document

        • Directory Browsing

        • HTTP Errors

        • Static Content

        • HTTP Redirection

      • Health and Diagnostics

        • HTTP Logging

        • Logging Tools

        • Request Monitor

        • Tracing

      • Performance

        • Static Content Compression

        • Dynamic Content Compression

      • Security

        • Request Filtering

        • Basic Authentication

        • Client Certificate Mapping Authentication

        • Digest Authentication

        • IIS Client Certificate Mapping Authentication

        • IP and Domain Restrictions

        • URL Authorization

        • Windows Authentication

      • Application Development

      • Management Tools

        • IIS Management Console

        • IIS 6 Management Compatibility

        • IIS Management Scripts and Tools

    For example:

    server roles


  • For Windows Server 2008, select the following roles. You select these in Server Manager, using the Add Roles and Features wizard.

    • Application Server

    • Web Server (IIS)

    • File Server

  • Configure an application pool. You can use the default application pool or create an application pool that is dedicated to Integration Broker.

Note:

See the VMware Product Interoperability Matrixes at http://www.vmware.com/resources/compatibility/sim/interop_matrix.php to verify version information.

Procedure

  1. If you are using IIS 8.0 or later, in IIS Manager, ensure that the http and https bindings for the Default Web Site do not have a host name configured. The Host name field for the http and https bindings should be blank. For example:


    http binding


  2. In IIS Manager, configure the default application pool or the one you set up to use with Integration Broker.
    1. Click the application pool.
    2. Verify these requirements.
      • .NET Framework version 2.0

      • Set 32-bit applications to true.

      Note:

      In Windows 2012 and Windows 2012 R2, the application pool may have been configured to a different version of .NET Framework by default. Ensure that you configure the application pool to .NET Framework 2.0.

  3. In IIS Manager, configure Identity.

    The Identity user must have the following roles:

    • At least Read-only Administrator on the Citrix farm

    • Administrator on the Integration Broker server

    1. Right-click the application pool.
    2. Click Identity in the Advanced Settings dialog.
    3. Click Custom Account and click Set.
    4. Type the Identity user credentials.
  4. Download and install the Citrix PowerShell SDK.
    1. Download and install the appropriate version.
      • If you are using XenApp 6.0, download and install version 6.0 of Citrix PowerShell SDK from the Citrix website.

      • If you are using XenApp 6.5, download and install version 6.5 of Citrix PowerShell SDK from the Citrix website.

      • If you are using XenApp 7.x or XenDesktop 7.x, install the following PowerShell SDKs from the XenApp or XenDesktop 7.x DVD, or from the Citrix website:

        • Citrix Broker PowerShell snap-in

        • Citrix Configuration Service PowerShell snap-in

    2. Set the execution policy for Citrix PowerShell Remoting.
    3. If the Citrix XenApp or XenDesktop farm's execution policy is configured to use remote sign on, you must add your root certificate to the Trusted Root Certification Authorities store. See the Microsoft website about adding root certificates to the store.

      If the Citrix XenApp or XenDesktop farm's execution policy is configured to unrestricted, you do not need to add root CAs to the Trusted Root Certification Authorities store.

  5. Before you run this command, verify that PowerShell SDK is successfully installed.
    1. Launch PowerShell SDK as administrator.
    2. Verify PowerShell remoting.

      This sample command applies to XenApp or XenDesktop 7.x.

      Get-BrokerDesktopGroup -AdminAddress CitrixServerName
      Get-ConfigSite -AdminAddress CitrixServerName
      

      This sample command applies to Citrix Server Farm 6.5.

      Get-XAApplication -ComputerName CITRIX SERVER NAME

      This sample command applies to Citrix Server Farm 6.0.

      Invoke-Command -ComputerName XENAPP_HOST_NAME -ScriptBlock { Add-PSSnapin Citrix* ;Get-XAApplication } -Credential DOMAIN\USERNAME
    3. Verify that the list includes all the applications hosted by Citrix.

What to do next

If the Invoke-Command command fails, see Memory Issue Prevents Proper Configuration of Integration Broker.

Next, deploy and configure Integration Broker.