What's new

This topic introduces the new features and improvements in OpenText Service Virtualization 26.3. To view enhancements for prior releases, see What's new in earlier versions.

Note: The Help Centers for 25.3 - 26.3 versions are streamlined into a single Help Center. Any version-specific changes are indicated where relevant.

Architecture updates

The embedded server architecture has been decoupled, and the embedded runtime now uses a standalone server model. Decoupling the embedded server architecture improves compatibility with modern runtime and deployment environments. It also reduces differences between local embedded usage and server-based deployments.

Agent and technology updates

  • Kafka support is introduced as a new Beta capability, integrated across SV Designer and SV Server.

  • Design and run Kafka-based virtual services, giving teams an early way to virtualize Kafka integrations in modern, event-driven environments.

For details, see Configure the Kafka agent.

Security and infrastructure improvements

  • This release includes continued security hardening and maintenance updates across the platform.

  • Third-party libraries and core dependencies were updated to newer supported versions to reduce security exposure and improve long-term supportability.

  • Additional .NET and Java dependency updates are included to improve maintainability.

  • Certificate handling was improved on Windows by automatically adding required chained certificates to the certificate store, reducing certificate-related setup and connectivity issues.

Bug fixes

The following issues have been resolved:

  • Fixed an issue where projects opened in SV Designer from server-exported archives could reference an associated server that was not present in the SV Designer server list.

  • Prevented credentials cached for deleted servers from being reused unexpectedly in SV Designer.

  • Corrected an issue in SV Manager where filtering by project did not always return the expected results.

  • Resolved an inconsistency in SV Manager service selection behavior.

  • Improved SV Designer startup stability by resolving initialization and context loading issues that could cause startup errors.

  • Corrected project ID inconsistencies that could occur when projects were exported and imported between SV Manager and SV Designer.

  • Resolved an issue where some error messages started with incorrect text, causing SV Manager to group different errors under the same Problem List category.

  • The HTTPS Gateway agent no longer fails to start with "The specified network password is not correct" when loading Service Virtualization-generated PKCS#12 certificates.

  • Fixed a crash in SV Designer caused by deeply nested request and response structures leading to a StackOverflowException on import.

See also