Sanav GC-101 Manuel d'installation télécharger pdf (Page 17)

5) Installing “track.war”

The "track.war" (Web-ARchive) runs in a Java Servlet container and works with the SQL DB datastore to provide a full-

featured web interface to the GPS location data captured in the SQL database from remote devices. The mapping

support currently uses OpenLayers/OpenStreetMap, but can be configured to use other commercial mapping service

providers.

5.1) Configuring the "webapp.conf" file

The default runtime configuration file "webapp.conf" includes the file "common.conf", which in-turn includes

"system.conf" and "custom.conf". For most installations, the default values specified in this file can be left as-is.

However, some items, such as your SMTP server specifications, should be configured to fit your system requirements.

5.2) Configuring the available reports

Various detail and summary reports can be defined using the file "reports.xml", which can be found at

"$GTS_HOME/reports.xml".

More detailed information can be found in the above "reports.xml" file, and elsewhere in this document. Here is a

summary of the available features in the "reports.xml" file (experience in the general format and editing of XML files

will be necessary).

"ReportLayout" defines the expected record format and the available columns for the defined report. The specific

report layout is defined by the specified Java class, and 2 report layouts have been provided:

• org.opengts.war.report.event.EventDataLayout - This layout expects to display EventData records

and specifies available columns based on the fields available in the EventData record.

• org.opengts.war.report.field.FieldLayout - This layout expects to display generic "FieldData"

records and specifies various available columns type which can be used to display pertinent data.

The "Report" tag specifies a Java class which is bound to a specific ReportLayout. The "Report" also specifies

how it is to be presented to the user (ie. the menu option), report title, displayed columns, and report selection criteria.

5.3) Configuring the Private Label look & feel

The configuration and customization of the web user interface can be specified in the file "$GTS_HOME/private.xml"

(or "$GTS_HOME/private/private_common.xml" for the GTS Enterprise). This file controls the following options

that are available on a 'Domain' basis (the domain name of the reference URL visiting the server):

– The Date/Time formats, and displayed TimeZones.

– The MapProvider used (ie. Google Maps, Microsoft Virtual Earth, Mapstraction, OpenLayers, etc). Including what

pushpin icons are to be displayed on the map.

– The ReverseGeocodeProviders used to convert latitude/longitude values into a street address (Geonames, etc.).

– The GeocodeProvider used to convert street addresses into a latitude/longitude (if available).

– Available menu options, webpages, and customizing JSP files.

– Available report options.

– Access-Control-List (ACL) definitions.

– And much, much more ...

Please refer to the comments contained within the "private.xml" (or "private_common.xml") file for more

information.

OpenGTS Configuration and Installation Manual Page 17 of 60

1 2 ... 12 13 14 15 16 17 18 19 20 21 22 ... 59 60

Pas de commentaire

Sanav GC-101 Manuel d'installation Page 17