On this page:
Target audience:
CAST AI Administrators
Summary: this section provides information about what you should expect after completing an upgrade and any action items you may need to complete.
Step 1: What you should expect after running an upgrade
- Run the CAST Management Studio from your new installation of CAST AIP.
- Connect to the upgraded Management Service on the server that hosts your upgraded CAST AIP schemas: you may need to create a new connection profile to do so. You will not need to enter a license key, or specify Delivery/Deployment folders.
This is what you can expect:
- Delivery and Deployment folders will remain as they were prior to the upgrade
- Applications will remain as they were prior to the upgrade, including:
- Any existing Deliveries
- The Current Version
- Any existing Analysis Units
- Any existing Modules
- Any existing Analyses/Snapshots
What happens to Assessment Models?
Step 2: Items for action
This step contains miscellaneous action points that, depending on the technologies you are upgrading, may need to be complete.
Assessment Models comparison process - optional
Customers using the Siebel extension
Customers upgrading with legacy BusinessObjects Analyzer results
Customers upgrading from CAST AIP 8.1.0 (baseline) - snapshot validation
Step 3: Generate a new post upgrade snapshot on the latest version
- Although not mandatory (except in the situation listed below), CAST highly recommends that it is nevertheless actioned because it provides a way to compare the analysis results of the same source code in two distinct releases of CAST AIP. If you don't want to generate a snapshot at this time, you can skip this paragraph and move on to Step 4: Reconfigure the CAST web applications. Following an upgrade to the current version of CAST AIP, you will need to use the CAST Delivery Manager Tool if you want to deliver new versions of your Application source code for analysis. This process is described in Delivery.
- This step is always mandatory when your Application contains DB2 (z/OS or UDB) source code AND you have not yet transitioned to the SQL Analyzer extension. This is to ensure that data for this technology is generated correctly.
- All the steps listed below should be run from CAST Management Studio from the new release of CAST AIP.
- A pre-prepared batch script is available that will perform this step (and others) silently. This script uses the Command Line Interface of various CAST AIP tools. See Automating the CAST AIP Upgrade process.
Update the delivery for the current version
Generate a new snapshot
Check the results of the snapshot
Step 4: Reconfigure the CAST web applications
This step corresponds to deploying the CAST web applications for use with the new release of CAST AIP:
- the CAST AIC Portal to manage the delivery and packaging of source code for analysis via the CAST Delivery Manager Tool (DMT)
- the Health Dashboard for high level data consumption
- the Engineering Dashboard for detailed data investigation
- the legacy CAST Engineering Dashboard and the CAST Discovery Portal for detailed data investigation (optional based on your license agreement)
Required actions - general process
CAST strongly recommends deploying the CAST web applications from the new release of CAST AIP "side-by-side" alongside any existing deployed web applications from previous releases of CAST AIP (including any deployed WARs from Alpha and Beta previews) to take advantage of new features and to comply with compatibility limitations. See Deploy the CAST web applications for information about deployment of the CAST web applications from the new release.
In a "side-by-side" deployment, you will need to transfer the details of your environment (stored in the configuration files such as web.xml/context.xml/other .properties/.xml files) from the old web application to the new. Please be aware that the structure and content of configuration files may have changed between releases of CAST AIP, so you should not perform a merge or overwrite configuration files (unless specifically requested to do so in the instructions below) - instead you must manually update the new configuration files with the details from the old configuration files.