##### Page tree
Go to start of banner

# FewsDatabase Import

Overview

TimeSeries reader for a FEWS Master Controller database. The identifier for this reader is "Fewsdatabase". This import allows a FSS or stand alone system to import data from another FEWS master controller database. The import reads the database directly and does NOT communicate with the MC. The following limitations apply:

1. It can only handle external historical and external forecasting data
2. It does not use the timestep as a key. As such the behavior is undefined if the remote database has the same series (location/parameter) with different timesteps.
3. It does not use the moduleInstanceId as a key.
4. The relativeViewPeriod element in the general section is required although the schema (see below) indicates it is optional.

## Configuration

The schema extension of the import module is shown below:

An example configuration file is attached to this page. This file imports one timeseries from the eami00 database on the fewdbsvr04 server; the figure below shows this file in XML-SPY grid format:

### Time series sets, location set id, or location id's

For this import there must be either time series sets, a location set id or location id's configured:

```	<import>
<general>
<importType>Fewsdatabase</importType>
<folder>$IMPORT_FOLDER$/fewsldb</folder>
<deleteImportedFiles>false</deleteImportedFiles>
<idMapId>IdImportCAWFirebird</idMapId>
<dataFeedId>CAW</dataFeedId>
</general>
<timeSeriesSet>
<moduleInstanceId>ImportCAW_AQUO</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>Q.meting.sec</parameterId>
<locationId>62079_Actuele_debiet_aflaat</locationId>
<locationId>62079_Actuele_debiet_inlaat</locationId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="nonequidistant"/>
<relativeViewPeriod unit="day" start="-3" end="0" startOverrulable="true" endOverrulable="true"/>
</timeSeriesSet>
</import>
```
```	<import>
<general>
<importType>Fewsdatabase</importType>
<folder>$IMPORT_FOLDER$/fewsldb</folder>
<deleteImportedFiles>false</deleteImportedFiles>
<idMapId>IdImportCAWFirebird</idMapId>
<dataFeedId>CAW</dataFeedId>
</general>
<locationSetId>X</locationSetId>
</import>
```
```	<import>
<general>
<importType>Fewsdatabase</importType>
<folder>$IMPORT_FOLDER$/fewsldb</folder>
<deleteImportedFiles>false</deleteImportedFiles>
<idMapId>IdImportCAWFirebird</idMapId>
<dataFeedId>CAW</dataFeedId>
</general>
<locationId>A</locationId>
<locationId>B</locationId>
</import>
```

### database types

Syntax for SQL Server:

```<jdbcDriverClass>net.sourceforge.jtds.jdbc.Driver</jdbcDriverClass>
<jdbcConnectionString>jdbc:jtds:sqlserver://dummy_hostname:1433;databaseName=dummy_databasename</jdbcConnectionString>
```

Syntax for Oracle:

```<jdbcDriverClass>oracle.jdbc.OracleDriver</jdbcDriverClass>
<jdbcConnectionString>jdbc:oracle:thin:@dummy_hostname:1521:dummy_databasename</jdbcConnectionString>
```

Syntax for PostgreSQL:

```<jdbcDriverClass>org.postgresql.Driver</jdbcDriverClass>
<jdbcConnectionString>jdbc:postgresql://dummy_hostname:5432/dummy_databasename</jdbcConnectionString>
```

Syntax for localDatastore, that should be placed into an import directory. Notice that jdbcDriverClass etc are not required, but import folder is required now. The system automatically detects if the type of the localdatastore (MSAccess, Derby or firebird)

```<importType>Fewsdatabase</importType>
<folder>$IMPORT_FOLDER_FEWS$</folder>
<failedFolder>$IMPORT_FAILED_FOLDER_FEWS$</failedFolder>
<backupFolder>$IMPORT_BACKUP_FOLDER_FEWS$</backupFolder>
```

Overview

TimeSeries reader for a FEWS Master Controller database. The identifier for this reader is "Fewsdatabase". This import allows a FSS or stand alone system to import data from another FEWS master controller database. The import reads the database directly and does NOT communicate with the MC. The following limitations apply:

1. It can only handle external historical and external forecasting data
2. It does not use the timestep as a key. As such the behavior is undefined if the remote database has the same series (location/parameter) with different timesteps.
3. It does not use the moduleInstanceId as a key.
4. The relativeViewPeriod element in the general section is required although the schema (see below) indicates it is optional.

## Configuration

The schema extension of the import module is shown below:

An example configuration file is attached to this page. This file imports one timeseries from the eami00 database on the fewdbsvr04 server; the figure below shows this file in XML-SPY grid format:

### Time series sets, location set id, or location id's

For this import there must be either time series sets, a location set id or location id's configured:

```	<import>
<general>
<importType>Fewsdatabase</importType>
<folder>$IMPORT_FOLDER$/fewsldb</folder>
<deleteImportedFiles>false</deleteImportedFiles>
<idMapId>IdImportCAWFirebird</idMapId>
<dataFeedId>CAW</dataFeedId>
</general>
<timeSeriesSet>
<moduleInstanceId>ImportCAW_AQUO</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>Q.meting.sec</parameterId>
<locationId>62079_Actuele_debiet_aflaat</locationId>
<locationId>62079_Actuele_debiet_inlaat</locationId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="nonequidistant"/>
<relativeViewPeriod unit="day" start="-3" end="0" startOverrulable="true" endOverrulable="true"/>
</timeSeriesSet>
</import>
```
```	<import>
<general>
<importType>Fewsdatabase</importType>
<folder>$IMPORT_FOLDER$/fewsldb</folder>
<deleteImportedFiles>false</deleteImportedFiles>
<idMapId>IdImportCAWFirebird</idMapId>
<dataFeedId>CAW</dataFeedId>
</general>
<locationSetId>X</locationSetId>
</import>
```
```	<import>
<general>
<importType>Fewsdatabase</importType>
<folder>$IMPORT_FOLDER$/fewsldb</folder>
<deleteImportedFiles>false</deleteImportedFiles>
<idMapId>IdImportCAWFirebird</idMapId>
<dataFeedId>CAW</dataFeedId>
</general>
<locationId>A</locationId>
<locationId>B</locationId>
</import>
```

### database types

Syntax for SQL Server:

```<jdbcDriverClass>net.sourceforge.jtds.jdbc.Driver</jdbcDriverClass>
<jdbcConnectionString>jdbc:jtds:sqlserver://dummy_hostname:1433;databaseName=dummy_databasename</jdbcConnectionString>
```

Syntax for oracle:

```<jdbcDriverClass>oracle.jdbc.OracleDriver</jdbcDriverClass>
<jdbcConnectionString>jdbc:oracle:thin:@dummy_hostname:1521:dummy_databasename</jdbcConnectionString>
```

Syntax for localDatastore, that should be placed into an import directory. Notice that jdbcDriverClass etc are not required, but import folder is required now. The system automatically detects if the type of the localdatastore (MSAccess, Derby or firebird)

```<importType>Fewsdatabase</importType>
<folder>$IMPORT_FOLDER_FEWS$</folder>
<failedFolder>$IMPORT_FAILED_FOLDER_FEWS$</failedFolder>
<backupFolder>$IMPORT_BACKUP_FOLDER_FEWS$</backupFolder>
```
• No labels