Supported transports to publish stubs to Istio or Kubernetes
You can review the transports that support publishing stubs to Kubernetes along with any considerations before you run stubs in Kubernetes. Stubs created based only on the HTTP transport are supported in Istio.
Important: Istio supports the stubs created in HCL OneTest™ API based only
on the HTTP transport.
Transport | Directory under UserLibs in the tar.gz file to which third-party library files are automatically copied. Where blank this entry is not applicable. (See explanation in Automatic copying of library files.) | Are rule host and port environment variables required when you run a stub in Kubernetes? |
---|---|---|
File | No | |
FIX | Yes, if you are routing to the stub by using the HTTP/TCP proxy. | |
HTTP1 | Yes, if you are routing to the stub by using the HTTP/TCP proxy. | |
JMS | JMS | Yes, if you are using the sift-and-pass-through stubbing mode. |
Kafka | ||
MQTT | Yes, if you are routing to the stub by using the HTTP/TCP proxy. | |
RabbitMQ | ||
SAP RFC | SAP | Yes |
Software AG webMethods Integration Server | webMethods | Yes |
TCP | Yes, if you are routing to the stub by using the HTTP/TCP proxy. | |
TIBCO EMS | TIBCO | Yes, if you are using the sift-and-pass-through stubbing mode. |
TIBCO Rendezvous | TIBCO | No |
TIBCO SmartSockets | TIBCO | No |
UDP | ||
WebSphere® Application Server Service Integration Bus (SIBus) | WAS | Yes, if you are using the SIBus Mediation, for example, to allow sift-and-pass-through stubbing. |
WebSphere® MQ | WMQ | No |
Automatic copying of library files
When you publish a stub to Kubernetes, the library files (JAR files) required by one or more transports that are used by the stub are automatically packaged as a tag.gz archive file named userlibs.tar.gz in the output directory. The files are copied from the location that you configured in the Library Manager.