Automating configuration in a root context

To automate Application Security configuration in a root context:

1. Open a text editor and create a file named _default_.autoconfig.

2. Add the following to the _default_.autoconfig file in the YAML format shown.

   Copy only the database properties for the database engine you use, and ensure that you remove the hash symbol (#) before each property.

   appProperties:
    # Include any property found in <fortify.home>/_default_/conf/app.properties. 
    # For example, host.url: 'https://ssc.example.com/'
    # searchIndex.location: '<fortify.home>/_default_/index' 
    # host.validation: false 
   datasourceProperties: 
    # Include any property found in <fortify.home>/_default_/conf/datasource.properties. 
    # For example: 
    # db.username: ssc_db_admin_username 
    # db.password: ssc_db_admin_password 
    # MSSQL database 
    # jdbc.url: 'jdbc:sqlserver://mssql-host:1433;database=ssc_db;sendStringParametersAsUnicode=false' 
    # MySQL database 
    # jdbc.url: 'jdbc:mysql://mysql-host:3306/ssc_db?  sessionVariables=collation_connection=latin1_general_cs&rewriteBatchedStatements=true' 
    # Oracle database 
    # jdbc.url: 'jdbc:oracle:thin:oracle-host:1521:ssc_db'  
   dbMigrationProperties: 
    # Enable automatic database migration 
    migration.enabled: true 
    # Optionally specify alternative migration credentials 
    # migration.username: ssc_db_admin_username 
    # migration.password: ssc_db_admin_password 
   seeds: 
    # Modify the path to the appropriate location for your environment  
    - '/home/ssc/bundles/ Fortify_Process_Seed_Bundle-2025_Q2_<build>.zip ' 
    - '/home/ssc/bundles/ Fortify_PCI_Basic_Seed_Bundle-2025_Q2_<build>.zip ' 
    - '/home/ssc/bundles/ Fortify_PCI_SSF_Basic_Seed_Bundle-2025_Q2_<build>.zip ' 
    - '/home/ssc/bundles/ Fortify_Report_Seed_Bundle-2025_Q2_<build>.zip '
   

3. Save the _default_.autoconfig file in the <fortify.home> directory.

4. Place a copy of the fortify.license file in your <fortify.home> folder.

5. Rename the ssc.war file to ROOT.war.

6. Start Tomcat server.

See Also

Automating Application Security configuration