Preparing for Upgrade to DevTest 10.7.0
search cancel

Preparing for Upgrade to DevTest 10.7.0


Article ID: 227984


Updated On:


Service Virtualization CA Continuous Application Insight (PathFinder) CA Application Test


Need steps for preparing to upgrade to DevTest 10.7.0.


DevTest 10.7.0





Download DevTest 10.7.0 from the Support Portal:

From My Dashboard choose Enterprise Software from the dropdown: 


Choose My Downloads and search for SERVICE VIRTUALIZATION:


Click on SERVICE VIRTUALIZATION and you will get the below display:



Expand SV: DevTest Runtime User Seeding MULTI-PLATFORM or any one of the other products that begin with SV: 

Click on Release 10.7



This icon is for getting the Token to Download DevTest Docker containers.

Choose the products you want to download by selecting the Download box and then selecting the Download Selected pushbutton. You also may download each component separately.




Each DevTest Installer has both Workstation and Server components. Choose Server to get both, or just Workstation to not install the Server components.


From DevTest 10.7.0 onwards, we ship the license file along with the installer.


Have a plan to backup the external databases and the folder where DevTest is installed if doing an upgrade in place, in case you have to do a rollback due to a failure during the upgrade.

Take screenshots of you LDAP configuration in IAM.

If going to have new databases for DevTest 10.7.0, you will need three databases for each environment, one for IAM, one for Enterprise Dashboard and one for Registry.  So if you have three environments, that would be nine databases; but can use existing databases.

DevTest 10.7.0 uses three databases:

One for Identity Access Manager (IAM)
One for Enterprise Dashboard (EDB)
One for Registry (REG)

By default, Apache Derby databases are used when verifying out of the box for the Enterprise Dashboard and Registry.  For IAM the default is H2, Keycloak's own embedded database.

To configure to an external database for each, they will require their own schema.  Multiple IAMs, EDBs and REGs cannot share the same schemas.

Recommended size for each:

IAM:   Requires its own unique database and must have at least 25 GB of storage
EDB:  Requires its own unique database and must have at least 50 GB of storage
REG:  Requires its own unique database and must have at least 500 GB of storage


If upgrading from a release earlier than 10.3.0, you will need to create a new database for IAM.  IAM was not mandatory in 10.3.0, so if you did run IAM for use with VS Catalog, then you can use the same IAM database with 10.7.0.


You can install to a new folder or do an update in place.  Determining which one to do will depend on how you are doing your upgrade. If on Windows and you need to still keep the previous release and do parallel testing on the same machine, be aware that when you install the new version, even if to a new folder, the services will get overwritten and point to the new install location.


IAM can run on the same server as your other components, but distribution of the components has a smaller footprint on each machine, it just depends on how much testing you are doing between test cases and virtual services to know how much memory to allocate on the machine and to each component.


There are new ports that will need to be open for DevTest, refer to this documentation link for default ports:


If not doing an in-place upgrade (using existing tables), find out if your DBA needs the DDL to build each schema. It is cleaner for DevTest to create the tables, and the user would just need DBA Authority to initially start, but then after tables are created, the permissions can be downgraded.  The DDL for IAM is located in DEVTEST_HOME\IdentityAccessManager\database\ddl.  The DDL for the Enterprise Dashboard, Registry and CAI are located in DEVTEST_HOME\database\ddl.


In-Place upgrade will upgrade the tables when the components are started, so the user needs to have DBA authority the first time. The one caveat is when installing, if you are going to be using an external database for IAM, that database must already exist during the install, which is different from the Enterprise Dashboard and Registry which can be configured after installation. It is suggested to have a DBA on standby when upgrading. 


If upgrading in place to the same folder, be aware of the files that get overlaid in the folders and ones that do not.  The following list describes what happens to the main property files in an in-place upgrade:

  • The file of the existing installation is replaced with the 10.7 version.
  • The file existing installation is replaced with the 10.7 version.
  • All files that are prefixed with an underscore is replaced with the 10.7 version.
  • Any customized properties files are not replaced with a DevTest 10.7 version.


After referring and reviewing all the information here in this article, prepare the upgrade plan as per attached spreadsheet template and open a Support Case for a pre-Upgrade review of your plan on how you are planning to do your upgrade.  


See attached spreadsheet for upgrade checklist.


NOTE: The Enterprise Dashboard is backward compatible through version 8.0 and supports connections from registries of multiple versions. However, the Enterprise Dashboard itself must be the most recent version. For example, Enterprise Dashboard 10.7 can accept connections from 10.6 and 10.5 registries. Enterprise Dashboard 10.6 cannot accept connections from a 10.7 registry.


NOTE: DevTest 10.7.0 patch to apply right after install on Linux or MAC, refer to this KB:  (IMPORTANT) 


NOTE: Post 10.7 Updates:


NOTE: log4j vulnerability and how to remediate it, please follow this KB: (IMPORTANT)


NOTE: Do not apply previous version patches to DevTest 10.7.0.  To find out if the previous version patches are included in DevTest 10.7.0 release, review the Release Notes. If that patch is needed for DevTest 10.7.0, please open a new support case.



Additional Information

What's New with Service Virtualization 10.7

Preparing Your DevTest Upgrade (in the documentation)


The Release Notes section outlines the new features, enhancements, and resolved issues for DevTest Solutions. Use the Release Notes as a starting point when you first install or upgrade to a new version of DevTest Solutions.


This section describes how to install DevTest Solutions and all required components. This section also provides information about upgrading from an earlier version.     (important)


This section describes how to use each of the following components in DevTest Solutions.


DevTest Solutions includes the following agents that support various features in the product suite:
  * The DevTest Java Agent is geared toward Java-based applications.
  * The DevTest CICS Agent and the DevTest LPAR Agent are geared toward mainframe applications.

DevTest Solutions also includes the mainframe bridge, which is a component that enables the registry to communicate with the mainframe agents.


This section provides administrators with procedures to help them perform regular administrative duties in DevTest Solutions.


This section provides detailed descriptions of elements that are commonly used in DevTest Solutions and also provides an overview of the REST Invoke API. The overview includes a link to the full API documentation.


This section provides quick links to the DevTest Solutions Community, Support pages by product, Education offerings, and other resources.


You can configure your product to collect and send telemetry data — product usage and system configuration data — to Broadcom. Use the information on this page to learn how to send usage data to Broadcom.


View the documentation Legal Notice


Knowledge Documents:

What JDBC Drivers are Delivered with DevTest

JRE Error When Installing on Red Hat 7.7
Enable HTTPS and SSL between DevTest Components Using Your Own Keystore


1.  Service Virtualization 10.7 is now GA!

Tech Tips: Best Practices Installing and Verifying DevTest Out of the Box

Configure User Federation (LDAP)
NOTE: When configuring your LDAP it is best to work with your LDAP Admin on getting the right values, sometimes after importing the authentication-providers.xml and ldap-mappings.xml files to IAM, some changes made need to be done.




1637262891136__Service_Virtualization_Upgrade_Runbook.xlsx get_app