Configuring Application Security after an upgrade
After you upgrade Application Security and enter your Application Security web address in a browser window, the Setup wizard opens. Use the Setup wizard to perform the database data migration and reseed the database.
The Setup wizard is available to Administrators only, and only after the first deployment of Application Security, after an upgrade, or after the server is placed in maintenance mode (see Placing Application Security in maintenance mode).
- Open the
<fortify.home>/<app_context>/init.tokenfile in a text editor. - Copy the contents of the
init.tokenfile to the clipboard. -
Open a web browser and type your Application Security server URL.
-
Click ADMINISTRATORS.
-
In the Setup wizard sign in, paste the string you copied from the
init.tokenfile into the Security Token field, and then click SIGN IN. -
If you need to change any configuration settings on the CONFIGURATION or CORE CONFIGURATION SETTINGS pages, you can do so using the instructions provided in Configuring Application Security for the first time.
- Click NEXT until you reach the DATABASE SETUP page.
-
On the DATABASE SETUP page, do the following:
-
In the DATABASE TYPE box, select the type that matches the Application Security database type.
-
In the DATABASE USERNAME box, type the username for your Application Security database.
For more information, see Database user account permissions.
- In the DATABASE PASSWORD box, type the password for your Application Security database.
-
In the JDBC URL box, type the URL for the Application Security database.
The database name (including letter case) in the JDBC URL must exactly match your Application Security database name.
The MariaDB JDBC driver connects to the MySQL database server. Any JDBC URL parameters must use MariaDB driver syntax. Example of the correct collation parameter syntax:
jdbc:mysql://<host>:3306/<database_name>?sessionVariables=collation_connection=<collation_name>
Replace the parameter
connectionCollation=<collation_name>withsessionVariables=collation_connection=<collation_name>. -
To test the connection to your database, click TEST CONNECTION.
If the connection test fails, check the
<fortify.home>/<app_context>/logs/ssc.logfile to troubleshoot the cause. -
After the Setup wizard indicates that the connection was successful, read the warning and instructions, and then click DOWNLOAD SCRIPT.
-
Save and run the
ssc-migration.sqlscript.For instructions, see About the Application Security database tables and schema.
Depending on the size of the source database, data migration might take several hours to complete.
-
- After you run the
ssc-migration.sqlscript, click NEXT. -
On the DATABASE SEEDING page, do the following:
- Click BROWSE to locate and select your process seed bundle ZIP file, and then click SEED DATABASE.
- Click BROWSE to locate and select your report seed bundle ZIP file, and then click SEED DATABASE.
- (Optional) Click BROWSE to locate and select your PCI SSF seed bundle ZIP file, and then click SEED DATABASE.
- (Optional) Click BROWSE to locate and select your PCI basic seed bundle ZIP file, and then click SEED DATABASE.
- Click NEXT.
- Click FINISH.
-
Restart Tomcat server.
If you later find that you need to change any of the configuration settings, you can place Application Security in maintenance mode, and then make any necessary changes. For instructions on how to place Application Security in maintenance mode, see Placing Application Security in maintenance mode.