Because tc Server is made up of a variety of components that can be hosted on different computers, the procedure for installing tc Server differs depending on your own scenario. SpringSource tc Server is made up of the following components that can be installed separately on different computers:
Note: Not all components are supported on all platforms; see Supported Configurations for details.
The simplest scenario is where you install all components on the same computer. In this case, the computer acts as a host for the tc Server application server and its deployed applications as well as a host to the AMS server and agent used to manage the tc Server and its deployed applications.
In the preceding figure, AMS is managing just one tc Server instance. AMS can, of course, manage multiple instances, as well as manage other kinds of servers. Note that, because the tc Server instance are all on one computer, you only need to install one AMS agent.
A slightly more complicated scenario is where you install multiple tc Server instances on one computer, say computerA, and the AMS server on computerB. In this case, you must install the AMS agent on computerA so that the AMS server is able to manage the tc Servers on computerA from computerB. SpringSource refers to computerA as a managed node.
Another scenario is where you continue to host the AMS server on computerB, but want to install tc Server application servers on many computers, possibly of different platforms such as Unix and Windows. In this case you must also install the platform-appropriate AMS agent on each computer (managed node) that hosts the tc Server instances.
In the following figure, for example, computerC might be a Windows platform while all the rest of the computers are Unix. Also note that each computer has a different set of tc Servers installed, but only one AMS agent. In the figure, all computers except computerB are managed nodes.