What are the different components that make SilkCentral and what is their role?



What are the different components that make SilkCentral and what is their role?



What are the different components that make SilkCentral and what is their role?


SilkCentral consists of the following components:

Front-end Server

The front-end server is responsible for the graphical user interface. It"s based on HTML and accessible with any web browser, such as Internet Explorer or Netscape Navigator. A user sends an appropriate HTTP request to the front-end server and receives a login page for authentication. After the user successfully logs in, he is able to use the corresponding application depending on the respective user rights. The front-end server is able to operate as a stand-alone HTTP server, or it can also be attached to a web server like IIS via ISAPI filter.

Application Server

The application server is needed to synchronise tasks such as distribution of schedules, control of execution servers and management of database configuration. These tasks need a centralised agency to ensure consistency and reliable behaviour of the application. The application server also evaluates results, saves them to the database and sends alerts depending on success conditions.

Execution Server

The execution server executes SilkTest and/or SilkPerformer tests that are scheduled by an authorized user. The user is responsible for the proper configuration of execution servers and additional resources that may be required for test executions. The system allows for the installation and configuration of multiple execution servers working independently of one another. Execution servers are independent of the application server. If they lose their connection or if the application server is down, the execution servers continue executing their scheduled test definitions.

Charting Server

The Chart Server is used to generate charts that are viewed in reports. The system allows for the configuration of a pool of Chart Servers. A built-in load balancing mechanism uses the pool to distribute chart generation.


System persistency is implemented using a RDBMS (Relational Database Management System).

SilkPerformer Agents

Agent computers are assigned to a particular SilkPerformer project from the pool of SilkPerformer Agent computers available to the controller computer. Together with SilkCentral Test Manager, the controller computer is an execution server. SilkPerformer Agent computers host the virtual users that are run during load tests. As many Agent computers as necessary can be added to a SilkPerformer project so that the required quantity of virtual users can be run. Configuration of Agents is done using SilkPerformer. See the SilkPerformer documentation for details on configuring Agents. SilkPerformer Agents are only supported by Test Manager.

SilkTest Agents

The same rules that apply to SilkPerformer Agents apply to SilkTest Agents, only SilkTest Agents host SilkTest tests. SilkTest Agents are only supported by Test Manager.

Old KB# 24875
Comment List
Related Discussions