Overview

This document describes the steps required to specify the Fully Qualified Domain Name (FQDN) for a server in the EditShare's landing page. An Editshare will automatically use the IP address of the primary network interface of each server to build the links to resources such as FLOW Control and AirFLOW etc on the landing page.

When a custom SSL certificate is configured for the FLOW resources, it may be preferable to reference the FQDN in the landing page rather than the "internal" IP address.

Prerequisites

The reader should have a configured functioning EditShare installation with working DNS that is able to resolve the FQDN to a reachable EditShare IP address.

Process Steps

In a precise, step-by-step approach, walk your reader through the process. Make sure your reader can reproduce your intended result by following your exact steps. Make the learning process efficient by supplying sample screen shots as necessary.

1.  Open a command prompt on the EditShare server hosting your landing page. For most customers this will be the server providing the metadata controller role. For customers with a High Availability configuration these steps should be repeated for both metadata controllers.

2.  Using your editor of choice, in this case vi, create a new configuration file:

   $ vi /etc/editshare/external_endpoint.conf

3. Create mappings between each servers internal (primary) and external FQDN's in the following format (note there are 4 spaces at the start of the PRIMARY_IP line and 8 spaces at the start of the external_endpoint line):

   cluster_nodes:
       <PRIMARY_IP>:
            external_endpoint: <EXTERNAL_FQDN>
       <PRIMARY_IP>:
            external_endpoint: <EXTERNAL_FQDN>

   For example in my two server cluster where my flow resources are on one server and no need for rewrites on the other it may look like this:

   cluster_nodes:
       10.15.10.10:
            external_endpoint: 10.15.10.10
       10.15.10.11:
            external_endpoint: flow.mydomain.com

4. Save the file and close the editor

5. Refresh the flow landing page on the server whose configuration you have changed to rewrite the landing page links:

   $ sudo era-cmd refresh_landing

   Note this refresh-config stage should be completed at a time when the system is not under a heavy load to avoid negatively impacting user experience.

6. Refresh your browser and you should now see links such as AirFLOW that previously pointed to 10.15.10.11 now point to flow.mydomain.com from the above example.

Summary

The above steps should allow to the user to reconfigure the landing page to point to either external IP addresses or FQDN's, typically those specified by a custom SSL certificate