Management of virtualized services

Disclaimer: This release contains access to the virtual services that virtualize the Istio based services feature in HCL OneTest™ Server as a Tech Preview. The Tech Preview is intended for you to view the capabilities for virtualized services offered by HCL OneTest™ Server, and to provide your feedback to the product team. You are permitted to use the information only for evaluation purposes and not for use in a production environment. HCL provides the information without obligation of support and "as is" without warranty of any kind.

You can find information about the tasks that you can perform on and manage the virtualized services that run on HCL OneTest™ Server. You can start or stop the virtual services that are available to HCL OneTest™ Server. You can view the routing rules and usage statistics of virtualized services, agents, or intercepts that are connected to HCL OneTest™ Server.

You can create stubs or virtual services in HCL OneTest™ API or in HCL OneTest™ Server. You must commit the virtual service resources to a remote Git repository, and then add the Git repository to your project on HCL OneTest™ Server if you used HCL OneTest™ API to create virtual service resources.

You can start a running instance of the virtual services from HCL OneTest™ Server to run on the following locations:
  • A registered API agent.
  • The default Kubernetes cluster of HCL OneTest™ Server.
  • A remote Kubernetes cluster.

You can run all virtual services on registered API agents except the virtual services that use CICS transport, DB2/Z transport, or Istio.

The default Kubernetes cluster or a remote Kubernetes cluster supports running of the following types of virtual services:
  • Virtual services that utilize the WebSphere® MQ transport.
  • Virtual services that utilize the HTTP transport.
  • Virtual services that virtualize the Istio based services. You can run virtual services for the following types of requests received or sent by the Istio service mesh:
    • Requests received by services in the Istio service mesh.
    • Requests sent from namespaces in the Istio service mesh to external services that are not in the Istio service mesh.
Restriction: You cannot run virtual services on a remote Docker host.
If running a virtual service in a Kubernetes cluster, the following are the considerations that decide the selection of a container:
  • Before a container is selected to run a virtual service, it is checked for a previous failure to start a virtual service or for a low heap size, and other conditions. If the container was not found suitable, then it is not selected for running the virtual service.
  • Multiple virtual services can be run in the same container if the following conditions are satisfied:
    • Subsequent virtual services are started by the same project member.
    • All virtual services are created and contained in the same HCL OneTest™ API project.
    • The requests to run the virtual services refer to the same version, meaning that the git commit IDs on which they are based are the same. If you use the UI, this means that the Version field in the Execute virtual service dialog are the same.
    • The settings that you configure in the Advanced settings for the virtual services are the same.
    • The datasets selected for an override are the same, if datasets are used.

Working with virtual services

You can perform the following tasks on virtual services on HCL OneTest™ Server: