Upgrade tasks
Upgrade to a new version of Application Security by performing the tasks described in the following table in the order listed.
| Task | Description |
|---|---|
| 1 | Stop Tomcat server. |
| 2 |
Delete the WAR file from the <tomcat> represents the root directory of the Tomcat instance. |
| 3 | Start Tomcat server. |
| 4 |
Open a browser and enter your Application Security web address to start the Setup wizard. |
| 5 | Use the Setup wizard to generate the migration SQL script (see Configuring Application Security after an upgrade). |
| 6 |
Run the migration script on your database (see Preparing to run the database upgrade script). Databases that contain over 1 TB of data might take five or more hours to migrate. (SQL Server databases only) After you migrate Application Security to a new SQL Server database version and back up and restore the database, you must change the compatibility level (from SQL Server Management Studio) to reflect the SQL engine version that currently hosts the Application Security database. |
| 7 | Use the Setup wizard to reseed the database. |
| 8 | Restart Tomcat server. |
| 9 |
Bug tracker plugins are not included in the |