MWS setting for Oracle wallet issue

, ,
1

in our webMethods project we have configured Oracle Wallet , OS is Linux. which is working fine alone.
The wallet setting looks like:
:/…/…/…/data/oracle/network/admin> cat tnsnames.ora
#############################################

TNS Entry for connect_string

#############################################

B2BBD_LSL = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCPS) (HOST = DBHOST) (PORT = XXXX) ) ) (CONNECT_DATA = (SERVICE_NAME = SID) )

Next we need to use that same wallet Alias inside mws.db.xml
we are trying to set the url as : jdbc:oracle:thin:/@B2BBD_LSL but its not working

getting below error while running the ./mws.sh getconfig cluster.xml

:/…/…/…/…/mws105/MWS/bin> ./mws.sh getconfig cluster.xml
JAVA_HOME: /…/…/…/…/mws105/jvm/jvm
MWS_HOME: /…/…/…/…/mws105/MWS
Connecting to MWS database…
ERROR
java.sql.SQLException: Unable to create connection to jdbc:oracle:thin:@B2BBD_LSL
at com.webMethods.portal.service.sql.core.BaseSqlWorker.init(BaseSqlWorker.java:156)
at com.webMethods.portal.service.sql.core.ConnectionManager.validateDatasource(ConnectionManager.java:732)
at com.webMethods.portal.service.sql.core.ConnectionManager.init(ConnectionManager.java:355)
at com.webMethods.portal.service.sql.core.ConnectionManager.init(ConnectionManager.java:277)
at com.webMethods.portal.system.config.ConfigManager.(ConfigManager.java:109)
at com.webMethods.portal.system.config.ConfigManager.main(ConfigManager.java:46)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.webMethods.portal.system.start.Main.start(Main.java:155)
at com.webMethods.portal.system.start.Main.main(Main.java:38)

the mws.db.xml looks like:

<?xml version="1.0" encoding="UTF-8" standalone="no"?> 
<CONNECTION default="true" displayname="Default" id="1" name="default" type="oracle">
    <SQLWORKERCLASS>com.webmethods.portal.service.sql.core.BaseSqlWorker</SQLWORKERCLASS>
    <CONNPROVIDERCLASS>com.webmethods.portal.service.sql.core.provider.pool.PooledConnectionProvider</CONNPROVIDERCLASS>
    <PARAMS>
        <DRIVER>com.wm.dd.jdbc.oracle.OracleDriver</DRIVER>
        <URL>jdbc:oracle:thin:/@B2BBD_LSL</URL>
        <USER>XXXX_MWS_OWNER</USER>
		<!-- Password could be specified in clear text, it will be automatically encrypted during MWS startup -->
        <PASSWORD>XXXXXXXXXXXXXXXX</PASSWORD> 
        <CACHESTATEMENTS>false</CACHESTATEMENTS>
        <TESTSQL>SELECT COUNT(*) FROM TBLTHING WHERE IDTHING = 1</TESTSQL>            
        <MAXCONNECTIONS>100</MAXCONNECTIONS>
        <MINCONNECTIONS>0</MINCONNECTIONS>
        <!-- Max amount of idle time (in seconds) of the objects pooled by this pool -->
        <IDLETIMEOUT>60</IDLETIMEOUT>
        <!-- Time (in seconds) between eviction runs -->
        <CLEANUPPERIOD>10</CLEANUPPERIOD>
    </PARAMS>
</CONNECTION>

need to how how to set the URL in mws DB config for oracle wallet?

2

Hi Avik,

first of all I notice a mismatch between selected driver and URL in your mws.db.xml.
The bundled DataDirect Driver mentioned in the config uses a different URL-prefix and I am not sure if this one knows about wallet configuration.

You will have to place the ojdbc8.jar under MWS/lib/ext directory and perform an update on the MWS with the following command:
in MWS/bin:
./mws.sh -s default update
This will update the class path in the startup.jar of MWS so it can load the Oracle Driver additionally to the DataDirect Driver.

Regards,
Holger

3

we have already ojdbc8.jar installed. just need to know how the URL we should specify & which driver should be used for wallet ?

4

As we never used wallet configuration with our oracle databases I can no longer assist here.
When opening the ojdbc8.jar with a tool which can hanled ZIP files you can browse the content and you will find an oracle.jdbc.driver.OracleDriver class in it.
Put this in the proper field of the mws.db.xml.

Regards,
Holger

5

This topic was automatically closed after 1083 days. New replies are no longer allowed.