Know how to deploy Adobe Connect Edge Server to enhance security, to decrease latency, to load balance, and to provide a failover.

Adobe Connect Edge Server installation workflow

Design edge server zones.

You can set up edge servers or clusters of edge servers in different locations, or zones, to allocate and balance access to Adobe Connect. For example, you could set up an edge server in San Francisco for West Coast users and an edge server in Boston for East Coast users.

Install Adobe Connect Edge Server.

Install Adobe Connect Edge Server on each computer in each zone. For example, if you have a cluster of edge servers in a zone, install Adobe Connect Edge Server on each computer in the cluster. See Install Adobe Connect Edge Server.

Modify the DNS server for each zone.

Map the FQDN of the origin Adobe Connect server to the static IP address of Adobe Connect Edge Server in each zone. See Deploying Adobe Connect Edge Server.

Configure the edge server.

Add configuration parameters to the custom.ini file on each Adobe Connect Edge Server. See Deploying Adobe Connect Edge Server.

Configure the origin server.

Add configuration parameters to the custom.ini file on each Adobe Connect server. Also, you must set the External Name of the edge server in the Application Management Console on the origin server. See Deploying Adobe Connect Edge Server.

Set up a load balancer.

If you set up multiple edge servers in a zone, you must use a load balancer to balance the load between edge servers and configure it to listen on port 80. The edge servers listen on port 8080. For more information, see the documentation provided by the vendor of the load balancer.

Deploy Adobe Connect Edge Server

Before you deploy Edge servers, have Adobe Connect and any additional features (for example, SSL, a directory service integration, single sign-on, or shared content storage) running successfully.

  1. On your DNS server, map the FQDN of the origin server to the static IP address of the edge server. If you’re installing edge servers in multiple zones, repeat this step for each zone.

    Note:

    Alternatively, you can use a hosts file; if you do, every client must have a hosts file that points the static IP address of the edge server to FQDN of the origin server.

  2. On the Adobe Connect Edge Server, open the file [root_install_dir]\edgeserver\win32\conf\HttpCache.xml and replace the computer name in the HostName tag with the FQDN of the edge server computer, for example, edge1.mycompany.com.
    <!-- The real name of this host. -->          
    <HostName>edge1.yourcompany.com</HostName>
  3. On the Adobe Connect Edge Server, create a file [root_install_dir]\edgeserver\custom.ini file and enter the following parameters and values.

    FCS_EDGE_HOST

    The FQDN of the edge server, for example, FCS_EDGE_HOST=edge1.yourcompany.com.

    FCS_EDGE_REGISTER_HOST

    The FQDN of the Adobe Connect origin server, for example, FCS_EDGE_REGISTER_HOST=connect.yourcompany.com.

    FCS_EDGE_CLUSTER_ID

    The name of the cluster. Each edge server cluster must have a unique ID. Each computer within the cluster must have the same ID. The recommended format is companyname-clustername, for example, FCS_EDGE_CLUSTER_ID=yourcompany-us. Configure this parameter, even if you are deploying only one Adobe Connect Edge Server.

     

    FCS.HTTPCACHE_BREEZE_SERVER_NORMAL_PORT

    The IP address or domain name and port number of the computer where Adobe Connect is installed, for example, FCS.HTTPCACHE_BREEZE_SERVER_NORMAL_PORT=connect.yourcompany.com:80. The Adobe Connect Edge Server connects to the Adobe Connect origin server at this location.

    FCS_EDGE_PASSWORD

    (Optional) A password for the edge server. If you set a value for this parameter, you must set the same value for every edge server and origin server.

    FCS_EDGE_EXPIRY_TIME

    (Optional) The number of milliseconds in which the edge server must register itself to the origin before it expires from the cluster and the system fails over to another edge. Start with the default value, FCS_EDGE_EXPIRY_TIME=60000.

    FCS_EDGE_REG_INTERVAL

    (Optional) The interval, in milliseconds, at which the edge server attempts to register with the origin server. This parameter determines how often the edge server makes itself available to the origin server. Start with the default value, FCS_EDGE_REG_INTERVAL=30000.

    DEFAULT_FCS_HOSTPORT

    (Optional) To configure the edge server ports, add the following line: DEFAULT_FCS_HOSTPORT=:1935,80,‑443.

    The minus sign (‑) in front of 443 designates port 443 as a secure port that receives only RTMPS connections. If you attempt an RTMPS connection request to port 1935 or 80, the connection fails. Similarly, an unsecured RTMP connection request to port 443 fails.

    If your edge server uses an external hardware accelerator, port 443 does not have to be configured as a secure port.

    The following are sample values for the config.ini file: FCS_EDGE_HOST=edge.yourcompany.com FCS_EDGE_REGISTER_HOST=connect.yourcompany.com FCS_EDGE_CLUSTER_ID=yourcompany-us FCS.HTTPCACHE_BREEZE_SERVER_NORMAL_PORT=connect.yourcompany.com:80

    FCS_EDGE_HOST=edge.yourcompany.com 
    FCS_EDGE_REGISTER_HOST=connect.yourcompany.com 
    FCS_EDGE_CLUSTER_ID=yourcompany-us 
    FCS.HTTPCACHE_BREEZE_SERVER_NORMAL_PORT=connect.yourcompany.com:80
  4. Restart the edge server.
  5. On the Adobe Connect origin server, open the [root_install_dir]\custom.ini file in a text editor and map the value of the FCS_EDGE_CLUSTER_ID parameter to a zone ID; the syntax is edge.FCS_EDGE_CLUSTER_ID=zone-id. Even if you are only deploying one edge server, you must map the cluster ID to a zone ID.

    Each edge server cluster must have a zone ID. A zone ID can be any positive integer greater than 0. For example, you could have three clusters mapped to zones 1 to 3:

    edge.yourcompany‑us=1 
    edge.yourcompany‑apac=2 
    edge.yourcompany‑emea=3

    The following is a sample custom.ini file for the origin server: DB_HOST=localhost DB_PORT=1433 DB_NAME=breeze DB_USER=sa DB_PASSWORD=#V1#4cUsRJ6oeFwZLnQPpS4f0w== # DEBUG LOGGING SETTINGS HTTP_TRACE=yes DB_LOG_ALL_QUERIES=yes # EDGE SERVER SETTINGS edge.yourcompany-us=1

    DB_HOST=localhost                                                                              
    DB_PORT=1433                                                                             
    DB_NAME=breeze                                                                             
    DB_USER=sa                                                                             
    DB_PASSWORD=#V1#4cUsRJ6oeFwZLnQPpS4f0w==                                                                            
    # DEBUG LOGGING SETTINGS                                                                            
    HTTP_TRACE=yes                                                                            
    DB_LOG_ALL_QUERIES=yes 
    # EDGE SERVER SETTINGS 
    edge.yourcompany-us=1

    Note:

    If you set an FCS_EDGE_PASSWORD parameter in the config.ini file on the edge server, set the same password in the custom.ini file on the origin server.

  6. Restart the origin server.
  7. On the origin server, open the Application Management Console (Start > Programs > Adobe Connect Server > Configure Adobe Connect Server). Select the Application Settings tab, then select Server Settings and, in the Host Mappings section, enter the External Name for the edge server. The External Name should be identical to the value set for the FCS_EDGE_HOST parameter on the edge server.
  8. On the origin server, configure the Windows firewall so the edge servers can access port 8506.
  9. Repeat steps 2‑4 for each edge server in each zone.
  10. Repeat steps 5‑7 for each origin server in each zone.

For help deploying edge servers, contact Adobe Support at www.adobe.com/support/programs/connect.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy