Installing a Command-Line-Driven Execution Server

Install a command-line-driven execution server to execute tests from a virtual infrastructure where execution servers are started and stopped on demand.

From Silk Central, you can download an executable JAR that starts a new execution server.

In the Silk Central menu, click Help > Tools > Execution Server Launcher to download the executable JAR that starts a new execution server.
Note: The latest version of Java 1.8 needs to be installed on the machine from which you want to start the execution server. The Silk Central application server needs permission to access the execution server port.
The launcher works for both Linux and Windows machines.

Locate the sc-execserverlauncher.jar and use a command-line call to start an execution server. Specify the following parameters.

Parameter Name	Long Parameter Name	Description
-u	--sc.url	The URL to the Silk Central server, in the format http://host:port[/instance]. The execution server machine needs access to the specified URL.
-t	--sc.token	The Silk Central web-service token, used for user authentication.
-l	--sc.location	The name of the server group (location) to which the execution server will be added.
-h	--sc.externalhost	Optional: The host name used by Silk Central to connect to this execution server. For example, if the execution server is started in Docker, specify the host where the container is accessible.
-p	--sc.externalport	Optional: The port used by Silk Central to connect to this execution server. The default port is 19124. For example, if the execution server is started in Docker, specify the published port of port 19124. The Silk Central application server needs permission to access this port.
-k	--sc.keywords	Optional: A comma-separated list of keywords that describe this execution server.
-n	--sc.execservername	Optional: The name the execution server should be registered with.
-sr	--sc.skipselfregistration	Optional: Suppress self-registration of the execution server. The options --sc.token and --sc.location are not required when this option is used.
-ssl	--sc.usessl	Optional: Whether to connect to the execution server through SSL. Boolean.
-ut	--sc.uptime	Optional: The time in hours after which the execution server is shut down and deregistered from Silk Central. If the server is executing some job at this time, the shutdown waits for the execution to finish first. The default value is 0, meaning that the execution server is never shut down and deregistered from Silk Central.
-esp	--sc.execserverport	Optional: The port on which the execution server listens for connections from the application server. The default port is port 19124 for non-SSL connections and port 19125 for SSL connections. Specify this parameter if multiple execution servers should run on the same machine in parallel. In that case, a different port must be used for each execution server. This parameter might be useful if the execution servers are used by different Silk Central instances or installations, or with different operating system permissions. Note: Micro Focus recommends not to run more than one execution server for the same instance. Instead of running multiple servers, disable the Exclusive Execution option for the execution plans to enable parallel execution on the same execution server.

For example, such a call might look like:

java -jar sc-execserverlauncher.jar -u http://sc-host:19120 -t d28930f4-9c77-4fc7-bc1d-aac4cd235d3 -l Local -ssl true

After upgrading to a newer version of Silk Central, the launcher automatically downloads the new execution server version and restarts the execution server. Additionally, whenever the execution server is terminated, for example because of a crash, the launcher will attempt to restart the execution server.