net.agmodel.metDriver
Class Amedas

java.lang.Object
  net.agmodel.dbUtility.InternetHost
      net.agmodel.dbUtility.JDBC
          net.agmodel.dbUtility.JDBCOracle
              net.agmodel.metDriver.Amedas

All Implemented Interfaces:

AccessMechanism, DBAccessMechanism, MetAccessMechanism

public class Amedas

extends JDBCOracle

implements MetAccessMechanism

Provides access to MAFF's AMeDAS database via a CGI script on MAFF's web server

Author:

Matthew Laurenson

Constructor Summary

Amedas(MetSourceForDrivers metSource, Properties properties)

Method Summary

boolean	connectForData(String username, String password) Called before data is retrieved from the AccessMechanism
TimeZone	getDatabaseTimeZone()
void	queryForStation(MetRequest request, String stationID, StationDataSetImpl result) Retrieve the relevant data from a single station.
void	updateRegionList() Update the list of regions (if any) held by the MetSource
void	updateStationList(String fromStation) Update the list of stations held by the MetSource

Methods inherited from class net.agmodel.dbUtility.JDBC

checkForDatabaseUpdates, connect, connectForMetaData, disconnectFromData, disconnectFromMetaData, getConn

Methods inherited from class net.agmodel.dbUtility.InternetHost

getHost, getPort

Methods inherited from class java.lang.Object

equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface net.agmodel.brokerImpl.DBAccessMechanism

checkForDatabaseUpdates, connectForMetaData, disconnectFromData, disconnectFromMetaData

Constructor Detail

Amedas

public Amedas(MetSourceForDrivers metSource,
              Properties properties)

Method Detail

getDatabaseTimeZone

public TimeZone getDatabaseTimeZone()

Specified by:

getDatabaseTimeZone in interface MetAccessMechanism

connectForData

public boolean connectForData(String username,
                              String password)
                       throws ConnectionException

Description copied from interface: DBAccessMechanism

Called before data is retrieved from the AccessMechanism

Specified by:

connectForData in interface DBAccessMechanism

Overrides:

connectForData in class JDBC

Throws:

ConnectionException

queryForStation

public void queryForStation(MetRequest request,
                            String stationID,
                            StationDataSetImpl result)
                     throws ConnectionException

Description copied from interface: MetAccessMechanism

Retrieve the relevant data from a single station.

Specified by:

queryForStation in interface MetAccessMechanism

Parameters:

request - describes what data is required

stationID - identifies which station from the met data source to query

result - the skeletal query result (created by MetSourceImpl) for the driver fill in with data hostID is the native identifier for the station on the host database system.
If the request is a StationMetRequest, then the hostID will also be embedded in the request but should be ignored by this method. If there is no data at all for the station, this method should return the skeletal query result untouched. If there is no data for a particular element, then no corresponding sequence should be inserted into the StationDataSetImpl.

Throws:

ConnectionException

updateRegionList

public void updateRegionList()
                      throws GeneralException

Description copied from interface: MetAccessMechanism

Update the list of regions (if any) held by the MetSource

Specified by:

updateRegionList in interface MetAccessMechanism

Throws:

GeneralException

updateStationList

public void updateStationList(String fromStation)
                       throws GeneralException

Description copied from interface: MetAccessMechanism

Update the list of stations held by the MetSource

Specified by:

updateStationList in interface MetAccessMechanism

Parameters:

fromStation - start the update from this station (the driver may ignore this value and update all stations) The fromStation parameter is intended to help with large databases where, particularly during driver development, the updating process may fail midway through. It avoids the need to start again from the beginning. Drivers are welcome to entirely ignore this parameter. A null parameter value indicates that updating should start from the beginning.

Throws:

GeneralException