Updating a managed stub by using the command line

For example, if you installed Test Virtualization Control Panel on your local host, then the command option can be:

--serverUrl https://localhost:5443/RTCP or -u https://localhost:5443/RTCP

For example, if you created the stub in the domain called default, then the command option can be:

--domain default or -d default

For example, if you created the stub in the environment called local, then the command option can be:

--environment local or -e local

For example, if you created the stub in the service component called MyServiceComp, then the command option can be:

--component MyServiceComp or -c MyServiceComp

For example, if you created the stub in the operation called StubOperation, then the command option can be:

--operation StubOperation or -o StubOperation

For example, if you created the stub with the name as Stub_1, then the command option can be:

--name Stub_1 or -o Stub_1

For example, if you published different stub versions from 1.0 to 1.5 and you want to start the stub with version 1.3, then the co--version 1.3mmand option can be:

or -v 1.3

For example, the stub with version 1.5 is started if no version is specified when you published different stub versions from 1.0 to 1.5.

For example, if you configured an agent with a particular attribute such as Windows 10, and you want this agent to be selected for running the stub, then the command option can be:

--attributes Windows10 or -t Windows10

• If you have configured Test Virtualization Control Panel to use your user credentials for a connection.
• If the environment is locked and the domain security is disabled.

For example, if you have set up Tester1 as a user on Test Virtualization Control Panel, then the command option can be:

--username Tester1 or -l Tester1

Specify the security token generated for you to authenticate with Test Virtualization Control Panel when the domain security is enabled. In the locked environment mode, the operation can be performed by the user who locked the environment.

For example, if the security token that is generated for you is X1akJHlq932i, then the command option can be:

--securityToken X1akJHlq932i

For example, if the stub has 10 worker threads defined, and you want to use 12 worker threads for its run, then the command option can be:

--workerThreadCount 12

Use this flag when you want to run the stub that uses a dedicated engine. The dedicated engine is not used to run other stubs even if they are published from the same project. If you do not use this flag in the command the stub is not run on any dedicated engine.

If you want to run the stub on a dedicated engine, you can also specify the JVM options by using the dedicatedEngineJvmOptions parameter. You can then specify the values for the attributes such as the maximum memory, the initial memory, and the garbage collection policy that must be applied for the dedicated engine.

For example, if you want to specify the attributes for the JVM to have 2GB RAM and 256GB disk space, the command can be:

IntegrationTesterCmd --serverUrl https://localhost:5443/RTCP --domain default --environment local --name ReqRepStub --version "1.0" --dedicatedEngine --dedicatedEngineJvmOptions "-Xmx2g -Xms256m -Dmy.option=\"my\ value\"" start-stub

• --force
• --forceIf
• --forceUnless

Enter the offline user token for authorizing the client to access HCL DevOps Test Hub (Test Hub) when the stub needs to access contents such as secrets.

For example, the command to start a stub using the --secretsAuthorization parameter follows:

IntegrationTesterCmd -u ${SERVER_URL} -d ${DOMAIN_NAME} -e ${ENV_NAME} -n ${STUB_NAME} --secretsAuthorization ${OFFLINE_USER_TOKEN} start-stub

For more information, see the related links.