- 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 DevTest 10.3.0 or earlier will need a new license, else, you can use your current license.
- Download DevTest 10.5.0 from the Support Portal, here is what each zip file contains (there are 2 pages):
Choose Product CA DevTest Runtime User Seeding (all products with a 10.5 release all have the same components.)
Each DevTest Installer has both Workstation and Server components.
DevTest 10.5 Windows x64 (includes JRE)
Virtual Service Catalog 10.5 Windows x64 (includes JRE)
DevTest 10.5 Linux x64 (includes JRE)
Virtual Service Catalog 10.5 Linux x64 (includes JRE)
DevTest 10.5 Demo Server (download only if you want to run the tutorials)
- 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.5.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 none databases. But,can use existing databases.
- 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.5.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:default-port-numbers
- 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 the Enterprise Dashboard is located in: DEVTEST_HOME\database\oracle_enterprisedashboard.ddl.
The DDLs for the Registry are located in DEVTEST_HOME\database\oracle.ddl and oracle_cai.ddl.
The DDL for IAM is located in DEVTEST_HOME\IdentityAccessManager\database\ddl\oracle.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.