THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Minor corrections by Pawel H Debski and Les Austin
Table of Contents |
---|
Related Documents
...
Sub-Element Name | How Many | Description |
---|---|---|
sql-load-path | 0 to many | Used to specify a list of full paths to directories that will be searched for XML and SQL files to import into the data source by the install page in the WebTools webapp. Each tag has two attributes: path for the path location, and prepend-env to optionally specify a Java environment property to prepend to the specified path. |
inline-jdbc | 0 or 1 | Used to specify the JDBC parameters to be used either by the connection pool or if no connection pool is available then by directly loading the driver (very slow). You must specify either inline-jdbc or jndi-jdbc, but not both, for the datasource. |
jndi-jdbc | 0 or 1 | Used to specify the jndi-server and jndi-name to get a Connection or XAConnection from JNDI. You must specify either inline-jdbc or jndi-jdbc, but not both, for the datasource. |
ANY | 0 or 1 | Any tag may go inside the datasource tag to specify parameters for other GenericHelper implementations. These will not be checked at load time unless the DTD is modified to describe them. |
The inline-jdbc
tag has the following attributes:
Attribute Name | Required? | Description |
---|---|---|
jdbc-driver | Y | The JDBC driver class for the database. |
jdbc-uri | Y | The URI used to specify the type and location of the database. |
jdbc-username | Y | The username to connect to the database as. |
jdbc-password | Y | The username's password. |
isolation-level | N | This is used by Tyrex to specify the transaction isolation level. The standard JDBC transaction isolation levels are available:
|
The jndi-jdbc
tag has the following attributes:
...