TDM Portal: Unable to run Data Model scan for Sybase database - Missing JDBC drivers or incorrect location

Products

• CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

When attempting to perform a Data Model scan or create a Connection Profile for a Sybase (SAP ASE) database in TDM Portal, the scan fails. Users may see errors in the TDMModelService.log similar to:

• java.lang.ClassNotFoundException: com.sybase.jdbc4.jdbc.SybDriver
• Could not load JDBC driver class [com.sybase.jdbc4.jdbc.SybDriver]

This occurs even if the user has manually added the jconn4.jar to the standard Tomcat library folders.

Environment

Product: CA Test Data Manager (TDM) Component: TDM Portal (Web UI) Version: 4.11 and above

Cause

There are two primary causes for this behavior in TDM Portal 4.11+:

1. Missing Support JARs: The Sybase JDBC driver (jconn4.jar) requires additional encryption and support libraries (cryptoj.jar, jTDS3.jar, etc.) to successfully negotiate metadata queries during a scan.
2. Incorrect Directory: Starting with version 4.x, TDM Portal utilizes a specific subdirectory (\tomcat\jdbc-drivers) for third-party JDBC drivers. Placing JARs in the standard \tomcat\lib folder may result in the driver failing to load or conflicting with the Portal's dynamic loading mechanism.

Resolution

To successfully scan a Sybase database, follow these steps to ensure the correct drivers are present in the correct location:

1. Acquire the Sybase Driver Package: Obtain the following five JAR files from your Sybase/SAP DBA or the SAP Software Download Center:

   • jconn4.jar
   • cryptoj.jar
   • cryptojce.jar
   • cryptojcommon.jar
   • jTDS3.jar

2. Deploy to TDM Portal: Copy all five files into the following directory on the TDM Portal server: C:\Program Files\CA\CA Test Data Manager Portal\tomcat\jdbc-drivers

3. Cleanup: If you previously placed jconn4.jar in C:\Program Files\CA\CA Test Data Manager Portal\tomcat\lib or ...\orientdb\lib, remove them to prevent classloader conflicts.

4. Restart Services: Restart the CA Test Data Manager Portal service from the Windows Services console.

5. Validation:

   • Log into the TDM Portal.
   • Go to Configuration > Connection Profiles.
   • Ensure the DBMS type is set to Sybase (JDBC 4.0).
   • Re-run the Data Model Scan.