OSV Glossary

Tosca OSV has processed all messages of the Scenario. You can display completed Scenarios in the OSV Monitor.

OSV messages are either inbound or outbound. You can specify the required direction in the Use the Virtualization tab.

OSV automatically detects the required message format.

Message detection algorithms use identification elements to create the Identifier for a Scenario.

The identifier helps OSV to distinguish between various pending Scenarios.

Communication between the system under test (SUT) and OSV.

Messages are characterized by their direction, transport, and payload.

A Scenario is comprised of multiple inbound and outbound messages.

OSV uses message detection algorithms to assign inbound messages to a Scenario.

The payload of a message consists of message elements, such as a name or address.

You use Module Attributes to steer these message elements in your Scenario.

An OSV Environment is a logical grouping for your test activities.

For instance, you can group different applications, systems, or test environments that you want to virtualize.

The OSV Host is the main OSV component that you install on a workstation. It hosts your OSV Environments.

You use the OSV Monitor to monitor and manage OSV Environments and Scenarios, and to record messages.

Each OSV user is part of an OSV user group. The group's rights determine the user's access rights to OSV-specific functions.

The payload contains the content and functional information of the message.

OSV is currently processing the messages of the Scenario.

You can check pending Scenarios in the OSV Monitor.

The service that you want to virtualize. You use it to record messages.

When you use the Recorder, OSV listens to the communication exchange between a client and a real service.

A Scenario maps a business case in Tosca OSV.

The process of defining message and Scenario elements.

You have defined a specific date and time for the processing of your Scenario.

A service port is a virtual service endpoint in an OSV Environment.

You create a service port for each real service that your application uses.

The service port type indicates which type of real service you virtualize in OSV. For example, HTTP or MSMQ.