Preparing for Upgrade to DevTest 10.6.0
search cancel

Preparing for Upgrade to DevTest 10.6.0


Article ID: 187023


Updated On:


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


Need steps for preparing to upgrade to DevTest 10.6.0.


Release : 10.6.0

Component : CA Service Virtualization




Notify your Broadcom Account Manager that you will be doing an upgrade of DevTest   
Provide a plan to your Broadcom Account Manager on how you are planning to do your upgrade. Your Broadcom Account Manager, will reach out to someone in Broadcom Support for review.
If upgrading from earlier than DevTest 10.3.0, will need a new license, else, you can use your current license.
Download DevTest 10.6.0 from the Support Portal  (there are 2 pages):
Choose Product SV: DevTest Runtime User Seeding MULTI-PLATFORM (all products with a 10.6 release all have the same components.)  If needing the Docker installer choose the green key and follow the instructions.

Each DevTest Installer has both Workstation and Server components.

Open a Support Case for a pre-Upgrade review of your plan.

Have a plan to back up the external databases and the folder where DevTest is installed, in case you have to do a rollback due to a failure during the upgrade.

If going to have new databases for DevTest 10.6.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.

Recommended size of external databases for DevTest 10.6.0 and later

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.6.0.

You can install to a new folder or do an update in place.  Determine which one to do will depend on how you are doing your upgrade. If upgrading from a release earlier than 10.3.0, suggest going to a new folder. If 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, 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 IAM and VS Catalog (51110 and 51111), 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. We think 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

In-Place upgrade will upgrade the tables as well 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:

Property Files
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.6 version.
  • The
     file of the existing installation is replaced with the 10.6 version.
  • The
     file of the existing installation is replaced with the 10.6 version.
  • The
     file of the existing installation is replaced with the 10.6 version.
  • The file of the existing installation is replaced with the 10.6 version.
  • The file existing installation is replaced with the 10.6 version.
  • If you created a
     file, the file is preserved as is.
    If you are upgrading from a version that predates the file, a
     file is created. Any customized properties for Enterprise Dashboard in your
     file are migrated to a
  • If you created a
     file, the file is preserved as is.
  • If you created a
     file, the file is preserved as is.
  • If you created a file, the file is preserved as is.
You are not supposed to modify the
 file. If you did make changes to the
 file, the upgrade process overwrites the changes.
If you had a patch in your previous version, go to the DevTest 10.6 Resolved Issues section of the documentation to see if it was included in this release: If you are upgrading from more than one older release, say from DevTest 10.4 and now going to DevTest 10.6, review the Resolved Issue in DevTest 10.5, if the patch was included in 10.5, then it will be included in 10.6.
If not, then open a support case to get the same patch for DevTest 10.6.0.
NOTE: Never apply a previous release patch to DevTest 10.6.0.
Preparing Your DevTest Upgrade

Additional Information



Knowledge Documents:

JRE Error When Installing on Red Hat 7.7

Enable HTTPS and SSL between DevTest Components Using Your Own Keystore



Service Virtualization 10.6 is now GA!

Tech Tips: DevTest Third-Party Files

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. We require more fields to be filled out now with DevTest 10.6.0.