"Current Setup: External Reference via tomcat9w.exe (Classpath Entries)
How it works: Adding a JAR to tomcat9w.exe’s Java Options/Classpath entries places it on Tomcat’s common or shared classpath. This allows the JDBC driver JAR to be loaded by a parent classloader, making it available to all deployed web applications, including IdentityIQ.
Recommendation: Proceed with the first option, using the current tomcat/bin path.
Pros:
- Centralized management: Only one driver copy is needed for all applications.
- Best practice: Given your existing external reference and general best practices for JDBC drivers in Tomcat, maintaining this approach is the most stable path forward. This aligns with the benefits of centralized management and memory leak prevention inherent in placing JDBC drivers on Tomcat’s shared classpath. IdentityIQ, being a single application on this Tomcat instance, benefits from its database driver being managed by Tomcat’s common classloader, which is a robust approach for stability.
Action: Replace the existing .jar in that external directory with mssql-jdbc-12.10.0.jre11.jar and update the path accordingly."