On this page:
Target audience:
CAST AI Administrators
On this page: Target audience: CAST AI Administrators |
| Summary: This guide provides details about how to upgrade and migrate from previous versions of CAST AIP to CAST AIP 8.2.x |
To upgrade to CAST AIP 8.2.x (i.e. baseline + Service Pack) please verify that your upgrade path is supported by this document:
Starting point | Supported | Notes |
|---|---|---|
| CAST AIP 8.2.x |  | |
| CAST AIP 8.1.x | | Note that:
|
| CAST AIP 8.0.x | | Note that:
|
| CAST AIP 7.3.x | | Note that:
|
| CAST AIP 7.2.x |  | Direct upgrades are not supported. Please upgrade as follows:
|
| CAST AIP 7.1.0 | | Please contact CAST Professional Services for assistance in the upgrade process. |
| CAST AIP 7.0.x | | Direct upgrades are not supported. Please upgrade as follows:
|
The time required to perform the upgrade action in the CAST Update Tool (CUT) has increased (by approximately double) compared to previous releases of CAST AIP. This reduction in performance is due to the improvements made to the way in which the Assessment Model is handled during the upgrade process in CUT.
CAST AIP 8.2.x is a 64-bit compliant application, therefore you must only use a supported 64-bit Operating System. Please also take into account the following information:
If you are actively using custom extensions (i.e. any extension not officially provided by CAST) and wish to upgrade to the current release of CAST AIP, then CAST highly recommends that you export your current Assessment Model to file (use the File > Export file option in the CAST Management Studio) before you begin the upgrade procedure. If necessary this Assessment Model can used in a comparison process at the end of the upgrade procedure.
In CAST AIP 8.0.x, CAST introduced a brand new .NET analyzer. Please therefore take note of the following important information regarding the upgrade of Applications containing .NET technologies to CAST AIP 8.2.x from 7.3.x.
| VB.NET | C# |
|---|---|
In other words, all VB.NET analyses will need to be reconfigured (new packages created and delivered using the CAST Delivery Manager Tool) and run from scratch in CAST AIP 8.2.x. This MUST be done during Phase 3: Generate a new post upgrade snapshot on the latest version - it is mandatory. |
|
If you are actively analyzing T-SQL 7 or 2000 with a CAST AIP 7.3.x, you cannot upgrade to CAST AIP 8.2.x at this time: the analysis of T-SQL 7 or 2000 is not supported in CAST AIP 8.2.x.
In CAST AIP 8.2.x, when creating sets in the CAST Transaction Configuration Center, DET and, RET values must be defined for Data Entity sets and Contribute values must be defined for End Point sets. These values replace the single "Default FP value" that was required previously. During the upgrade, the following will therefore occur:
As a direct result of this, .TCCSetup files that have been created with previous releases of CAST AIP 7.3.x will be reconfigured to include the required DET, RET and Contribute values, as follows:
Note that if the file required reconfiguration, it will be saved with a new name: "V8.1" will be added as follows:
|
Please note that the extraction/analysis of Oracle 8i is not supported in CAST AIP 8.2.x. If you are actively analyzing Oracle 8i with CAST AIP 7.3.x or 8.0.x, and you would like to upgrade to CAST AIP 8.2.x there are two possibilities open to you, both of which MUST be done prior to starting the upgrade to CAST AIP 8.2.x:
| Note that these workarounds are nor necessary when upgrading to CAST AIP 8.2.4 and above as the issue has been fixed. |
In CAST AIP 8.2.0 a check box called "ALL Access Mode" has been added to the CAST Delivery Manager Tool, specifically for Oracle Server extractions:
This option is only relevant for those that run extractions with a user that does not have access to the DBA_* Oracle views, and instead can only access the ALL_* Oracle views. In CAST AIP 8.2.0, if the user is accessing the ALL_* views, then this ALL access mode check box must also be ticked otherwise the extraction will fail (please see Required RDBMS rights for packaging a database for more information).
This option was introduced in CAST AIP 7.3.9 and in CAST AIP 8.0.1, and you must explicitly tick this check box in the following situations:
Failure to tick the check box will cause the extraction process to fail.
Please also consult:
...which contain information about changes made between previous releases of CAST AIP and CAST AIP 8.2.x, which may impact the results of your post-upgrade snapshot.
The basic workflow for a migration is similar (but not identical) to the workflow used when installing CAST AIP from scratch (i.e. a "greenfield" installation):
| Summary: This step provides instructions for actions that must be executed BEFORE the new CAST AIP 8.2.0 "baseline" and Service Pack setup is installed. |
Before starting the upgrade to CAST AIP 8.2.x, CAST strongly recommends that any existing analysis and result data from previous releases of CAST AIP is backed up. You should backup the following items as a basic minimum so that the existing AIP environment can be restored in case an error occurs during the upgrade process.
| Item to backup | How to back it up |
|---|---|
| CAST AIP schemas (Management / Analysis / Dashboard / Measurement Services | CAST Storage Service 2
Commercial RDBMS (Oracle Server or Microsoft SQL Server)
|
| CAST Delivery folder | Please ensure that you make a copy of your Delivery folder - simply by copying the folder to another location on disk (unrelated to CAST AIP). |
When working with an Oracle Server as the host for the CAST schemas, you must ensure that you are NOT connecting to the Management, Analysis, Dashboard or Measurement Services using the Oracle "system" user. The upgrade process using the CUT tool (see Update process)
In CAST AIP 8.2.x the stored procedures used to configure Impact Factor (see the CAST Transaction Configuration product help for more information) for Transactional Functions were renamed as follows
This is so that their names are in-line with the stored procedures added in CAST AIP 8.1.x for configuring Impact Factor for Data Functions. By default and to avoid a situation where configurations from CAST AIP 8.0.x are not used following an upgrade to CAST AIP 8.2.x, CAST has included a call to the legacy 8.0.x stored procedures in the new 8.2.x stored procedures, for example:
However CAST highly recommends that you take a copy of the scripts in the legacy stored procedures so that you can start using them in CAST AIP 8.1.x in the new stored procedures.
This step corresponds to running the CAST AIP 8.2.0 (baseline) and/or CAST AIP 8.2.x Service Pack setup.exe to create a CAST Administration workstation that will host all CAST end-user applications that you need to setup and/or run the CAST Application Platform. This step is identical to the step described for a greenfield installation.
See Install CAST AIP components. Please take note of the following actions for the various starting points:
| Starting point | Action | |
|---|---|---|
| CAST AIP 8.2.x |
| |
| CAST AIP 8.1.x | ||
CAST AIP 8.0.x | ||
| CAST AIP 7.3.x |
Please pay attention to the following notes before proceeding with this step:
|
Before beginning the update process, please ensure that you have carried out all of the following tasks:
| CAST AIP schema backup | Before beginning, please ensure that you action a backup of the all CAST AIP schemas that will be upgraded as described in the Prepare the upgrade step.
| |
| Database access exclusivity | Ensure that you have exclusive access to the schemas you want to update - i.e. that the schema is not being used by any other user, application (such as the CAST Management Studio) or web portal (such as the CAST Application Analysis/Engineering Dashboards). | |
| Check free RAM memory | Before starting this step, please ensure that you have at least 1GB of free RAM memory on your workstation. If you do not have sufficient free RAM memory, there is a risk that some of the actions described in this step may fail. | |
| Stop the CAST AIC Portal on the application server | Please ensure that you STOP the existing deployment of the CAST AIC Portal (using the built in application server management system) before starting the update process. | |
| Ensure your custom and official CAST AIP extensions are compatible (optional) | If you have custom or official CAST AIP extensions installed in the current release of CAST AIP, you must ensure they are compatible with the new release of CAST AIP you are upgrading to. | |
| Ensure that your cast-ms.connectionProfiles.pmx file is accessible | The CAST Update Tool that is used to do the upgrade (CUT.exe or CUT-CLI.exe - please see Appendix: Using the CAST Update Tool - GUI) will attempt to locate a CAST Management Studio connection profile (a cast-ms.connectionProfiles.pmx file) on your local machine (located in the %APPDATA%\CAST\CAST\8.2 folder) to connect to all CAST Management Services declared in the PMX file. Previous release of CAST AIP present on the machineIf a previous release of CAST AIP is already installed on the machine, then the CAST AIP setup will have copied the cast-ms.connectionProfiles.pmx file from this previous release into the %APPDATA%\CAST\CAST\8.2 folder - as such, CUT will connect to all the CAST Management Services declared in this PMX file. Note that if more than one previous release exists on the machine (for example 8.0 and 8.1) then the CAST AIP 8.2.x setup will have copied the cast-ms.connectionProfiles.pmx file from the most recent previous CAST AIP release present on the machine. No previous release of CAST AIP present on the machineIf the current machine does NOT have a previous release of CAST AIP installed on it (for example you are using a new "clean" machine for CAST AIP 8.2.x), then when opening CUT in GUI mode, the following dialog box will be displayed (in CLI mode, the CLI will fail). This indicates that no CAST Management Studio connection profile (a cast-ms.connectionProfiles.pmx file) exists in the %APPDATA%\CAST\CAST\8.2 folder- i.e. the CAST AIP setup was not able to copy the cast-ms.connectionProfiles.pmx file from a previous release of CAST AIP.
In this situation you will need to copy the cast-ms.connectionProfiles.pmx file from a machine on which CAST AIP 7.3.x/8.0.x/8.1.x has been installed and paste it over to the machine designated for CAST AIP 8.2.x, as follows:
|
Because the Delivery folder is "locked" to a specific version of CAST AIP, when it is updated to the new version of CAST AIP, any Management Services (and Applications managed in them) that have not themselves been selected for update in the CAST Update Tool (CUT) will no longer be permitted to use the Delivery folder and you will receive the following error in the CAST Management Studio when trying to work with the Applications that have not been updated:
If you do not want to update ALL your Management Services to the newer version of CAST AIP, you have two options:
In this scenario, we are migrating from CAST AIP 7.3.x to CAST AIP 8.2.x as an example (but the same applies when updating between other supported paths):
| You can ignore this section if you actively use |
The update process is carried out with the end user application CAST Update Tool (please see Appendix: Using the CAST Update Tool - GUI for more detailed information about this tool).
| CAST Server Manager must not be used for updating Management, Analysis and Dashboard Services in CAST AIP 8.2.x. CAST Server Manager is only to be used for updating the CAST Measurement Service (see below), installing new CAST databases/schemas and dropping databases/schemas. |
| A Management Service and its accompanying Dashboard and Analysis Services can only be updated if their statuses are "Not up to date" as shown in the below image - a blue icon over the database. Please see Appendix: Using the CAST Update Tool - GUI for more detailed information about this tool. |
Because the Delivery folder is "locked" to a specific version of CAST AIP, when it is updated to the new version of CAST AIP, all Management Services that refer to the same Delivery Folder should be selected together. However, if you have chosen to update only some of the Management Services that use your configured Delivery folder, the following message will be displayed indicating the Management Services that CUT has detected within the configured Delivery folder:
Note that this scenario is only applicable to those that have MULTIPLE Management Services using one single Delivery folder. |
Now you need to execute the upgrade on the Management Services that you have selected:
| Option | Description |
|---|---|
| Preserve Assessment Model customizations, activate new rules from AIP 8.2.0 | These two options will preserve the current Assessment Model assigned to your CAST Dashboard Service schemas and merge in any new rules delivered with the CAST AIP 8.2.x Assessment Model - depending on your option choice, these new rules will either be activated (provides the benefits of the new release with all options actived) or disabled (therefore making post upgrade results more stable and in-line with the previous release of CAST AIP but not benefiting from updates in the new release). Please see Assessment Model updates for more information about new Quality Rules that may have been added in this release of CAST AIP. If you have chosen either of these options, the following Assessment Model values will be retained:
However, the Assessment Model will still be subject to an upgrade process to modify some values to make them compatible with CAST AIP 8.2.x, for example:
|
| Preserve Assessment Model customizations, leave new rules disabled | |
If you have chosen this option, the new Assessment Model from CAST AIP 8.2.x will be assigned to the CAST Dashboard Service schemas selected for update, therefore replacing any existing Assessment Models. |
Note that:
|
| You can ignore this section if you do not use |
The update process is carried out with the end user application CAST Update Tool in CLI mode (please see Automating CAST Update Tool tasks for more detailed information about this).
| Note that in CLI mode, ALL CAST Management Services schemas declared in the cast-ms.connectionProfiles.pmx (together with their associated Analysis and Dashboard Service schemas) will be upgraded! If you do not want to upgrade ALL CAST Management Services schemas declared in the PMX file, please comment out all the lines in cast-ms.connectionProfiles.pmx located in the %APPDATA%\CAST\CAST\8.2 folder (using a text editor) that refer to Management Service schemas you DO NOT want to upgrade. |
You must run the upgrade in CLI mode (using the CUT-CLI.exe file from your new installation of CAST AIP 8.2.x) ensuring you use the "retain" option, as follows:
CUT-CLI.exe -productInstallationDir "C:\Program Files\CAST\8.2" -assessmentModelUpgrade retain -y -logFile D:\CUT-CLI.castlog2 |
This command line will:
When complete, please ensure you Validate the CAST Upgrade Tool execution to check additional logs generated by the CLI process.
| Note that the retain option is NOT available in the CAST Update Tool when run in GUI mode. |
from your new installation of CAST AIP 8.2.x in GUI mode:
| GUI Option | CLI option | Description |
|---|---|---|
| Preserve Assessment Model customizations, activate new rules from AIP 8.2.x | -migrateAssessment progressive | These two options will preserve the current Assessment Model assigned to your CAST Dashboard Service schemas and merge in any new rules delivered with the CAST AIP 8.2.x Assessment Model - depending on your option choice, these new rules will either be activated (provides the benefits of the new release with all options actived) or disabled (therefore making post upgrade results more stable and in-line with the previous release of CAST AIP but not benefiting from updates in the new release). Please see Assessment Model updates for more information about new Quality Rules that may have been added in this release of CAST AIP. If you have chosen either of these options, the following Assessment Model values will be retained:
However, the Assessment Model will still be subject to an upgrade process to modify some values to make them compatible with CAST AIP 8.2.x, for example:
|
| Preserve Assessment Model customizations, leave new rules disabled | -migrateAssessment conservative | |
| -migrateAssessment true | If you have chosen this option, the new Assessment Model from CAST AIP 8.2.x will be assigned to the CAST Dashboard Service schemas selected for update, therefore replacing any existing Assessment Models. |
Notes:
|
| Note that in CLI mode, ALL Assessment Models attached to an Application/Dashboard Service schema in ALL CAST Management Services schemas declared in the cast-ms.connectionProfiles.pmx will be upgraded! If you do not want the upgrade to run on ALL CAST Management Services schemas declared in the PMX file, please comment out all the lines in cast-ms.connectionProfiles.pmx located in the %APPDATA%\CAST\CAST\8.2 folder (using a text editor) that refer to Management Service schemas you DO NOT want the upgrade to run on. |
You must run the upgrade in CLI mode (using the CAST-MS-CLI.exe file from your new installation of CAST AIP 8.2.x), using one of the following command lines, depending on your choice of Assessment Model handling option:
Progressive (Preserve Assessment Model customizations, activate new rules from AIP 8.2.x)
CAST-MS-CLI.exe PreserveExistingAssessmentModel -migrateAssessment progressive -connectionProfile test_mngt -logFilePath D:\CUT-CLI.log |
Conservative (Preserve Assessment Model customizations, leave new rules disabled)
CAST-MS-CLI.exe PreserveExistingAssessmentModel -migrateAssessment conservative -connectionProfile test_mngt -logFilePath D:\CUT-CLI.log |
True (
CAST-MS-CLI.exe PreserveExistingAssessmentModel -migrateAssessment true -connectionProfile test_mngt -logFilePath D:\CUT-CLI.log |
This command line will:
Please ensure that you thoroughly check the log files in the following location to make sure that the upgrade has indeed completed successfully:
%TEMP%\CAST\CAST\8.2\CUT |
CASTLog2Viewer.exe <path_to_CastLog2_file> |
For example:
CASTLog2Viewer.exe C:\Users\<user>\AppData\Local\Temp\CAST\CAST\8.2\CUT\log.CASTLOG2 |
You can query the DSS_HISTORY table in the CAST Dashboard Service to view the status of each existing snapshot after the upgrade process has been completed by the CAST Update Tool. Messages will be entered into the table as follows for each snapshot that is handled as part of the upgrade:
The update process for the CAST Measurement Service used by the CAST Application Analytics Dashboard, is (exceptionally) carried out with the end user application CAST Server Manager.
As mentioned already:
|
If no connection profiles are available a message will be displayed as shown below. Please create a new connection profile to the CAST Storage Service 2 on which your CAST Measurement Service is installed.
|
This step has three phases:
To validate the migration actioned in the CAST Upgrade Tool:
This is what you can expect:
During the upgrade process, the following actions will be performed:
| Label | |
|---|---|
| "[current label] (upgraded, [version] new rules enabled)" | |
| Preserve Assessment Model customizations, leave new rules disabled | "[current label] (upgraded, [version] new rules disabled)" |
"Default Assessment Model ([version] + Extensions)" |
| Unassociated Assessment Models will retain their existing label |
 |  |
|  |
Warning : There are more than 3 Assessment Models declared in the current management base, this can degrade the performances of CAST Management Studio. You should consider removing those which are no longer needed. |
If you are upgrading from CAST AIP 8.1.0 (baseline) ONLY, you should check your snapshots for errors that may have occurred during the upgrade of the Measurement Service schema with CAST Server Manager. To do so:
CAST highly recommends that this comparison process is completed so that you can identify the differences between the OLD and NEW Assessment Models, however, it is not a mandatory part of the upgrade process and you can skip the step if you prefer not to do this. See for more information.
If you have used the CAST Siebel extension and have generated a snapshot in a previous release of CAST AIP, then you must follow the instructions explained in the Siebel documentation about re-running the Vanilla analysis BEFORE you generate a new snapshot with the new release of CAST AIP. Please see Note about running a CAST AIP upgrade or an Extension upgrade for more information.
Please be aware that when upgrading to a new version of CAST AIP (excluding between Service Packs), configuration files that are used by various CAST features and tools are not automatically upgraded. In other words, you need to ensure that any customization that has been applied to configuration files in the existing version of CAST AIP is manually transferred to the corresponding configuration file in the new version of CAST AIP. This task must be completed before you generate a new snapshot (see below) otherwise the default configuration file will be used and your analysis results may be impacted.
A non-exhaustive list of modifiable configuration files is shown below. Please check them for any customizations that you have made and ensure they are transferred to the new version of CAST AIP:
File name | Location | Usage | Frequency |
|---|---|---|---|
| Default CAST AIP Environment Profiles from legacy releases of CAST AIP | %CommonProgramFiles%\CAST\CAST\EnvProf\*.* or %CommonProgramFiles(x86)%\CAST\CAST\EnvProf\*.* | Installed with previous versions of CAST AIP for default CAST AIP Environment Profiles. These files are no longer used by CAST AIP 8.2.x and above. If you have altered any files in this location then you must transfer those changes to the equivalent location in <CAST_install>\EnvProf. See also Technical Information. | All previous releases of CAST AIP. |
cast-tag.extensions.xml | <CAST_install>\configuration\J2EE\web-inf | Specify tag libraries that need to be taken into account during an analysis.
| |
| *.tagsextension | CAST Management Studio (GUI) > Application > Platform Setting > CAST Tags Extensions Folder | - | |
| <CAST_install>\EnvProf\J2EE\ | - | ||
| *.blackbox.xml |
| User Input Security feature: black box methods | |
| ExternalLinksRules.xml | <CAST_install>\configuration\parametrization | Legacy Dynamic Link Manager link parametrization | This file is no longer used in CAST AIP 8.2.2 and above - it has been replaced by the CustomExternalLinksRules.xml file. Therefore if you have previously modified this file to provide your own parametrization and after an upgrade to CAST AIP 8.2.2 or above, you must ensure that you copy your custom rules from this file into the CustomExternalLinksRules.xml file (located in the same folder). If the CustomExternalLinksRules.xml file does not exist (specifically when you have installed CAST AIP 8.2.2 in standalone mode and neither AIP 8.2.0 and 8.2.1 exist on the workstation), you may need to create it yourself. |
| CustomExternalLinksRules.xml | <CAST_install>\configuration\parametrization | Legacy Dynamic Link Manager link parametrization | |
| Parametrization_Cobol.xml | <CAST_install>\configuration\parametrization\cobol | Parametrization of Mainframe Analyzer for Cobol | |
| AdvancedJCL.xml | <CAST_install>\ | Parametrization of Mainframe Analyzer for JCL | |
*.xml | <CAST_install>\configuration\AMT | Management of the AMT (task, memory, etc.) |
|
| CastMetrics.xml | <CAST_install>\ | Metric Assistant V1 | This file is no longer used in CAST AIP 7.2.x and above - it has been replaced by the XXXCastMetrics.xml file. Therefore you should transfer your customization into one or several XXXCastMetrics.xml files. It is highly recommended to have one file per custom language or one file for custom metrics for a standard language. See Using the XXXCastMetrics.xml file for more information. |
*.xml | <CAST-install>\configuration\Metrics | Metric Assistant V2 |
|
| *.xml | <CAST-install>\configuration\MetricAssistant | Metric Assistant V3 | |
Background Facts upload file | - | Upload of Background Facts such as Effort and Cost data |
|
| XXXCastMetrics.xml | %ALLUSERSPROFILE%\CAST\CAST\<version>\Configuration\Languages\<language> | Custom metric configuration for standard CAST AIP technologies | |
*.castscript | <CAST-install>\configuration\Script_Libraries | CAST Script | CAST AIP 7.0.x only. |
| *.castscript | CAST Management Studio (GUI) > Application > Platform Setting > CAST Script Library Directory | CAST Script | CAST 7.2.x and above. |
Cast.aex | <CAST-install>\configuration\EnvProf | Environment profiles are stored in the KB but you may have changed the file to apply it to new installation. | |
| JAR, XQuery, CASTScript | Referenced by custom Environment Profiles | Custom Environment Profiles |
Note also that if the new version of CAST AIP has been installed on a new machine, any files such as JAR, XQuery, CASTScript that are referenced by any custom Environment Profiles will need to be manually copied to the new machine. |
The current release of CAST AIP is 64bit compliant and therefore requires a 64bit compatible machine for installation purposes. However, the CAST Visual Basic analyzer contains components that cannot be re-factored to 64bit and therefore CAST has had to deliver these components as 32bit modules. This has been achieved by placing the required components in the Vb6 folder located at the root of the CAST installation location.
If you have upgraded from a previous release of CAST AIP (i.e. CAST AIP 7.3.x) that was not 64bit compliant, you MUST ensure that you manually transfer these changes from the relevant files in the <CAST_install_folder>\configuration folder in the previous install, to the relevant files in the <CAST_install_folder>Vb6\configuration folder in the new install of CAST AIP.
If you have migrated Universal Analyzer jobs from a previous version of CAST:
If you have migrated Universal Importer jobs from a previous version of CAST, you must ensure that:
If your .UAX files reference the CAST metamodel object types CAST_SQL_Instance and CAST_SQL_Schema, you must update them: CAST_SQL_Instance must be changed to CAST_Oracle_Instance and CAST_SQL_Schema must be changed to CAST_Oracle_Schema.
Your .UAX files must be saved in Unicode (UTF-8) format and a UTF-8 encoding declaration must be present in each file as follows: <?xml version="1.0" encoding="UTF-8"?>
Note that you may find that the Validation view in the CAST Management Studio displays "Missing Object Filter" in Modules or "Missing Target" in Dependencies when you have migrated Universal Importer jobs with dependencies, or Reference Pattern/User Defined Modules that use the Universal Importer job results. To workaround this issue, you should:
|
In CAST AIP 8.2.x, the type names used by CAST AIP to define all VB.NET objects have been modified and have been given new values, therefore, any configuration that uses VB.NET type names will need to be reviewed and modified as described below before you re-run the post-upgrade analysis and snapshot. You can find a list of the new type name values in Metamodel type changes for VB.NET types in .NET.
For example, the following configurations/features can use type names and may therefore need to be reviewed (other configurations may also exist):
If you actively used the CAST Transaction Configuration Center with a previous release of CAST AIP 7.3.x specifically to work with Function Point counting in legacy VB.NET analyses you will need to check your configuration settings before you run the post-upgrade snapshot (see below). It is possible to configure VB.NET objects as transaction entry/end points/excluded items based on their type name and these will need to be reviewed as described below.
When using the GUI, CAST highly recommends that you create NEW configurations for each set that involves a VB.NET type. Then, once the new configurations are in place, you need to DELETE the existing configuration. This is because changing the type in an existing set does not apply the new name correctly.
If you use .TCCSetup files to define your configuration, you will need to modify the .TCCSetup file and then re-apply it. This will overwrite the existing set with the correct information. For example if your .TCCSetup file contained a configuration for a VB.NET Class as follows:
<argument name="type"> <value>NET_CLASS_VB</value> </argument> |
You will need to replace the <value> with the new type name for the object in question:
<argument name="type"> <value>CAST_DotNet_ClassVB</value> </argument> |
When you have a Refined Target rule based on type names you will need to modify the configuration to remove the existing type names and then add the corresponding new type names:
If you made use of any .ini or properties files (such as enlighten.ini, rcenter.ini etc.) to enable or disable features in the previous version of CAST AIP, you may need to transfer the preferences in these files to the relevant files in the CAST AIP 8.2.x file structure. The migration process will not handle this transfer for you.
Additionally, any preferences you may have set in the CAST Management Studio (i.e. window locations and sizes) will not be transferred. You will need to set these again manually.
The following is a non exhaustive list of preference files that you may need to investigate:
As outlined in Phase 1, if any of your snapshot Version names contain the string “MIGR_ERROR_ALG_xxx_x_x” (for example “MIGRERROR_ALG_1106776204_3_4”) and these snapshots have been consolidated into the Measurement Service schema in the previous release of CAST AIP, then you need to first remove and then re-consolidate the snapshots (containing the error) in the Measurement Service schema. To do so:
This step is:
|
| All these steps should be run from CAST Management Studio from the new release of CAST AIP. |
| The objective is to apply any fixes that may have been delivered in the new release of the CAST Delivery Manager Tool and to include the results from additional extensions that may have been introduced in the new release of the CAST Delivery Manager Tool. |
| Note that you may need to re-input the password for access to databases, SVN or TFS if the original Delivery Manager chose to stored these passwords locally on his own workstation, rather than storing them in the CAST AIC Portal. |
| Note that for File system packages ONLY, you can skip the deployment of the source code (untick the Deploy sources option) if you want to save some time. |
For each Application involved in the migration, generate a snapshot. The rational of doing so now is so that you can compare the pre and post migration snapshots. To generate a snapshot:
Please ensure that you:
|
When the snapshot has completed, you can check the contents by launching the temporary CAST Engineering Dashboard:
This step corresponds to deploying the CAST web applications that are required for using CAST AIP 8.2.x:
CAST strongly recommends deploying the CAST web applications in "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. Specific details are listed below for each web application.
When redeploying the CAST AIC Portal, ensure the following is always done:
%CATALINA_HOME%\webapps\CAST-AICP\database\security.properties %CATALINA_HOME%\webapps\CAST-AICP\database\security.script |
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd"> <properties> <comment/> <!-- <entry key="4454b831-7931-405c-85e2-60727ebaef74_4454b831-7931-405c-85e2-60727ebaef74.entity.xml_checksum">4a8579cf20d2a7fb74da82b70940ce3c</entry> <entry key="4454b831-7931-405c-85e2-60727ebaef74_4454b831-7931-405c-85e2-60727ebaef74.entity.xml_lastModified">1435072140917</entry> <entry key="4454b831-7931-405c-85e2-60727ebaef74_4454b831-7931-405c-85e2-60727ebaef74.entity.xml_length">2287</entry> <entry key="4454b831-7931-405c-85e2-60727ebaef74_manager"></entry> <entry key="4454b831-7931-405c-85e2-60727ebaef74_mngtId">1764613107</entry> <entry key="4454b831-7931-405c-85e2-60727ebaef74_name">SEVRES</entry> <entry key="4454b831-7931-405c-85e2-60727ebaef74_owner"></entry> <entry key="4454b831-7931-405c-85e2-60727ebaef74_syncId">4</entry> <entry key="4454b831-7931-405c-85e2-60727ebaef74_type">delivery.Application</entry> <entry key="4454b831-7931-405c-85e2-60727ebaef74_uuid">4454b831-7931-405c-85e2-60727ebaef74</entry> --> <entry key="c8bf6626-4840-44eb-ac3a-080370e67bbf_c8bf6626-4840-44eb-ac3a-080370e67bbf.entity.xml_checksum">3387ef40b17e24ae225cea19f52a6d48</entry> <entry key="c8bf6626-4840-44eb-ac3a-080370e67bbf_c8bf6626-4840-44eb-ac3a-080370e67bbf.entity.xml_lastModified">1434985964337</entry> <entry key="c8bf6626-4840-44eb-ac3a-080370e67bbf_c8bf6626-4840-44eb-ac3a-080370e67bbf.entity.xml_length">2287</entry> <entry key="c8bf6626-4840-44eb-ac3a-080370e67bbf_manager"></entry> <entry key="c8bf6626-4840-44eb-ac3a-080370e67bbf_mngtId">1764613107</entry> <entry key="c8bf6626-4840-44eb-ac3a-080370e67bbf_name">MEUDON</entry> <entry key="c8bf6626-4840-44eb-ac3a-080370e67bbf_owner"></entry> <entry key="c8bf6626-4840-44eb-ac3a-080370e67bbf_syncId">4</entry> <entry key="c8bf6626-4840-44eb-ac3a-080370e67bbf_type">delivery.Application</entry> <entry key="c8bf6626-4840-44eb-ac3a-080370e67bbf_uuid">c8bf6626-4840-44eb-ac3a-080370e67bbf</entry> </properties> |
When redeploying the CAST Application / Engineering Dashboards, please note the following:
CAST Application Analytics Dashboard only - note that in CAST AIP 8.2.x and all future releases CAST has implemented a new enhancement Function Point counting mode (see CAST AIP enhancement Function Point counting mode in Upgrading to CAST AIP 8.2.x) and has therefore modified the CAST Application Analytics Dashboard default Enhancement Function Point tile configuration (see Automated Enhancement Point in Upgrading to CAST AIP 8.2.x) to pull data ONLY from the new AEP measure. However, Applications on-boarded in previous releases of CAST AIP and upgraded to CAST AIP 8.2.x and above will continue to use the legacy EFP measure mode for future snapshots (unless manually changed) and as such, the new tile in the dashboard will display no information (N/A) about enhancement Function Points. If you need to display tiles that are configured to display EFP data, please copy the following section of text from the existing deployed WAR (%CATALINA_HOME%\webapps\CAST-AAD\portal\resources\app.json file) into the equivalent file in the newly deployed WAR:
{
"id": 2,
"title": "Software Enhancement Function Points (since previous version)",
"panels": [
{
"id": 2000,
"plugin": "FunctionalWeightMeasureResult",
"color": "blue",
"parameters": {
"title": "",
"functionalWeightMeasure": {
"id": "ADDED_FUNCTION_POINTS",
"format": "0,000",
"description": "Automated FPs Added"
}
}
},
{
"id": 2002,
"plugin": "FunctionalWeightMeasureResult",
"color": "green",
"parameters": {
"title": "",
"functionalWeightMeasure": {
"id": "MODIFIED_FUNCTION_POINTS",
"format": "0,000",
"description": "Automated FPs Modified"
}
}
},
{
"id": 2001,
"plugin": "FunctionalWeightMeasureResult",
"color": "purple",
"parameters": {
"title": "",
"functionalWeightMeasure": {
"id": "DELETED_FUNCTION_POINTS",
"format": "0,000",
"description": "Automated FPs Deleted"
}
}
} |
CAST AIP 8.1.3 and above
