Configuration template for the oracle-ds.xml in JBoss.

<? XML version = "1.0" encoding = "UTF-8"?> </P> <p> <! -- ===================================================== ======================================= --> <Br/> <! --> <Br/> <! -- JBoss server configuration --> <br/> <! --> <Br/> <! -- ===================================================== ========================================= --> </P> <p> <! -- See http://www.jboss.org/community/wiki/Multiple1PC for information about local-TX-datasource --> <br/> <! -- $ ID: oracle-ds.xml 88948 14: 09: 08z Jesper. Pedersen $ --> <br/> <! -- ===================================================== ============================================>< Br/> <! -- Datasource config for Oracle originally from Steven coy --> <br/> <! -- ===================================================== =========================================--> </P> <p> <CES> <br/> <local-TX-datasource> <br/> <JNDI-Name> oracleds </JNDI-Name> <br/> <connection-URL> JDBC: ORACLE: thin: @ 10.28.10.37: 1521: orcl </connection-URL> <br/> <! -- </P> <p> here are a couple of the possible OCI configurations. <br/> For more information, see http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/java.920/a96654/toc.htm </P> <p> <connection-URL> JDBC: oracle: OCI: @ youroracle-TNS-name </connection-URL> <br/> or <br/> <connection-URL> JDBC: oracle: OCI: @ (description = (address = (host = youroraclehost) (Protocol = TCP) (Port = 1521) (CONNECT_DATA = (service_nam E = yourservicename) </connection-URL> </P> <p> clearly, its better to have TNS set up properly. <br/> --> <br/> <driver-class> oracle. JDBC. driver. oracledriver </driver-class> <br/> <user-Name> hadiantest </user-Name> <br/> <password> hadiantest </password> <br/> <! -- Uses the pingdatabase method to check a connection is still valid before handing it out from the pool --> <br/> <! -- Valid-connection-checker-class-Name> Org. JBoss. resource. adapter. JDBC. vendor. oraclevalidconnectionchecker </valid-connection-checker-class-name --> <br/> <! -- Checks the Oracle error codes and messages for fatal errors --> <br/> <exception-sorter-class-Name> Org. JBoss. resource. adapter. JDBC. vendor. oracleexceptionsorter </exception-sorter-class-Name> <br/> <! -- SQL to call when connection is created <br/> <New-connection-SQL> some arbitrary SQL </new-connection-SQL> <br/> --> </P> <p> <! -- SQL to call on an existing pooled connection when it is obtained from pool-The oraclevalidconnectionchecker is prefered <br/> <check-valid-connection-SQL> some arbitrary SQL </check- valid-connection-SQL> <br/> --> </P> <p> <! -- Corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) --> <br/> <metadata> <br/> <type-mapping> Oracle9i </type-mapping> <br/> <min-pool-size> 5 </min -Pool-size> <br/> <max-pool-size> 10 </max-pool-size> <br/> <idle-timeout-minutes> 1 </idle -Timeout-minutes> <br/> <track-statements/> <br/> <prepared-statement-Cache-size> 32 </Prepared-statement-Cache-size> <br/> <check-valid-connection-SQL> select 1 from dual </check-valid-connection-SQL> <br/> <New-connection-SQL> select 1 from dual </new-connection-SQL> <br/> <exception-sorter-class-Name> Org. JBoss. resource. adapter. JDBC. vendor. oracleexceptionsorter </exception-sorter-class-Name> <br/> <valid-connection-checker-class-Name> Org. JBoss. resource. adapter. JDBC. vendor. oraclevalidconnectionchecker </valid-connection-checker-class-Name> <br/> </metadata> <br/> </Local-TX-datasource> </P> <p> </datasources> <br/>