...

D:\temp
	|-----PowerBuilder
	|-----OtherTechno1
	|-----OtherTechno2

Anchor
options options

PowerBuilder

...

version

In order for a PowerBuilder analysis to complete successfully, AIP Console needs to know two things (see also PowerBuilder - Analysis configuration):

Image Removed

...

the

...

PowerBuilder IDE

...

must be installed on the machine on which the analysis is running - i.e. the AIP Node.

...

 AIP Console then needs to know the version of

...

AIP Console behaves as follows with regard to these optionsPowerBuilder you are delivering/analyzing:

• 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, it will populate the relevant fields in the AIP Console GUI (see screenshot above PowerBuilder - Analysis configuration).
• If no registry key is found, 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. However, you can manually configure choose the location PowerBuilder version directly in the AIP Console GUI once you have delivered the source code and accepted/imported it as the current version. This requires that you perform an Advanced onboarding in order not to generate a snapshot as part of the source code delivery process.

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

...