Modular installation of AppScan 360° on a single virtual machine

Modular installation is an optional flow for running installation in smaller, controlled steps. This works on both express and custom installation modes. The existing behavior of the full installer remains unchanged. If you do not use --modular, the installer follows the standard full installation path.

When to use modular mode

Modular mode is intended for component-wise installation in case any component fails during the regular installation process.

Start modular installation

To start single VM installation in modular mode, run:
sudo ./AppScan360_SingleVMsetup_v<version>.run -- $PWD --modular

Automatic modular prompt after a previous attempt

If you start the installer without --modular and a previous installation attempt (log file presence check) is detected, the installer asks whether to continue from the last successful step.
  • If you choose Yes (or press Enter), the installer switches to modular mode.
  • If you choose No, the installer continues with regular full installation.

Available modular modes

  1. Install one component only Runs only the selected component, then exits.

  2. Resume from component and continue forward Starts at the selected component and proceeds in supported forward order.

Supported forward order

The modular flow uses this sequence:

  1. ipr (Internal Private Registry for storing supporting images)

  2. dpr (Docker Private Registry for storing application images)

  3. mssql (Microsoft SQL Server DB)

  4. k0s (Kubernetes cluster)

  5. cert-manager (Certificate Manager for Kubernetes)

  6. istio (Gateway controller for Kubernetes)

  7. ascp (ASCP kit)

  8. asra (ASRA kit)

  9. dtcs (DTCS kit)

  10. sca (SCA kit)

Example for resume mode if we select 5 or cert-manager:
cert-manager -> istio -> ascp -> asra -> dtcs -> sca

Component visibility notes

The list shown in modular mode can vary based on deployment choices and available kits.

  • dtcs is shown only when a DTCS kit is available.

  • sca is shown only when SCA installation is enabled.

  • mssql is shown only for POC/Express deployments.

  • dpr visibility depends on deployment mode and DPR selection.

Advisory checks before execution

Before running a component, the installer checks whether it may already be active.
  • For most components, you are warned and asked whether to continue.
  • For istio, if it is already active, the installer warns and skips reinstall in modular flow.

If you need to reinstall istio, clean it first and then resume from istio.

Failure and recovery

If a component fails, modular execution stops at that component.

To recover:
  1. Check the engage log for the failed component.
  2. Resolve the underlying issue.
  3. Run modular installation again.
  4. Choose resume mode and select the failed component.