Home
Installing
Learn how to install the product.
Advanced installation scenarios
Installation roadmap for AppScan® Source deployment
Information to help you understand the requirements for a successful installation.
Configuring an AppScan® Source Oracle database with AppScan® Enterprise Server
If you are configuring AppScan® Source to log into AppScan Enterprise, a Java™ Virtual Machine (JVM) parameter needs to be added to tell AppScan Enterprise where your AppScan Source Oracle tnsnames.ora file is located. How you do this depends on your OS and configuration.

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.
- 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
  - Installing multiple instances of the Enterprise Console on a single server
    You have the option of installing a default instance, or multiple instances on a single computer. Each instance is an independent set of configuration information with its own database.
  - Setting up an external scanner for AppScan Enterprise in the DMZ
    If you're testing websites that are outside the firewall, you can set AppScan Enterprise to go through the firewall to test them. However, opening a port through the firewall poses a security risk, as does having a system that stores potentially sensitive files outside the firewall (such as logs and scan data). As an alternative, consider setting up a proxy to provide access outside the firewall.
  - Installation roadmap for AppScan® Source deployment
    Information to help you understand the requirements for a successful installation.
    - Configuring an AppScan® Source Oracle database with AppScan® Enterprise Server
      If you are configuring AppScan® Source to log into AppScan Enterprise, a Java™ Virtual Machine (JVM) parameter needs to be added to tell AppScan Enterprise where your AppScan Source Oracle tnsnames.ora file is located. How you do this depends on your OS and configuration.
  - Configuring more than one IP address for the host computer
    If the computer that hosts AppScan Enterprise Server uses more than one IP address, you must modify the server.xml file so that AppScan Enterprise can properly authenticate with Liberty.
  - Uninstalling an instance of the Enterprise Console
    Remove instances that are no longer needed on a single server.
  - Un-installing the software
    You might want to uninstall and reinstall the Server if the installation failed.

Configuring an AppScan® Source Oracle database with AppScan® Enterprise Server

If you are configuring AppScan® Source to log into AppScan® Enterprise, a Java™ Virtual Machine (JVM) parameter needs to be added to tell AppScan® Enterprise where your AppScan® Source Oracle tnsnames.ora file is located. How you do this depends on your OS and configuration.

Procedure

The parameter to add is: -Doracle.net.tns_admin={path to directory containing the tnsnames.ora file). For example: -Doracle.net.tns_admin=c:\oracle\product\10.2.0\client_1\NETWORK\ADMIN
Choose your deployment:
1. If you are running on Windows, update the <install-dir>/appscan enterprise/Liberty/usr/servers/ase/jvm.options file.
2. If you are running on Linux™, update the /opt/HCL/AppScan_Server/Liberty/usr/servers/ase jvm.options file.
Stop the Liberty service and restart it for the changes to take effect.