Transactions with OAS

Hi,

    We have to develop a multi-tier application using EJBs and we intend to use the OAS as our ORB. We will have one Oracle 8.1.5 database to keep all the data and an OAS 4.0.8 running on the same machine (Windows NT).

    I've been playing with the OAS, especially with transactions, for a while and I found out (thanks to Yoshio Lyo Hisamichi) that to use a DTC (used for distributed transactions), we have to use an Oracle 8.0.5 database. Does this mean we have to purchase an OAS, an Oracle 8.1.5 and an Oracle 8.0.5? If so, since everything will probably be installed on the same machine, won't it load the machine unnessarily? How hard will this kind of environment be to manage?

    According to the context specified above (one database and EJBs), would I need to use a JTS anyway? Will JDBC transactions be sufficient for my purpose? Using JDBC, can a transaction span over multiple method calls like when using the JTS? For example, call ejb1.method1() and start a transaction there, then call ejb1.method2() and continue the processing, and, finally, call ejb1.method3() to commit/rollback the transaction. Does this scenario can cause problems assuming that the ejb1 object keeps a reference to the JDBC connection between calls? According to the OAS documentation, this scenario is not supported, but I tested it and it seems to work.

    Finally, I read in the release notes that the JDBC driver shipped with the OAS 4.0.8 is 8.0.5.2. Can this driver be used without problems with a 8.1.5 database?

    Any comments/thoughts/opinions regarding this will be welcome.

    Thanks a lot in advance.

Ghislain Gadbois, Senior Programmer
Sisca inc.

Tel.: 1-819-564-1199, ext. 2225
E-Mail: Ghislain.Gadbois_at_sisca.com
Internet: http://www.sisca.com Received on Fri Mar 31 2000 - 08:36:33 CST