Child pages
  • Integrating Terracotta DSO
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

About Terracotta Documentation

This documentation is about Terracotta DSO, an advanced distributed-computing technology aimed at meeting special clustering requirements.

Terracotta products without the overhead and complexity of DSO meet the needs of almost all use cases and clustering requirements. To learn how to migrate from Terracotta DSO to standard Terracotta products, see Migrating From Terracotta DSO. To find documentation on non-DSO (standard) Terracotta products, see Terracotta Documentation. Terracotta release information, such as release notes and platform compatibility, is found in Product Information.

Unknown macro: {div9}
Release: 3.6
Publish Date: November, 2011

Documentation Archive »

Integrating Terracotta DSO

Introduction

Terracotta Distributed Shared Objects (DSO integrates with many of the most powerful Java technologies available today. This document includes resources and provides tips on integrating Terracotta DSO with popular frameworks and libraries.

To learn about integrating with Terracotta products, including Ehcache and Sessions, second-level cache for Hibernate, and Spring, see the .

Integrating with a specific application server such as Tomcat is covered in . For example, clustering a web application on Tomcat is covered in Clustering Web Applications with Terracotta in .

How Integration Works

Integration with Terracotta DSO is implemented using Terracotta Integration Modules (TIMs), which are installed along with Terracotta clients on the application servers in a cluster. A TIM is a set of configuration elements packaged together as a single, includable module within the Terracotta configuration. Including a TIM in your project is as simple as adding one line to a configuration file.

In the following example, support for clustering [Spring Security 2.0] with Terracotta is achieved by adding the following line to the Terracotta configuration file:

 <module name="tim-spring-security-2.0" />  

While a Terracotta configuration file resides with a Terracotta server instance, TIMs are never installed on Terracotta server instances. This is because applications are never integrated with Terracotta server instances, only with Terracotta clients. Terracotta clients get their TIM configurations when they fetch the Terracotta configuration file from a Terracotta server instance or by having their own Terracotta configuration files.

TIMs are available for many software products, including [Hibernate], [Tomcat], and the Terracotta Distributed Cache.

The easiest and most efficient way to download and install TIMs is through the
TIM Update Center.

Other Integration Resources

  • The TIM Manual – What if your technology isn't listed? Build your own Terracotta Integration Module (TIM)! Also learn how to manage TIM versions in accordance with Terracotta policies.
  • [Enterprise Services] – If a TIM is not available for your technology and you can't devote resources to build your own, we can custom-build it.
  • Certified platforms page – A one-page list of certified platforms for the current release.
  • [The Terracotta Forge] – One of the most effective resources available for successfully integrating your project with Terracotta is the Terracotta Forge.
Unknown macro: {div9}
  • No labels