|CAST Imaging up and running||Your designated CAST Imaging instance must be up and running in order to accept data from AIP Console. Only one CAST Imaging instance can be configured in AIP Console to accept data.|
|CAST Imaging user with the ADMIN role||At least one CAST Imaging user must be configured with the CAST Imaging ADMIN role (see Admin Center - Role and access permission managementUsers panel) - this user should be specified in AIP Console as explained below.|
|CAST Imaging license must be valid||You must ensure that the license applied in CAST Imaging is valid.|
Enter the URL to your CAST Imaging instance, including the port number if appropriate, for example:
If the CAST Imaging instance is remote to the AIP Console host server as recommended, then you may need to configure the firewall on the CAST Imaging instance instance to accept incoming TCP connections on the specific port you are using (8083 by default).
|Imaging username||Enter a CAST Imaging user name that has the ADMIN role (see Admin Center - Role and access permission managementUsers panel).|
|Imaging password||Enter the password that corresponds to the user name you have entered.|
Enter the host name or IP address of the server hosting the CAST Imaging ETL component. This should be the host name/IP address on which the CAST Imaging instance is running - in other words it should match the hostname or IP address used in the Imaging URL field above:
Enter the ETL port number for your CAST Imaging instance. By default the ETL service on your CAST Imaging instance (which is responsible for accepting the data from AIP Console) runs on port 9001, so you should enter this number unless you have customized your internal services. If the CAST Imaging instance is remote to the AIP Console host server as recommended, then you may need to configure the firewall on the CAST Imaging instance instance to accept incoming TCP connections on port 9001.
Enter the ETL token. The token can be found in the following file on the server hosting your CAST Imaging instance:
For example (in the example below, the token that should be used is D5ED6A406775FC71B8D2A978883E8ED4):
The Publish to CAST Imaging option will be enabled in the run analysis/snapshot wizard:
Click to enlarge
When the Publish to CAST Imaging option is selected when adding a new version, a new corresponding step will be visible in the analysis/snapshot process:
The CAST Imaging icon will be visible in the AIP Console - Application Management screen for both new Applications and rescan of existing Applications:
If you delete an Application or a snapshot using AIP Console, no corresponding data will be removed from your designated CAST Imaging instance. If you need to remove the data from CAST Imaging, please see Admin Center - Application management panel.
Where is the exported data stored?
Configuring AIP Console to use the Extend Proxy feature
This beta release includes the ability to configure AIP Console to interface with a new component called CAST Extend Proxy (currently also in beta). At first glance, this component is very similar to CAST Extend Offline, however, CAST Extend Proxy has one major difference: it is configured to connect to CAST's Extend system (extend.castsoftware.com) to fetch extensions over the public internet (all other functionality provided in CAST Extend Offline is included in CAST Extend Proxy):
To use CAST Extend Proxy in AIP Console there are two methods:
Configuration during initial start-up wizard (new installations)
During the initial start-up wizard, a new option will be available in Step 4: Connect to CAST Extend:
The required information is as follows:
Configuration in System Settings (existing upgraded installations)
If you are currently using CAST Extend (live) or CAST Extend Offline, you can switch to CAST Extend Proxy using the CAST Extend - System Settings in the Administration Center. The same settings are required as explained above for the initial startup-wizard:
These two options are already available when choosing to run an analysis/take a new snapshot, whether for a new application/version in Advanced onboarding mode or an existing application with a new version in Advanced rescan mode, although they have been renamed in this beta release:
- Source code to be viewed when validating Dynamic Links
- Architecture Models results to be checked before generating a snapshot
Previously the Run analysis option (available only when choosing to run an analysis/take a new snapshot, whether for a new application/version in Advanced onboarding mode or an existing application with a new version in Advanced rescan mode) did not include this step, therefore a full snapshot was required to be generated in order to correctly validate dynamic links or view Architecture Models results.