|
Name
|
You can change the name of the published stub and to save your changes, click
SAVE.
|
|
Version
|
You can set the version of the stub by selecting the version available in the
list. Note: If the Test Virtualization Control Panel command line or Apache Ant tasks are used to start a stub, and if no stub
version information is provided, it is the latest version of a stub that is
run. |
|
Logging Level
|
Use the Logging Level option to modify the
currently selected stubs log level that determines the level of details that are
written to the project results database. By default, logging is disabled when you
deploy a stub to improve performance. Note: The changes to the
Logging Level option are immediately applied to the
running stub without the stub restarting. Log level options are as follows:
- None (default)
- Normal
- Debug
Log messages are written to the project results database if you have configured
one, and to the HCL DevOps Test Integrations and APIs Agent (Test Integrations and APIs Agent) log file. Normal log messages are saved to the project results database
only. With Debug logging, more messages (in addition to those found in the
project results database, if any) are written to the Test Integrations and APIs Agent log file. Example:
- Normal:
[07/03/2018, 15:43:55.642] Instance 1: Message Case: "Text" using schema "Text" Stub input filters passed, continuing to subtree.
- Debug:
[07/03/2018, 15:43:55.658] [Debug] Instance 1: Tag write: Value1 (1)
[07/03/2018, 15:43:55.658] [Debug] Instance 1: Tag write: Value2 (2)
Note: If you observe any delays with the stub response time, set the
log level to None. This would avoid any delays due to the time taken to log
details to the results database.
|
|
Input tags
|
Displays the input tags of the currently selected version of the stub.
Use this section to override the configured input tag values for the currently
selected version of the stub.
Expand Input tags section to list the input tags specified
for the selected version of the stub. To override the configured value of an input
tag, click Input tags enter a new name under the
tag name field and enter the value under the
result field associated with it. To force the value of a
tag to be null, push the slide-button to the right against the Is
Null? field.
Note: The changes that you make to the input tags are
immediately applied to a running stub without a restart of the running stub.
However, if you want to change any input tag values that are used within stub
behaviors, you must first stop the running stub, modify the input tag values, and
then restart the stub for the changed values to be applied.
|
|
Response Time
|
Use this section to override the currently selected stubs response time behavior.
By default, the stub response time behavior will be as it was defined when the stub
was published. You can choose to have no delay to responses, or to configure a
fixed, uniform or Gaussian delay distribution. Note: The overridden settings apply
to all operations in the stub. Delay distributions options are as follows:
| Option |
Description |
|
No delay
|
Select this option for a response time with no delay.
|
|
Fixed delay
|
Select this option for a fixed delay in the response time by entering the
required delay in milliseconds (ms).
|
|
Uniform distribution
|
Select this option for a uniformly distributed random time by specifying the
minimum and maximum delay, by sliding the pointer to the required delay in
milliseconds (ms).
|
|
Gaussian distribution
|
Select this option for a random time with Gaussian distribution by specifying
the minimum and maximum delay, by sliding the pointer to the required delay in
milliseconds (ms).
|
Note: After a stub has started, its response time can be modified while it is
running.
|
|
Agent Tags
|
You can view and choose the agent tags to restrict agents where the stubs are
run.
|
|
Dedicated JVM
|
You can choose to use a dedicated Virtual Machine (VM) to run the stubs that
allows for customized JVM arguments to be run on the stubs. If you intend to use
this resource, click the Required check box and provide the
details of the dedicated JVM.
|
|
Performance
|
You can modify the currently selected stubs performance settings. By default, a
stub uses the performance option that is set when the stub was published. This
includes specifying the number of requests to the stub that can be handled
simultaneously. You can optimize the performance by selecting the
Optimize performance check box. You can also enter the
number of simultaneous requests in the Worker Threads field
or use the increase/decrease button ( ) to change the
available threads.
For more information on the Performance optimization settings, see The Properties tab.
|
|
Pass-through
|
You can modify the stubs behavior to respond to messages received. You can select
an option from the list that modifies what was set in Test Integrations and APIs for the stubs responses to messages received:
| Simulate Error |
Use this option to simulate an error when a message is
received. |
| Pass-through |
Use this option for the stub to pass the message to the next operation.
If no other operation exists, the stub moves the message to the
application. |
| Discard |
Use this option to discard the message. |
|
