LoadRunner protocol bundles and license scope

LoadRunner is licensed not only by Vuser count but by the protocols those Vusers exercise, and the protocol bundle in your entitlement defines the scope of what you are permitted to test. When an audit reads protocol usage loosely, or treats the use of a premium protocol as if it triggered a wider entitlement requirement, the LoadRunner finding overreaches beyond the license scope you actually hold.

Performance testing tools generate virtual users that simulate real traffic, and that traffic runs over protocols: web, database, messaging, enterprise application, and a range of more specialised options that are sometimes packaged into separate or premium bundles. The entitlement that matters describes both how many Vusers you may run and which protocols they may use. An audit that counts a peak Vuser figure without regard to which protocols were exercised, or that asserts a premium protocol entitlement on the basis of incidental or test use, charges for scope the deployment did not genuinely consume. Because the EULA places compliance on the licensee, the buyer must be able to show what was actually run and under which protocol entitlement, and that evidence is where the scope argument is won.

How LoadRunner protocol scope is actually licensed

The Vuser count and the protocol scope are two separate dimensions of a LoadRunner entitlement, and a finding can overreach on either. The Vuser dimension is about volume, the peak number of simultaneous virtual users, and that question is addressed in how Vuser counting inflates a LoadRunner finding. The protocol dimension is about breadth, which categories of traffic your license permits. A bundle typically covers a defined set of protocols, and premium or specialised protocols may sit outside the standard bundle, requiring their own entitlement. The defensible position establishes which protocols the deployment genuinely uses in sustained testing, and matches that to the bundle held, rather than accepting an assertion that every protocol the tooling can technically address has been licensed or must be.

The trap appears when incidental use is read as in scope requirement. A protocol exercised once in a trial script, or available in the installation but never run in anger, is not evidence of a sustained entitlement need. Separating genuine, sustained protocol use from incidental presence is the heart of the scope defense, and it parallels the burst against sustained distinction made for Vusers in how to scope LoadRunner Vuser bursts.

Where the LoadRunner protocol scope overstates

Installed but unused protocols

LoadRunner can address many protocols out of the installation, but capability is not consumption. Showing which protocols were actually run, and which were merely present, removes the scope the deployment never used, the same capability against use distinction at work in environment scoping.

Premium protocols asserted from incidental use

A premium protocol exercised in a trial or proof of concept is not a sustained entitlement need. The usage evidence that separates the two is the discipline set out in reducing a LoadRunner finding with concurrency evidence.

Scope conflated with Vuser count

Protocol scope and Vuser volume are different dimensions, and a finding that lets one inflate the other double charges. Keeping them separate is essential, and the volume side is examined in how Vuser counting inflates a LoadRunner finding.

How we defend a LoadRunner protocol finding under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. We take over the single controlled channel and ensure the protocol usage records, the test scripts, and the entitlement bundle are captured together, because the scope argument needs all three.

Reconstruct. We build the effective license position by establishing which protocols the deployment genuinely uses in sustained testing and matching that to the bundle held, before any vendor measurement script runs.

Rebut. We challenge every line that counts installed but unused protocols, that asserts a premium entitlement from incidental use, or that lets protocol scope and Vuser volume inflate one another. The finding falls by the scope the deployment did not consume.

Resolve. We settle on the genuinely used protocol scope and, where it serves you, convert forward into an OpenPass agreement that records which protocol bundle applies, so a later review cannot reopen the scope question on installed capability alone.

An anonymised outcome

The reason protocol scope matters is the remedy behind the finding. On noncompliance the licensee is deemed to have acquired licenses at then current list price, owes back maintenance and support, owes first year maintenance on the new licenses, and reimburses the cost OpenText incurs performing the audit, so a premium protocol charged on incidental use carries that whole stack with it. Our anonymised case files show reductions of comparable scale across the estate, including a banking ArcSight finding reduced from $6.0M to $1.8M, a 70 percent reduction achieved by separating what was genuinely sustained from what merely appeared in the data. A LoadRunner protocol finding responds to the same approach: distinguish installed capability from actual use, and the overreaching scope comes off.

Match the bundle to genuine use

The lasting lesson is that a LoadRunner license is bounded on two axes, volume and protocol scope, and the scope axis is defended with evidence of genuine, sustained use rather than installed capability. A buyer who shows which protocols were actually run, and which were merely present, holds the finding to the bundle that genuinely applies. To carry the analysis further, read LoadRunner environment counts and license exposure and the Vuser volume side in how to scope LoadRunner Vuser bursts. For the full method see our ALM and LoadRunner audit defense track and our complete OpenText audit defense playbook for 2026. If a LoadRunner finding has overreached on protocol scope, open a case.