Summary: documentation for the Applications panel in the Console Administration Center.
Accessing the Applications panel
Login with a user account that already has the Admin role and switch to the Admin Center:
Now move to the Applications panel:
Options available in the Applications panel are global to the entire Console, i.e. all Applications managed in Console.
The Applications option provide a means to add new Applications and Domains and administer existing Applications and Domains:
Click to enlarge
Click to enlarge
Note that the Import applications button is NOT visible when the following is true:
If a legacy license key or a Contributing Developer license key is being used, then the button is visible.
The left hand panel displays existing domains and provides a means to configure them. A "domain" is a method of grouping Applications together so that user roles can be assigned. Out of the box, no domains are provided and all new Applications will not belong to any domain (they will appear in the N/A group):
Click this button to add a new Domain to Console. You can create any number of domains:
The tick box along side the name of the domains allows you to filter the list of Applications in the right hand panel. Ticking a domain will only display Applications belonging to the selected domain:
Edit: edit an existing domain - i.e. change its name:
Delete: delete an existing domain. You can only delete a domain if no Applications are assigned to it.
|Manage User Roles: This option enables you to add resource level roles to the current domain and any applications belonging to that domain. See Administration Center - Security - User Roles.|
Any Application that has been added in Console will be visible in this list. The list displays applications based on the domain that they are assigned to. In the following example, there are three Applications:
- one belongs to TEST_DOMAIN1 (MEUDON)
- one belongs to TEST_DOMAIN2 (SEVRES)
- one does not belong to any domain ISSY)
Click to enlarge
This option allows you to perform an Application/schema upgrade on one or multiple applications. By default the icon is disabled until you select an Application that is eligible for upgrade, and will then enable:
- ≥ 2.x: applications will be eligible for upgrade when their AIP Core release is older than the AIP Core release available on ANY Node managed in Console
- 1.x: applications will be eligible for upgrade when the AIP Core release used for the Application is older than the AIP Core release installed on the current Node
When you click the icon, a warning is displayed (see image below) before the upgrade action is started. In ≥ 2.x, you can also choose the target AIP Core release - this drop down box will list all the AIP Core releases available on Nodes managed by Console that are NEWER than the AIP Core release used for the current Application:
|Search apps||Use this field to search for a specific Application. The search is performed on the Application name.|
If you would like to import into Console ≥ 2.x any existing applications that are currently managed entirely with CAST Management Studio, then you can use the Import Applications button.
- This feature must NOT be considered as a full migration - any specific configuration applied to the Application in CAST Management Studio will not be transferred (for example a specific Reference Finder configuration).
- If you would like to import existing Applications currently managed in Console 1.x into Console ≥ 2.x, please see Console V2 Migration Tool.
- The Delivery folder for the Applications you want to import must ALREADY be stored in the shared Delivery folder defined for Console ≥ 2.x. In other words, the delivery folder path for the Application in CAST Management Studio must match the Delivery folder path defined for Console ≥ 2.x. You can check the location of the Delivery folder for Console ≥ 2.x by accessing the following URL and looking for the path defined by the entry
- Console ≥ 2.x must have Node instance defined within it that is running the same release of AIP Core as used by the applications you want to import.
- The Application schemas for the applications you want to import must be stored on a CAST Storage Service/PostgreSQL instance that has already been declared in Console ≥ 2.x - see Administration Center - Settings - CSS and Measurement settings.
Click Import Applications and choose the host CAST Storage Service/PostgreSQL instance on which the schemas for your Application are stored - Console will then scan the selected host and display a list of Applications that are not already managed in Console ≥ 2.x:
Select the Application(s) you want to import, then click the Import button:
During the import, Console will check that the selected Application's delivery folder can be located in the shared Delivery folder location. If this Delivery folder is located, a successful import will be indicated by the following message (the Application will also appear in the list of available applications in the Administration Center and in the AIP Console - Application Management screen:
The following message indicates that Console cannot find the Application's Delivery folder (in the shared Delivery folder location) and the import has failed:
Used in conjunction with the icon to manage application/schema upgrades.
|Application||Name of the application.|
|Domain||Lists the domain that the Application belongs to, if any.|
|Node (≥ 2.4 only)||Indicates which Node was last |
This icon indicates the release of AIP Core currently used for each application:
If any Node currently managed in Console is using a NEWER release of AIP Core then the upgrade eligibility icon will also be displayed. This indicates that the Application can be upgraded (schema/application upgrade) to the newer release of AIP Core. Clicking the icon will start the upgrade process.
|Upgrade available (1.x only)|
This icon indicates that the application is eligible for a schema upgrade - in other words, the AIP Core release used for the Application is older than the AIP Core release installed on the Node. You can find out more about this in Application and schema upgrade using AIP Console.
|View last action outcome|
Displays the list of actions most recently actioned for the domain in a slide out window:
|Upgrade (1.x only)|
This option is only visible when an application is eligible for a schema upgrade - in other words, the AIP Core release used for the Application is older than the AIP Core release installed on the Node:
An icon will also be visible in the Application list:
You can find out more about this in Application and schema upgrade using AIP Console.
This will take you to the Application details screen where you can view information about the Application.
The Resync option will resolve a desynchronization between the Node and Console and will bring Console back up-to-date. This option should be used in the following situations:
- When you have run a Application and schema upgrade on the Application's parent Node.
- When you have performed an action in the CAST Management Studio: currently Console does not contain every single option and setting that is available in CAST Management Studio, as such it is sometimes necessary to use CAST Management Studio on a Node to perform one of these actions when working in Advanced onboarding mode. If you need to perform any of the following actions in CAST Management Studio, Console will become "desynchronized" because it does not know what has been done:
- run a new analysis/generate a new snapshot
- change any setting or option in CAST Management Studio which has an equivalent in Console
- delete an existing snapshot
Option to rename the Application. Note that when using Console ≥ 2.2 AND when a Named Application license key scope has been chosen in Complete start-up wizard - v. 2.x, a License Key field will be displayed in the rename dialog box - you must ensure that a new Named Application license key for the renamed application is entered into this field:
When the Application is renamed:
- the associated Deployment folder (which uses the Application name) will NOT be updated to use the new Application name. This is so that impacts to existing analysis results are avoided (renaming the Deployment folder will cause the status of all objects to be Deleted/Added in any future snapshots). The Deployment folder is located in the following place by default:
≥ 2.x \\share\aip-node-data\deploy\<application_name>
- the schemas associated to the Application are NOT renamed.
- the Application name will use the new name in the CAST Dashboards.
|Change Domain||Option to change the Domain to which the Application has been assigned.|
|Manage User Roles||Option to assign resource roles for the specific Application.|
Over time and through continued use, the efficiency of your Application schemas (Analysis, Dashboard and Management) may well start to degrade ("gaps" in table data, inefficient indexes etc.) - this degradation can significantly impact performance, with the most visible impact seen in the performance of the CAST Dashboards. To counter this, CAST provides a feature (known as CssOptimize) that can be run manually to optimize the Application schemas stored in the Application's associated CAST Storage Service/PostgreSQL instance - i.e. to clean up defects that have appeared over time. Click the button and choose the action you require. The optimization action will run immediately:
Option to delete the Application. When an Application is deleted, the Application's delivery / deploy folders and all Application schemas stored on the CAST Storage Service/PostgreSQL instance will be deleted. If you want to retain the Application schemas, ensure you tick the Keep data in CSS option.
In Console ≥ 1.25 it is possible to delete an application even if the application's AIP Core/schema version is older than the current Node which is managing the application. In previous releases this was not possible.
Use with caution: deleting an Application will cause irrevocable loss of data
. Ensure the Application has been backed up