About the fortify.home Directory

The fortify.home directory is where the configuration file and other Fortify Software Security Center resources reside. After Fortify Software Security Center deployment, you can find it in:

Note: These are the default directories. You can specify a different directory using the Setup wizard during configuration. (See Configuring Fortify Software Security Center for the First Time.)

Directory Structure

The fortify.home directory is structured as follows:

<fortify.home>/
    <app_context>/
         conf/
             app.properties
             datasource.properties
             log4j2.xml
             version.properties
         logs/ 
             ssc.log
             ...
         init.token
	      ...	
	 plugin-framework/
    fortify.license
  

where

log4j2.xml is the log configuration, which you can change on the fly.
init.token

represents a new security token that is generated each time the Setup wizard is loaded (start of server in configuration mode). The user who configures Fortify Software Security Center uses this token to access the Setup wizard at the <host>:<port>/init URL.

app.properties

is a file that contains the applicationClosedA customer codebase evaluated by Fortify software. The top-level container for one or more application versions. When you work with a new codebase, the application and first application version are automatically created. An application includes one or more application versions that users create and configure. properties that the customer can configure (extracted from ssc.properties).

datasource.properties

is a file that contains the database connection properties.

version.properties

is a file that stores information about current and previous versions of Fortify Software Security Center for application upgrade purposes.

plugin-framework is the plugin framework configuration and temporary storage (internal).
fortify.license

is the license file for Fortify Software Security Center.