CloudTest provides five background services. Checking a box for a given service places the default URL value into the entry field for each checked box.
- Check the box beside a given service to use its default location. Alternate locations can be typed into the entry field. For each checked box in the list, ensure that the URL is as expected.
- Click the Key if the service requires HTTP authentication.
At this point, refer back to your network setup. If the individual servers in the location can be contacted from outside, then you are done. Otherwise, you will need to provide URLs that a server outside the location can use to contact CloudTest.
If individual servers cannot be contacted from external locations, due to firewall restrictions for example, then there must be some single host name or IP address that can be used. Typically, this is a load balancer. When using this setup, the location must include URLs that a machine outside the network can use to contact CloudTest web services.
If the individual servers within the location can be contacted from outside, then these URLs are optional.
- Test Server: The 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 be geographically distributed while still producing a single integrated set of test results and analytics.
- Repository: The Repository is the underlying database layer for 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.).