The Integration Broker is a Workspace ONE Access component that is used to communicate with the Citrix server farm. You install the Integration Broker on premises on a supported Windows server.
Follow these guidelines when you deploy the Integration Broker.
- You can install the Integration Broker on Windows Server 2016 or Windows Server 2012 R2.
Table 1. Integration Broker Server Requirements Requirement Notes Windows Server 2016 or Windows Server 2012 R2 with dual core processor 4 GB RAM 30 GB This includes the storage required for the Windows OS.
- Integration Broker version requirements:
Workspace ONE Access(VMware Identity Manager) Service or Connector Version Integration Broker Version Supported Workspace ONE Access Cloud service 19.03.0.1 Workspace ONE Access 20.10 19.03.0.1 VMware Identity Manager Connector 19.03.0.1 19.03.0.1 Workspace ONE Access 20.01 19.03 VMware Identity Manager 19.03 19.03 VMware Identity Manager Connector 19.03 19.03Note: Using the latest available version of Workspace ONE Access and its components is recommended.
- The connector must be able to communicate with the Integration Broker. If you set up multiple connector instances, ensure that all of them can communicate with the Integration Broker.
Note: You must connect over SSL to any Integration Broker instance that is used for launch.
- A single Integration Broker instance can support multiple Citrix environments.
- Follow these guidelines for the Windows version of the connector.
- Installing the Integration Broker and the connector on different servers is recommended.
- If you are installing the Integration Broker on the same server as the connector, ensure that the HTTP and HTTPS binding ports do not conflict with the ports used by the connector.
The VMware Identity Manager Windows connector (versions 3.3 and 19.03) always uses port 80. It also uses 443, unless a different port is configured during installation. For more information on the ports used, see Installing and Configuring VMware Identity Manager Connector 19.03 (Windows).
- A self-signed certificate is generated during the connector installation. If you are installing the Integration Broker on the same server as the connector, you can use this certificate. Install the certificate in the Microsoft store and use it for the HTTPS binding.
- Before you start, plan your deployment strategy. See Integration Broker Deployment Models for recommendations for common scenarios.