webMethods

 View Only

 After myWebmethods fix ugrade, "This driver is locked for use with embedded applications"

Renan Kaic Lopes's profile image
Renan Kaic Lopes posted Mon May 12, 2025 07:45 AM

Hello. 

We successfully upgraded our I.S 10.3 to fix 31 on our DEV enviroment.

Our I.S is running fine and it's doing its job

We also had to upgrade myWebmethods server with the latest fix.

However, after upgrading myWebmethods, we started receiving the following exception in our logs:

My webMethods Server 10.3.0.0002-0260My webMethods Server 10.3.0.0002-0260My webMethods Server 10.3.0.0002-0260My webMethods Server 10.3.0.0002-0260My webMethods Server 10.3.0.0002-0260My webMethods Server 10.3.0.0002-02602025-05-11 12:41:35 GMT-03:00 [CommonLib.MWS.0010I] Initializing MWSLibrary
2025-05-11 12:41:35 GMT-03:00 [CommonLib.MWS.0012I] Loading configuration from the MWS database using connection system properties
2025-05-11 12:41:35 GMT-03:00 [CommonLib.MWS.0001E] [SoftwareAG][Oracle JDBC Driver]This driver is locked for use with embedded applications.
java.sql.SQLException: [SoftwareAG][Oracle JDBC Driver]This driver is locked for use with embedded applications.
        at com.wm.dd.jdbc.oraclebase.BaseExceptions.b(BaseExceptions.java:1106)
        at com.wm.dd.jdbc.oraclebase.BaseExceptions.a(BaseExceptions.java:977)
        at com.wm.dd.jdbc.oraclebase.BaseExceptions.a(BaseExceptions.java:1115)
        at com.wm.dd.jdbc.oraclebase.BaseExceptions.aw(BaseExceptions.java:658)
        at com.wm.dd.jdbc.oraclebase.BaseConnection.createStatement(BaseConnection.java:2203)
        at com.wm.dd.jdbc.oraclebase.BaseConnection.createStatement(BaseConnection.java:2171)
        at com.webmethods.sc.mws.MWSLibrary.init(MWSLibrary.java:214)
        at com.wm.app.b2b.server.cds.CDSUserManager.initialize(CDSUserManager.java:188)
        at com.wm.app.b2b.server.UserManager.jndiInit(UserManager.java:594)
        at com.wm.app.b2b.server.UserManager.init(UserManager.java:523)
        at com.wm.app.b2b.server.Server.run(Server.java:665)
2025-05-11 12:41:35 GMT-03:00 [CommonLib.MWS.0016I] com.webmethods.sc.mws.clusterId: null
2025-05-11 12:41:35 GMT-03:00 [CommonLib.MWS.0016I] com.webmethods.sc.mws.jndiProviderUrl: null
2025-05-11 12:41:35 GMT-03:00 [CommonLib.MWS.0016I] com.webmethods.sc.mws.frontEndUrl: null

I've tried to created a new Driver Alias to use with it:

Unfortunately, it didn't solve the problem.

Please, could you let me know what should I do to fix this issue?

Should I use an specific Oracle JDBC driver?

Holger von Thomsen's profile image
Holger von Thomsen posted Mon May 12, 2025 11:59 AM

Hi Renan,

usually MWS should be able to use the branded DataDirect Driver bundled with the wM Suite.
Same applies to the MWS and CentralUsers functions under the JDBC Pools section of IS Admin.
Make sure, that you use the URL format starting with "jdbc:wm:oracle://" for your Oracle database connection.

Please note, that the DB connection used by the MWS itself is not configured via IS Admin, but in a file called "MWS/server/default/config/mws.db.xml".

Additionally check, if you have applied latest Fix for DataDirect driver along with your update. There might be a compatibility issue, when not all components are on the latest fix level available.

As 10.3 sounds fairly old, you should consider upgrading to 10.15 (last version provided by SAG, before IBM took over the wM Suite).

Regards,
Holger

Related Content