...
- pom.xml (For Microsoft SQL only)
JDBC driver for SSP-Platform if not using PostgreSQL
Warning The pom.xml should only be changed with extreme care. The Microsoft SQL Server jdbc driver needs to be identified in the build. The parameter defines the location of the driver in the local repository.
- File Location:
<platform-src-dir>/pom.xml Configuration Values: parameters
Action: modify the
jdbc.*parameters to refer to the JTDS driver instead of the PostgreSQL driver:Code Block title JDBC driver identified in the pom.xml <!-- The JDBC Driver used by SSP --> <jdbc.groupId>net.sourceforge.jtds</jdbc.groupId> <jdbc.artifactId>jtds</jdbc.artifactId> <jdbc.version>1.2.4</jdbc.version>
- local.properties
- The local.properties file must be modifed for database connectivity and email settings
- File Location: <platform-src-dir>/filters/local.properties
Configuration Values:
Value Description environment.build.hibernate.connection.driver_class jdbc driver file
For best results with SQL Server, the JTDS driver included with the Platform installation is recommended.
environment.build.hibernate.connection.url jdbc connection syntax
For best results with SQL Server, the JTDS driver included with the Platform installation is recommended.
environment.build.hibernate.connection.username jdbc connection database username environment.build.hibernate.connection.password jdbc connection database password environment.build.hibernate.dialect jdbc connection dialect
For best results with SQL Server, the JTDS driver included with the Platform installation is recommended.
4. Build SSP-Platform
- Use the following command to build, deploy, and initialize the SSP-Platform project:
...