JDBC adapter 6.0.2 and Default Schema name for DB2

We are connecting to a DB2 database using JDBC adapter 6.0.2.The problem is we have different schema names for our dev,test and prod envrionment.We have abt 100 adapter services.

We are looking for a way to programatically changing the schema names when we move from dev to test to prod.Is it possible ,if yes how?

we had similar problems in that we had different parameters on our dev, test and prod system. In order to make certain services portable from one system to another we decided to create a “system” package that has the same package/folder/service structure on all three machines where we have simple services (like mappings) that point to the correct parameters. Now when we reference to one of these “system-services” from a normal package it allways points to the same service on the respective machine but since there are different parameters we can solve the problem of deploying a package from dev to test to prod without having to change anything. Of course if you change the “system-package” you have to do it individually on all three systems and not deploy it the normal way. This is thatfar not so nice because you have to “develop” (or at least modify) services directly on the test and prod system. But it solves a lot of other problems.


We have a similar problem. We have a database at each one of our plants that are exactly the same. We want to have the same set of adapter services for all of them. We can not dynamically change the database that we run the adapter services on. In fact, we can not even make a copy of the adapter services and change the connection in developer. I have a feature request in, and webMethods says, that it will be in the next major release of the Adapter Development Kit.

For your problem, if you use the and the on your adapter services, you should be fine. Then your database connection parameters change for each environment, and your adapter services don’t have to. We are using Oracle, and each user has a default schema. I don’t know if this will work for DB2, but it seems that it should.

I have problem connecting to DB2 version 7.x using JDBC adapter 6.0.2. Installed DB Connect on IS box. Added db2java.zip and db2jcc.jar files in IS classpath. Getting this error
“Adapter Runtime (Connection): Unable to enable connection resource db2:db2coonection.
[ART.118.5036] Adapter Runtime (Connection): Unable to configure connection manager.
[ADA.1.204] Cannot connect to the database with DataSource class “COM.ibm.db2.jdbc.DB2DataSource”.
[IBM][JDBC Driver] CLI0615E Error receiving from socket, server is not responding. SQLSTATE=08S01”

Appreciate your help

We have encountered the exact error, we upgraded to adapter 6.03 and using the jar file for the db2 universal driver and were able to connect. You will need to read the ibm site for the maintenance that must be applied to the db2 environment if you are hitting db2 7 on the host