Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.properties file 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. However, you can manually choose the 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).

...