Roger, I think I figured out why. The 2 JDBC Adapter services use 2 different JDBC Connections (one to AS400, one to SQL Server), and both JDBC connections have “LOCAL_TRANSACTION” as TRANSACTION TYPE. The error message of “more than 1 local trans enlisted” makes me think only 1 “LOCAL_TRANSACTION” is allowed somehow. So I made one of the JDBC connection “NO_TRANSACTION” for my SelectSQL adapter service, and keep everything else the same. It works like a charm!
This solution, though works, may not be the best solution. What if I do need both JDBC connection to be "“LOCAL_TRANSACTION”? Maybe I will have to use pub.db services instead of JDBC Adapters.
BTW, I am using wM 6.1, and I did not find pub.art.transaction. They maybe available in earlier versions of wM. But I do have pub.db services which is equivalent.
If I understand correctly, you suggest I use “pub.db:” flow services instead of JDBC adapters. I am sure that will work also, but JDBC adapter is another alternative I would like to use.
Thanks
Jin
#Integration-Server-and-ESB#webMethods#Adapters-and-E-Standards