Kettle Transformation attributes not being detected after Import / Driver could not be found errors

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Identity Suite

Issue/Introduction

The custom attributes from the roles are not being detected when we launch the campaign.  The roles have the custom attributes which are imported using a Role Enrichment PDI Kettle transformation which appeared to be successful. However, when I launch a campaign to used one of the role attribute, I get a message that there are no certifications to launch.

Environment

Release : 14.3

Component : GovernanceMinder(Role & Compliance Manager)

Cause

Issue was due to the Spoon.bat/sh app not having a JDBC driver, which we can see in the eurekify.log file:

09:18:26,487 INFO  [stdout] (Thread-513) [EXEC]: 2020/06/26 09:18:26 - Table input.0 - Error occurred while trying to connect to the database
09:18:26,487 INFO  [stdout] (Thread-513) [EXEC]: 2020/06/26 09:18:26 - Table input.0 - 
09:18:26,487 INFO  [stdout] (Thread-513) [EXEC]: 2020/06/26 09:18:26 - Table input.0 - Driver class 'net.sourceforge.jtds.jdbc.Driver' could not be found, make sure the 'MS SQL Server' driver (jar file) is installed.
09:18:26,487 INFO  [stdout] (Thread-513) [EXEC]: 2020/06/26 09:18:26 - Table input.0 - net.sourceforge.jtds.jdbc.Driver
09:18:26,503 INFO  [stdout] (Thread-513) [EXEC]: 2020/06/26 09:18:26 - Table input.0 - ERROR (version 7.1.0.0-12, build 1 from 2017-05-16 17.18.02 by buildguy) : Error initializing step [Table input]
09:18:27,206 INFO  [stdout] (Thread-513) [EXEC]: 2020/06/26 09:18:27 - Role_enrichment - ERROR (version 7.1.0.0-12, build 1 from 2017-05-16 17.18.02 by buildguy) : Step [Table input.0] failed to initialize!

And directly in Spoon:

Resolution

This issue was solved by copying the driver sqljdbc.jar into "C:\Program Files\CA\RCM\Server\data-integration\lib".
The driver was gathered from Microsoft's website "https://docs.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver15#62".

After supplying the JDBC driver and restarting the PDI everything worked as expected.