I’m not sure exactly what the nature of your problem is, but I’ll tackle the two possibilities that come to mind, JDBC Pooling and JDBC adapter connections.
JDBC pooling connects the Integration Server to the database. This is not required for out of the box basic functionality. To set up JDBC pooling, I usually create a schema or database in Oracle or SQL 2000 that I call wmsupport. I then create a user that has read/write/execute permissions for the new schema. This is probably where you have the problem, is that you did not configure the new db user with the correct permissions.
If you are having trouble other than user problems, then check the URL. webMethods has a funky way of creating the URL:
jdbc:wm:oracle://ipaddress:port;databaseName=wmsupport
Notice the “wm” in the URL.
For the JDBC adapter connection setting, you need to use the vendor specific URL.
You need to make sure that the database user has the permissions necessary to invoke the type of functionality. For example, if your user can only select, do not expect to insert or update records.
There’s not much more than this. If you are running Oracle, be sure that the TNS Listener is up and running.
Once you have properly configured the connection, then it should work.
As to your specific question, look in the directory ./config/jdbc/pool and you will notice a file named after your pool (like wmsupport.xml).
The password is sha-1 encrypted. Good luck trying to hack.
#Integration-Server-and-ESB#webMethods#Adapters-and-E-Standards