- CAST Imaging
- Typical architecture
- Deployment modes
- Console (front end) package requirements
- Node (back end) package requirements
- Requirements for end users accessing Console and embedded Dashboards
- CAST Extend Offline/Proxy (optional) requirements
- CAST Storage Service / PostgreSQL storage
- Supported features of Directory Systems
CAST Imaging
Traditional installer for Microsoft Windows
| Software | Required | Notes |
|---|---|---|
| Host Operating System |  | Microsoft Windows
Installations of Windows Server using only Server Core (i.e. without a GUI) are not supported. |
| JDK | | A JDK (≥ 1.8.x 64bits) is required. Supported versions are as follows:
|
| Powershell | | The ability to execute Powershell scripts is required during the installation process. |
Docker (Microsoft Windows or Linux)
| Software | Required | Notes |
|---|---|---|
| Host Operating System | | Microsoft Windows
Linux
|
Third-party software required | | Docker on Linux When using the Docker Installer extension
|
Docker on Microsoft Windows
Note that when using Hyper-V mode for Docker Desktop only, the following must also be configured:
When using WSL2 mode, these changes are not required. Docker Desktop will automatically manage RAM memory and file sharing. | ||
| JDK | Optional | A JDK (≥ 1.8.x 64bits) is required if using SAML authentication to generate the public/private key pairs for SAML/SSL . Supported versions are as follows:
|
Kubernetes cluster
| Software | Required | Notes |
|---|---|---|
| Kubernetes | | Supported in CAST Imaging ≥ 2.1.0. See https://github.com/CAST-Extend/com.castsoftware.imaging.kubernetessetup for more information. |
| Helm | |
License key
CAST Imaging requires a license key before any Application data can be imported. Please contact CAST Support to obtain your license key.
Required ports
| Windows Service name | Docker container name | Description | Default Listening Port | Notes |
|---|---|---|---|---|
| CAST Imaging System - imaging-ETL | etl | CAST Imaging application management service. | 9001 | - |
| CAST Imaging System - Frontend service | nginx | CAST Imaging front-end web service. | 80 (≤ 2.0.0-beta5) 8083 (≥ 2.0.0-beta6) For ≥ 2.0.0-beta6, if port 8083 is not free, the next available port will be used. | From 2.1.0-funcrel this image is no longer pushed. Merged into "server". |
| CAST Imaging System - imaging-service | server | CAST Imaging back-end web service. | 9000 | - |
| CAST Imaging System - login service | login | CAST Imaging login and authentication service. | 8084 | From 2.1.0-funcrel this image is no longer pushed. Merged into "server". |
| CAST Imaging System - sourcecode service | sourcecode | CAST Imaging sourcecode service. | 9980 | From 2.1.0-funcrel this image is no longer pushed. Merged into "server". |
| CAST Imaging System - Neo4j Graph Database | neo4j | Neo4j Graph Database instance. | 6362, 7473, 7474, 7687 | - |
End users accessing CAST Imaging - browsers
| Browser | Supported | Notes |
|---|---|---|
| Microsoft Edge | | Minimum supported release: Windows 10 Creators Update (1703) |
Mozilla Firefox | | Minimum supported release: ≥ 63.0 |
| Google Chrome | | Minimum supported release: ≥ 70.0 |
Analysis Service schema
Analysis Service schemas from the following releases of AIP Core are supported for data generation and import:
| CAST AIP 8.3.x | |
|---|---|
| CAST AIP 8.2.x | |
- Currently, it is possible to extract data only from an Analysis Service which contains a single Application.
- The actions generate snapshot or prepare snapshot (where the Application does not contain any Architecture Models, or transaction/data call graphs) must have already been run before data generation and import takes place. Note that where the prepare snapshot or generate snapshot actions have already been run and a subsequent "run analysis only" is executed on the entire Application or one single Analysis Unit within the Application, you must either run the prepare snapshot or generate snapshot options again BEFORE data generation and import takes place.
Typical architecture
2.x
Click to enlarge
Deployment modes
Before beginning the installation process, you should be aware of the various deployment methods available:
| Release | Deployment mode | Deployment scenario | Details |
|---|---|---|---|
| 2.x | Enterprise | Docker for Linux or Docker Desktop for Microsoft Windows | Enterprise mode using Docker is highly recommended wherever possible:
|
| Enterprise | Single installer (exe) for Microsoft Windows only | ||
| Enterprise | Java JAR installers (multiple) | ||
| Standalone | Java JAR installer (single) for Microsoft Windows only | Standalone mode is targeted at deployments on Microsoft Windows on one single machine. The installer includes all required services in one single Java JAR installer:
Note that this mode has some limitations which are explained in 2.x - Standalone mode - Installation of AIP Console front-end in standalone mode. | |
| 1.x | - | Java JAR installer (single) | In 1.x, one single Java JAR installer is provided containing:
|
Console (front end) package requirements
2.x - Docker install
| Software | Required | Notes |
|---|---|---|
| Host Operating System | | Microsoft Windows
See https://docs.docker.com/desktop/windows/install/. Linux
|
Third-party software required | | Docker on Linux
|
Docker on Microsoft Windows
Note that when using Hyper-V mode for Docker Desktop only, the following must also be configured:
When using WSL2 mode, these changes are not required. Docker Desktop will automatically manage RAM memory and file sharing. | ||
| Access to at least one CAST Storage Service /PostgreSQL | | An installation of the CAST Storage Service/PostgreSQL, which must be accessible over the network. This is used to host the schemas required for storing analysis results - these schemas do not need to be pre-installed as Console will manage their installation.
Note that a PostgreSQL instance is provided as a Docker container running on port 2285 - it will be preconfigured in Console. This instance is used to store the following:
This CAST Storage Service/PostgreSQL instance can ALSO be used to host schemas (Management, Analysis, Dashboard, Measurement) that are required for analysis/snapshot storage. |
| Ports | | The following ports must be opened inbound on the host server. These correspond to each Docker container required by Console (front-end). This is so that remote Node instance can access the required services:
These ports can be customized if required. |
| User permissions | | To run the Docker install, Administrator privileges are required:
|
| Access to hub.docker.com | | All Docker containers are pulled direct from https://hub.docker.com/, therefore the host server must have access to this. |
| Global CAST License | | Console requires a global CAST license key. This key will be applied to all Node packages that you install. |
| CAST Extend | | In order to install any CAST AIP Extensions automatically, Console needs to connect to CAST's managed service known as "Extend" over the public internet. You will therefore need to register a CAST Extend account (https://extend.castsoftware.com/#/register) and generate an API key (this key is used by Console in the start-up wizard). In addition, access to the following URL on port 443 via TCP is required: Note that if (due to security concerns) your organization cannot interact over the public internet with CAST's managed services, you can alternatively use CAST Extend Offline/Proxy. |
2.x - Multiple JAR install
The JAR installers are an alternative to a Docker deployment. See 2.x - Enterprise mode - Installation of AIP Console front-end via Java JAR installers.
| Software | Required | Notes | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Host Operating System | | Supported versions of Windows:
Installations of Windows Server using only Server Core (i.e. without a GUI) are not supported.
| ||||||||||||||||||||||||
Java (JRE/JDK) | | A 64bit Java JRE or JDK is required to install and run Console. Most Java variants certified by the OpenJDK Community Technology Compatibility Kit are compatible with Console (you can verify if a company has access to the TCK on the OpenJDK website). However, CAST highly recommends using the following LTS releases which are known to function with v. ≥ 2.0:
| ||||||||||||||||||||||||
| JAVA_HOME environment variable | | A JAVA_HOME system wide environment variable must exist on all host machines, pointing to the installation location of your Java JRE or JDK. | ||||||||||||||||||||||||
| Access to at least one CAST Storage Service /PostgreSQL | | An installation of at least one CAST Storage Service/PostgreSQL, which must be accessible over the network. This is used to host various items required by Console/Nodes:
You can use one single CAST Storage Service/PostgreSQL to host all required items, or dedicated CAST Storage Service/PostgreSQL instances to host each item. Note that the CAST Storage Service/PostgreSQL instance defined in the Service Registry Java installer will also be made available for use as storage for application analysis/snapshot requirements. | ||||||||||||||||||||||||
| Ports | | The various services run on the following ports by default:
These ports can be customized if required. | ||||||||||||||||||||||||
| User permissions | | To run the setup start and run the Console package on the server, the follow user permissions are required:
| ||||||||||||||||||||||||
| Global CAST License | | Console requires a global CAST license key. This key will be applied to all Node packages that you install. | ||||||||||||||||||||||||
| CAST Extend | | In order to install any CAST AIP Extensions automatically, Console needs to connect to CAST's managed service known as "Extend" over the public internet. You will therefore need to register a CAST Extend account (https://extend.castsoftware.com/#/register) and generate an API key (this key is used by Console in the start-up wizard). In addition, access to the following URL on port 443 via TCP is required: Note that if (due to security concerns) your organization cannot interact over the public internet with CAST's managed services, you can alternatively use CAST Extend Offline/Proxy. |
1.x - JAR install
| Software | Required | Notes | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Host Operating System | | The Console package can be installed on both Windows and Linux operating systems:
Installations of Windows Server using only Server Core (i.e. without a GUI) are not supported.
| ||||||||||||||||||||||||
Java (JRE/JDK) | | A 64bit Java JRE or JDK is required to install and run Console. Most Java variants certified by the OpenJDK Community Technology Compatibility Kit are compatible with Console (you can verify if a company has access to the TCK on the OpenJDK website). However, CAST highly recommends using the following LTS releases which are known to function with v. ≥ 1.14.0:
sudo update-alternatives --config java
| ||||||||||||||||||||||||
| JAVA_HOME environment variable | | A JAVA_HOME system wide environment variable must exist on all host machines, pointing to the installation location of your Java JRE or JDK. | ||||||||||||||||||||||||
| User permissions | | To run the setup start and run the Console package on the server, the follow user permissions are required:
| ||||||||||||||||||||||||
| Access to Node(s) | | The Console package requires access to the analysis nodes on which the Node package/AIP Core has been installed:
| ||||||||||||||||||||||||
| Access on port 8081 | | The Console package runs by default on port 8081 (although you can customize this if required - CAST recommends enabling secure HTTPS connection) therefore you will need to adjust firewall rules on the host server to allow access to the appropriate port so that users can access Console in their browser. | ||||||||||||||||||||||||
| Global CAST License | | The Console package requires a global CAST license key. This key will be applied to all Node packages that you install. | ||||||||||||||||||||||||
| CAST Extend | | In order to install any CAST AIP Extensions automatically, Console needs to connect to CAST's managed service known as "Extend" over the public internet. You will also need login credentials for Extend - i.e. you will need to register an account. Access to the following URL on port 443 via TCP is required: Note that if (due to security concerns) your organization cannot interact over the public internet with CAST's managed services, you can alternatively use CAST Extend Offline/Proxy. |
Node (back end) package requirements
See also Managing multiple applications in Hardware requirements for more information.
| Software | Required | Notes | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Host Operating System | | The Node package must be installed on a Windows host operating system since it requires the presence of AIP Core. Supported versions of Windows:
| ||||||||||||||
| AIP Core | | A standard installation (i.e. run from the AIP Core setup) of AIP Core ≥ 8.3.6 is required on the target node.
| ||||||||||||||
| CAST Storage Service /PostgreSQL | | An installation of the CAST Storage Service/PostgreSQL, which must be available either on the target node or on another dedicated server accessible over the network. This is used to host the schemas required for storing analysis results - these schemas do not need to be pre-installed as Console will manage their installation.
| ||||||||||||||
| Java (JRE/JDK) | | A Java JRE or JDK is required to install and run Node. See Java (JRE/JDK) above for more information about requirements. | ||||||||||||||
| Data storage folders | | The following folders are required by the Node and must be accessible. CAST recommends the use of a common network share for all Nodes. Note however that in v. 1.x, these folder will be located, by default on each Node.
| ||||||||||||||
| Network access | | v. 2.x The Node package runs on the following ports (this port is used for communication from the Node to Console):
The Node instance requires outbound access from the following default ports to the server hosting Console:
In addition, outbound access to any CAST Storage Service/PostgreSQL instances configured for Analysis/Snapshot/Measurement storage requirements is required. v. 1.x The Node package runs by default on port 8082 (although you can customize this if required - CAST recommends enabling secure HTTPS connection) and this port is used for communication from Console to the Node(s), therefore you will need to adjust firewall rules on the Node instance to allow inbound access from Console. In addition, outbound access to any CAST Storage Service/PostgreSQL instances configured for Analysis/Snapshot/Measurement storage requirements is required. | ||||||||||||||
| CAST Extend | | In order to install any CAST AIP Extensions automatically, each Node needs to connect to CAST's managed service known as "Extend" over the public internet. You will also need login credentials for Extend - i.e. you will need to register an account: Access to the following URL on port 443 via TCP is required: Note that if (due to security concerns) your organization cannot interact over the public internet with CAST's managed services, you can alternatively use CAST Extend local server. | ||||||||||||||
| User permissions | | To run the setup and start/run the Node package on the server, local Administrator privileges are required. |
Requirements for end users accessing Console and embedded Dashboards
Browsers
The following browsers are supported when run on Linux, macOS or Microsoft Windows. We regularly test with a subset of the available versions, and aim to fix issues found with any of them.
Browser | Supported | Notes |
|---|---|---|
| Microsoft Edge | | Minimum supported release: 44 and above |
Mozilla Firefox | | Minimum supported release: 95 and above |
| Google Chrome | | Minimum supported release: most recent only |
| Safari | | Minimum supported release: 12 and above |
See Standalone dashboard - installation requirements if you intend NOT to use the Dashboards embedded in CAST Console.
CAST Extend Offline/Proxy (optional) requirements
See:
CAST Storage Service / PostgreSQL storage
See:
Supported features of Directory Systems
Directory Services | |
|
|---|---|---|
Microsoft Active Directory Lightweight Directory Services | Partially | Microsoft AD LDS does not have all the information in the server itself, but may provide a pointer to another server where that information is stored. Depending on what is stored, authentication and authorization may fail if pointing to a AD LDS server and not enough information is present. If this occurs, the configuration should be modified to point to a full Microsoft Active Directory server. |
| Global Catalog Servers (GCS) | | Sometimes required if an Active Directory or other Directory Services server contains multiple domains or domains and sub-domains. as the Global Catalog Server contains LDAP information for all domains. In this case the LDAP URL should point to the GCS server URL (normally same as LDAP URL with port 3268 for LDAP and 3269 for LDAPS) |
Proxies | Partially |
|
Referrals | Partially | If a referral is used, the machine name needs to be able to be resolved the Doman Name Service (DNS) process. This may require that DNS or a local hosts file is modified to ensure that it occurs. |
SSO (Single Sign On) | | Supported for AIP Console/CAST Imaging via SAML |
| Nested Groups | | - |
