Prepare and deliver the source code
Introduction
Discovery is a process that is actioned during the packaging process whereby CAST will attempt to automatically identify projects within your application using a set of predefined rules. Discoverers are currently embedded in CAST Imaging:
You should read the relevant documentation for each discoverer (provided in the link above) to understand how the source code will be handled.
When the Package action is complete, you can view the projects that have been identified in the Package Content tab. When a successfully Packaged application is subsequently deployed in the CAST Management Studio, an Analysis Unit will be created for each project that has been identified during the Discovery process and is not excluded by a rule or filter.
Using CAST Imaging Console
CAST Imaging Console expects either a ZIP/archive file or source code located in a folder configured in CAST Imaging Console. You should include in the ZIP/source code folder all the output from the CAST Database Extractor, i.e:
.castextraction |
CAST Imaging Console supports this file type as follows:
When a .castextraction file is delivered to CAST Imaging Console, it will be transformed automatically into the required .uaxDirectory/.uax./src files during the source code delivery process. Technically the following occurs:
With regard to T-SQL .castextraction files:
|
---|---|
|
Supported for both PL/SQL (Oracle Server) schemas and T-SQL (Microsoft SQL Server/Sybase ASE/Azure SQL) databases. |
CAST highly recommends placing the files in a folder dedicated to your extraction. If you are using a ZIP/archive file, zip the folders in the “temp” folder - but do not zip the “temp” folder itself, nor create any intermediary folders:
D:\temp
|-----LegacySQLExtaction
|-----OtherTechno1
|-----OtherTechno2