Server-based stubs

You can find information about the ways in which the stubs are managed in HCL® Quality Server 9.2.1 or later.

Earlier to 9.2.1, a stub that was authored and published to the server was shown in the hierarchical view of components and operations and was a one-to-one presentation of the stub definition that came from HCL OneTest™ API. Also, all configuration settings were to be specified as part of the request to start a stub.

In HCL® Quality Server 9.2.1 or later, the way in which stubs are worked with has changed. Stubs are now a representation of both their definition (published from HCL OneTest™ API) and the server-based configuration settings that is used when the stub is started. You must use both when the stub is started and managed by HCL® Quality Server. You can now pre-configure the settings that you want to use before you control the execution of the stub. A server-based stub remains in the dashboard with its current settings while new versions of the same definition are published and older versions are removed when projects are deleted in the administration page. The server-based stub continue to remain in the dashboard until all versions of the underlying definitions are removed.

When you publish a stub definition from HCL OneTest™ API, a server-based stub with a default configuration is created in HCL® Quality Server. Pre-existing stub definitions that are present in the server earlier to 9.2.1 are also migrated as new server-based stubs with default configurations. Interactions with pre-existing stub definitions are adapted to the new model in 9.2.1 and are displayed as externally-created instances of running stubs in the Environments Dashboard, where they remain in this state until they are stopped in HCL® Quality Server. For example, you can by using the HCL OneTest™ API command-line client, start a pre-existing stub definition along with its configuration settings, resulting in the creation and starting of an instance of the stub in HCL® Quality Server (displayed as an externally-created running stub instance in the Environments Dashboard).

The following stub definitions become server-based stubs:

Stub definitions published from HCL OneTest™ API 9.2.1 or later.
Pre-existing stub definitions that are migrated from HCL® Quality Server 9.2.1 or earlier, are automatically displayed in the RUNNING state.

The following stub definitions become managed stubs:

Stub definitions of both new and existing stubs that are published from the IntegrationTesterCmd tool.
Migrated stubs from HCL® Quality Server 9.2.1 or earlier, which are started after the running stubs are stopped.

If the stubs are available on HCL® Quality Server and you start the stubs, the result can be as shown in the following table:


Stub existing as a result of:	If you start the stub definition from:	Result
Stub definitions published from HCL OneTest™ API 9.2.1 or later. Pre-existing stub definitions migrated from HCL® Quality Server 9.2.1 or earlier, and are in the `STOPPED` state.	HCL® Quality Server	The same stub is started. The running stub is displayed with the icon.
	IntegrationTesterCmd by using the switch-on stub options	Another instance of the stub with the same name and configuration parameters is created on Rational Test Control Panel. The running stub is displayed with the icon.
	IntegrationTesterCmd by using the start stub options	Another instance of the stub with the same name and configuration parameters is created on Rational Test Control Panel. The running stub is displayed with the icon. Note: The stub is displayed only when it is in the `RUNNING` state and is removed from the Environments Dashboard when the stub is stopped.