Service Virtualization

Welcome to Service Virtualization Community!

This is where Service Virtualization Current Community Members and product experts connect to share questions, ideas and feedback. Here you will find the right people and tools to help you with every stage of your journey, whether you are just getting started, need help, or want to make the most of your investment. We’re glad you’ve joined us!

 View Only

What's New

  • Heads up: Upcoming End of Support dates for Service Virtualization 10.8.x

    Hi everyone,

    Just wanted to flag some important dates coming up regarding the lifecycle of the Service Virtualization 10.8 family.

    It’s time to start planning your upgrades, as we have announced the End of Service (EOS) schedule for several versions. Here is the timeline you need to know:

    • Service Virtualization 10.8 & 10.8.1: Support ends January 31, 2027
    • Service Virtualization 10.8.3 & 10.8.4: Support ends September 1, 2027

    The Recommendation: To stay supported and get the newest features, the move is to upgrade to Service Virtualization 10.9.

    Want to see what's new?

    We are hosting a webinar to walk through the 10.9 features. It’s a good opportunity to see what you'll be gaining in the upgrade.

    Thursday, Feb 26, 2026 | 12:30 PM EST

    👉 Secure your spot here

    📢 You can check out the official announcement here for more details:

    EOS Announcement for versions 10.8 and 10.8.1

    EOS Announcement for versions 10.8.3 and 10.8.4

  • 🚀 Service Virtualization 10.9 is Live! (Released Dec 3, 2025)

    We are excited to announce that Service Virtualization Solutions 10.9 is officially here! As of December 3, 2025, this release is available for download. We’ve focused heavily on performance scaling, usability improvements, and keeping your environments secure.

    Here is a look at the highlights of what you can expect in v10.9.

    🌟 Top New Features

    1. Automated VSE Scaling (Kubernetes/OpenShift)

    For those running performance tests, this is a game-changer. VSE instances can now scale dynamically based on workload.

    • How it works: When the load increases, additional Kubernetes Pods are automatically provisioned to handle the traffic.
    • Why it matters: This ensures optimal resource utilization during your peak testing times without manual intervention.
    • ⚠️ Important Licensing Note: To use this "Performance Mode," you will need a 'VSE for Performance' license. Every scaled Pod counts as a separate copy for licensing purposes. Please reach out to Sales and Technical Support to enable this on your environment.

    2. Enhanced Logging for Better Troubleshooting 🛠️

    We know that debugging in replicated environments can be tough. We've overhauled the logging system to make your life easier:

    • Hostname Identification: Log files now include the hostname in the filename, so you know exactly which replica generated the log.
    • Better Organization: Logs are now neatly segmented into component-specific subfolders within $(Service Virtualization_HOME)/logs/.

    3. Virtual Service Catalog UI Makeover

    The Catalog has a fresh new look and improved usability!

    • New UI: A modernized, cleaner interface.
    • Simplified Configuration: We’ve made the application.properties file easier to read (with auto-migration included) and simplified custom port configurations.
    • IAM Updates: A streamlined process for updating your IAM instance URL.


    🛡️ Security & Compatibility Updates

    Security Patches

    We take security seriously. This release addresses a significant number of vulnerabilities to keep your testing pipeline secure.

    🖥️New Platform Support

    We have added support for the latest OS and Database versions to ensure you can run Service Virtualization where you need it:

    • Operating Systems: Windows Server 2025, Red Hat Enterprise Linux 10, and MAC OSX 15.6.
    • Database: PostgreSQL 17.6.

    📚 Learn More

    For the deep dive into Configure Virtual Service Environment Scaling or the full list of fixed CVEs, please check out the official Release Notes documentation.

Search Community

Latest Discussions

  • Hi Vinay,, VS Response time is total time of the transaction processed from when it is received and responded. You might see more time based on the network delays or any Think Time is in the VSM steps. Based on the Match Style, transaction match will ...

  • We have a consumer app sending a request which has an image data of 1.4 MB average, and at lisa the response is set to operation mode. When lisa is parsing the request, is lisa considering payload size for responding ? or just ignore payload and send ...

Latest Blog Posts

  • Broadcom Service Virtualization – Helping Dev Teams Test Mainframe and Distributed Systems Faster and Safer By Uttam Anand Mainframe application testing is essential to ensure the reliability, performance, and security of systems that support ...

Latest Shared Files