Protocols that support 64 bit recording in 11.50, 11.51 and 11.52
In general, 64-bit applications ported from a 32-bit client version should work identically to the 32-bit client. There is a small risk that new clients will use the power of native 64-bit applications. For example, when using 64-bit long types for Identifiers in DB tables, the identifier value will be cut and the query will fail.
The following guidelines apply:
- The environment for 64-bit recording must be a Windows 7 x64 or Windows 8 x64 (Windows 8 x64 added in Service Pack 11.52), and a 64-bit Application Under Test (AUT).
- Recording on 64-bit operating system for 32 and 64-bit applications (running as a 64-bit application) is supported.
- Replay is only supported for 32-bit.
- For the Java Over HTTP protocol: JVM 32-bit is required for replay.
- For the .NET protocol: There are two available 64-bit types for .NET applications (AnyCPU and pure 64-bit). LoadRunner only supports AnyCPU. There is currently no solution for pure 64-bit applications.
For replay, LoadRunner uses the same AnyCPU dlls that were used for Recording.
- Oracle 2-Tier: Both 32-bit and 64-bit clients need to be installed (the 32-bit client is required for replay).
The following table shows the protocol support for Async, IPv6, and 64-bit recording: