First-time Server Setup
For a first-time installation, perform the following steps in the order shown:
- Install the Database Security Server.
IMPORTANT:
- The class javax.xml.bind.DatatypeConverter was removed in Java 9. If you install a version of Java later than 8, this class is unavailable and migration fails.
- When installing, make sure that you select the HSQLDB option. Do not select the option to migrate the back-end database.
- After you have finished the installation, do not start the Database Security Server.
- If you are not running Database Security Server 4.6.4 or later, install the latest Java Runtime (JRE) 8:
- Download JRE 8 from the Java Downloads site.
NOTE: Make sure that you download the correct version (32-bit or 64-bit) of JRE, for the platform used by the Database Security Server.
If you are installing Database Security Server 4.6.4 or later, you already have an appropriate version of Java and can skip to step 5.
- Add the system path:
See the "How do I set or change the PATH system variable" Java site for full steps.
- Upgrade the Java Virtual Machine (JVM) of the Database Security Server to Java 8.
See KB88438 - How to update the Java Virtual Machine in McAfee Database Security to Java 8.
- Modify the migration script:
NOTE: You only need to perform this step for a Windows installation.
- Go to: /bin/
- Open migration_tool.bat in a text editor of your choice.
- Change:
if exist "%BINPATH%\..\java\jre6\bin" goto local_java_path
to
REM if exist "%BINPATH%\..\java\jre6\bin" goto local_java_path
- If you are not running Database Security Server 4.6.6 or later, upgrade the Microsoft JDBC 4.2 driver for SQL Server to 6.0.
NOTE: If you are installing Database Security Server 4.6.6 or later, you already have an appropriate version of this driver and can skip to step 6.
- Download the driver at Microsoft JDBC Driver 6.0 for SQL Server.
- After the downloaded file has been extracted, you find the following file inside: sqljdbc42.jar.
Copy this file to the /webapps/ROOT/WEB-INF/lib folder.
- Rename the file sqljdbc4-3.0.jar to sqljdbc4-3.0.jar.BAK.
- Migrate the back-end database to the MSSQL 2016 instance by running the migration script, then follow the instructions to migrate the database:
- For Windows run: migration_tool.bat
- For Linux run: migration-tool.sh
- Set the MSSQL 2016 compatibility level to SQL 2014:
- Open a command-line session.
- Log on to the MSSQL 2016 command line.
- Type ALTER DATABASE SNTRSRV SET COMPATIBILITY_LEVEL = 120; and press Enter.
NOTE: For more information about running this command, see this Microsoft article.
- Start the McAfee Database Security Server Service.
Verify the server log files to make sure that no errors occur during connection to the back-end SQL Server.
To upgrade an existing back-end database on MSSQL to MSSQL 2016:
When you upgrade only the back-end database to MSSQL 2016, there is no need for the migration steps.
Instead, perform the following steps:
NOTE: Some steps are described in detail above. If you are running Database Security Server 4.6.6 or later, skip to
step 5.
- Stop the McAfee Database Security service.
- Install the latest Java Runtime 8 (JRE).
- Upgrade the JVM of the Database Security Server to Java 8. See KB88438 - How to update the Java Virtual Machine in McAfee Database Security to Java 8.
- Upgrade the Microsoft JDBC 4.2 driver for SQL Server to 6.0.
- Set the MSSQL 2016 compatibility level to: SQL 2014.
- Update the back-end database connection parameters to match the new database:
- Go to /conf/.
- Open server-custom.properties in a text editor of your choice.
- Edit the server-custom.properties file as in the following example:
database.url=jdbc\:sqlserver\://\:;databaseName\=SNTRSRV
database.user=
database.password=
- Start the McAfee Database Security service.