Using the Custom Installation Configuration Wizard

The Custom Installation Wizard appears and identifies that you are about to create a configuration file to use for an AppScan® Source installation.

About this task

If you run the Custom Installation Wizard on a Windows™ system, the Linux™ daemon user step appears. If a Windows™ installation uses the final configuration file, it ignores this value.

Tip: If you run the wizard with an existing configuration file, it reads the values from the file and uses them as the default values.

Procedure

  1. In the Silent Installation Option panel, configure the installation type by indicating if the installation should be silent or not. Select No if you want to create an interactive custom installation.
    Note: If you create a custom silent installation, it will not succeed when running on any Turkish language locale (for example, tr and tr_TR).
    Click Next to advance to the next installation panel.
  2. Interactive custom installations only: If you are creating an interactive custom installer (No was selected in the Silent Installation Option panel), you will need to complete three Component Selection panels:
    1. In the first panel, select the AppScan® Source components that will be available (or display) in the interactive custom installation:
      • AppScan® Source for Automation
      • AppScan® Source for Analysis
      • AppScan® Source Command Line Interface
      • AppScan® Source for Development for Visual Studio 2013
      • AppScan® Source for Development for Visual Studio 2015
      • AppScan® Source for Development for Visual Studio 2017
      • AppScan® Source for Development for Visual Studio 2019
      • AppScan® Source for Development for Eclipse, MobileFirst
      Note: If the target operating system does not support a selected component - or if a selected component relies on software that does not exist on the system - the installation will ignore it, even if it is selected. For example, if the custom installer will be used for installing on a system that does not have a supported version of Microsoft™ Visual Studio installed on it, selecting AppScan® Source for Development for Visual Studio 92 for installation will be ignored when the custom installer is deployed.

      The remaining Component Selection panels allow you to indicate if displayed components are selected by default or enabled in the installation panel (components that are not enabled are greyed out when the installer is deployed and cannot be selected). For example, you may want the custom installer to force the installation of a component. You can achieve this by having the component selected by default, but not enabled.

      If a component is set to be available, but not selected by default or enabled, the component will not install (it will be greyed out and not selected for installation).

      Click Next to advance to the next installation panel.

    2. The next Component Selection panel only displays components that were selected to be available in the interactive custom installation. In this panel, identify which available components are to be selected by default. Click Next to advance to the next installation panel.
    3. Identify the components to enable for user selection/deselection in the custom installation. Disabling a component makes the installation of that component mandatory (provided it has been set to be selected by default). Click Next to advance to the next installation panel.
  3. Silent custom installations only: If you are creating a silent custom installer (Yes was selected in the Silent Installation Option panel), select the AppScan® Source components that the silent installer will install:
    • AppScan® Source for Automation
    • AppScan® Source for Analysis
    • AppScan® Source Command Line Interface
    • AppScan® Source for Development for Visual Studio 2013
    • AppScan® Source for Development for Visual Studio 2015
    • AppScan® Source for Development for Visual Studio 2017
    • AppScan® Source for Development for Visual Studio 2019
    • AppScan® Source for Development for Eclipse, MobileFirst
    Note: If the target operating system does not support a selected component - or if a selected component relies on software that does not exist on the system - the installation will ignore it, even if it is selected. For example, if the custom installer will be used for installing on a system that does not have a supported version of Microsoft™ Visual Studio installed on it, selecting AppScan® Source for Development for Visual Studio 92 for installation will be ignored when the custom installer is deployed.
  4. Select the target installation directory. For a silent installation, this is the installation directory. For an interactive installation, this is the default value.

    Click Next to advance to the next installation panel.

  5. In the License File Specification panel, specify the location of your license file or indicate the host name and port of your license server. Click Next to advance to the next installation panel.
  6. In the Specify Properties File panel, specify the name and location of the target properties file. If the wizard uses an existing configuration file, the default path name appears. You can change the file name to create a new configuration file.

    For Linux™ server installations only: Identify which Linux™ user will run the AppScan® Source daemons. After copying files, you must identify the service user. Select Create User 'ounce' or Run with Existing User, either to create the default user, ounce, or run with the existing user. (The installation validates that user. Note that the selected user must have a valid shell.)

    Click Next to save the properties file.