Software AG has developed some configuration guidelines and suggestions to maximize Optimize system performance when using a Terracotta Server Array. Some of these configuration changes are requirements for Analytic Engine clustering, and some are additions and modifications to a standard Terracotta configuration that testing has shown will enhance system performance in typical clustered environments. This section describes these guidelines and the benefits and trade-offs involved in various Terracotta configurations. This section does not describe the specific procedures required for setting up a TSA in a particular environment as those procedures are beyond the scope of this document. For information on setting up a TSA, see the Terracotta website and associated documentation.

Note that if you are setting up a clustered system with various components running under different operating systems, you must be aware of and plan for some complications in regards to Terracotta and timestamps. For instance, you can configure your TSA on hardware running under Linux and have your Analytic Engines on hardware running Microsoft Windows. In such cases, problems can arise due to the fact that the different operating systems use different timestamp protocols, and because Terracotta uses these timestamps to keep track of data. If you are configuring a system that uses different operating systems you must be aware of these issues and implement the appropriate strategies to deal with them. Refer to the Terracotta discussion boards for information about identifying and dealing with these issues.

You must consider the following areas when you customize your Terracotta installation in an Analytic Engine clustered environment, based on system configuration considerations and desired performance characteristics:

For detailed information about customizing Terracotta, see the Terracotta website and associated documentation.