Sample installation scenarios

When installing AppScan® Source, it is important to follow the correct installation workflow. These topics guide you through the workflow involved in some sample installation scenarios.

Note: As of version, AppScan Source no longer supports macOS or iOS Xcode project scanning.

AppScan Source consists of key components, listed here in the order in which they should be installed:

  • HCL® AppScan License Server: This is required for AppScan Enterprise Server license application. It is also used for applying AppScan Source floating licenses (but not for applying AppScan Source local license files).
  • AppScan Enterprise Server: All AppScan Source products and components must communicate with an AppScan Enterprise Server. Once installed, you specify the HCL AppScan License Server to which you have imported the AppScan Enterprise Server license.
  • AppScan Source product images: This includes AppScan Source for Analysis, AppScan Source for Automation, AppScan Source for Development, and AppScan Source for Remediation. Once installed, you specify the AppScan Enterprise Server that the AppScan Source Database will connect to. In addition, if you will make use of a floating license for AppScan Source, you specify the HCL AppScan License Server to which you have imported the AppScan Source license.

The instructions in these scenarios assume that:

  • All components are being installed on Microsoft™ Windows™. For some instructions, basic Linux™ settings and information are provided - however, main scenario workflow is described only for Windows.
  • You have administrative privileges on the machine or machines on which you are installing AppScan Source components.
  • A floating license will be used for activating the AppScan Enterprise Server and local license files will be used for activating AppScan Source components.