This page is no longer maintained and may be obsolete.







Platform administration information




There are five main basic use cases for handling Assessment Models customizations:

  1. Distribute a custom Assessment Model from one 7.2.x implementation to another
  2. Reuse a custom Assessment Model from one 7.2.x Dashboard Service to another
  3. Merge enrichments (new indicators) from multiple Assessment Models into one
  4. Install enrichments (new indicators) from 7.2.x Server Manager custom installation packages
  5. Merge settings (weight, critical contribution, thresholds, ...) from two Assessment Models into one

Each is explained in more detail below.

They can obviously be combined together to achieve larger goals:

Use case overview

Use Case #1: Distribute a custom Assessment Model from one 7.2.x implementation to another

Starting from:

That is:

And you want to:

Use Case #2: Reuse a custom Assessment Model from one 7.2.x Dashboard Service to another

Starting from:

That is:

And you want to:

Use Case #3: Merge enrichments (new indicators) from multiple Assessment Models into one

Starting from:

That are:

And you want to:

Use Case #4: Install enrichments (new indicators) from 7.2.x Server Manager custom installation packages

Starting from:

That is:

And you want to:

Use Case #5: Merge settings (weight, critical contribution, thresholds, ...) from two Assessment Models into one

Starting from:

That are:

And you want to:


Use case process description

This section presents the steps to perform that relates to Assessment Model customization handling.

Use Case #1: Distribute a custom Assessment Model from one 7.2.x implementation to another

The distribution of a custom Assessment Model from one 7.2.x implementation to another relies on CAST Management Studio import/export as PMX file capability

(the chart above refers to 7.1.x yet is still valid with 7.2.x)

Basically, this is about

  1. Exporting from the source Management Base the Assessment Model to share as a PMX file
  2. Connecting to the target Management Base (and transfer the export PMX file to a location accessible from the CAST Management Studio in use)
  3. Importing into the target Management Base the Assessment Model present in the PMX file. Important note: use the "create" action from the import wizard
  4. Assign the imported Assessment Model to the appropriate Dashboard Service
  5. Run a validation Snapshot to ensure that all required configuration is present in the target environment.

Details on some of the tasks

Exporting Assessment Model as PMX file

In the CAST Management Studio:

Import Assessment Model as PMX file

In the CAST Management Studio

Assign the Assessment Model to a Dashboard Service

In the CAST Management Studio

Use Case #2: Reuse a custom Assessment Model from one 7.2.x Dashboard Service to another

The reuse of a custom Assessment Model from one 7.2.x Dashboard Service to another relies on shared assignment of a single Assessment Model by multiple Dashboard Services

(the chart above refers to 7.1.x yet is still valid with 7.2.x)

Basically, this is about

  1. Assign the Assessment Model to reuse to the appropriate Dashboard Service
  2. Run a validation Snapshot to ensure that all required configuration is present in the target environment.

Details on some of the tasks

Assign the Assessment Model to a Dashboard Service

In the CAST Management Studio

Use Case #3: Merge enrichments (new indicators) from multiple Assessment Models into one

The merge of enrichments (new indicators) from multiple Assessment Models into one relies on XMLtoDB tooling that can import/export specific scope of data into/from Dashboard Services

(the chart above refers to 7.1.x yet is still valid with 7.2.x)

Basically, this is about:

  1. Synchronizing a first Assessment Model, considered as the target, onto a target Dashboard Service (Best option is to Syncrhonize the default CAST 7.1.x Assessment Model)
  2. Remove this Assessment Model from the CAST Management Studio
  3. Synchronizing a second Assessment Model, considered as the source, onto a temporary Dashboard Service
  4. Export custom indicators from the temporary Dashboard Service using XMLtoDB tooling and a custom export Scope to accurately target some or all custom indicators
  5. Import custom indicators into the target Dashboard Service using XMLtoDB tooling and the same Scope. Go back to the 3rd step in case you have multiple source Assessment Model to process. Important note: when dealing with multiple sources, ensure the indicators' external IDs do not overlap (if so, update external IDs prior to the synchronization step.)
  6. From CAST Management Studio, Import the Assessment Model from the target Dashboard Service that will now contain the custom indicators from the source Assessment Model(s).
  7. Run a validation Snapshot to ensure that all required configuration is present in the target environment.

