Sunday, November 29, 2009

Exception: [MERANT][SequeLink JDBC Driver][SequeLink Server]License verification failed. JDBC database connection DriverManager.getConnection()

Exception: [MERANT][SequeLink JDBC Driver][SequeLink Server]License verification failed.

Sometimes query with database using DriverManager.getConnection() will cause the following error message

Exception: [MERANT][SequeLink JDBC Driver][SequeLink Server]License verification failed.

There is no problem if the application uses WebSphere's DataSource.

Solution
The SequeLink Java Client is branded and shipped with WebSphere Application Server 3.5.3+, 4.0.x and 5.0.x (sljc.jar and sljcx.jar which are in $WAS_HOME\lib directory where $WAS_HOME is the directory where WebSphere Application Server is installed). The branded SequeLink Java Client provides an encrypted OEM password which unlocks the SequeLink OEM Server.

The branded SequeLink Java Client can be unlocked by JDBC applications that call a special method, which is defined in the com.merant.SlExtensionInterface interface. If you fail to unlock the branded SequeLink Java Client, or if another unauthorized application tries to use the branded SequeLink Java Client, the above exception is generated.

If the application uses the DriverManager.getConnection() method, then it must call that special method to unlock the SequeLink OEM Server by itself. As a SequeLink OEM, IBM WebSphere can't give out the OEM password to customers.. If you really want to use the DriverManager.getConnection() method to obtain the database connection, then you must buy the license copy of the SequeLink Server from MERANT.

When you use WebSphere's DataSource, the Connection Manager calls that special method to unlock the SequeLink OEM Server.

Note: In 2001, DataDirect business unit spins off from MERANT to form privately-held, independent software vendor, called DataDirect Technologies.

No comments:

Post a Comment