Using Servers

Document created by Chris Sommerstad Employee on Jul 20, 2017Last modified by B-F-F08DRX on Oct 11, 2017
Version 3Show Document
  • View in full screen mode

All of the components of the SOASTA CloudTest architecture are services-based and can be installed on different physical servers to maximize scale and performance. While most SOASTA CloudTest installations use the same server for all SOASTA Web services—it is possible to have the SOASTA CloudTest user interface, the SOASTA Coordinator (the server side of SOASTA Conductor), and the SOASTA CloudTest Repository on different servers.

In many cases, SOASTA staff will configure servers on your behalf based on information you provide. The following instructions specify the necessary information for a user with Administrative privileges to configure a new server or a given server in the Servers list.

Creating a New Server

In the following steps, create a server using the New Server dialog box. If necessary, after server creation, perform any additional steps using the servers lower panel tabs (e.g. select the given server in the Servers list).

One common use of the New Server process is to create additional servers other than on the main CloudTest instance. For example, users may define an external Maestro on a Windows machine for use with Integration Windows Authentication. There are many, many reasons why a server is defined other than on the main instance. Servers can be configured for use with one service (e.g. such as a Maestro or Results Server) or many.

  1. Select Central list > Servers .
    1. Click New.
    2. In the New Server dialog box, define the following required settings:
      • Select from among configured locations
      • Give the server a name (the name may be such that it indicates its own purpose, such as "Windows Maestro" for an external Maestro on a Windows server).
      • Specify the host name of the machine where the server runs
      • Specify IP Address of the the machine where the server runs

If “localhost” is specified in the Repository and Results Service URLs of the Main CloudTest instance, then it must be replaced by the IP address of the main serve when definining a remote server. Otherwise, the remote Maestro server cannot gain access to the repository and results of the CloudTest main server.

  • Location

Note: A Location must exist prior to server creations. Create a Location before attempting to create a server. See Using Locations.

Specify a SOASTA CloudTest location for this server from the list of configured locations. This server will respond to test compositions specifying that location.

  • Name

Type a name for the Server. For example, QA Server Lab 1 might be one in a series of servers.

  • Description

Optionally, provide a description that identifies the server.

  • Host Name/IP Address

Specify a host name or IP Address for the server.

  • Enabled

Specify whether this server is enabled, or active, by checking or unchecking the box.

  • Services

Specify the SOASTA CloudTest services for this server. To use the default location for SOASTA CloudTest, simply tick the box for each. Click "Specify additional URLs outside of the location" if the additional services are not installed on this physical server.

  • Test Server

Test Server is a test engine, implemented as a massively multi-threaded service, which executes all or parts of a complex test composition. A single Test Server node is capable of sending and validating responses to thousands of http messages per second. Multiple Test Servers can be combined to each execute parts of a large load test that can scale out to tens and hundreds of thousands of virtual users. Test Servers can be geographically distributed and single test compositions can run geographically distributed while still producing a single integrated set of test results and analytics.

  • Repository

The Repository is the underlying database layer for SOASTA CloudTest.

  • Results

The Results Service generates all of the analytic data presented via the Analytic Dashboard widgets.

  • Coordinator

The Coordinator is vital for those tests that involve the use of:

  • Browser actions
  • HTTP recording
  • HTTPS recording
  • Monitoring sessions

Specifically, those monitoring sessions that involve the use of the Conductor (you can monitor without the Conductor which would also mean without the Coordinator).

  • Monitor

This service provides resource monitoring (hardware, network, load balancer, firewall, Web server, database, application server, content management system, etc.).


Viewing and Editing Server Settings


  1. To view server settings for a given item, select Central > Servers, and then select the server in the list.

The server settings are displayed in the sub-panel with the General tab displayed.

  1. The General tab settings include the server name, description, host name, IP Address, and location.Make changes, if necessary, and then click the Services tab to proceed.

  1. The Services tab displays the currently configured service locations for this server. Make changes, if necessary, and proceed to the Settings tab.

  1. The Settings tab defines additional settings based on the values defined within the Server Classes per service.

For example, select the Test Server service from the Services drop-down.

HTTP.MaxReceiveContentLength has a default value of -1.

Checking Server Dependencies

The Dependencies tab displays those objects currently dependant on this server. The server cannot be deleted while dependent objects use it. For example, a test composition that uses this server will prevent deletion of the server to which it is bound.

Using Check Servers

You can check the connectivity of your Servers by clicking the Check Server tab.

Error conditions for check servers include:

  • Incorrectly configured Server List (i.e. user error).
  • Network issue outside of our control (i.e. hardware failure or unreliable network connectivity)
  • One of the servers is not running.

Alternately, select a Server in the Server list and then click the Check Servers tab in the sub-pane.

Check Servers can also be accessed from the Server Instances list sub-pane.


Terminate, Reboot, and Replace Servers (Cloud Only)

You can terminate (shut down), reboot, and replace servers from the Servers list sub-pane while in cloud-based environments. This UI is hidden in a physical appliance setup.

You can select Central list > Servers and then select the server from the list that you want to perform an action on.

Once the server sub-pane appears, click the Check Server(s) tab.

From the sub-pane, select one or more servers in the list, and then access the context menu by right-clicking.

When you apply an action to selected server(s), a prompt appears to confirm the action before it is completed.

Orphaned Servers

The Orphaned Servers tab appears in the sub-pane for Servers and Server Instances.

The Orphaned Servers tab allows you to manage servers that, for any reason, CloudTest is no longer aware of. For example, when working with Amazon EC2, the Orphaned Servers list may include servers that were not launched by SOASTA CloudTest at all. You can right-click any server in this list to terminate it.

Default Grid Tagging


As of SOASTA 56.15, CloudTest will tag every grid deployed to help you monitor CloudTest's interactions with your AWS account. All tag information will be available in your AWS console and will look something like the image below: