Preparing for Upgrade to DevTest 10.7.2
search cancel

Preparing for Upgrade to DevTest 10.7.2

book

Article ID: 238001

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

Steps for preparing to upgrade to DevTest 10.7.2.

Environment

Read the System Requirements (important) for operating systems, databases and JVM we support with DevTest 10.7.2.

Resolution

Download the DevTest 10.7.2 Software

Download from the Support Portal: https://support.broadcom.com . From My Dashboard chose 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 the above SV: DevTest Runtime User Seeding MULTI-PLATFORM or any one of the other products that begin with SV: 

Click on Release 10.7.2

 

 

This icon is to get the Token Downloading for 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.

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

 

Type of Upgrade

. In-place (same folder)
* Backup your current DEVTEST_HOME folder on all machines where DevTest is installed and planning to do an upgrade.
* Backup all your current DevTest databases used by IAM, Enterprise Dashboard and Registry(s).
* Take screenshots of you LDAP configuration in IAM. 
For upgrading in place to the same folder, be aware of the files that are 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 lisa.properties file of the existing installation is replaced with the 10.7.2 version.
  • The logging.properties file of the existing installation is replaced with the 10.7.2 version   (NOTE: the format of this file has changed, so do not overlay a previous release logging.properties file)
  • The iam.properties file existing installation is replaced with the 10.7.2 version.
  • All files that prefixed with an underscore is replaced with the 10.7.2 version.
  • Any customized properties files are not replaced with a DevTest 10.7.2 version.
 
. New Folder
* Backup all your current DevTest databases.
* Take screenshots of you LDAP configuration in IAM.
* Important:  Once the software is installed, DO NOT copy any earlier versions of a deliverable jar file to any of the folders.

 

 NOTE: applies to In-place and New Folder when using H2 database for IAM:

Migrate Data for the Default IAM Embedded Database (H2) Before Upgrading to DevTest 10.7.2

 

External Databases

New Databases:
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.2 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, you will require own database for each component.  Multiple IAMs, EDBs and REGs cannot share the same databases.

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

Find out if your DBA needs the DDL to build each database. 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 are located in DEVTEST_HOME\database\ddl.

NOTE: The Registry database has two DDL files to run.  database.dll and database_cai.dll. Where database is the database you will be using.

If your DBA is not creating the tables and letting DevTest do this, the user needs to have DBA authority the first time. 

 

Existing Databases
The upgrade will upgrade the tables when the components are started, so the user needs to have DBA authority the first time. 

 

Checklist

After referring and reviewing all the above information 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.

 

Post Upgrade

1. DO NOT apply previous version patches to DevTest 10.7.2.  To find out if the previous version patches are included in DevTest 10.7.2 release, review the Release Notes.  2

2. DO NOT copy a previous versions property files to the current version. If there are properties you need from a previous version, copy and paste each property from the old to the new version properties file.

3. Post 10.7.2 Updates:  Post 10.7 Updates  (DevTest 10.7.2 updates can be found in the DevTest 10.7.0 documentation.) 

4. Post 10.7.2 Updates concerning Log4j,  commands have changed so review the properties: Log4j Upgrade

5. DevTest 10.7.2 patches: Service Virtualization: Hot Fixes (Support Patches) and Service Packs


 

Additional Information

 
10.7.2 includes all the great new features in 10.7 as well as:
Upgrading Apache Log4J to Apache Log4J 2.17.1
  • V3 API Enhancement: Ability to Specify Match Tolerance for RR Pair Import
  • Support for Ubuntu 20.04
  • The latest vulnerability and defect fixes
 

DevTest Documentation:  DevTest Solutions 10.7

 

 

Knowledge Documents:

How to run multiple VSEs on Linux in DevTest 10.7.0 and later

What JDBC Drivers are Delivered with DevTest

JRE Error When Installing on Red Hat 7.7

Best Practices Installing and Verifying DevTest Out of the Box

 

Attachments

1637262891136__Service_Virtualization_Upgrade_Runbook_1648504709292.xlsx get_app