CMS - Services view

Please note that any services associated with the database server will also be removed. This will also impact items in your Delivery Unit associated to the services.

In addition the validation check will also take into account the external context - for instance, for components that rely on files, a check will be made to ensure that the files exist and are valid (e.g.: Layers and Definition Rules files in the Architecture Model editor).

Results are displayed in the Verification view.

Notes

• This check-up is similar to the check carried out automatically in the Validation view.

Select the Applications you wish to cleanup and click Finish to remove them.

For example, if the connection between the client and server is lost for whatever reason during the snapshot generation process, then a lock will be set by the server preventing any further snapshot processing (you will see the error message: "Compute Metrics REJECTED: A snapshot is already being processed - the operation requested can not be completed now.").

The option is intended to reset this type of lock so that you can continue processing your snapshots.

- Before using the option, make sure that no connection is currently running a snapshot computation - running two concurrent computations on the same database will produce erratic results.

- In most circumstances, locks will be removed from the server automatically (indeed this is the recommended action), but this process can take a long time. This option is designed to override this automatic unlocking process.

The CAST Health Dashboard enables users to access directly the underlying CAST Engineering / Security Dashboard that provides detailed information about the top level data displayed in the CAST Health Dashboard.

If you have deployed the combined "Health / Engineering" WAR file then this URL is configured automatically, however if you have separate standalone deployments of the CAST-Health.war and CAST-Engineering.war files will then access to the CAST Engineering Dashboard (ED) is not implemented automatically and you will need to proceed as follows.

Although you can activate a Measurement Service to store all snapshot data for the current Management Service (see Measurement Service editor), users will not be able to drill down into the underlying CAST Engineering Dashboard unless you specifically add the URL of your CAST Engineering Dashboard into the Measurement Service.

This option allows you to do so. See Dashboard Service editor for more details.

Notes

• When using the option you will be prompted for login credentials > admin/cast (case-sensitive): note that this user has the ADMIN role only.
• CAST AIP schemas hosted in Microsoft SQL Server environment - please be aware that the CAST Engineering / Security Dashboard will fail to load if you carried out a combined installation in CAST Server Manager using a Trusted connection (i.e. using Windows authentication) and are still using the automatically configured connection profile in the CAST Management Studio.

General Checks

• Info: Lists the status number for the existing snapshots
• Info: Lists the status number for the next snapshot
• Info: Lists the ADG procedures that are not referenced in the metrics
• Warning: A metric whose name does not match its technology category

Check Objects Consistency

• Error: Checks that only one CORPORATE object exists
• Error: Checks the coherence of the technological objects via parent objects
• Error: Checks the direction of the links - Corporate > System > Application > Module and Organization > Team > Dev > Module

Check Metrics Consistency

• Error: Checks all references in the metric tree
• Error: Searches for orphans
• Warning: Searches for business/technical criteria without any contributions
• Error: Checks that all the metrics calculate a value
• Warning: Checks that all the parameters have a value
• Error: Checks that all the parameter values are defined
• Warning: Checks that the count operator for a Quality Rule is distinct
• Error: Checks that UA languages have the necessary configuration
• Error: Checks that the thresholds are only ascending or descending
• Error: Checks for the absence of obsolete metric groups (7, 8 and 9)
• Error: Checks the coherence of the metric execution locations
  Group = 1, 4, 5, 10, 13 > Type = 3
  Group = 2 > Type = 2
• Warning: For types that equal 0 (deactivated)
• Error: Metrics without a description in the metric tree
• Warning: Checks for metrics whose description is identical to the name*
• Error: Tests the existence of metric procedures (only on the Central Site)
• Error: Tests that the metric procedures have four NUMBER parameters

Check Results Consistency

• Error: Checks that all the snapshots are consolidated, except, possibly the last one
• Warning: Checks for any repetitions in the RESULTS
• Checks for the Quality Rule 'Total' result impose 'Detail' result
• Quality Rule: 'Total' result impose 'Grade' result
• Distribution: 'Category' result impose 'Grade' result
• Distribution (5.6+): no flat distribution
• Measure: 'Measure' result impose 'Grade' result
• Quality Rule non-regression: number of executed Quality Rules
• Quality Rule: ratio of executed Quality Rules per technology
• Quality Rule: 'Grade' results for module impose 'Grade' results for containers

Check Status Consistency

• Checks for the absence of status on deleted snapshots
• Error: Checks for the absence of repetitions in the STATUS
• Error: Checks that the status of the object correctly reflects the last change of status
• Error: Check the consistency of the object IDs

For example, if the connection between the client and server is lost for whatever reason during the snapshot generation process, then a lock will be set by the server preventing any further snapshot processing (you will see the error message: "Compute Metrics REJECTED: A snapshot is already being processed - the operation requested can not be completed now.").

The Remove database lock option is intended to reset this type of lock so that you can continue processing your snapshots.

- Before using the option, make sure that no connection is currently running a snapshot computation - running two concurrent computations on the same database will produce erratic results.

- In most circumstances, locks will be removed from the server automatically (indeed this is the recommended action), but this process can take a long time. This option is designed to override this automatic unlocking process.

The corresponding Database Server editor will be displayed allowing you to edit the details.