Summary: This section describes how to prepare and deliver the source code of your PowerBuilder application.
Preparation - source code discovery
Discovery is a process that is actioned during the delivery process CAST will attempt to automatically identify "projects" within your application using a set of predefined rules. Discoverers are currently embedded in CAST AIP Core:
You should read the relevant documentation for each discoverer (provided in the link above) to understand how the source code will be handled.
Using CAST AIP Console
- Supported in AIP Console v. ≥ 1.17.
- See Application onboarding for more information.
Source code delivery
AIP Console expects either a ZIP/archive file or source code located in a folder configured in AIP Console. You should include in the ZIP/source code folder all PowerBuilder source code:
CAST highly recommends placing the files in a folder dedicated to PowerBuilder. 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:
In order for a PowerBuilder analysis to complete successfully
- the PowerBuilder IDE must be installed on the machine on which the analysis is running - i.e. the AIP Node
or the path to the pborxx.dll file and the PowerBuilder version must be populated in the
<AIP_node_installation>\AipNode\data\aip-node-app.propertiesfile if the PowerBuilder IDE is not installed on the AIP Node.
In essence, AIP Console needs to know the version of PowerBuilder you are delivering/analyzing and where the pborxx.dll file is located:
- AIP Console will first attempt to discover the location of the pborcXXX.dll file/PowerBuilder version using the Windows registry (on the AIP Node) during the source code delivery process. If AIP Console finds a registry key on the AIP Node, it will populate the relevant fields in the AIP Console GUI (see PowerBuilder - Analysis configuration).
- If no registry key is found (i.e. the PowerBuilder IDE is not installed on the AIP Node), then AIP Console will look in the following file on the target AIP Node. For example - these locations can be filled in BEFORE delivering the source code (you must restart the AIP Node so that the changes are taken into account):
- If neither method reveals the location of the pborcXXX.dll file/PowerBuilder version, then the analysis will fail.
Above all, the options defined in the AIP Console GUI have priority over the Windows registry and the aip-node-app.properties file (in that order).
Using legacy CAST Delivery Manager Tool
How do I add a source code package to my delivery
What you should package?
When creating packages to discover and extract your PowerBuilder application you should create them as listed below:
Source code root folder
Use the "Files on your file system" / SVN / TFS options in the CAST Delivery Manager Tool:
Click to enlarge
How do I fine-tune my Version ?
See How do I fine-tune my Version for more information.
How do I deliver the Version for analysis?
See How do I deliver the Version for analysis for more information.
See Validate and Accept the Delivery for more information.