SV Lab Protocols
The SV Lab supports a variety of transport protocol and message format combinations:
| Transport | Binary/Text | XML | JSON | SOAP |
|---|---|---|---|---|
| HTTP/HTTPS (1) | ✓ | ✓ | ✓ | ✓ |
| AMQP 1.0 (2) | ✓ | ✓ | ✓ | |
| Apache Kafka | ✓ | ✓ | ✓ | |
| Azure Service Bus | ✓ | ✓ | ✓ | |
| IBM MQ | ✓ | ✓ | ✓ | |
| JMS | ✓ | ✓ | ✓ | |
| MQTT | ✓ | ✓ | ✓ | |
| RabbitMQ (AMQP 0.9) | ✓ | ✓ | ✓ |
Notes:
- [1] Including REST services with JSON, XML and binary/text messages
- [2] AMQP 1.0 supported using the Apache Qpid JMS library and JMS protocol
Detailed documentation
While service models are written using a protocol-independent simulation language, the service interface and virtual lab configuration are based on protocol used by virtual service.
The protocol specifics of service interface, connector and endpoint configuration are documented in following chapters:
| Protocol | Service Interface | Lab Configuration |
|---|---|---|
| REST | REST service interface | HTTP proxy connector |
| SOAP | SOAP service interface | HTTP proxy connector |
| Apache Kafka | Kafka service interface | Kafka connector |
| Azure Service Bus | JMS service interface | JMS connector (Azure) |
| IBM MQ | JMS service interface | JMS connector (MQ) |
| JMS | JMS service interface | JMS connector |
| MQTT | MQTT service interface | MQTT connector |
| RabbitMQ | RabbitMQ service interface | RabbitMQ connector |
Virtual service licensing
The license consumed by virtual service in simulation or invocation mode depends on the protocol group:
- WEB/IoT protocols
- HTTP/HTTP(S)
- MQTT
- JMS
- IBM MQ
- Enterprise protocols
- Apache Kafka
- RabbitMQ