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 the service port, OSV automatically detects which message protocol it has to use.

Forwarding and learning

It's possible that OSV doesn't know how to virtualize a request that it receives from the system under test (SUT). In this case, it can forward this request to the real service instead. All you need to do is configure your service port with data of the real service and enable Forwarding. Alternatively, you can set a proxy server on your SUT and configure OSV to act as a proxy.

If you want to know which messages OSV couldn't virtualize and forwarded to the real service, you can allow OSV to record them. This means that OSV stores the forwarded messages in the Recorder tab for you to analyze. All you need to do is enable Learning.

Configure your service port

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

• ActiveMQ Artemis

• 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