CAST AIP 8.3.x Documentation
Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

On this page:

Summary: CAST AIP 8.3.8 introduces a number of features and changes as listed below. To view the impacts of these changes on analysis results, see: Changes in results post upgrade.

Technology support changes

Please see Technology coverage changes in CAST AIP 8.3.x for more detailed discussion of this subject.

Installation and deployment

CAST Server Manager - CLI

Two new commands have been added - see Automating CAST Server Manager installation tasks for more details. 

Note that -INSTALL_CONFIG_FILE and -UPGRADE are deprecated and you should use the above commands instead.

-INSTALL_COMBINED

This option is equivalent to the Schema Installation option in the GUI for "combined" and will:

  • create a combined installation from scratch (Management, Analysis and Dashboard Service schemas)
  • provide a means to specify any additional extensions that need to be installed to the new combined installation (over and above the extensions that are always installed with CAST AIP)
  • configure the Delivery folder path for the combined installation (not currently used)

-MODIFY_COMBINED

This option is a multi-functional command that is aimed at two scenarios:

  • Upgrade an existing combined installation (Management, Analysis and Dashboard Service schemas) to a new release of CAST AIP - equivalent to the Upgrade Installation option in GUI.
  • Install new extensions, upgrade existing extensions or deactivate existing extensions to an existing combined installation (Management, Analysis and Dashboard Service schemas) - equivalent to the Manage Extensions option in the GUI.
  • A combination of the above can also be run.

CAST Transaction Configuration Center

Excluding items as "technical" objects on a per-snapshot basis

When the default Automated Enhancement Points (AEP) measure is in use for snapshot generation (the default measure), it is now possible to configure all objects in an Excluded Item set as "technical" objects on a per-snapshot basis.  In other words:

  • objects which may be (but not necessarily) entry points, data entities and end points will be considered as "technical objects" and they will not impact the status of Transactional Functions in the next snapshot when the Automated Enhancement Point (AEP) measure is being used
  • if the objects are entry points, data entities or end points, the complete Data Function or Transactional Function which have these objects as entry points, data entities or end points will not be considered at all for Function Point calculations in the next snapshot and the objects will be considered as "technical objects".

Values for previous snapshots will not be impacted by this new option, which is in contrast to excluding objects in the Evolution node, which is global to all snapshots.

Objects can be set as "technical" in any of the sub-nodes of the Excluded Items node:

Enhancement node - layout changes

  • The button Recompute checksums and snapshot statuses has now been removed and is now available as a right click menu option on the snapshot:

  • A new option is available in the right click menu to view the excluded objects in the selected snapshot - these objects will not impact Transactional Function values:

  • The  Keep existing exclusion checkbox has been removed from Shared objects exclusion dialog box. Now the objects identified by the sharing counter will be excluded and appended to the already existing exclusion objects. If needed, you can un-exclude any objects in the Enhancement Panel:

  • No labels