Details on some of the tasks

Synchronize Assessment Model in Dashboard Service

In the CAST Management Studio

Removing Assessment Model

In the CAST Management Studio:

XMLtoDB export scope definition

A scope is the declaration of a list of SQL Tables to consider for data transfer to or from an XML file.
It can refine the range of rows to consider in these SQL Tables through the declaration of filters on Column field values.

To create your own export/import scope:

XMLtoDB export from Dashboard Service

To export custom indicators from the source Dashboard Service database using your scope (CAST Storage Service 2 sample), run the following command in a Microsoft DOS Command Prompt:

<installation directory>/xmltodb /src:db /c:<MyCentralModel>.xml /scp:<CustomerMetricsScope1> /f:<MyExportFromSourceDSUsingCustomerMetricsScope1>.xml /db:<SourceDashboardServiceName> /cs:LIBPQ:localhost:2280,postgres /st:caststorageservice /u:operator /p:CastAIP

(change values where appropriate)

XMLtoDB import in Dashboard Service

To import custom indicators into the target Dashboard Service database using your scope (CAST Storage Service 2 sample), run the following command in a Microsoft DOS Command Prompt:

<installation directory>/xmltodb /src:xml /c:<MyCentralModel>.xml /scp:<CustomerMetricsScope1> /f:<MyExportFromDSUsingCustomerMetricsScope1>.xml /db:<TargetDashboardServiceName> /cs:LIBPQ:localhost:2280,postgres /st:caststorageservice /u:operator /p:CastAIP

(change values where appropriate)

Import Assessment Model in CAST Management Studio

In the CAST Management Studio

  • open the Dashboard Service editor
  • select the Assessment Model tab
  • invoke the "Import Assessment Model" action to load from the Dashboard Service the default 7.1.0 Assessment Model enriched with the custom indicators from the XMLtoDB import
  • control the execution status in the task progress window

Use Case #4: Install enrichments (new indicators) from 7.2.x Server Manager custom installation packages

The installion of enrichments (new indicators) from 7.2.x Server Manager custom installation packages relies on CAST Management Studio Assessment Model import from Dashboard Services

(the chart above refers to 7.1.x yet is still valid with 7.2.x)

Basically, this is about

  1. Deploying the custom installation packages on the machine Server Manager is installed: please refer to Where are custom components stored? section from the CAST Server Manager User Components User Guide

  2. Install a new Dashboard Service using these packages. Important note : please remove custom installation packages from the deployment location once you are done so as to avoid unwillingly and unknowingly using them for future installations.

  3. From CAST Management Studio, discover the new Dashboard Service

  4. Import its Assessment Model
  5. Run a validation Snapshot to ensure that all required configuration is present in the target environment.

Details on some of the tasks

Import Assessment Model in CAST Management Studio

In the CAST Management Studio

Use Case #5: Merge settings (weight, critical contribution, thresholds, ...) from two Assessment Models into one

The merge of settings (weight, critical contribution, thresholds, ...) from two Assessment Models into one relies on CAST Management Studio import/export as PMX file capability and Microsoft Excel comparison tooling


(the chart above refers to 7.1.x yet is still valid with 7.2.x) 

Basically, this is about

  1. Exporting as a PMX file a first Assessment Model, customized or not, considered as the target,
  2. Exporting as a PMX file a second Assessment Model, whose customizations are to be - partially or totally - preserved, considered as the source,
  3. Comparing the two PMX files using the Microsoft Excel comparison tool
  4. Updating the target Assessment Model where appropriate to match source configuration

Details on some of the tasks

Exporting Assessment Model as PMX file

In the CAST Management Studio:

Compare Assessment Model PMX files

Running the comparison tool

The comparison tool can be found here: AssessmentModel(Documentation)Comparator_toBeUnzippedIn-Y-Drive.zip

In Microsoft Windows Explorer

In Microsoft Excel

Identify and understand differences

The comparison tool will help you identify the differences you may want to use to further update the migrated Assessment Model (using Assessment Model editor in CAST Management Studio).

The comparison tool will identify evolutions of different types:

What to do with differences

As general guidelines, please process the differences the following way:

Manually update target Assessment Model according to your needs

Back in the CAST Management Studio