Multi-project workspaces and central governance
Role-based projects, shared library management, and central scheduling make Enterprise PE the right shape for a performance CoE running work for many application teams.
OpenText • Performance testing
OpenText Enterprise Performance Engineering
Enterprise Performance Engineering is the centralized enterprise edition of the LoadRunner family for multi-team programs running large-scale load. Available as SaaS, on-prem, or customer-managed cloud (BYOC). Merito runs the CoE.
Merito sells OpenText Enterprise Performance Engineering (LoadRunner Enterprise lineage) and delivers centralized multi-team performance programs with project workspaces, flexible deployment (SaaS, on-prem, or BYOC), and SAP-scale load capacity.
- Best for
- Performance CoE Leads running enterprise performance programs, SAP CoE Performance Leaders for SAP peak rehearsals, Infrastructure Leaders owning on-prem generator capacity
- Hosting
- Hybrid
- Time to value
- Single program onboarded to Enterprise PE in as little as one week. First program onboarded to Enterprise PE in three to four months. Full CoE operating model (multiple projects, shared libraries, generator capacity planning) typically takes six to nine months.
- Security posture
- SOC 2 Type II (SaaS deployment), ISO 27001, GDPR
- Last reviewed
- 2026-04-26
What it is
OpenText Enterprise Performance Engineering in the enterprise stack
OpenText Enterprise Performance Engineering is the centralized enterprise edition of the LoadRunner family. It is built for enterprise performance CoEs running large-scale load tests, with multi-project and multi-team workspaces, role-based access, and long-term result archival. Deployment options span SaaS, on-prem, and customer-managed cloud (BYOC) so programs pick the hosting shape that matches their data residency and operating model.
Enterprise PE's audience is the performance CoE that runs many programs on behalf of many application teams. It is designed around shared infrastructure (generator pools on the customer's chosen hosting shape), shared scripts (reusable libraries), and shared governance (central reporting, capacity allocation). That centralized shape is exactly what large regulated programs need, and is the differentiator from Core PE's single-SaaS model and Professional PE's single-engineer workstation model.
For SAP programs running month-end close rehearsals, quarter-end financial-close load tests, and S/4HANA migration performance validation, Enterprise PE is a common fit. Customer-owned or SaaS generator capacity, scripts that match SAP user models, and centralized governance that survives audit reviews are the features SAP peak programs lean on.
Ideal use cases
- Centralized multi-team performance CoE operations
- SAP month-end close, quarter-end close, and peak-rehearsal load tests
- Large-scale load testing under customer choice of SaaS, on-prem, or BYOC hosting
- Regulated performance programs with strict data residency requirements
- S/4HANA migration performance validation
What it is best at
Where OpenText Enterprise Performance Engineering earns its seat
Customer-owned generator capacity for data residency
Load generators sit on customer infrastructure, so test traffic and test data stay inside customer governance boundaries. Required for many regulated programs.
Proven at SAP and financial-services scale
Enterprise PE (and the LoadRunner Enterprise lineage before it) is deeply deployed across SAP ECC and S/4HANA programs, banking, and insurance, where peak tests run at hundreds of thousands of virtual users.
Core capabilities
OpenText Enterprise Performance Engineering capabilities, grouped by outcome
Central program management
Multi-project workspaces, role-based access, and shared libraries for performance CoEs.
Project workspaces
Isolated workspaces per application team with central management and cross-project reporting.
Role-based access
Granular roles for performance engineers, project leads, and program managers.
Shared script libraries
Reusable scripts, data sources, and scenarios across teams and projects.
On-prem execution
Customer-owned generator pools with large-scale concurrent execution.
On-prem generator pools
Generator hosts sized for peak loads, typically across a data center or multiple data centers.
Hybrid cloud bursting
Optional cloud generators added for peak-event scenarios without permanent cloud footprint.
Large-scale concurrent execution
Hundreds of thousands of concurrent virtual users for peak rehearsals.
Enterprise reporting and governance
Centralized reporting and audit trails across all performance programs.
Long-term result archival
Historical results archived for trend analysis and audit evidence.
Regulated audit trail
Execution evidence linked to change records for audit review.
Cross-program dashboards
Performance posture across many application teams in one view.
Where it fits in the stack
How OpenText Enterprise Performance Engineering connects to the rest of your landscape
OpenText DevOps catalog (native)
Native- OpenText Core Performance EngineeringHybrid programs add Core PE for cloud bursting alongside Enterprise PE.
- OpenText Professional Performance EngineeringScripts authored in Professional run at scale in Enterprise PE.
- OpenText Service VirtualizationSimulated endpoints for dependency-constrained enterprise load tests.
- OpenText Application Quality ManagementPerformance evidence linked to regulated QA in AQM.
SAP and APM (certified)
Certified- SAP S/4HANA, SAP ECCSAP GUI and Fiori performance at enterprise scale.
- Dynatrace, New Relic, AppDynamics, DatadogAPM correlation across enterprise load tests.
Identity and data (custom)
Custom- SAML SSO and SCIMIdentity from corporate IdP.
- Data warehouse exportHistorical result export for long-term performance trending.
Deployment and implementation
How it rolls out
- Hosting
- Hybrid (North America, EMEA, APJ)
- Implementation complexity
- High
- Typical time to value
- Single program onboarded to Enterprise PE in as little as one week. First program onboarded to Enterprise PE in three to four months. Full CoE operating model (multiple projects, shared libraries, generator capacity planning) typically takes six to nine months.
- Prerequisites
- Named performance CoE owner
- Deployment shape decided (SaaS, on-prem, or BYOC) and generator capacity sized accordingly
- Multi-project governance model agreed
- Script migration plan from legacy LoadRunner Enterprise if upgrading
- What Merito usually handles
- Enterprise PE is available as SaaS, on-prem, and customer-managed cloud (BYOC); Merito picks the deployment shape that fits the customer's data residency and operating model. Merito handles environment setup, generator capacity design, CoE operating model, multi-project configuration, version upgrades from older LoadRunner Enterprise releases, and script migrations from JMeter or NeoLoad for customers consolidating onto Enterprise PE. For long-running performance CoEs, Merito's Managed Services option covers ongoing capacity management, scenario maintenance, and peak-event rehearsals.
Licensing and packaging
How it is bought
- Model
- Subscription
- What to expect
- OpenText Enterprise Performance Engineering is subscription-licensed with packaging keyed to virtual-user concurrency, project counts, and generator capacity. Pricing depends on peak concurrent VUs, number of projects, and deployment shape. Merito sells Enterprise PE alongside the CoE operating-model work that turns the license into a sustained program.
- Editions and modules
Enterprise PE standard
Multi-project performance CoE available as SaaS, on-prem, or BYOC.
Best for: Performance CoEs running work for many application teams.
Enterprise PE with Service Virtualization
Standard plus Service Virtualization for dependency-constrained load tests.
Best for: Programs where backend dependencies block end-to-end performance tests.
- Common expansion areas
- Higher VU-concurrency tiers as peak scope grows
- Core PE for cloud bursting alongside Enterprise PE
- Service Virtualization for dependency-constrained tests
- Managed Services for ongoing CoE operations
- SAP performance training for CoE engineers
Merito services
How Merito helps you win with OpenText Enterprise Performance Engineering
Merito sells licenses and the delivery work around them. Pick the service that matches where you are in the lifecycle.
01
Performance CoE Design
Operating model, project structures, generator capacity planning, and shared library governance.
Explore service02SAP Performance Testing
SAP peak-rehearsal programs (month-end close, quarter-close, S/4HANA migration) on Enterprise PE.
Explore solution03Upgrade and Migration
Upgrades to the latest Enterprise PE release (scripts and history carry forward), plus script migrations from JMeter or NeoLoad when customers consolidate onto Enterprise PE.
Explore service04DevOps Consulting
Enterprise PE wired into CI/CD pipelines for automated release gates.
Explore service05Premium Support
Named engineer, priority SLAs, and release-time coverage for Enterprise PE in production.
Explore service06Managed Services
Long-term run support including peak-event rehearsals, scenario maintenance, and generator capacity management.
Explore service07Training and Enablement
Role-based training for performance engineers, project leads, and CoE managers.
Explore service08Staff Augmentation
Merito-placed performance engineers and CoE consultants for long-running programs.
Explore serviceEnterprise PE licensing
Buy Enterprise PE from the partner that also runs the performance CoE.
Merito sells OpenText Enterprise Performance Engineering and delivers the CoE operating model, generator capacity planning, version upgrades, script migrations from JMeter or NeoLoad, and SAP peak-rehearsal programs.
Merito point of view
Enterprise PE without a CoE operating model is a license, not a program.
Merito has seen customers buy Enterprise PE expecting the license to produce a performance CoE and find that without a defined operating model, projects, scripts, and generators end up fragmented. The product supports centralization; it does not create it. Merito's engagement starts with the CoE operating model before touching the installation.
For SAP-dominant programs, Enterprise PE could be the right default. For cloud-first non-SAP programs, Core PE could be the better call. Hybrid programs run both. Merito's guidance is scope and governance first, product second.
Cloud bursting (adding Core PE capacity to an Enterprise PE program for occasional peak events) is a strong middle path. Customers retain on-prem control for day-to-day runs and buy elastic cloud capacity only for peak events that would require permanent on-prem over-provisioning.
What buyers usually underestimate
- Installing Enterprise PE before the CoE operating model is defined.
- Under-sizing generator capacity, so peak tests block on capacity rather than producing results.
- Running Enterprise PE as an infrastructure tool instead of a program governance tool.
- Skipping shared library design, so every team writes scripts differently.
- Not planning for cloud bursting, so peak events force over-provisioning.
Related from Merito
Continue exploring OpenText Enterprise Performance Engineering on Merito
Related solutions
Related services
Related products
- OpenText Core Performance EngineeringSaaS edition for cloud-first programs and hybrid cloud bursting.
- OpenText Professional Performance EngineeringDesktop edition for local script authoring.
- OpenText Service VirtualizationSimulated endpoints for dependency-constrained Enterprise runs.
- OpenText DevOps AviatorAI-assisted scenario drafting for Enterprise PE programs.
- OpenText (vendor portfolio)OpenText hub and the full DevOps and Content catalogs.
Frequently Asked Questions
OpenText Enterprise Performance Engineering FAQs
Consultation request
Talk to Merito about OpenText Enterprise Performance Engineering
Share your performance CoE scope, SAP footprint, and data-residency requirements. A Merito performance specialist follows up within one business day.
CoE first
Operating model drives the rollout
Merito designs the multi-team CoE operating model before installing Enterprise PE.
Cloud burst where it fits
Hybrid on-prem and cloud
Customers often pair Enterprise PE with Core PE for occasional cloud bursting on peak events.
Next step
Design the CoE. Size the generators. Migrate the scripts.
A Merito Enterprise PE engagement starts with the CoE operating model, sizes generator capacity against peak scope, and migrates scripts from legacy LoadRunner Enterprise.