SilkCentral
Administration Module
2009 SP1
Borland Software Corporation 4 Hutton Centre Dr., Suite 900 Santa Ana, CA 92707
Copyright 2009 Micro Focus (IP) Limited. All Rights Reserved. SilkCentral Test Manager contains derivative works of Borland Software Corporation, Copyright 2004-2009 Borland Software Corporation (a Micro Focus company). MICRO FOCUS and the Micro Focus logo, among others, are trademarks or registered trademarks of Micro Focus (IP) Limited or its subsidiaries or affiliated companies in the United States, United Kingdom and other countries. BORLAND, the Borland logo and SilkCentral Test Manager are trademarks or registered trademarks of
Borland Software Corporation or its subsidiaries or affiliated companies in the United States, United Kingdom and other countries.
All other marks are the property of their respective owners. October 2009
Getting Started
Getting StartedConcepts ... 11
Introduction to SilkCentral Administration Module ... 12
SilkCentral Architecture ... 13
Welcome to SilkCentral Test Manager ... 16
SilkCentral Issue Manager ... 17
Access and Licensing ... 18
Help on Help ... 19
Procedures ... 20
Configuring the Application Server ... 21
Configuring Secure Connections with Microsoft IIS ... 22
Specifying a Location for the Application Server ... 23
Connecting to a Repository ... 24
Enabling the TCP/IP Protocol for MS SQL Server 2005 ... 25
Creating a New Repository ... 26
Concepts
ConceptsConfiguring the System ... 31
Secure Web Server Connections with SSL ... 32
Application Server Location ... 33
SilkCentral Repositories ... 34
Initial Login ... 36
System Administrator Accounts ... 37
Chart Server Location ... 38
Mail Host Location ... 39
SMS Host Settings ... 40
PageGate Gateway Access ... 41
SNMP Trap Notification ... 42
System Proxies ... 43
LDAP Authentication ... 44
SilkPerformer Load-Test Agent Clusters ... 46
Configuring the Application ... 47
User Roles and Permissions ... 48
User and Group Accounts ... 53
Projects ... 54
Project Templates ... 55
Locations ... 56
Execution Server Setup ... 57
VMware Lab Manager Virtual Configurations ... 59
Report Templates ... 60
BIRT C 61 Audit Log ... 62
Server Log Files .. 64
Task Management Tools ... 65
Products and Platforms ... 66
Value Lists ... 67
Global Schedules 68
File Pool ... 69
Time Zones ... 70
Configuring Advanced Settings ... 71
Login Options ... 72
Service Manager . 73 Suspicious Execution Duration ... 75
Date and Time Formats ... 76
HTML Response Compression ... 78
Host Name Display ... 79
Log Levels ... 80
CVS Repository Access using Ext Method (using PuTTY) ... 81
Data Caching in Test Plan Unit ... 82
JMX Measures for LQM Reporting Updater ... 83
Procedures
ProceduresSystem Configuration . 87
Changing the Password of the System Administrator Account ... 88
Configuring a System Proxy ... 89
Configuring Access to the PageGate Gateway ... 90
Configuring LDAP Integration ... 91
Adding LDAP Servers ... 92
Editing LDAP Servers ... 93
Testing LDAP Servers ... 94
Deleting LDAP Servers ... 95
Configuring Load Test Agent Clusters Files ... 96
Uploading Load Test Agent Cluster Files ... 97
Deleting Load Test Agent Clusters Files ... 98
Editing Load Test Agent Cluster Files ... 99
Configuring Secure Connections with Microsoft IIS ... 100
Applying for a Certificate to use SSL ... 101
Applying the Certificate to IIS ... 103
Configuring Secure Connections with Tomcat Web Server ... 104
Configuring Settings for an SMS Host ... 106
Configuring SNMP Trap Notification ... 107
Connecting to a Repository ... 108
Enabling the TCP/IP Protocol for MS SQL Server 2005 ... 109
Creating a New Repository ... 110
Accessing an Existing Repository ... 112
Disconnecting from a SilkCentral Repository ... 113
Logging in for the First Time ... 114
Specifying a Location for the Mail Host ... 115
Specifying Locations for Chart Servers ... 116
Adding Chart Servers ... 117
Editing Chart Servers ... 118
Removing Chart Servers ... 119
Application Configuration ... 120
Integrating Task Management Tools ... 121
Integrating VersionOne in Test Manager ... 122
Managing Accounts and User Roles ... 123
Maintaining Group Accounts ... 124
Adding Group Accounts ... 125
Deleting Group Accounts ... 126
Editing Group Accounts ... 127
Maintaining User Accounts ... 128
Adding User Accounts ... 129
Deleting User Accounts ... 130
Editing User Accounts ... 131
Maintaining User Roles ... 132
Adding User Roles ... 133
Copying User Roles ... 134
Deleting User Roles ... 135
Editing User Roles ... 136
Managing Products and Platforms ... 137
Downloading Report Templates ... 138
Managing Builds ... 139
Editing Builds ... 141
Deleting Builds ... 142
Activating/Deactivating Builds ... 143
Sorting the Builds List ... 144
Managing Components ... 145
Adding Components ... 146
Editing Components ... 147
Deleting Components ... 148
Activating/Deactivating Components ... 149
Sorting the Components List ... 150
Managing Platforms ... 151
Adding Platforms ... 152
Editing Platforms ... 153
Deleting Platforms ... 154
Activating/Deactivating Platforms ... 155
Sorting the Platforms List ... 156
Managing Products ... 157
Adding Products ... 158
Editing Products ... 159
Deleting Products ... 160
Activating/Deactivating Products ... 161
Sorting the Products List ... 162
Managing Versions ... 163
Adding Versions ... 164
Editing Versions ... 165
Deleting Versions ... 166
Activating/Deactivating Versions ... 167
Sorting the Versions List ... 168
Managing the File Pool ... 169
Uploading Files From SilkPerformer ... 170
Uploading Files From a Browser ... 171
Configuring Global Schedules ... 172
Adding Global Schedules ... 173
Editing Global Schedules ... 174
Deleting Global Schedules ... 175
Activating/Deactivating Global Schedules ... 176
Scheduling Exclusions ... 177
Scheduling Definite Runs ... 178
Configuring Real Experience Monitoring ... 179
Maintaining Value Lists ... 180
Adding Value Lists ... 181
Editing Value Lists ... 182
Deleting Value Lists ... 183
Activating/Deactivating Value Lists ... 184
Sorting Values Within Value Lists ... 185
Managing Custom Report Templates With BIRT ... 186
Installing BIRT From SilkCentral ... 187
Configuring BIRT For SilkCentral ... 188
Establishing Database Access For a New Report Template ... 189
Considerations for Adapting Existing Report Templates ... 190
Uploading Report Templates ... 191
Updating Report Sources ... 192
Managing Locations ... 193
Adding Locations ... 194
Deleting Locations ... 196 Managing Projects ... 197 Adding Projects ... 198 Editing Projects ... 199 Activating/Deactivating Projects ... 200 Copying Projects ... 201 Deleting Projects ... 203
Managing Report Templates ... 204
Downloading Report Templates ... 205
Uploading Report Templates ... 206
Updating Report Sources ... 207
Setting and Editing Report Permissions and Associations ... 208
Deleting Report Templates ... 209
Setting Up Execution Servers ... 210
Configuring Physical Execution Servers ... 211
Working with VMware Lab Manager ... 213
Creating New Execution-Server Keywords ... 214
Assigning Keywords to an Execution Server ... 215
Activating or Deactivating Execution Servers ... 217
Deleting Execution Servers ... 218
Using the Audit Log ... 219
Viewing Server Log Files ... 220
Analyzing Server Log Files ... 221
Downloading Server Log Files ... 222
Deleting Server Log Files ... 223
Working with VMware Lab Manager ... 224
Configuring Access to VMware Lab Manager Servers ... 225
Configuring Virtual Execution Servers on VMware Lab Manager ... 226
Advanced Configuration ... 228
Using the SilkCentral Service Manager ... 230
Managing Which SilkCentral Services Shall Be Running At System Start ... 231
Starting or Stopping All SilkCentral Services ... 232
Starting or Stopping Individual SilkCentral Services ... 233
Starting The SilkCentral Execution Server As Windows Process ... 234
Viewing Log Files From The SilkCentral Service Manager Console ... 235
Accessing a CVS Repository using Ext Method (using PuTTY) ... 236
Changing Log Levels of the SilkCentral Servers ... 237
Configuring a Non-Standard SSL Port for Execution Servers ... 239
Configuring Login Options ... 240
Configuring the SilkCentral Test Manager Location in SilkCentral Issue Manager ... 241
Configuring the LQM Reporting Updater ... 242
Configuring the Report Update Interval ... 243
Customizing Date and Time Formats ... 244
Disabling The Caching of Host Name Resolutions ... 245
Disabling Unused Ports ... 246
Displaying or Hiding the Host Name in the Title Bar of Your Web Browser ... 247
Enabling/Disabling HTML Response Compression ... 248
Setting Maximum Number of MRU Reports ... 249
Reference
ReferenceUser Interface Reference ... 253
Database Settings Page ... 255
Login Page ... 257
Chart Servers Page ... 258
Email Notification Page ... 259
SMS Notification Page ... 260
PageGate Gateway Settings Page ... 261
SNMP Trap Settings Page ... 262
System Proxy Page ... 263
LDAP Servers Page ... 264
Load Test Agent Clusters Page ... 266
VMware Lab Manager Servers Page ... 267
User Settings Page ... 268
Group Settings Page ... 270
Roles Settings Page ... 271
Project Settings Page ... 272
Copy Project Dialog ... 273
Location Settings Dialog ... 275
Execution Server Settings Page ... 277
Report Templates Page ... 279
Audit Log Page . 280 Front-end Server Log Page ... 281
Application Server Log Page ... 282
Execution Server Log Page ... 283
Products Configuration Page ... 285
Platform Configuration Page ... 286
List of Values Configuration Page ... 287
Schedules Configuration Page ... 288
File Pool Page .. 289
General Reference ... 290
BIRT Data Source Settings ... 291
Additional Settings for SilkTest Executions ... 292
JMX Measures for Caching in Test Plan Unit ... 293
JMX Measures for Monitoring the LQM Reporting Updater ... 294
Getting Started
This section contains an overview of SilkCentral and its components.
In This Section
Concepts
Topics in this section contain the concepts you need to get started using SilkCentral.
Procedures
Concepts
Topics in this section contain the concepts you need to get started using SilkCentral.
In This Section
Introduction to SilkCentral Administration Module
This section provides an overview of SilkCentral and its components.
Help on Help
Introduction to SilkCentral Administration Module
The SilkCentral suite of products includes the applications SilkCentral Issue Manager (Issue Manager) and SilkCentral Test Manager (Test Manager). SilkCentral products, used individually or in combination, support the continuous and efficient quality assurance of your software development process. The Web-based products Issue Manager and Test Manager work together to deliver the information you require to make informed decisions about product readiness for shipment and live posting. They provide information on:
♦
Test coverage and results versus defined requirements♦
Component- and system-level risk assessment metrics♦
Defect tracking and closure dataThis information is vital for any person or group of people who are responsible for bringing a product or system into production.
In This Section
SilkCentral Architecture
Provides an overview of SilkCentral's architecture.
Welcome to SilkCentral Test Manager
Manage your testing, from requirements management, through test planning, text execution, code analysis, and issue management with SilkCentral Issue Manager.
SilkCentral Issue Manager
SilkCentral Issue Manager, SilkCentral’s issue-tracking tool, is fully integrated with Test Manager.
Access and Licensing
SilkCentral Architecture
SilkCentral products are based on SilkCentral Architecture (SCA), which allows for common administration of Web-based products.
The following sections describe the SilkCentral components.
♦
Overview♦
Front-end server♦
Application server♦
Execution server♦
Chart server♦
Database serverOverview
Front-end server
The front-end server is responsible for the graphical user interface. This server is based on HTML and is accessible from any Web browser, such as Internet Explorer or Firefox. A user sends an appropriate HTTP request to the front-end server and receives a login page for authentication. After successful login, the user can use the corresponding
application based on the respective user rights. The front-end server can operate as a stand-alone HTTP server, or it can be attached to a Web server, such as IIS via ISAPI filter.
To prevent third-party users from accessing SilkCentral from unattended computers, for security reasons, SilkCentral terminates sessions once users have logged out or closed the browser for 30 minutes. SilkCentral then checks in the license.
Application server
The application server synchronizes tasks such as the distribution of schedules, control of execution servers, and management of database configuration. These tasks require a centralized agency to ensure the consistent, reliable behavior of the application. The application server also evaluates results, saves them to the database, and sends alerts based on success conditions.
Execution server
The execution server executes SilkTest and/or SilkPerformer tests that are scheduled by authorized users. Users are responsible for the proper configuration of execution servers and additional resources that are required for test executions. The system allows for the installation and configuration of multiple execution servers working
independently of one another.
Chart 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. The chart server is also used to generate reports and deliver them directly to the end-user for viewing within a browser.
Database server
System persistency is implemented using a RDBMS (Relational Database Management System). SilkCentral supports MS SQL Server 2005 and 2008 (including Express), Oracle 9i (version 9.2.0.8 or later), and Oracle 10g (We recommend version 10.2).
Agent computers
SilkPerformer and SilkTest agent computers are assigned to particular SilkPerformer / SilkTest projects from the pool of agent computers that are available to the controller computer. In combination with SilkCentral Test Manager, the controller computer acts as an execution server.
SilkPerformer agents
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 via SilkPerformer. See SilkPerformer documentation for details on configuring agents.
SilkTest agents
The same rules that apply to SilkPerformer agents apply to SilkTest agents, except SilkTest agents host SilkTest tests.
Related Concepts
Application Server Location Chart Server Location SilkCentral Repositories User Roles and Permissions Time Zones
Welcome to SilkCentral Test Manager
As a key component of your complete testing solution, Test Manager’s Requirements unit enables you to maintain control over system requirements during development: managing the creation, modification, and deletion of requirements; association of test definitions with requirements; change-history tracking; and the ability to generate test plans directly from requirement lists. As with all Test Manager functionality, the Requirements unit is 100% Web enabled and accessible through your Web browser.
Test Manager’s Test Plan unit enables you to maintain control over test planning across the system development lifecycle. The Test Plan unit allows you to create and manage test plans, including the definition of both automated (SilkPerformer, SilkTest, JUnit, NUnit, and Windows Scripting) tests and manual tests. Files and links can be uploaded and associated with test containers and definitions as attachments. Issues that are uncovered can easily be associated with the test definitions that led to their discovery. Full history of all changes to test plans is also tracked.
The Test Execution unit enables you to configure test scenarios from the Test Plan unit and to schedule those scenarios for execution on your execution servers. Test definitions can be statically assigned to execution definitions or test definitions can be grouped dynamically using predefined filters on the Test Plan tree. Custom schedules can be defined for execution definitions, or predefined schedules can be used.
The Code Analysis unit enables you to evaluate the degree to which the code of your AUT is covered by test cases. Intuitive histographs display the percentage of coverage provided for products, code packages, lines of code, class files, and methods. Code-coverage analysis enables you to make informed estimates regarding effort/cost and risk associated with specific code changes.
Related Concepts
SilkCentral Issue Manager
SilkCentral Issue Manager, SilkCentral’s issue-tracking tool, is fully integrated with Test Manager, enabling you to correlate issues with system requirements and executed tests.
Test-definition issues can be added and managed through the Issues tab in the Test Plan unit (Test Plan View). [See “Managing Issues” in the Issue Manager Help for details].
Note: StarTeam and IBM Rational ClearQuest are also supported by Test Manager “out of the box”. Additional issue tracking systems can be configured by installing a custom plug-in [see the SilkCentral Test Manager API documentation for detailed information].
Related Concepts
Access and Licensing
SilkMeter, the licensing software that accompanies Silk products, determines the SilkCentral-application functionality that you may access. For more information on licensing, see the respective product’s installation instructions.
Help on Help
This section includes information about:
♦
SilkCentral Help♦
Typographic Conventions Used in the HelpSilkCentral Help
SilkCentral Help includes conceptual overviews and procedural how-to's. This allows you to navigate from general to more specific information as needed.
Additionally, the persistent navigation panes in the Help window make it easier to locate information.
Conceptual Overviews
The conceptual overviews provide information about product architecture, components, and other information you need to help you work with SilkCentral.
At the end of most of the overviews, you will find links to related, more detailed information. An icon indicates that a link leads to a Web site.
How-To Procedures
The how-to procedures provide step-by-step instructions.
All of the procedures are located under Procedures in the Content pane of the Help window. Additionally, most of the conceptual overviews provide links to the pertinent procedures.
Typographic Conventions Used in the Help
The following typographic conventions are used through the SilkCentral online Help.
Convention Used to indicate
Monospace type Source code and text that you must type.
Boldface References to dialog boxes and other user interface elements.
Italics Identifiers, such as variables. Italicized text is also used to emphasize new terms. A link to Web resources.
Procedures
Topics in this section contain the tasks you need to get started with SilkCentral.
In This Section
Configuring the Application Server
Describes the process of configuring the application server for SilkCentral.
Connecting to a Repository
Configuring the Application Server
After installing a SilkCentral application, there are a number of initial steps that must be performed by the system administrator before you can begin working with the software. The following procedure takes you through each of the necessary steps.
Note: You must login as an administrator to perform the actions outlined in this Help.
To configure the application server
1 Configuring Secure Connections with Microsoft IIS
Tip: If you are not using an SSL connection to SilkCentral, proceed with the next step.
Configuring Secure Connections with Microsoft IIS
2 Specifying a Location for the Application Server
Specifying a Location for the Application Server
Related Concepts
Application Server Location SilkCentral Architecture
Secure Web Server Connections with SSL
Related Procedures
Configuring Secure Connections with Microsoft IIS
To use SilkCentral with Secure Sockets Layer (SSL), you must first obtain a certificate from a Certificate Authority
and then apply the certificate to Internet Information Services (IIS).
To apply for a certificate to use SSL and apply it to IIS
1 Apply for a certificate to use SSL:
Applying for a Certificate to use SSL
2 Apply the certificate to IIS:
Applying the Certificate to IIS
Related Concepts
Secure Web Server Connections with SSL Application Server Location
Related Procedures
Configuring the Application Server
Specifying a Location for the Application Server
When you use the Standard Setup option for installing a SilkCentral application, you do not need to specify an application server location. Setup automatically configures the localhost to be the application server (see the application’s installation instructions for more information regarding setup options). In this case you can skip this procedure.
To specify a location for the application server
1 Once you have installed the SilkCentral software, connect to SilkCentral using a Web browser.
Tip: If you installed ISAPI Web Server, use as the http://<Web-server-name>/login as the URL.
Tip: If you installed the stand-alone Web Server, use http://<Web-server-name>: 19120//login as the URL (the stand-alone Web server uses port 19120 by default). You will receive a confirmation stating that the application server connection has not yet been defined.
2 Enter the Host or IP address and the Port of the application server (the computer where you installed SilkCentral’s application server component). The default port is 19122.
3 Click Login to proceed. If your specifications are correct and the respective computer is running with the installed software, you will be returned to the login page with the message Application server connected
successfully.
4 The Database Administration page displays.
Related Concepts
Application Server Location
Related Procedures
Creating a New Repository Accessing an Existing Repository
Connecting to a Repository
If this is a new installation, you need to set up a database (also known as a “repository”). If this is an upgrade installation, you will probably want to connect to an existing repository.
In This Section
1 If you are using MS SQL Server 2005 or MS SQL Server 2005 Express, you need to configure SQL Server to use the TCP/IP protocol. If you are using a different database system, please skip this step.
Enabling the TCP/IP Protocol for MS SQL Server 2005
2 To set up a new database:
Creating a New Repository
3 To connect to an existing database:
Accessing an Existing Repository
Related Concepts
SilkCentral Repositories
Related Procedures
Disconnecting from a SilkCentral Repository
Related Reference
Enabling the TCP/IP Protocol for MS SQL Server 2005
If you are using MS SQL Server 2005 or MS SQL Server 2005 Express, you need to configure SQL Server to use the TCP/IP protocol. If you are using a different database system, please skip this procedure.
You need to verify the following settings on the computer hosting the SQL Server installation:
♦
The SQL Server Browser service must run on Windows. We recommend that you change the properties of this service to Startup type: Automatic (Windows Services settings can be found in Start SettingsControl Panel Adminstrative Tools Services).
♦
The SQL Server must use the TCP/IP protocol.To enable the TCP/IP protocol for MS SQL Server 2005
1 Run the SQL Server Configuration Manager tool that comes with MS SQL Server 2005.
2 In the displayed tree, select SQL Server 2005 Network Configuration Protocols for MSSQLSERVER.
Tip: Select SQL Server 2005 Network Configuration Protocols for SQLEXRESS if you installed MS SQL Server Express.
3 In the pane to the right of the tree view, right-click TCP/IP and choose Enable.
4 Back in the tree view pane, select SQL Server 2005 Services.
5 In the pane to the right of the tree view, right-click SQL Server (MSSQLSERVER) (SQL Server (SQLEXPRESS) if you installed MS SQL Server Express) and select Restart from the context menu.
Related Concepts
SilkCentral Repositories
Related Procedures
Connecting to a Repository Creating a New Repository Accessing an Existing Repository
Creating a New Repository
If this is a new installation, the next step is to set up a database (also known as a repository).
Note: If you are currently connected to a SilkCentral database, you must disconnect from the database before you can create a new database.
To create a new repository:
1 If you have already set up your SilkCentral application server, the Database Administration page will display in a browser window, and you can proceed to step 3 of this procedure.
Tip: Alternatively, you can browse to your SilkCentral site with a Web browser (default URL is
http://<computer name>:<port>/login).
Tip: When you use the Standard Setup option for installing SilkCentral, the Database Administration page displays immediately after you connect to the application. On the computer where the front-end server is installed, you can also select Start Programs Micro Focus SilkCentral Test Manager Test Manager Home Page.
2 If not already logged in, log in (admin is the default value for both the username and the password). Navigate to Administration System Database.
3 Enter the information for the new database, then click Connect. You can create a database on the locally installed Microsoft SQL Server 2008 Express, a locally installed MS SQL Server or Oracle installation, or on a network server that has MS SQL Server or Oracle installed. SilkCentral supports MSSQL Server 2005 and 2008 (including Express), Oracle 9i (version 9.2.0.8 or later), and Oracle 10g (We recommend version 10.2).
Tip: See the related reference topic for detailed information on the individual connection settings on this page.
4 The Create Database dialog box displays. To create a new database, you must provide the database administrator credentials.
If you installed SilkCentral using the evaluation setup package, type sa in both the Username and Password
text boxes, then click OK.
Tip: If you are creating a local or network MS-SQL Server or Oracle database, enter the login information provided to you by your database administrator, then click OK.
Note: This process can take up to a few minutes.
1 Enter a unique repository ID into the ALM Repository ID text box in the Create ALM Repository ID dialog box and click OK.
5 A Messages dialog box may display, informing you of servers that were found on the local computer and have automatically been added to the system configuration. Confirm this dialog box by clicking OK. If you receive a warning message stating Couldn't define localhost as Execution Server, you need to configure your execution servers manually.
6 You will be notified that the repository has been created successfully. Confirm the message by clicking OK.
7 The login page displays. Log in using your standard username and password (the default is admin/admin). Do not log in as a database administrator. Information about the currently connected database is displayed on the Database Administration page, but other available databases are not displayed anywhere in the
SilkCentral user interface. You must make a note of the database name for future reference. Your system is now ready for use.
Related Concepts
SilkCentral Repositories
Related Procedures
Connecting to a Repository Accessing an Existing Repository Logging in for the First Time
Disconnecting from a SilkCentral Repository
Related Reference
Database Settings Page Login Page
Accessing an Existing Repository
To access an existing repository
1 Navigate to the Administration System Database page. If you are already connected to a repository, click Disconnect. A confirmation dialog box displays, asking you if you really want to disconnect from the current repository. Click Yes to disconnect.
2 Enter (or confirm) the information for the database, then click Connect.
Tip: See the related reference topic for detailed information on the individual connection settings on this page.
1 If the repository has not yet been given an ALM repository ID, the Create ALM Repository ID dialog box displays. Enter a unique repository ID into the ALM Repository ID field on the Create ALM Repository ID
dialog box and click OK.
3 After the database connection has been established, a confirmation message displays. Confirm the message by clicking OK. The SilkCentral login page displays.
4 Log in to SilkCentral (admin is the default value for both the username and password). After you log in, you should have access to SilkCentral.
Related Concepts
SilkCentral Repositories
Related Procedures
Creating a New Repository Connecting to a Repository Logging in for the First Time
Related Reference
Database Settings Page Login Page
Concepts
This section contains all the conceptual topics.
In This Section
Configuring the System
Topics in this section explain the basic settings to configure a running SilkCentral system.
Configuring the Application
This section contains conceptual information about user accounts, projects, locations and execution servers, and other common entities.
Configuring Advanced Settings
Configuring the System
Topics in this section explain the basic settings to configure a running SilkCentral system.
In This Section
Secure Web Server Connections with SSL
Explains the relationship between ISAPI, IIS, and SSL as related to secure Web server connections.
Application Server Location
Explains the basics of the SilkCentral application server.
SilkCentral Repositories
Explains the usage of a database (repository) in SilkCentral.
Initial Login
Once connected to a repository, you are ready to login using the default system administrator account.
System Administrator Accounts
Explains details about the default SuperUser account.
Chart Server Location
A chart server is a service that computes data and produces graphs.
Mail Host Location
To have reports emailed to you to update you about results from your application, you must specify the location of your mail server.
SMS Host Settings
You may configure SilkCentral to send notifications of results from your application through Short Messaging Service (SMS).
PageGate Gateway Access
You may configure SilkCentral to send notifications of results from your application to a pager through PageGate Gateway.
SNMP Trap Notification
You may configure SilkCentral to send notifications of results from your application through SNMP trap messages.
System Proxies
Configure a system proxy to enable execution servers of a certain location to communicate with the application server through a proxy.
LDAP Authentication
Configure LDAP authentication to enable SilkCentral logins through an LDAP server.
SilkPerformer Load-Test Agent Clusters
Describes SilkPerformer load-test agent clusters and their support of dynamic workload assignment across multiple test agents.
Secure Web Server Connections with SSL
If you intend to work using a secure connection and have opted to install the ISAPI Web Server, then you must configure Microsoft Internet Information Services (IIS) to use the Secure Sockets Layer (SSL). You must first obtain a certificate from a Certificate Authority to gain access to the Secure Sockets Layer.
The SilkCentral default standalone Web server (Tomcat) can also be configured to use SSL (Secure Sockets Layer).
Related Procedures
Configuring Secure Connections with Microsoft IIS Configuring Secure Connections with Tomcat Web Server
Application Server Location
The application server synchronizes tasks such as the distribution of schedules, control of execution servers, and management of database configuration. Before you can start working with SilkCentral applications, you need to specify the location of the application server.
Related Procedures
SilkCentral Repositories
The terms “database” and “repository” are sometimes used interchangeably, but generally a repository is defined as a central place in which an aggregation of data is kept and maintained. The conceptual model for SilkCentral is that of a data repository that contains the application data.
A repository is a database used by SilkCentral products to store, maintain, and analyze data. You must first choose which database system you want to use for your repository and take the necessary steps in the SilkCentral GUI to access the repository. You must be connected to a repository to work with SilkCentral products.
You may set up multiple repositories, though only one repository at a time may be active.
To connect to a new SilkCentral database, you must first disconnect from the current database. Note that users receive error messages if they try to work with SilkCentral while the database is disconnected. We recommend to perform administrative tasks that require the database to be disconnected during off-hours. If this is not possible, make sure to inform the users about the system-outage and its duration.
Note: If you are not planning on using LDAP authentication, user accounts will be stored in the repository. If you plan to use multiple repositories, you will have to maintain separate user accounts for each repository.
Repository IDs
Each SilkCentral Test Manager repository must have a unique repository ID. This ID is used in ALM URIs to uniquely identify Test Manager requirements and test definitions across multiple Test Manager repositories. The repository ID must be unique within your company's Test Manager installations. The supplied repository ID will be part of the ALM URI. It is good practice to use a descriptive ID, for example USCA01 (for USA, California, repository #01) or
GEBE02 (for Germany, Berlin, repository #02) . Allowed characters are letters, numbers, period (.), and minus (-). ID's must have a length of 1 to 20 characters.
Each repository ID must be unique within your company's Test Manager installations.
Warning: Once a repository ID has been set, it cannot be changed.
ALM URIs
Repository IDs are incorporated into ALM URIs (Application Lifecycle Management Uniform Resource Identifiers). ALM URIs offer a means of addressing elements across ALM Server platform and the ability to distinguish and track elements between applications. Among other things, ALM URIs are used to uniquely identify Test Manager requirements and test definitions across multiple Test Manager repositories.
Test Manager & Issue Manager ALM URIs
The ALM element URI syntax is as follows:
<ALM URI> = alm://<source project>/<source element path>[?<source version>] <source project> = <source type>!<project identity>
For Test Manager, <source type> = sctm. For Issue Manager, <source type> = scim. Project identity is built as follows:
<project identity> = sctm!<repository ID>_<project ID>
<repository ID> is a unique identifier for each Test Manager and Issue Manager repository. Each Test Manager and Issue Manager repository generates a unique identifier that is stored inside the repository. Uniqueness is
guaranteed across all Test Manager and Issue Manager repositories that you may have installed. <project ID> is an identifier for a Test Manager or Issue Manager project. This identifier is unique in the context of each repository.
Source Element Path:
For Test Manager and Issue Manager, the following syntax for referencing artifacts is used:
Test Manager native requirements (requirements that are not linked with an external requirement management system):
<source element path> = /<requirement ID>;ns=requirement
Test Manager tests
<source element path> = /<test ID>;ns=test
Test Manager and Issue Manager issues
<source element path> = /<issue ID>;ns=issue
Example ALM URI: alm://sctm!USCA01_23/602;ns=test
Test Manager repository USCA01, project ID 23, element ID 602, element type test.
Related Procedures
Creating a New Repository Connecting to a Repository Accessing an Existing Repository
Enabling the TCP/IP Protocol for MS SQL Server 2005
Related Reference
Initial Login
Once connected to a repository, you are ready to login using the default system administrator account.
After logging in, you are automatically logged out when you are idle for more than 30 minutes. To change the duration of the session time-out for all users, see the related procedure below for changing the cookie duration.
Warning: Because the SuperUser account admin has all administrative privileges, you should immediately designate a new password for this user to prevent unlimited access to these privileges. See the related
Changing the Password of the System Administrator Account procedure below to find out how to change the password.
Related Concepts
System Administrator Accounts User Roles and Permissions User and Group Accounts
Related Procedures
Logging in for the First Time
Changing the Password of the System Administrator Account Managing Accounts and User Roles
Related Reference
System Administrator Accounts
Adding user accounts allows different users to create projects and have access rights to work with them.
By default, the SuperUser account admin is available in the set up installation with the password admin. Since this user has all administrative privileges, you should immediately designate a new password to prevent unauthorized access to this account. The SuperUser is the only user role that can configure the application-, Web-, and chart server locations; and set up and maintain repositories and notification settings. The other user types and their capabilities are described in the related User Roles topic.
Warning: Because the SuperUser account admin has all administrative privileges, you should immediately designate a new password for this user to prevent unlimited access to these privileges. See the related
Changing the Password of the System Administrator Account procedure below to find out how to change the password.
Related Concepts
User Roles and Permissions User and Group Accounts
Related Procedures
Changing the Password of the System Administrator Account Managing Accounts and User Roles
Related Reference
Chart Server Location
A chart server is a service that computes data and produces graphs. These graphs are viewable within the SilkCentral application. This service can be installed with the SilkCentral setup on a computer of your choice. You must specify the location of your chart server in order to display graphs.
Note: You can define as many chart servers as you want; SilkCentral automatically implements a load balancing mechanism for chart generation.
Related Procedures
Specifying Locations for Chart Servers Adding Chart Servers
Editing Chart Servers Removing Chart Servers
Related Reference
Mail Host Location
To have reports emailed to you to update you about results from your application, you must specify the location of your mail server. You may only configure email settings if you have administrator privileges.
Note: SilkCentral supports basic SMTP authentication (LOGIN PLAIN).
Related Procedures
Specifying a Location for the Mail Host
Related Reference
SMS Host Settings
You may configure SilkCentral to send notifications of results from your application via Short Messaging Service (SMS). To do so, you must specify information about your mobile phone provider. Your mobile network provider should be able to give you the required information.
To make optimal use of the SilkCentral SMS service, you may need to define a standard set of abbreviations or short-hand “codes” that your team can use for system communications.
Note: This service only works after you configure email notification; messages are sent to your mobile provider through email (see the related Specifying a Location for the Mail Host topic). You may only configure these settings if you have administrator privileges.
Related Concepts
Mail Host Location
Related Procedures
Configuring Settings for an SMS Host Specifying a Location for the Mail Host
Related Reference
PageGate Gateway Access
To receive pages that include reports regarding results from your application, configure SilkCentral to page you through PageGate™. You must already have PageGate installed and configured to use this service and you must specify information regarding how SilkCentral is to send messages through PageGate.
PageGate is a third-party product that is used to send text messages to wireless devices (pagers, SMS, etc.). SilkCentral uses PageGate’s GetAscii interface.
Related Procedures
Configuring Access to the PageGate Gateway
Related Reference
SNMP Trap Notification
To have reports sent to you with results from your application, you may configure SilkCentral to notify you through a Simple Network Management Protocol (SNMP) Version 2 trap message. You must already have this software installed and configured on a computer in your LAN to use this service and to view data through the third-party software. This type of notification can be used for transferring alarms directly into your existing system management tool.
Related Procedures
Configuring SNMP Trap Notification
Related Reference
System Proxies
Configure a system proxy to enable execution servers of a certain location to communicate with the application server through a proxy. Once you have specified the location of a proxy server, you can select the defined proxy server in your location configuration. Enabling this setting will force all execution servers of the location to communicate with the application server through the defined system proxy.
Related Concepts
Locations
Related Procedures
Configuring a System Proxy Managing Locations
Related Reference
LDAP Authentication
Configure LDAP authentication to enable SilkCentral logins via an LDAP server.
Light Weight Directory Access Protocol (LDAP) is an open network protocol standard that is designed to provide access to directory services. LDAP provides a mechanism for querying and modifying information that resides in a directory information tree (DIT). A directory information tree typically contains a broad range of information about different types of network objects including users, printers, applications, and other network resources.
SilkCentral LDAP integration
The most important aspect of LDAP integration in SilkCentral is user authentication. In most directories it is not possible to retrieve a user’s password, so LDAP must be accessed each time a user needs to be authenticated. SilkCentral LDAP integration supports plain-text authentication and SSL authentication. The directory service must either allow anonymous queries or a user with read rights on the directory must be provided.
The following properties must be provided for LDAP servers:
♦
LDAP server URL♦
LDAP port♦
Base DN (root node, base distinguished name)♦
(optional) username and password♦
Filter, for querying user (object)Authentication logic
Standard mode authentication means that a user can only authenticate against LDAP, if an LDAP server is defined and active. Mixed mode authentication means that a user can login with either LDAP or local credentials.
Note: For either authentication mode, a user can only be logged in when their username exists in the SilkCentral database.
Standard mode authentication
Standard mode authentication is enabled when at least one LDAP server is active. When no LDAP server is defined, users will only be able to login with local credentials. Each defined LDAP server is checked to determine if a user (with specific username and password) can be authenticated. Access is granted when authentication succeeds on one of the servers.
Mixed mode authentication
When no LDAP server is defined, users will only be able to login with local credentials. If at least one LDAP server is active and a user account is set to use mixed mode authentication, each defined LDAP server is checked to determine if a user (with specific username and password) can be authenticated. If the user is unknown on all defined LDAP servers, then local database authentication is attempted. Access is denied when a user is also unknown based on local credentials. If a user is known on an LDAP server, but the credentials are incorrect, access is denied.
Related Concepts
User and Group Accounts
Related Procedures
Configuring LDAP Integration Adding LDAP Servers Editing LDAP Servers Testing LDAP Servers Deleting LDAP Servers
Managing Accounts and User Roles
Related Reference
SilkPerformer Load-Test Agent Clusters
In addition to assigning workload to individual agents, you have the option of assigning SilkPerformer workload to clusters of agents with defined capabilities. SilkPerformer's dynamic workload-assignment functionality matches specific load-test requirements to the replay capabilities of available agent computers at execution time. The capabilities that are defined for test agents in SilkPerformer are used to optimize workload-to-agent assignment. For example, if a test requires a workload that only an agent computer with a SAPGUI client can deliver, then dynamic workload-assignment functionality can ensure that the test's workload is assigned only to available agents with SAPGUI clients. Additionally, the percentage of required workload or virtual users that can be allocated to each agent can be configured, thereby ensuring that agents are not pushed beyond their capacities.
Upon execution of a SilkPerformer test definition, a Test Manager load-test agent-clusters XML file is checked out of the appropriate execution server and used for dynamic workload assignment during execution. You must specify the location of your project's load-test agent clusters XML file by way of Administration System settings. An advantage of dynamic assignment of workload to load-test agent clusters is that successful execution of tests is not contingent on maintaining a static test-execution environment. SilkPerformer can dynamically assign an unavailable agent's workload to an available agent in the same cluster that has the same capabilities. This feature is of particular value when SilkPerformer load tests are managed and executed based on predefined schedules in Test Manager. The manner in which workload is balanced across agents and the health of individual agents are not issues to consider from the Test Manager perspective.
For details regarding dynamic workload assignment, refer to the SilkPerformer Help.
Related Procedures
Uploading Load Test Agent Cluster Files Deleting Load Test Agent Clusters Files Editing Load Test Agent Cluster Files
Related Reference
Configuring the Application
This section contains conceptual information about user accounts, projects, locations and execution servers. It also covers the administration of custom reports and managing uploaded files, and the configuration of other common entities.
In This Section
User Roles and Permissions
This topic defines each permission type and details the specific permissions that are associated with each user role.
User and Group Accounts
Describes the conceptual background of user accounts and group accounts in SilkCentral.
Projects
Describes the conceptual background of projects in SilkCentral.
Project Templates
Describes the conceptual background of project templates in SilkCentral.
Locations
Describes the conceptual background of locations in SilkCentral.
Execution Server Setup
Describes the conceptual background of execution servers in SilkCentral.
VMware Lab Manager Virtual Configurations
VMware Lab Manager configurations offer an effective means of virtualizing complex software-testing lab environments.
Report Templates
Conceptual background of report templates in SilkCentral.
Audit Log
The audit log allows administrators to view all recorded SilkCentral user activity.
Server Log Files
Server log files provide valuable information to administrators for error analysis.
Task Management Tools
Describes how to integrate external task management tools with Test Manager.
Products and Platforms
SilkCentral enables you to create and organize products, product components, versions of products, and build numbers of product versions.
Value Lists
Value lists are used to populate custom properties within custom issue tabs that can be configured for SilkCentral Issue Manager.
Global Schedules
SilkCentral lets you define global schedules that can be re-used in Test Manager for the scheduling of execution definitions.
File Pool
The file pool is an upload/download area on the SilkCentral Web server (the front-end server).
Time Zones
User Roles and Permissions
When working with SilkCentral, tasks are assigned to designated groups of users who have access to assigned projects. Within groups, users are granted specific roles within those projects. User permissions are configured based on user role type and group membership. This topic defines each permission type and details the specific permissions that are associated with each user role.
Each user account can belong to one or multiple groups. A group specifies which roles a user has within that group. Groups are assigned to projects. So the permissions that each individual user has are derived from the group/role assignments that have been defined for them. Defined permissions apply only to the projects that are assigned to the groups in which each user has a group/role assignment.
There are seven predefined user roles: SuperUser, Administrator, Project Manager, Test Manager, Tester,
Analyst, and Reporter.
Predefined User Roles
The following user roles are predefined within SilkCentral. These roles cannot be modified or deleted. They can however be copied and thereby used as the basis for customized roles.
SuperUser
The SuperUser role is a special role that is granted all privileges across SilkCentral applications. The SuperUser has no access restrictions. SuperUsers can add, modify, and delete entities in the Administration area, as well as in all sections of SilkCentral applications.
Administrator
Administrator tasks include the configuring of application-, Web- and chart server locations; setting up and maintaining repositories and notification settings; creating accounts; configuring locations and execution servers, etc.
Administrators are granted all privileges across the SilkCentral Administration Module and Issue Manager.
Project Manager
Project Managers maintain the projects for which they are responsible. Project Managers do not have write access to the SilkCentral Administration Module. Project Managers can only access the projects to which they have been assigned as Project Managers, where they have full write access to all project-related features.
Project Managers also have all Issue Manager permissions for projects that are assigned to them.
Test Manager
Test Manager responsibilities include the planning and execution of test definitions, including the deletion of test definitions. Test Managers also have full read access to SilkCentral Test Manager’s Requirements unit.
Tester
The Tester role relates to SilkCentral Test Manager privileges. The Tester’s tasks include the planning and execution of test definitions—though Testers cannot delete test definitions. Testers also have full read access to SilkCentral Test Manager’s Requirements unit.
Analyst
Analysts analyze the results of projects that have been assigned to them. They cannot modify project settings or schedules and have read-only privileges.
Reporter
In addition to having all the rights of Analysts, Reporters additionally have the right to edit and delete reports in
Advanced mode. Advanced mode allows reporters to enter, modify, and delete SQL statements for advanced reports (see the respective SilkCentral application Help for details on advanced reports).
Permission Definitions
This section explains the permissions that govern user ability to perform tasks and access secure areas within SilkCentral Test Manager. There is a separate list for each permission category: Test Manager configuration,
Requirements, Test Plan, System, Users/Projects/Locations/Configuration/Files, Locations, and Reports/Log files.
Test Manager Configuration Permissions
Permission Description
View project settings Permission to view all areas of Test Manager Settings
Edit project settings Permission to edit settings in all areas of Test Manager Settings, except in Integrations Configuration.
Delete project settings Permission to delete settings in all areas of Test Manager Settings, except in Integrations Configuration.
Manage requirements integration settings Permission to create, edit, and delete configurations in Test Manager Settings Integration Configuration.
Requirements Permissions
Permission Description
View Requirements Permission to view all areas of Test Manager Requirements.
Manage Requirements Permission to create, edit, and delete objects in all areas of Test Manager Requirements, including associations to test definitions and synchronization with external RMS.
Test Plan Permissions
Permission Description
View test plans and executions Permission to view all areas of Test Manager Test Plan and Test Manager Execution, including associations.
Manage test plans and executions Permission to create and edit objects in all areas of Test Manager Test Plan and Test Manager Execution, including associations.
Delete test plans and executions Permission to delete objects in all areas of Test Manager Test Plan and
System Permissions
Permission Description
View system settings Permission to view all areas of Administration System.
Manage system settings Permission to create, edit, and delete settings in all areas of Administration System.
Users, Projects, Locations, Configuration, and Files Permissions
Permission Description
View administration settings Permission to view all areas of the Administration module, except
Administration System.
Manage administration settings Permission to create, edit, and delete settings in all areas of the Administration module, except Administration System.
Locations Permissions
Permission Description
Manage execution servers Permission to create, edit, and delete execution servers in Administration Locations Execution Servers.
Report and Log Files Permissions
Permission Description
View reports Permission to edit report parameters and view all areas of Test Manager Reports and Administration Reports.
Manage reports Permission to create, edit, and delete objects in all areas of Test Manager Reports and Administration Reports.
Manage advanced reports Permission to create and edit advanced reports, including the option to write SQL queries with direct access to a database. Roles with this permission should also have the Manage reports permission, so that report objects can be created and deleted. View server log files Permission to view Front-end Server Log, Application Server Log, and Execution
Server Log in Administration Reports.
Predefined User Role Permissions
The charts below detail the permissions that are associated with each user type. There is a separate chart for each permission category: Test Manager configuration, Requirements, Test Plan, System, Users/
Projects/Locations/Configuration/Files, Locations, and Reports/Log files.
Note: Permissions for predefined roles can not be edited. Permissions for custom roles can be edited.
Test Manager Configuration Permissions
SuperUser Administrator Project Manager Test Manager Tester Analyst Reporter
Edit project settings X X X X
Delete project settings X X X
Manage requirements integration
configuration X X X X
Requirements Permissions
SuperUser Administrator Project Manager Test Manager Tester Analyst Reporter
View requirements X X X X X X
Manage requirements X X
Test Plan Permissions
SuperUser Administrator Project Manager Test Manager Tester Analyst Reporter
View test plans and executions X X X X X X
Manage test plans and executions X X X
Delete test plans and executions X X
System Permissions
SuperUser Administrator Project Manager Test Manager Tester Analyst Reporter
View system settings X X X X X
Manage system settings X X
Users, Projects, Locations, Configuration, and Files Permissions
SuperUser Administrator Project Manager Test Manager Tester Analyst Reporter
View administration settings X X X X X
Manage administration settings X X
Locations Permissions
SuperUser Administrator Project Manager Test Manager Tester Analyst Reporter Manage execution servers X X
Reports and Log File Permissions
SuperUser Administrator Project Manager Test Manager Tester Analyst Reporter
Manage reports X X X X X
Manage advanced reports X X
View server log files X X X X X
Related Concepts
User and Group Accounts System Administrator Accounts
Related Procedures
Maintaining User Roles Maintaining Group Accounts Maintaining User Accounts
Related Reference
User and Group Accounts
A user account must be created for each user working with SilkCentral. Groups of users (one or more) are assigned to specific projects. Only with a user account, user role, and a group assignment can a user work with a SilkCentral project.
User Accounts
User accounts track login data and configuration settings for individual users. They also enable user login. User accounts are typically assigned to group accounts with one or more specific user roles for specific projects.
Note: By default, the SuperUser account admin is available after initial installation with the password admin. Since this user has all administrative privileges, you should immediately designate a new password for this user to prevent unauthorized access to these privileges. The SuperUser is the only user role that can, among other things, configure the application-, Web-, and chart server locations; and set up and maintain repositories and notification settings.
Group Accounts
Group accounts define access to specific projects. Each user can be associated with one or more group accounts from which they inherit the access rights to the projects that are defined for the selected group account.
Note: Users can be added to group accounts with multiple roles, allowing advanced user permission configuration.
Related Concepts
System Administrator Accounts User Roles and Permissions
Related Procedures
Changing the Password of the System Administrator Account Maintaining Group Accounts
Maintaining User Accounts Maintaining User Roles Configuring LDAP Integration
Related Reference
User Settings Page Group Settings Page Roles Settings Page
Projects
This topic describes the conceptual background of projects in SilkCentral.
Projects are a prerequisite for beginning work with any SilkCentral application. Projects serve as containers for related sets of tasks and results. Resources such as project managers and analysts are allocated to projects by assigning them to user groups, which have access rights to certain projects.
Note: Projects can be created and maintained by the administrator, project manager, and SuperUser roles.
Related Concepts
User Roles and Permissions User and Group Accounts Locations
Project Templates
Related Procedures
Managing Projects
Managing Accounts and User Roles Managing Locations
Related Reference
Project Templates
This topic describes the conceptual background of project templates in SilkCentral.
A project template is used to support the interaction between SilkCentral and VersionOne or other agile project management tools. The template is a project with the specific attributes sprint and release. When you create a new project using this template, a default test container and a default folder are also created. When the project
management tool creates a test, the test is added to the default folder. No source control profile and no product are specified for the test container and the folder, therefore they are marked as incomplete in the test plan.
Related Concepts
Task Management Tools
Related Procedures
Locations
This topic describes the conceptual background of locations in SilkCentral.
Locations are logical containers for execution servers (see the related Execution Server Setup topic for information on setting up execution servers). Since SilkCentral supports worldwide distribution of PoP’s (Points of Presence) — the distribution of execution servers — it is desirable to group execution servers into locations.
Note: SilkCentral automatically creates a default location called Local.
Related Concepts
Execution Server Setup Projects
Related Procedures
Managing Locations
Setting Up Execution Servers Managing Projects
Related Reference
Execution Server Setup
SilkCentral’s execution servers are responsible for executing scheduled test definitions, for example SilkTest and SilkPerformer scripts. To execute SilkTest and SilkPerformer tests, SilkTest or SilkPerformer software must be installed on the same computer on which SilkCentral execution servers are installed.
When executing SilkPerformer scripts against multibyte applications or Web pages, please review the Multibyte Support section in the SilkPerformer Online Help.
For further details regarding the installation of execution servers, refer to the respective SilkCentral product’s Help. For information regarding SilkTest and SilkPerformer, please see the respective product documentation.
Hardware Provisioning with Keywords
Test Manager's hardware-provisioning technology helps you manage test environments that include numerous execution servers. Rather than having to configure a one-to-one direct relationship between each execution server and execution definition, keywords enable Test Manager to select the most appropriate execution server for each execution definition. This is done through dynamic comparison of an execution definition's keyword list with the keyword lists of all active execution servers.
Keywords typically describe the environment of an execution server (for example, platform, operating system, and pre-installed applications). When an execution definition is executed, Test Manager compares the execution definition's keywords with the keywords of all available execution servers. The execution is then run on the execution server that matches the execution-definition's keyword list. If there is no matching execution server, the execution will not be run. If there are multiple execution servers with matching keyword lists, the execution will be run on the first identified execution server.
Reserved Default Keywords
If you do not require hardware provisioning, you can rely on the reserved keywords that are created automatically for each execution server. In such cases, it is not necessary that you manually assign keywords to your execution servers. Instead, you can configure a one-to-one static execution-server assignment for each execution definition. A reserved keyword is assigned automatically to each newly created execution server. Reserved keywords are structured in the following form: #<execution name>@<location name>.
Reserved keywords are available when assigning keywords to execution definitions. They are neither available or applicable when assigning keywords to execution servers.
In addition to the reserved keywords that are set up automatically for each defined execution server, reserved keywords are also set up for each execution server type:
#PHYSICAL Limits execution-server provisioning to physical execution servers. #VIRTUAL Limits execution-server provisioning to virtual execution servers.
Keywords and Virtual Execution Servers
Keywords are assigned to virtual execution servers in the same way that they are assigned to physical execution servers. When you configure at least one virtual execution server, the #VIRTUAL keyword is dynamically cr
