Monitoring Terracotta BigMemory Max from Command Central
Monitoring a Single Terracotta Server from Command Central
To show the status of a Terracotta Server, the Terracotta Server name must be entered into the tc-config.xml file of Command Central (Terracotta Server Instance page > Configuration tab). By default the tc-config.xml is configured to your machine host name and therefore can't address the Terracotta Server.
1. Add the tc-config.xml to <installDir>\Terracotta\server\wrapper\conf\.
2. Update the server name in the <installDir>\Terracotta\server\wrapper\conf\custom_wrapper.conf for parameter.6 and parameter .13.
3. Use the scripts
<installDir>\Terracotta\server\wrapper\bin\startup.bat to start the Terracotta Server and ...
<installDir>\Terracotta\server\wrapper\bin\shutdown.bat for stopping the server.
The Command Central configuration for the Terracotta Server instance must be set as follows:
1. Login to Command Central and navigate to Terracotta Server instance page.
2. Select the Configuration tab of the Terracotta instance.
3. Select the tc-config and then click on TC-config.
4. Select the Edit button and replace the content with the server's tc-config.xml file content
or
Update the tc-config with the desired configuration.
5. Save these settings.
6. Choose the Terracotta Server's name in the dropdown.
7. Click the default Server name.
8. Update the name to the name of the Terracotta Server as per tc-config.xml file and Save this server name.
9. Start the Terracotta Server in case it is not yet started.
10. Select the Overview tab and click Refresh to display the Terracotta Server's running status.
Monitoring Multiple Terracotta Servers from Command Central
If the scenario consists of several Terracotta Servers then each Server requires a different installation with the same tc-config.xml added to <installDir>\Terracotta\server\wrapper\conf\.
1. Update the server's names in <installDir>\Terracotta\server\wrapper\conf\custom_wrapper.conf for parameters .6 and parameters .13.
2. Disable the auto-restart feature of the wrapper.
Note:
The auto-restart feature of the wrapper must be disabled to avoid interfering with any fail-over or recovery behavior of the Terracotta Cluster.
Edit
<SAG>/Terracotta/server/wrapper/conf/custom_wrapper.conf
and set the following property ...
wrapper.disable_restarts.automatic=TRUE.
3. Use the following scripts to start and to stop the Servers:
<installDir>\Terracotta\server\wrapper\bin\startup.bat
<installDir>\Terracotta\server\wrapper\bin\shutdown.bat
Next Step is to add another Terracotta Server into the same Command Central:
1. In Command Central Home > Installations > All
Choose + to add a Terracotta installation.
2. Enter the host name and select whatever fits best:
Platform Manager is already installed or Install Platform Manager remotely.
3. Enter the SPM port number, username, password.
Note:
To find out the SPM Port Number open the file
<SAG>\profiles\SPM\configuration\com.softwareag.platform.config.propsloader.
As an example
\com.softwareag.catalina.connector.http.pid-8312.properties
means that 8312 is the http port for SPM.
4. Enter a Display Name of your choice and choose Finish.
To finish the set-up you need to configure Command Central for the Terracotta instances as follows:
1. Login to Command Central and navigate to Terracotta Server instance page.
2. Select the Configuration tab of the Terracotta instance.
3. Select the tc-config and then click on TC-config.
4. Select the Edit button and replace the content with the server's tc-config.xml file content
or
Update the tc-config with the desired configuration.
5. Save these settings.
6. Choose the Terracotta Server's name in the dropdown menu.
7. Click the default Server name.
8. Update the name to the name of the Terracotta Server as per tc-config.xml file and Save this server name.
9. Start the Terracotta Server in case it is not yet started.
10. Select the Overview tab and click Refresh to display the Terracotta Server's running status.
Monitoring a Secure Terracotta Server from Command Central
To monitor an SSL enabled Terracotta Server from Command Central follow these steps:
1. Allow the SPM plugin to trust the outbound connection to the secure Terracotta server. To do that, you need to import the server’s certificate to the SPM’s JVM’s cacerts file present at <installDir>/jvm/jvm/jre/lib/security/cacerts. Import the certificate with the java keytool command:
Keytool -import -alias <server-alias> -file <server-cert-file>
-keystore <cacerts-file>
or
2. Restart SPM for the changes to take effect.
3. Provide a truststore location for the Terracotta server. This enables the server to become part of one cluster and allows the secured TMC to connect to it. To do that:
Login to Command Central and navigate to the Terracotta server instance page.
Click on the
Configuration tab and select the
Truststore Location option from the dropdown menu.
Select a Truststore Location under
Name column.
Click the
Edit button and provide the path of server’s truststore location.
Save the changes and restart the server.
or
Update the property present in the <installDir>/Terracotta/server/wrapper/conf/custom_wrapper.conf file:
wrapper.java.additional.9=-Djavax.net.ssl.truststore=”path_to_truststore”
where path_to_truststore is a valid path to the server's trustore location.
4. Similar steps can be followed for other servers in a secured cluster.