About the Controller

The ScanCentral SAST Controller (Controller) is a standalone server that sits between the ScanCentral SAST clients, sensors, and optionally, Fortify Software Security Center. The Controller accepts scan requests issued by the clients and passes them on to an available sensor. A sensor returns scan results to the Controller, which stores them temporarily.

Installing the Controller

Important! Before you install the Controller, you must first download and configure a Java Runtime Environment (JRE). For information about supported JRE versions, see the Micro Focus Fortify Software System Requirements guide. For information about how to download and configure a JRE, see the documentation for the supported JRE version.

Caution! The name of the directory into which you install the Controller must not include spaces.

To install the ScanCentral ControllerClosed Server that receives the Fortify Static Code Analyzer mobile build sessions and scan instructions from the ScanCentral SAST clients (or project packages with translation and scan instructions), routes the information to ScanCentral SAST sensors, and (optionally) uploads scan results (FPR files) to Fortify Software Security Center. (on a Linux or Windows system):

Note: In this document, <controller_dir> refers to the ScanCentral Controller installation directory, <sca_install_dir> refers to the Fortify Static Code Analyzer installation directory, and <ssc_install_dir> refers to the Fortify Software Security Center server installation directory.

After you install the ScanCentral Controller, <controller_dir> resembles the following:


bin/
db-migrate/
tomcat/
readme.txt

Installing the Controller as a Service

To install the Controller as a service on a machine without other Tomcat instances running:

  1. Log on to Windows as a local user with administrator privileges.

  2. Check to make sure that the JRE_HOME and JAVA_HOME environment variables are correctly configured.
  3. Check to make sure that the CATALINA_HOME environment variableClosed Building blocks for performance indicators; storage for measurement values that count issues, conditions, and similar categories of numeric data. is either empty or set up to point to the ScanCentral SAST Tomcat directory.

  4. Navigate to the <controller_dir>/tomcat/bin directory, and then run the following:

    service.bat install

This creates a service with the name "Tomcat9."

To install the Controller as a service with a different name:

  1. Check to make sure that the JRE_HOME and JAVA_HOME environment variables are correctly configured.
  2. Check to make sure that the CATALINA_HOME environment variable is either empty or set up to point to the ScanCentral SAST Tomcat directory.

  3. Navigate to the <controller_dir>/tomcat/bin directory, and then run the following:

    service.bat install <service_name>

Important! The service name must not contain any spaces.

Configuring the Java Memory for the Service

To configure the Java memory for the Controller service:

  1. Run tomcat9w.exe.

  2. In the Apache Tomcat Properties window, select the Java tab, and then set the Maximum memory pool value.

  3. Restart the service.

Uninstalling the Controller Service

To uninstall the Apache Tomcat 9.0 service:

  1. Stop the service.

  2. Navigate to the <controller_dir>/tomcat/bin directory, and then run the following:

    service.bat remove

To uninstall the controller as a service with a name other than Apache Tomcat 9.0:

  1. Stop the service.

  2. Navigate to the <controller_dir>/tomcat/bin directory, and then run the following:

    service.bat remove <service_name>

See Next

Configuring the ScanCentral SAST Controller

See Also

Starting the ScanCentral SAST Controller

For information about how to update your Controller, see About Upgrading ScanCentral SAST Components and Upgrading the ScanCentral SAST Controller.