In this procedure you create an Hyperic group of multiple tc Runtime instances. You can then deploy a Web application to the group in a procedure similar to Deploy a Web Application to a tc Server Runtime Instance, and Hyperic does the work of deploying the Web application to each member of the group. Similarly, you can stop, start, and restart all the servers in the group with a procedure similar to Restart a tc Runtime Instance.
Using Hyperic groups saves a lot of time if you need to control multiple tc Runtime instances running on many different computers, as well as deploy and manage their applications.
It is assumed in this procedure that you have at least two tc Runtime instances running and that you have added them to the Hyperic inventory. See Creating a New tc Runtime Instance and Getting Started with the Hyperic User Interface.
It might take a while for the Hyperic user interface to auto-detect a new tc Runtime instance after you start it. You can force a new auto-discovery to speed the process.
To force an auto-discovery, browse to the platform resource where you started the new tc Runtime instance. For example, in this tutorial the platform resource is called juliet-desktop. Then click New Auto-Discovery in the Tools Menu. In the Quick Auto-Discovery Scan section, click OK. The new tc Runtime instance should show up in the Auto-Disocvery portlet of the main Dashboard very shortly. You can then add it using the Add to Inventory button as usual.
Click the Resources > Browse link at the top of the Hyperic user interface.
Click the Servers (X) link to
list all the servers in your resource inventory. The tc Runtime
instances are listed as Server Type
SpringSource tc Runtime
SpringSource tc Runtime 7.0.
If there are many server resources listed in the table, you can narrow down the list by selecting a server type in the Search drop-down list, then clicking the green arrow all the way to the right of the Search line.
For each tc Runtime instance you want to include in the new group, check the box to the left of the instance's entry in the table.
Note that the Hyperic UI itself internally uses an instance of
tc Runtime (called
hq-server); you should not change the
configuration of this instance or add it to your groups.
The following graphic shows how to group together two tc Runtime
tc Runtime anotherserver and
In the Group Manager window, click Add to New Group.
In the General Properties section, enter a name for the group,
tcserverGroup and an optional description and
location, such as
Depending on the members of the group, Hyperic creates a
Compatible Group/Cluster or
Mixed Group. The
first type of group consists of a single type of server, such as
only tc Runtime instances. The second mixed group
consists of different types of servers, such as both tc Runtime
instances and Apache Tomcat servers.
To stop or restart the group of servers, and deploy an application to the group:
Click Resources > Browse at the top of the Hyperic user interface.
Click Compatible Groups/Clusters if your group consists of the same servers, or Mixed Groups if your group consists of different types of servers.
In the table, click on the name of the group.
To stop or start all the servers in the group, click the
Control tab, then follow the steps
for controlling a single server, as described in Restart a tc Runtime
Instance. The breadcrumbs at the top of the console page list
the group name (
tcserverGroup in this case) rather than
the tc Runtime instance name.
To deploy and manage applications on all servers in the group, click the Views > Application Management tab, then follow the steps for deploying or managing the applications of a single server, as described in Deploy a Web Application to a tc Server Instance.
In this release of tc Server, you cannot update the configuration
of a group of tc Runtime instances from the Views
> Server Configuration tab. You can update the
configurations of servers in a group using the
command-line interface. See "Using the tcsadmin Command-Line Interface"
in vFabric tc Server Administration Guide.