N.B. After modifying the file in your $LAS_HOME you can make the new configuration available to your running server using the "ant deploy" command in $LAS_HOME. The LAS database service accesses data stored in a Relational Database Management System (RDBMS) and creates intermediate NetCDF files for potential downstream use by the another service -- typically the 'ferret' service. The database service uses JDBC drivers to communicate with the RDBMS.
The following file is used to configure the database service:
$LAS_HOME/JavaSource/resources/database/DatabaseBackendConfig.xml
If you configured your LAS to set up the sample in-situ datasets this file should contain:
<databases>
<database name="LAS_insitu_demo"
driver="com.mysql.jdbc.Driver"
connectionURL="mysql://your.domain.name:3306/LAS_insitu_demo?autoReconnect=true"
user="las" password="lasrules"/>
</databases>
The <databases> XML element contains a list of <database .../> tags that describe how the 'database' service can connect to the approprite RDBMS associated with an LAS dataset.
To add your own database to LAS you must add another <database .../> tag to this file that describes access to your RDBMS.
The attributes of the <database .../> tag are:
- name
- matches the value of the <db_name> tag in the dataset configuration file (see Creating the dataset configuration file)
- driver
- database dependent JDBC driver to use. Available choices include:
- com.mysql.jdbc.Driver
- oracle.jdbc.driver.OracleDriver (Available from Oracle)
- connectionURL
- fully qualified URL for remote access to your RDBMS
- user
- RDBMS user ID with permission to view tables in the specified database
- password
- password for user