Customizing Studio database caching

You can customize Studio's database cache configuration, if needed.

The most likely change you'd want to make would be to update the IP address and port number at the top of each configuration file: 

<cacheManagerPeerProviderFactory
		class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
		properties="peerDiscovery=automatic,multicastGroupAddress=230.0.0.1,multicastGroupPort=4446,timeToLive=1"
		propertySeparator=","
	/>

Note that any changes you make must be made on all Studio nodes.

To customize Studio's database caching:

  1. Extract the default files from the ehcache directory in portal-impl.jar.

    The file is in the WEB-INF/lib directory, which is located in endeca-portal.war, which is in bdd-studio.ear.

  2. Update the files as needed.
    To ensure that Studio uses the correct files, you may want to rename the customized files to something like:
    • hibernate-clustered-custom.xml
    • liferay-multi-vm-clustered-custom.xml
  3. Deploy the customized files:
    1. Undeploy bdd-studio.ear.

      Use the appropriate method to undeploy the file based on whether you auto-deployed the .ear file or installed it.

    2. Update bdd-studio.ear to add a subdirectory APP-INF/classes/ehcache/ that contains the customized XML files.
    3. Redeploy the updated .ear file.
  4. If needed, update portal-ext.properties to reflect the customized file names: 
    net.sf.ehcache.configurationResourceName=/ehcache/hibernate-clustered-custom.xml
ehcache.multi.vm.config.location=/ehcache/liferay-multi-vm-clustered-custom.xml