|
|
| This is an easy way to configure the
server. Database and webserver are installed on the same server. You
see a not so save kind of configuration, because the database
can't be protected by a firewall, but it is a bit faster than
installing the tdbengine on a separated server. The client
can be a Webbrowser or a Windows-/Linux-frontend. |
Example 1: tdbengine and webserver installed on one server
|
| That's the most common way of
configuration. In this case the database is seperated from
the webserver. Additionally you can protect the database with a
firewall. The webserver accesses the data via sql-commands over
the TCP interface. |
Example 2: tdbengine and webserver seperated from each other on two servers. Database is protected by firewall.
|
You also can use a
Windows-/Linux-frontend to work up your data. In that case tdbengine
can be installed on the local computer or it can be installed on a
central server. If users should be able to access data from more than
one Computer tdbSQL should be installed on a central server.
The Windows-/Linux-frontend can be programed in every program language
where a interface to tdbSQL exists. Projected are all the known
advanced languages like C, C++, Java, C# etc.
|
Example 1: tdbengine and webserver installed on one server
|
|
