Preparing for Upgrade to DevTest 10.9.2

Products

• Service Virtualization

Issue/Introduction

Steps for preparing to upgrade to DevTest 10.9.2

Environment

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

After install read the Post-Installation

Resolution

Download the DevTest 10.9.2 Software

Download from the Broadcom Support Portal.

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: Service Virtualization Functional Transactions MULTI-PLATFORM or any one of the other products that begin with SV: 

Click on Release 10.9.2

 

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.

Scroll down to see more:

 

NOTE: Refer to Artifacts - Docker Images to get the Docker images.

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

Preparing Your DevTest Upgrade

Upgrade DevTest

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

• 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.9.2 version.
  The logging.properties file of the existing installation is replaced with the 10.9.2 version
  The iam.properties file existing installation is replaced with the 10.9.2 version.
  All files that prefixed with an underscore are replaced with the 10.9.2 version.
  Any customized properties or vmoptions files are not replaced with a DevTest 10.9.2 version.

. New Folder

• Backup all your current DevTest databases.

• Important: Once the software is installed, DO NOT copy any earlier versions of a deliverable jar files to any of the folders.

External Databases

New Databases:

DevTest 10.9.2 uses three databases:  You will need one for IAM, one for Enterprise Dashboard and one for Registry.  Each component must have it's own database.  So if you have three IAMs, Enterprise Dashboards and Registries, that would be nine databases. IAM, Enterprise Dashboard and Registry cannot share the same database. 

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.

 

Post Upgrade  Read the Post-Installation

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

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.  Exceptions: You can copy the *.vmoptions files from earlier versions.

Log File Location

DEVTEST_HOME Environment Variable

The primary location for DevTest Solutions files is determined by the DEVTEST_HOME environment variable. For more information, see DevTest Home Folder.  The DevTest installer automatically defines the DEVTEST_HOME environment variable if it is not already set.  If DEVTEST_HOME  is not explicitly defined, the default locations are:

• • Linux/macOS:  ${HOME}/.devtest/
  • Windows:  %ALLUSERSPROFILE%/.devtest

Most of the DevTest files are stored under the ${DEVTEST_HOME}/logs/ directory. Within this directory, logs are further organized into subfolders based on the specific DevTest component type.

 

Workstation Installation Folder Permissions  - The chosen folder must be one the user has write permissions for, such as %ALLUSERSPROFILE%. Using %USERPROFILE% can cause issues if the Workstation is installed via a silent installer running under an admin user; in that scenario, %USERPROFILE% may resolve to the admin's home folder, which the standard user will not have write access to.

 

 

 

 

Additional Information

Service Virtualization Best Practices

DevTest Solutions 10.9.2

Release Notes

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. 

Getting Started

Installing

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

Using

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

Agents

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.

 

Administrating

 

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

Reference

 

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

 

Connect

 

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

 

Usage Data (Telemetry)

 

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.  If you are licensed to use this product under a Portfolio License Agreement (PLA) subscription, you must configure it to collect and send product-specific usage data. If you are licensed to use this product under a standard license, you can consent to have this product collect and send usage data. By default, this product does not collect and send usage data.