Page tree
Skip to end of metadata
Go to start of metadata



In place upgrade from beta1 to beta2 is supported in this release. See

New Features

UI - Embedded DashboardsThis release provides a new Docker container dedicated to the Health and Engineering Dashboards. See for more information. No configuration is required other than assigning the correct roles to users/groups to allow them to access the application data they need - this is explained in Access to the Dashboards is exactly as in v. 1.x, using the icons available in UI.

Other Updates

Internal IdDetails
WEBI-11077Delivered Engineering Dashboard release: 2.4.0-funcrel. Delivered Health Dashboard release: 2.4.0-funcrel.

Known Issues

Internal IdDetails
WEBI-11163Deleting a CAST Storage Service/PostgreSQL instance in AIP Console does not delete the configuration in Dashboards.
WEBI-11163Measurement schema stored in the file may not match the expected data source if the same schema exists in multiple schemas.
WEBI-11163When accessing the Health Dashboard or Engineering Dashboard without any application created or analyzed/snapshot generated in AIP Console, an error message indicating a misconfiguration will appear. This error will disappear once you have created a snapshot for an application.
WEBI-11163The Report Generation feature in the Engineering Dashboard is disabled and will not work (Report Generator is not part of any docker container).
WEBI-11163Only users with the "dashboards_admin" role can see application in the Health and Engineering Dashboards. This role allows the user to access all applications regardless of the user's application authorization in AIP Console.



This is a beta release and the following limitations are in place:

  • No in place upgrade from AIP Console v. 1.x (same for AIP Node instances)
  • No import of Applications currently managed in CAST Management Studio (applications can be imported from AIP Console v 1.x)
  • No ability to interact with embedded CAST Dashboards (standalone CAST Dashboards can be used)

All documentation is available in:

New Features

Architecture restructureAIP Console front-end has been entirely restructured around Linux based Docker containers to improve deployment flexibility. One container each for the following items front-end UI, a PostgreSQL internal database to store settings (new in this release), a gateway and service manager to manage connections from AIP Node instances, and an open-source authentication provider (Keycloak). Deployment is compatible with Docker on Microsoft Windows (Linux containers must be enabled) and Linux. See
AIP Node instances are now statelessAIP Node instances are now considered to be stateless (the applications are not attached to a specific AIP Node instance). All AIP Node instances register themselves in AIP Console and use common a configuration provided by AIP Console (stored in the PostgreSQL database provided as a Docker container - the AIP Node Database). Thus, all AIP Node instances connect to the same PostgreSQL database (the AIP Node Database) to fetch settings and options and all use the same locations for delivery, deploy and common data (these locations must now always be deployed as shared folders).
CAST Storage Service/PostgreSQL instance managementThe management of CAST Storage Service/PostgreSQL instances that will be used for your analysis schema storage and for your Measurement schema has changed in AIP Console v.2. Out of the box, both storage requirements will be set to use the internal AIP Node database (provided as a PostgreSQL Docker container). As part of the initial deployment process, you should add your additional standalone CAST Storage Services/PostgreSQL instances into the AIP Console UI - when added, each storage service can be used either for the Measurement schema or for analysis storage schemas. When creating a new application, you will now need to chose the target CAST Storage Service/PostgreSQL instance - the Application is then tied to this instance. In other words, all AIP Node instances can now use any CAST Storage Service/PostgreSQL instance defined in AIP Console. See

Feature Improvements

Authentication improvementsThe AIP Console authentication provider has been totally restructured and now uses the open-source OAuth2 compatible Keycloak system. Keycloak provides local authentication, and can also interact with other enterprise authentication systems such as LDAP and SAML. This change greatly simplifies the configuration of the authentication method you choose. See
Application managementApplication management is similar to v 1.x, however, Applications are no longer tied to one single AIP Node instance. All required storage locations such as deploy/delivery must now be configured as shared folders. AIP Console will also automatically operate in load-balancing mode where the least used AIP Node instance is selected from the pool of AIP Node instances to perform the next job (analysis/snapshot etc.). Therefore when creating a new Application, an AIP Node instance is no longer defined, however, it is now necessary to define a specific CAST Storage Service/PostgreSQL instance for your Application storage requirements at this time (the application remains "tied" to this storage instance).
Initial start-up wizard restructuredOnly two steps now exist in the initial start-up wizard: 1) entry of the AIP license key, 2) connection to CAST Extend services. All other steps are either no longer required (installation verification) or are provided directly in the UI Administration Center (Measurement schema definition and Admin role assignment).
Import Applications from AIP Console v. 1.xIt is now possible to import Applications that are currently managed with AIP Console v.1.x into AIP Console v. 2.x. See
Application and schema upgradeApplication and schema upgrade has been improved in this release to take into account stateless AIP Node instances: the upgrade paths available for selection depend entirely on the releases of AIP Core that your AIP Node instances are running. See

Other Updates

Internal IdDetails
WEBI-9781Global Dynamic Links Rules files are no longer replicated to AIP Node instances. See
WEBI-10304Move Architecture Studio from AIP Console to AIP Node instance. See
  • No labels