Structure and organization

Geoweb is made up of a components' set of different kinds, that create an instance together. The instance sets out authentication functionalities and therefore one or more application forms, intended to operate graphical and alphanumerical databases, through user interfaces and/or procedural steps.

Web Application is the application filled in java, which constitutes Geoweb's engine. The application contains the basic mechanisms, the composition and the user interface rendering, the implementing logic, etc. etc. The application resides and is performed by an application server. Geoweb is developed and released on Apache Tomcat, but it is compatible with other technologies.

There is a web Application for the client and one dedicated for the server:
geowebclient.war → Applicazione Client
geowebadmin.war → Applicazione Admin

The release of a new version mainly consists in the sostitution of web Applications.

Geoweb uses a database organized in two types of data schematic, denominated: Metadata and Data.

The Metadata scheme contains all configurations defined by the interfaces of the application Admin's Administration.

Therefore, the configurations that define the user interfaces behaviour are collected and saved in the data structure. Following is a scheme about how information are organized, organized in thematic tables linked together by very specific cardinality constraints.

The Data scheme collects the user information that are managed within the application.

The Data scheme can be just one or a multiplicity of schemes, but they must be reachable by a single database connection (host:port:db:user:pwd).

In the data scheme there aren't necessary constraints, other than those definied by the normal rules of a Relational DB construction. However, some Geoweb components have been developed to fulfil specific user functionalities and they require tables with a title and a very clear data structure.

These data structures will be described in the paragraphs dedicated to these components.

The last framework basic component consists of a folder that must be avalaible and reachable on the web. In this folder there are the following elements:

• folder conf with the client application configuration files (configuration.properties, log4j.properties, webconfig.ini)
• folder confadmin with the admin application configuration (configuration.properties, log4j.properties)
• folder WEB that in turn contains:
  • images: folder of the images used by geoweb in the application forms (icons, banner)
  • license: folder with the license file's header
  • templates: folder bound to contain the source files of Report Jasper used by the applications
  • groovy: folder bound to contain support files groovy to geoweb automatisms(application trigger, procedural system task, actions, etc.)
  • any additional folders in support of application forms (e.g. BIM, cloud, photo360, ecc.)

In the event that Geoweb uses Blueprints or geographical, it is necessary to configure the needed maps set to look up for the visualization.

A maps and layer library shall be available, installed in a maps server MapGuide OpenSource, that shall be reachable by the Application server where Geoweb resides.

Geoweb implements the CMIS protocol, used for talking to the most used documentary operators, like Alfresco,MS Share Point, etc.). Therefore this component can be used to store and to manage massive amounts of documents, and to define in Geoweb the appropriate checks to establish the links to these documents.

(to be defined)