Home
Installing
Learn how to install the product.
Planning the deployment and installation
The configuration you use depends on a number of factors: what you plan to do with the software, how your organization and website or applications are structured, and how the information is to be distributed. Before you install the current release, review the information about hardware and software requirements, licensing, and other deployment considerations.
Installation topology examples
These examples illustrate installation topologies that are commonly used for deployment. Use the example that closely matches your situation. Each topology provides more information about when and how to use it.
Production topology example
This enterprise topology example is useful for production or medium-sized teams and multiple server deployments. In this type of installation, databases are installed on a single database server and each application is installed on a dedicated application server. You can install multiple instances of an application on separate application servers.

Installing
Learn how to install the product.
- Planning the deployment and installation
  The configuration you use depends on a number of factors: what you plan to do with the software, how your organization and website or applications are structured, and how the information is to be distributed. Before you install the current release, review the information about hardware and software requirements, licensing, and other deployment considerations.
  - Planning checklist
    Before you install HCL® AppScan® Enterprise, review and complete all of the necessary tasks on the planning checklist.
  - Installation requirements
    The Installation of AppScan® Enterprise requires the correct hardware, software, operating system, and other factors.
  - Installation topology examples
    These examples illustrate installation topologies that are commonly used for deployment. Use the example that closely matches your situation. Each topology provides more information about when and how to use it.
    - Evaluation topology example
      Evaluation installations are useful for demonstration or training deployments.
    - Production topology example
      This enterprise topology example is useful for production or medium-sized teams and multiple server deployments. In this type of installation, databases are installed on a single database server and each application is installed on a dedicated application server. You can install multiple instances of an application on separate application servers.
- Preinstallation tasks
  Before you install AppScan® Enterprise, you will need to prepare and configure your system.
- Installation tasks
  This section provides the instructions for installing AppScan® Enterprise.
- Post installation tasks
  After you install AppScan® Enterprise, complete these postinstallation tasks.
- Advanced installation scenarios

Production topology example

This enterprise topology example is useful for production or medium-sized teams and multiple server deployments. In this type of installation, databases are installed on a single database server and each application is installed on a dedicated application server. You can install multiple instances of an application on separate application servers.

production environment topology diagram

Improved traffic performance for DAST scanning

As of AppScan® Enterprise version 10.1.0, scan data is now written into a local built-in database on the DAST scan server. At the end of the scan, data is transferred to the central SQL Server database which resides on the AppScan® Enterprise Server. The increase in network traffic between the scan server and the target application reduces the network bandwidth between the scan server and the database. This improves the performance of the Web UI, enables organizations to run more simultaneous scans on a single scan server, and addresses the latency concerns when the scan server is located far from the database server.

Network traffic benchmarks for AppScan® Enterprise DAST scanning

The following benchmarks are based on a dynamic analysis scan of a test website 'Altoro Mutual' (demo.testfire.net). The web application is hosted in Texas, USA; the DAST scan server and the SQL Server database are hosted in Bangalore, India. The test scan was completed by AppScan® Enterprise 10.1.0 in 47 minutes, covered 58 pages, and included 20,914 unique security tests.

The specifications of the computer that hosted AppScan® Enterprise Sever and the SQL Server database are:

Windows™ 2019 R2 SP1
4 CPU 16G RAM
Microsoft™ SQL Server 2019 R2 (SP2), 10.50.4000.0 (x64)

The specifications of the computer that hosted the DAST scanner are:

Windows™ 2019 R2 SP1
2 CPU 4G RAM

Table 1. Network traffic data
Server	Total bytes	Bytes sent	KB/second sent	Bytes received	KB/second received
SQL Database Server	167,471,086	81,546,724	258.6	85,924,362	272.5
DAST Scan Server	329,359,220	112,187,145	355.8	217,172,075	688.8
Web Server	161,890,890	135,628,107	472.5	26,262,783	91.5

The total traffic usage between the SQL Database Server and the DAST scan server is 81,546,724 (Bytes sent) +85,924,362 (Bytes received) =167,471,086 bytes.

The total traffic usage between the DAST scan server and the Web Server is 135,628,107 (Bytes sent) +26,262,783 (Bytes received) =161,890,890 bytes.