Updating portal-ext.properties to synchronize caching for Studio instances

The portal-ext.properties file for each instance includes commented-out settings for synchronizing the caches for Studio instances.

For each Studio instance, uncomment the following clustering settings in portal-ext.properties. You should be able to use the default values provided.

##
## Cluster
##
# Uncomment the following properties to enable clustering
# Note: Clustering will not work with Hypersonic.  Configure a common database for all cluster nodes.

#net.sf.ehcache.configurationResourceName=/ehcache/hibernate-clustered.xml
#ehcache.multi.vm.config.location=/ehcache/liferay-multi-vm-clustered.xml
#org.quartz.jobStore.isClustered=true

This table lists settings in portal-ext.properties used to enable synchronized caching of Studio instances (in a cluster of Studio instances). For each setting, the table provides a description of the required value.

Setting	Description
`net.sf.ehcache.configurationResourceName`	The name and location of the XML configuration file for Hibernate caching. Hibernate is used by Studio to read from and write to the Studio application database. In the default portal.properties file, the configuration file is set to hibernate.xml, to implement caching in a non-clustered Studio implementation. When you uncomment this property in portal-ext.properties, which changes the configuration file to hibernate-clustered.xml, then Hibernate synchronizes the cache with the other Studio instances in the Studio cluster.
`ehcache.multi.vm.config.location`	The name and location of the XML configuration file for Ehcache. In the default portal.properties file, the file is set to liferay-multi-vm.xml, to implement caching in a non-clustered Studio implementation. When you uncomment this property in portal-ext.properties, which changes the configuration file to liferay-multi-vm-clustered.xml, then the cache is synchronized with the other Studio instances in the Studio cluster.
`org.quartz.jobStore.isClustered`	Enables clustering of Studio instances on the built-in Quartz job scheduling engine.

Setting

Description

net.sf.ehcache.configurationResourceName

The name and location of the XML configuration file for Hibernate caching. Hibernate is used by Studio to read from and write to the Studio application database.

In the default portal.properties file, the configuration file is set to hibernate.xml, to implement caching in a non-clustered Studio implementation.

When you uncomment this property in portal-ext.properties, which changes the configuration file to hibernate-clustered.xml, then Hibernate synchronizes the cache with the other Studio instances in the Studio cluster.

ehcache.multi.vm.config.location

The name and location of the XML configuration file for Ehcache.

In the default portal.properties file, the file is set to liferay-multi-vm.xml, to implement caching in a non-clustered Studio implementation.

When you uncomment this property in portal-ext.properties, which changes the configuration file to liferay-multi-vm-clustered.xml, then the cache is synchronized with the other Studio instances in the Studio cluster.

org.quartz.jobStore.isClustered

Enables clustering of Studio instances on the built-in Quartz job scheduling engine.

These configuration files are configured to automatically detect the other Studio instances in the Studio cluster, and to use IP address 233.0.0.1 and port 4446 to send the updated cache information.