Release: 2.4 Previous Releases
Publish Date: October, 2007

rate-6226455-71433

Article Rating?

1

2

3

4

5

Multi-Node Guide

Description
Getting Started
Running the sample server on server-host
Running the Pojo Sample Launcher on clientA and clientB
What is really happening?
Monitoring the Terracotta Server
Appendix

Contacting Terracotta
Platform Support

Description

This guide details the steps required to run the Terracotta samples on multiple machines. When you're finished with this guide you will have the Shared Editor sample running on two different machines, using a Terracotta server on yet another machine.

Common instructions:

Install kits on target machines
Run sample server

For using the Sample Launcher:

run sample launcher on clients
Use File|Servers dialog to specify server host machine
Run Shared Editor sample

For command-line:

set TC_SERVER environment variable to server-host:9510
run Shared Editor sample using command-line script

Monitor server activity:

Start AdminConsole, connecting to server

Getting Started

Let's assume for the purposes of this guide that the Terracotta samples will be run on two different computers named clientA and clientB, and that the Terracotta server will be run on a computer named server-host.

Install the Terracotta distribution on each of these machines. Currently Terracotta clients and server must be of the same version.

Running the sample server on server-host

On server-host, run the sample server by executing the TC_HOME/samples/start-demo-server script appropriate for your host environment, .bat for Windows and .sh for everything else.

Running the Pojo Sample Launcher on clientA and clientB

On clientA and clientB, run the graphical Pojo SampleLauncher by executing the TC_HOME/tools/pojo/samples script. The SampleLauncher will appear:

Use the File|Servers menu to specify server-host as the remote server for the sample clients:

The samples will now use the Terracotta server on server-host instead of the local server that is automatically started by the SampleLauncher. Launch the Shared Editor sample.

What is really happening?

The Remote server item of the SampleLauncher's Server dialog simply causes the tc.server Java system property to be passed to the Terracotta sample client. The tc.server property is known as a server specification, a comma-separated list of DSO server addresses. A DSO server address is a DSO server hostname followed by an optional DSO server port. For example,

server1-host:9510,server2-host:9510

In our case the SampleLauncher passes -Dtc.server=server-host:9510 to the sample client, causing it to use the specified server specification in place of the servers listed in the sample's configuration file.

If you wish to run the samples using the command-line scripts, you can simply set the TC_SERVER environment variable prior to invoking the sample runner scripts:

$ set TC_SERVER=server-host:9510
$ TC_HOME/samples/pojo/sharededitor/run

The sample runner scripts make use of the dso-env helper script to setup the JAVA_OPTS required to activate the Terracotta runtime. When dso-env sees that TC_SERVER has been set, it will include that value as the tc.server Java system property.

Monitoring the Terracotta Server

Now that you have the samples running on multiple nodes, you can start the AdminConsole by running the TC_HOME/bin/admin script. Specify server-host in the Hostname field and click the Connect button. You're can now monitor the server activity generated by the running samples.

Appendix

Contacting Terracotta

Contact Terracotta at the following:
Web site: http://www.terracotta.org
Online forums: http://forums.terracottatech.com/forums/
Information: info@terracottatech.com

Platform Support

See Platform Support for information on which platforms are supported by Terracotta.
See Integrations to see the status of integrations with third-party technologies.

Copyright Information

This publication (the "Documentation") and the Terracotta software which it describes (the "Software") are protected to the maximum extent permitted under applicable law, including but not limited to, the regulations set forth in Title 17 of the United States Code, and California law. This Documentation, or any parts thereof, may not be reproduced in any form, by any method, for any purpose, without the express written consent of Terracotta. Terracotta makes no warranty, either express or implied, including but not limited to any implied warranties of merchantability or fitness for a particular purpose, with respect to the Software discussed in this Documentation, and the Documentation itself (collectively, "the Materials"). The Materials are made available solely on an "as-is" basis. In no event shall Terracotta be liable to anyone for special, collateral, incidental, indirect, punitive, exemplary, or consequential damages in connection with, or arising from the purchase or use of, the Materials. Under no circumstances and regardless of the cause of action alleged, shall Terracotta's liability exceed the purchase price of the Software described herein. Terracotta reserves the right to revise and improve its Software and Documentation as it deems fit. The Documentation describes the state of the Software at the time of publication.

Trademarks
"Terracotta," the stylized "T" logo, and "Open Terracotta" are trademarks of Terracotta. All other brand names, product names, or trademarks belong to their respective holders. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. All other brand names, product names, or trademarks belong to their respective holders.

Government Use
Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR 12.212 (Commercial Computer Software-Restricted Rights) and DFAR 267.7202 (Rights in Technical Data and Computer Software), as applicable.