Edit runtime-config.properties File for Omnissa Access in Secondary Data Center to Set Read-Only Mode

You must edit the runtime-config.properties files for the Omnissa Access appliances in the secondary data center to configure the appliances for read-only access. Also change the JDBC URL on the secondary data center nodes if you are not using technologies such as SQL Server Always On.

Make these changes in each Omnissa Access appliance in the secondary data center.

Procedure

1. Using an SSH client, log in to the Omnissa Access appliance as the root user.

2. Open the /usr/local/horizon/conf/runtime-config.properties file.

3. Configure the Omnissa Access appliance to have read-only access by adding the following line:

   read.only.service=true

4. Also add the following line to the file:

   cache.service.type=ehcache

   Note: cache.service.type=ehcache is required if you set read.only.service=true. If read.only.service=false or if the read.only.service key is not specified, then the default is cache.service.type=rds.

5. Set the value of the ehcache.replication.rmi.servers entry to the fully qualified domain names (FQDN) of the other nodes in the secondary data center. Use a colon : as the separator.

   For this example, we have three nodes in the secondary data center (sva1.example.com, sva2.example.com, and sva3.example.com). The current node is sva1.example.com. Configure the entry as follows.

   ehcache.replication.rmi.servers=sva2.example.com:sva3.example.com
   

6. Save the file.

7. Change the JDBC URL on the secondary data center nodes if you are not using technologies such as SQL Server Always On.

   See Manage Omnissa Access External Database Settings for information.

8. Restart the Tomcat server on the appliance.

   service horizon-workspace restart

9. Repeat the preceding steps on the remaining nodes in the secondary data center.

   For this example, the remaining nodes to configure are sva2.example.com and sva3.example.com.