@hmafzal Did you try copying the required jars to packages\WmJDBCAdapter\code\jars\static as well into WmJDBCAdapter\lib? Seems like the error is because of not able to find the required jar/driver. Give it a try. Restart the server after copying the jars.
there should be no need to copy the ojdbc-jar anywhere else than packages\WmJDBCAdapter\code\jars and to reload the package WmJDBCAdapter.
More likely there is a typo in the configuration parameters:
“Other Properties” should be “driverType=thin” instead of just “thin”.
“Network Protocol” can be omitted as only “tcp” is supported.
Please check all fields carefully for leading and trailing blanks and remove these as these are well-known to cause issues during makeUrl-initialization.
Remember that the IS internal DB Pools are using a different driver (DataDirect vs. plain Oracle) with a different protocol prefix. That is the reason why these are working (preconfigured during installation).
For further checking I would like to ask you to share a screen shot of pool “Intigria” as well as to confirm that you really want to connect with User/Schema “Administrator” to your Oracle instance.
If there are still issues please check if replacing “localhost” with a real pc name or ip adress resolves them.
Please keep us updates with the outcome of the above hints.
now we are encountering another error message (no matching auth protocol; this one is sent from the DB) than before (makeUrl; this one was inside the adapter).
Can you check the logs for the ORCL instance of the DB?
Please provide the exact DB version additionally for checking.
As I have never encountered such an error this is getting difficult for me to assist further.