Moving SSC to a New Server

We need to move our instance of SSC to a new VM. The current VM is running Windows Server 2016 and the new one will be running Windows Server 2019. 

The file paths for both instances will be the same as will the version of SSC and Tomcat. 

My question is, how is the best way to move SSC? Can I copy the existing Tomcat directory and move it to the new server? Or should I installed Tomcat on the new server first, then run the SSC Setup Wizard from the new server. 

The database will remain the same, again, this is simply putting the existing application on a new VM, then modifying DNS to point to the new IP address.

Any suggestions or advice for this would be greatly appreciated.


  • Verified Answer

    I think this covers everything! The most important folder is the fortify.home\ssc\conf as it contains the secret.key.

    1. Place the SSC instance in maintenance mode
    2. Stop Tomcat service
    3. Go to <tomcat>/bin and run “service.bat remove”
    4. Create a backup of the SSC database
    5. Verify backup of database
    6. Copy the Tomcat folder to the new server on the same path where it was previously
    7. Copy the fortify.home directory to the new server on the same path where it was previously
    8. Copy the JAVA keystore to the new server
    9. Go to <tomcat>/bin and run “service.bat install”
    10. Configure the Tomcat service to run with the same credentials as on the old machine as this determines where the fortify.home directory is located
    11. Start the Tomcat service
    12. Access SSC application and go through initialization options without seeding database
    13. Restart new SSC server to take out of maintenance mode

    Good luck!

  • Suggested Answer

    @ebell Thanks for this! I appreciate the level of detail!

  • i have similar type of question but in my case, we are planning to setup SSC in production environment. Database, sever everything will be change, but we want to migrate our old data from UAT environment database to production environment database. How we can do that, could you please help me in that.

  • The database is key, so be sure you have a most recent back-up that you can restore/apply to a new database.  You will need to deploy SSC Server fresh in the new environment, including any certificates and plugins you depend on being applied.  Provided the SSC app version is the same, the connection to the database will be just a connection.  Where most users run into trouble is when they simultaneously upgrade the app version, which then requires upgrade scripts for the database connected-to, and may involve additional changes to the system Java/resources/et al.  Also, be certain the network connectivity for the new SSC Server matches that of the old one; do not assume all users will be able to reach it without verifying the network details.