Optimize 10.5 | webMethods Optimize Documentation | Configuring BAM | Managing webMethods Optimize Environments | Configuring Logical Servers | Analytic Engine Clustering | Defining Analytic Engine Cluster Settings
 
Defining Analytic Engine Cluster Settings
There are two types of Analytic Engine cluster configurations used for Optimize systems, depending on the number of available Analytic Engines and whether or not you have configured a Terracotta Server Array. Note that if you want to use Analytic Engine clustering, you must have a TSA:
*Non-clustered - A system configuration in which there is no TSA and a single local Analytic Engine for all data processing.
*Clustered - Used when there is a TSA and one or more Analytic Engines in a system configuration. All the data is maintained on the TSA and handed to the Analytic Engine nodes when those nodes are working on the data.
After your machines are configured appropriately, you must update the environment configuration as described in the following procedure.
*To configure the Terracotta Server Array setting on the My webMethods Edit Environment page
1. Under the Default Settings node in the configuration tree (on the Configure Servers tab), click Terracotta Server Array Configuration.
2. On the Terracotta Server Array for Environment Default Settings panel, type the URL for the TSA in the Terracotta Server Array URL field.
Typically, the format for a single node TSA URL is as follows: host:port
For a multiple node TSA, the URL would use the following format: server_host1:port,server_host2:port
3. Click Save to save changes or click Cancel to discard any changes you have made in this settings area.
If you click Finish without clicking Save, any changes made to the settings will be lost.
4. To configure another logical server subcomponent, click the name of that subcomponent in the configuration tree.
5. Click Finish to close this page and return to the Define Environments page.
If you receive an error indicating that one or more machines cannot join the cluster, you may need to change the cluster port to a different setting.