|Applies To||RSA Product Set: RSA Identity Governance & Lifecycle |
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
Platform/Application Server: WildFly
|Issue||The jTDS JDBC driver is a third party JDBC driver that can be used in place of the default JDBC driver for connections to SQL databases. Specifically this driver is often used for connections to Microsoft SQL server if Windows authentication is required to establish the connection (as this is not supported by the native driver). Due to licensing restrictions, RSA is unable to provide the jTDS driver with the product but it can be sourced from the internet. |
This RSA Knowledge Base Article explains the steps to installing the jTDS driver on an RSA Identity Governance & Lifecycle 7.x WildFly appliance. In the case of a clustered configuration, the steps, at a high level, are the same, the difference being the .ear file needs to be deployed on each node of the cluster. Steps to do this are documented in the RSA Identity Governance and Lifecycle Installation Guide for your version.
|Resolution||To install the jTDS 1.3.x driver on WildFly, use the customizeACM.sh utility to add the jTDS driver to the aveksa.ear file and restart RSA Identity Governance & Lifecycle.|
For detailed steps on using the customizeACM.sh utility, please see RSA Knowledge Base Article 000038700 -- How to customize the application using customizeACM.sh in RSA Identity Governance & Lifecycle.
Place the new driver in the lib directory indicated below and remove the existing driver. Execute these commands as the oracle user.
As the oracle user:
|Notes||Please note that installing the jTDS JDBC driver is an example. You may use this approach for including any custom/external JDBC driver.|
This RSA Knowledge Base Article covers installing the jTDS driver for use with data collections. To use the jTDS driver with AFX, see RSA Knowledge Base Article 000029641 -- How to install the jTDS JDBC driver for use with AFX in RSA Identity Governance & Lifecycle.
To install the jTDS 1.2.x driver on RSA Identity Governance & Lifecycle versions 6.9.1 and below, Place the new driver in the lib folder and remove the existing driver. Execute these commands as the oracle user.