|Applies To||RSA Product Set: RSA Identity Governance & Lifecycle|
RSA Version/Condition: 7.0.0 +
|Issue||With the switch from JBoss to WildFly for RSA Identity Governance & Lifecycle 7.0.0, significant changes were made to the filesystem within /home/oracle. Because of these changes, the process for installing the jTDS JDBC driver (used for Windows authentication against a SQL Server database) has changed. |
This document outlines how to install the jTDS driver on an RSA Identity Governance & Lifecycle 7.0 non-clustered appliance/soft 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 Installation Guide for each RSA Identity Governance & Lifecycle version 7.0 and above.
Therefore this article assumes the customer is using a standalone soft/hard appliance
1. Installation Method
In JBoss 4, all that was necessary to install the jTDS driver was to place the jtds.jar file in an appropriate folder, and restart the server.
In WildFly, the strategy is a bit different. Now the process is to add the driver to the .ear file which requires customizing the .ear file. Steps to do this are documented in the Installation Guide for each RSA Identity Governance & Lifecycle version 7.0 and above.
2. Customize the .ear File
Use the following commands to add the driver to the .ear file:
|Notes||Please note that installing the jTDS JDBC driver is an example. You may use this approach for including any custom/external JDBC driver.|
To get this driver working with AFX, please refer to article 000029641 - How to install the third party jTDS database driver using RSA Identity Governance & Lifecycle Access Fulfillment Express (AFX).