OneData 10.7 | Managing Master Data with webMethods OneData | Using Terracotta with webMethods Products | Installing and Configuring the Terracotta Server Array for Use with webMethods Products | Creating the tc-config File
 
Creating the tc-config File
The tc-config file is not installed with the Terracotta program files. You must create this file and configure it for your particular server array.
By default, a Terracotta server expects to find the tc-config file in the Software AG_directory /terracotta/server/bin directory. If you maintain the tc-config file in the default location, you must place an identical copy of the tc-config file in the Software AG_directory /terracotta/server/bin directory of every server in the array. (Typically, you create the tc-config file on one server and then copy it to the other servers in the array.) Alternatively, you can place the tc-config file in a central location where all servers in the array can access it. If you use this approach, you must specify the location of the tcconfig file when you invoke the start-up script on each server.
Below is a sample file you can use as a template to create the tc-config file for your Terracotta Server Array. This sample includes settings in the <tc-properties> and <clients> sections that are required by webMethods products. The <servers> section in this sample defines an array consisting of two mirrored Terracotta servers. Revise this section as needed to define the configuration of your particular server array. For more information about defining the configuration of the Terracotta Server Array, see BigMemory Max product documentation for 4.1 at http://terracotta.org/documentation/4.1/bigmemorymax/overview.
For complete information about creating and configuring the tc-config file, see the section on configuring the Terracotta Server Array in the Terracotta product documentation.
<tc:tc-config xmlns:tc="http://www.terracotta.org/config">
<!-- Replace the host and name values for your server -->
<server host="host" name="name">
<data>server-data</data> ]
<logs>server-logs</logs>
<!-- Adjust the data storage size for the total amount of data -->
<!-- being stored by the server array up to the maximum allowed -->
<!-- by your Terracotta license.-->
<dataStorage size="20g">
<!-- hybrid mode is required by the Terracotta license provided -->
<!-- with webMethods products. -->
<!-- Terracotta server off heap is required to hold the keys -->
<!-- used for all caches. -->
<offheap size="2g"/>
<hybrid/>
</dataStorage>
</server>
<server host="host" name="name">
<data>server-data</data>
<logs>server-logs</logs>
<!-- The data storage settings must be identical for each server -->
<!-- in the mirror group. -->
<dataStorage size="20g">
<offheap size="2g"/>
<hybrid/>
</dataStorage>
</server>
<!-- This replaces the permanent-store attribute -->
<!-- from the 3.7.X version. This is not required to be enabled. -->
<!-- The setting applies to all servers in the mirror group. -->
<restartable enabled="true"/>
</servers>
<clients>
<logs>%(com.softwareag.tc.client.logs.directory)</logs>
</clients>
</tc:tc-config>
The minimum off-heap memory required for webMethods clustering in hybrid mode is 2GB. For details about the off-heap memory configuration required for non-hybrid deployments, distributed caching and other applications, see the Terracotta product documentation.