WISKI Web FAQ's

Inter- and Intranet Access on WISKI DataWater Resources Management System KISTERS - the Water Resources Information System"

Which web server products are supported?

Apache, IIS (others are possible but have to be discussed)

How can the output from the package be made available to a web server? (virtual directories, copying, etc.)

The package is pure PHP code and is generated dynamically (on demand from the database to the browser) HTML information. If you don't want to have direct access from the public area to the database you can:

Are the pages produced by this package static or dynamic? (i.e., whether the output can be produced dynamically following an online query, or must be preprocessed and stored)

The outputs of both packages WISKI Web Pro and WISKI Web Public are produced dynamically. WISKI Web Pro has many degrees of user interaction and needs to used directly
End user <-> Webserver/PHP <-> database
WISKI Web Public has a low user interaction degree (predefined time periods...) and consists of a dedicated amount of pages. So we can use an automatism to periodically collect all those pages and convert/transfer them to another place via e.g. FTP (so we don't need a second database and have a public site with proc-essed PNG/HTM which is able to serve many of the public's requests).
Public USER <- Public Webserver <- WSP <-> Internal Webserver / PHP <-> Database
WSP is a buffer - working with a dedicated performance around the clock even in times of flood.

Which types of queries can be made?

WISKI Web Pro allows WISKI Web Public allows

What options exist for re-styling the output?


Page elements are adressed with CSS-class-names. So you can work on one file "styles.css" in order to change color, fonts, background, border etc. However you can not alter the page's constitution and order of elements.

For any further questions
please don't hesitate to contact  Stefan Fuest