Broad protocol coverage
REST, SOAP, JMS, MQ, mainframe bridges, and dozens more. Covers the protocols that actually block enterprise test scope.
OpenText • Performance testing
OpenText Service Virtualization
Service Virtualization simulates the systems your tests depend on so performance and functional suites run without waiting for environments. Merito designs the virtual-service catalog.
Merito sells OpenText Service Virtualization and delivers virtual-service catalog design, protocol modeling, and CI-pipeline integration so performance and functional tests run without blocking on backend dependencies.
- Best for
- Performance Engineers unable to run load tests due to downstream dependencies, Test Architects designing dependency strategies for functional regression, QA Leaders managing SIT environment access for partner systems
- Hosting
- On-prem
- Time to value
- First virtual service live in as little as one week for narrow scope. First virtual service live in four to six weeks. Meaningful catalog (ten or more services) built in three to five months.
- Security posture
- ISO 27001, GDPR, SAML SSO
- Last reviewed
- 2026-04-26
What it is
OpenText Service Virtualization in the enterprise stack
OpenText Service Virtualization (SV) simulates the services your tests depend on (downstream APIs, third-party systems, mainframe bridges, message queues) so tests run consistently regardless of whether the real dependency is available, rate-limited, or cost-restricted. It is a companion product to Core PE, Professional PE, Enterprise PE, Functional Testing, and Functional Testing for Developers.
The value of SV is not replacing integration tests; it is unblocking performance and regression work when a dependency is not test-ready. Mainframe access windows, third-party API rate limits, and partner SIT environment capacity often block load tests and large regression runs. A simulated endpoint that responds realistically removes the block.
Service Virtualization is easy to adopt poorly. Teams that simulate everything lose confidence that the tests reflect real behavior. Merito's engagements scope SV narrowly and simulate what is blocking the test, keep the real dependency in the loop where trust matters, and document the fidelity profile of each virtual service.
Ideal use cases
- Unblocking performance tests when downstream APIs are rate-limited
- Simulating mainframe and legacy dependencies for front-end load tests
- Modeling partner SIT environments for regression under backend-constrained scenarios
- Reducing third-party API cost during large load tests
- Parallel feature development when backend services are not yet available
What it is best at
Where OpenText Service Virtualization earns its seat
Fidelity-aware modeling
SV supports static, dynamic, and record-replay modeling, so each simulated service can be tuned to the fidelity the test actually requires.
Integrates natively with Core, Professional, and Enterprise PE
Performance engineers wire virtual services into load scenarios without custom adapters. Functional testing integrations work the same way.
Core capabilities
OpenText Service Virtualization capabilities, grouped by outcome
Protocol modeling
Enterprise protocol coverage for service virtualization across test scopes.
REST and SOAP
Web service simulation with content-based routing and templated responses.
Messaging
JMS, MQ, Kafka, and broker-based messaging simulation.
Mainframe and legacy
Mainframe (3270, 5250) and thick-client simulation for legacy integration scenarios.
Fidelity modes
Simulation tuned to the fidelity the test requires.
Static responses
Fixed response modeling for predictable tests.
Dynamic responses
Stateful simulation with response logic based on request content.
Record and replay
Capture real traffic and replay under load with realistic latency profiles.
Program integration
Virtual-service catalogs used across performance and functional testing programs.
Performance Engineering integration
Virtual services consumed natively by Core, Professional, and Enterprise PE scenarios.
Functional Testing integration
Functional Testing and Functional Testing for Developers use virtual services to unblock end-to-end flows.
CI pipeline integration
Virtual services deployed and torn down as part of pipeline execution.
Where it fits in the stack
How OpenText Service Virtualization connects to the rest of your landscape
OpenText DevOps catalog (native)
Native- OpenText Core Performance EngineeringVirtual services consumed by Core PE SaaS scenarios.
- OpenText Professional Performance EngineeringLocal Professional runs use virtual services for dependency-constrained scripts.
- OpenText Enterprise Performance EngineeringEnterprise CoE programs use virtual services at scale.
- OpenText Functional TestingFunctional suites use virtual services to unblock end-to-end flows.
Protocols (certified)
Certified- REST, SOAP, JMS, MQ, Kafka, mainframe protocolsBroad enterprise protocol coverage.
- SAP interfaces (RFC, IDoc)SAP integration simulation for SAP-adjacent performance and functional tests.
CI/CD (custom)
Custom- Jenkins, Azure DevOps, GitHub Actions, GitLab CIVirtual services deployed and torn down as part of pipeline execution.
- KubernetesVirtual services run as containerized workloads for modern deployment patterns.
Deployment and implementation
How it rolls out
- Hosting
- On-prem (North America, EMEA, APJ)
- Implementation complexity
- Moderate
- Typical time to value
- First virtual service live in as little as one week for narrow scope. First virtual service live in four to six weeks. Meaningful catalog (ten or more services) built in three to five months.
- Prerequisites
- Identified dependencies blocking performance or functional tests
- Named virtual-service catalog owner inside the performance or QA CoE
- Protocol inventory for the dependencies in scope
- Fidelity profile agreed per virtual service
- What Merito usually handles
- Merito handles Service Virtualization setup, protocol modeling, virtual-service catalog design, and CI integration. SV enablement feeds existing performance and functional testing programs; Managed Services and Staff Augmentation cover ongoing catalog maintenance and operations when programs want Merito to run them.
Licensing and packaging
How it is bought
- Model
- Subscription
- What to expect
- OpenText Service Virtualization is subscription-licensed with packaging keyed to concurrent virtual services and user seats. Pricing depends on service counts, concurrency, and bundling with Performance Engineering editions. Merito typically sells SV alongside Core PE, Professional PE, or Enterprise PE where dependency-constrained tests are the primary use case.
- Editions and modules
Service Virtualization standard
Virtual service modeling, runtime, and CI integration.
Best for: Performance and functional testing programs blocked by dependencies.
- Common expansion areas
- Additional virtual service capacity as the catalog grows
- Higher concurrency tiers for multi-team CoE programs
- Functional Testing integration for end-to-end flow testing
- Training for virtual-service catalog engineers
- Managed Services for ongoing catalog maintenance
Merito services
How Merito helps you win with OpenText Service Virtualization
Merito sells licenses and the delivery work around them. Pick the service that matches where you are in the lifecycle.
01
Virtual Service Catalog Design
Protocol modeling, fidelity profiles, and catalog governance across programs.
Explore service02SAP Testing
SAP-adjacent dependency simulation (RFC, IDoc) for SAP load and functional tests.
Explore solution03DevOps Consulting
Virtual services integrated with CI pipelines for ephemeral deployment.
Explore service04Premium Support
Named engineer, priority SLAs, and release-time coverage for Service Virtualization in production.
Explore service05Managed Services
Ongoing catalog maintenance, fidelity tuning, and protocol updates.
Explore service06Training and Enablement
Protocol modeling workshops and catalog-engineer training.
Explore service07Staff Augmentation
Merito-placed virtualization engineers embedded with performance and QA CoEs.
Explore serviceSV licensing
Buy SV from the partner that also designs the virtual-service catalog.
Merito sells OpenText Service Virtualization and delivers the protocol modeling, fidelity-profile design, and CI integration that unblock performance and functional tests without losing trust in results.
Merito point of view
Virtualize what blocks the test. Keep the real dependency in the loop where trust matters.
Merito has seen customers virtualize every backend dependency and lose confidence in their test results. The pattern is and simulate when a dependency is actually blocking, keep the real system in the loop when behavior matters. Each virtual service has a documented fidelity profile; tests that need high fidelity do not run against virtual services.
Service Virtualization pays back fastest on performance tests constrained by rate-limited third-party APIs or mainframe access windows. It pays back slowest on functional tests where integration coverage matters. Merito's engagement scopes SV narrowly to the dependencies that actually block the program.
Virtual services need maintenance. When the real service evolves, the simulation drifts. Merito's Managed Services option covers ongoing catalog maintenance so programs do not accumulate stale simulations.
What buyers usually underestimate
- Simulating dependencies where integration coverage actually matters.
- Not documenting fidelity profiles, so tests inadvertently depend on low-fidelity simulations.
- Letting virtual services drift when real services evolve.
- Treating SV as a QA backup rather than a performance-program enabler.
- Trying to build the full catalog before any tests actually run against it.
Related from Merito
Continue exploring OpenText Service Virtualization on Merito
Related solutions
Related services
Related products
- OpenText Core Performance EngineeringSaaS performance testing that consumes virtual services.
- OpenText Enterprise Performance EngineeringOn-prem performance CoE that consumes virtual services at scale.
- OpenText Functional TestingFunctional automation using virtual services to unblock end-to-end flows.
- OpenText DevOps AviatorAI-assisted defect categorization for virtualized test runs.
- OpenText (vendor portfolio)OpenText hub and the full DevOps and Content catalogs.
Frequently Asked Questions
OpenText Service Virtualization FAQs
Consultation request
Talk to Merito about OpenText Service Virtualization
Share the dependencies blocking your performance or functional tests. A Merito SV specialist follows up within one business day.
Narrow scope
Simulate the blocker, not the world
Merito's SV engagements focus on the dependencies that actually block performance or functional tests.
Fidelity documented
Each virtual service has a profile
Every simulated service ships with a documented fidelity profile so tests know what they are relying on.
Next step
Simulate what blocks. Keep the real service where it matters.
A Merito SV engagement scopes virtual services narrowly to the dependencies that block your tests and documents fidelity for each one.