Solution
When Integration Server cannot connect to the Terracotta Server Array, do the following:
![*](bullet.gif)
Start the
Terracotta Server Array if it is not already started.
![*](bullet.gif)
Make sure the machine on which
Integration Server is running can reach the
Terracotta Server Array host specified in the tc-config.xml file.
![*](bullet.gif)
Test the connection by pinging the servers in the
Terracotta Server Array. The servers are listed in the
Terracotta Server Array URLs list on the
Settings > Caching > Add Cache Manager screen.
![*](bullet.gif)
Make sure the same version of
Terracotta software is running on the client and the
Terracotta Server Array. Check the ehcache.log file located in the
Integration Server_directory /instances/
instance_name/logs directory. If the
Terracotta software version numbers are not the same, a version mismatch error will be logged and
Integration Server shuts down.
![*](bullet.gif)
Make sure the
Integration Server has a valid
Terracotta license key. If the
Integration Server does not have a valid license key, you can enable clustering on the
Integration Server; however, it will not be able to connect to the
Terracotta Server Array. When the
Integration Server starts up, it will write an error to the server log and then take the action associated with the selected option for the
Action on Startup Error parameter. You can add a
Terracotta license key by placing the
Terracotta license file into the
SoftwareAG_directory\common\conf directory of the
Integration Server. You must restart the
Integration Server after adding a
Terracotta license. Alternatively, you can use the
Settings > License > License Details > Edit page in
Integration Server Administrator to point to a
Terracotta license file at a different location. For more information about adding the
Terracotta license file, see
webMethods Integration Server Administrator’s Guide.