DWB network

From Workbench
Jump to: navigation, search

Before installing a DWB environment the Technical documentation at a glance should be checked.

If a DWB network of its own is envisaged, for instance, cases 'green' and 'yellow ' among the DWB environments alternatives, a set up of a DWB network with browser-independent rich clients, browser-embedded clients, web user interfaces and machine-readable REST web services should be considered.

Four general solutions using different transfer protocols and formats accessing, editing and processing data in the network are shown below.


DWB-Netzwerk



Data processing Type A (red): For a DWB network this is the most recommended method for managing data in MS SQL Server databases. The browser-independent .NET rich clients provide high functionality on user client side and might be easily expanded to fulfill further user requests. The Silverlight web client and apps for WindowsPhone use the same MS specific data transfer protocols.


Data processing Type B (blue) uses JAVA rich clients for managing data of MS SQL Server databases or a mirror of MS SQL databases to PostgreSQL databases based on a DWB information model.

  • Type B is realised for DiversityDescriptions to be accessed with the DiversityNavigator client.


Data processing Type C (apricot): There exists a number of transfer protocols for creating web browser-embedded clients and services. In the DWB network context, they are mainly set up for read-only access to cache databases (MS SQL Server and PostgresSQL cache).


Data processing Type D (purple): REST (Representational state transfer) is a simple methode that uses http as data transfer protocol. It is suitable to transfer documents of various formats (XML, JSON).

  • We started to develop a REST service to transfer information on taxonomic names (lists, simple hierarchies) managed in DiversityTaxonNames. Example is: DWB REST Webservice for Taxon Lists

see also