Process invalid driver name after upgrade to 16.0.3+

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

After upgrade to 16.0.3, some of our custom processes fail with error

BPM-0704: An error occurred while executing custom script:
org.apache.commons.jelly.JellyTagException: null:41:164: <sql:setDataSource> In &lt;driver&gt;,

invalid driver class name: "com.ca.clarity.jdbc.oracle.OracleDriver"

• at org.apache.commons.jelly.tags.sql.SetDataSourceTag.doTag(SetDataSourceTag.java:116)
• at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:248)
• at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
• at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187)
• at com.niku.union.gel.tags.ScriptTag.doTag(ScriptTag.java:20) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:248)
• at com.niku.union.gel.GELScript.run(GELScript.java:58)
• at com.niku.union.gel.GELController.invoke(GELController.java:79)
• at com.niku.bpm.services.ExecuteCustomAction.run(ExecuteCustomAction.java:217)
• at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
• at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
• at java.base/java.lang.Thread.run(Thread.java:829)

Environment

Release : 16.0.2+

Cause

DataDirect driver was replaced with Oracle native driver

Resolution

1. In the GEL script, replace:

com.ca.clarity.jdbc.oracle.OracleDriver with oracle.jdbc.driver.OracleDriver

2. Save and Validate, then test your process