Configure service ports

A service port is a virtual service endpoint. You can create one for each real service that your application uses. Your system under test (SUT) then sends its requests to these Tosca OSV service ports.

Service port types

During service port configuration, you have to define which type of virtual service endpoint you want to create.

For instance, you can create an HTTP service port that uses SOAP protocol. Or you can use a directory as service port, which reads and writes messages locally on your machine.

You can also work with Java Message Service (JMS) in OSV. When you configure a JMS service port, OSV acts as a consumer or publisher of messages. For detailed information on JMS messaging, see chapter "Run JMS messages".

Once you have configured a service port, OSV automatically detects which message protocol it has to use. Furthermore, OSV can forward messages to a real service, if you configure the service port with data of the real service. This enables OSV to forward a request from the SUT to the real service in case it doesn't know how to virtualize it. Alternatively, you can set a proxy server on your SUT and configure OSV to act as a proxy.

Get started

If you want to learn how to create any service port, see chapter "Create and edit service ports".

If you want to know more about configuring specific service port types, select a type from the list below:

• ActiveMQ

• Directory

• HTTP (HTTPS)

• IBM MQ

• Kafka

• Minimal Lower Layer Protocol (MLLP)

• Microsoft Message Queuing (MSMQ)

• Oracle WebLogic

• Rabbit MQ

• Secure File Transfer Protocol (SFTP)

• Tibco EMS