While I do not have a direct answer for your question, I would like to point out that OCI drivers come with some potential issues. Those are NOT specific to webMethods, but are "part of the deal" when using native (non-Java) libraries with JNI. Another prominent example are SAP JCO libraries that can(!) cause similar problems.
As already mentioned you need an OS-specific driver that has its own dependencies and therefore deployment challenges.
The bigger thing is that such native drivers can completely kill the entire JVM. This cannot be avoided and is a risk you have to live with. You would not even see a single line in any log file or a stack trace. The entire JVM would simply be gone.
I cannot say how probable such a scenario is nowadays. The last time I had to deal with OCI drivers was more than 15 years ago. Also, I have not seen anyone use OCI drivers since then. At the time they supported a few exotic things that were not possible with JDBC and also seemed to have better performance (no idea how much better).
Can you share why you specifically need to use OCI drivers?