Service Virtualization Objects

Service Virtualization Objects define the capture and injection points for a specific virtualization application. Additionally, users can specify behavior (Injection, Synchronous, Asynchronous). Finally, users can configure the response profile (e.g., existing mapping) or select responding from historical messages according to the configured values.

Starting Service Virtualization Objects

Start by logging into Your SAP Fiori cockpit. Depending on Your user authorization, You will see a screen with sets of Fiori tiles. Find the one related to Service Virtualization Objects and click it.

Service Virtualization Objects elements

Once started Manage Virtualization Objects cockpit present list of Virtualization Objects created. Virtualization Object is described with ID, Description, Type and Response profile.

List of Virtualization Objects

Service Virtualization Objects create and change

Each of the Virtualization Objects can be changed by selecting it from the list. Create button allows Virtualization Object creation. To create Virtualization Object, Object Id and Description needs to be provided.

Service Virtualization Objects create and change

Basic Information

Basic Information consist of Type and Response Profile.

Type of the Virtualization Object is the key value defining what type of virtualization behavior will be perform.

Type	Description
Synchronous	Create synchronous response for the triggering message. Response is always automatic. Responses can be generated via configuration (mapping) or via historic message search.
Asynchronous	Create asynchronous response for the triggering message. Response can be manually controlled or automatic. Responses can be generated via configuration (mapping) or via historic message search.
Inject	Allow injection of the collected messages to middleware platform or the ABAP backend. Messages are collected from reference environment and can be injected to other environments. For example collected in production system and injected to test system. Injection is a manual process, there is no automatic triggering. Collection of historic data is automatic.

Response profile of Virtualization Object is the key value for the asynchronous Virtualization Object type. It is defining how the response for triggering message should be created.

Response profile

Description

History Based

Response messages are collected from the reference environment.

When triggering message is catched, Int4 Messenger is scanning response messages collected from the reference environment for the response that will match the triggering message. Found message is saved as a response.

Configuration Based

Response is created by processing triggering message through the mapping.

Result of the mapping is saved as a response.

Processing

Processing consist of Automation Object that is used to monitor triggering messages - Trigger Object and Automation Object that is used to inject message - Response Object.

Message collection for the Inject and History Based Virtualizations are collected based on the Response Automation Object.

Read more about Automation Objects Automation Objects

Response Mapping

This section is used by the Asynchronous Virtualization Object Type and its content is dynamic, based on the Response Profile.

a) History Based - values found for the trigger object needs to be found in the collected responses in a provided Folder with historic data. Many pairs of values Trigger/Response can be defined as a key for this search. Result of the search is the response that is send back as a virtualized response.

If the synchronous trigger is GET message with empty body, whole HTTP call with all header parameters is stored as a Request and can be scan via REGEX expression.

Parameter	Description
Trigger Value	Expression (XPath, JSONPath or REGEX) that is used to fetch values from the triggering message
Response Value	Expression (XPath, JSONPath or REGEX) that is used to fetch values from the collected response messages

b) Configuration Based

Parameter

Description

Mapping Type

Two mapping types are available

a) Integration Platform Mapping - mapping is performed via integration platform supported by Int4 Suite or Generic HTTP service (test type 54)

b) XSLT Mapping - mapping is performed via XSLT mapping in ABAP backend where Int4 Messenger is installed

Mapping

Int4 Suite Test Case number that contains either reference to the Integration Platform Mapping or XSLT mapping