Sanav GC-101 Manual de Instalação descarregar pdf (Página 18)

OpenGTS includes mapping support for OpenLayers/OpenStreetMap, Google Maps, Microsoft Virtual Earth, and

Mapstraction (which can support several other mapping service providers as well). Contact us regarding support for

other commercial mapping service providers. If you will be using Google Maps for your map provider, you must also

"private.xml" (or "private_common.xml") file at the location indicated (ie. replace "*** Place Google Maps

Key Here ***" with your quoted key). To change the default displayed map pushpins, you can create your own

'Pushpins' section within your chosen MapProvider. See the 'private.xml' file Pushpins section (in the

"openLayers" MapProvider section) for more information regarding customizing pushpin icons.

Consult the contents of the provided private-label file at "$GTS_HOME/private.xml" for more information on specific

customizations (experiance in the general format, editing, and syntax of XML files will be necessary).

5.3.a) Maintain proper XML syntax when modifying "private.xml" or "reports.xml"

Make sure that any changes to the 'private.xml' file still comply with proper XML syntax. XML is very

particular about proper syntax, and introducing an XML syntax error often results in an error message similar to

the following when attempting to view the login page in a web browser:

Invalid 'private.xml' configuration, please contact the System Administrator

Run "bin/checkInstall.sh" to help diagnose any XML syntax errors that may have been introduced.

The general look-and-feel of the web-interface can also be changed by modifying the JSP file

"$GTS_HOME/war/track/jsp/loginSession.jsp" and the various CSS files in the directory

"$GTS_HOME/war/track/css/". Look for the "WebPages" tag section in the "private.xml" file for additional

information regarding the customization of the "loginSession.jsp" file.

5.3.b) IMPORTANT: Redeploy all servlets after modifying any runtime configuration file

Changes to any of "private.xml", "reports.xml", "webapp.conf", "common.conf", "system.conf", or

"custom.conf" files (or other ".xml" or ".conf" file) will require that the "track.war" (as well as the other

servlets) file be re-built and re-deployed.

5.4) Compiling/Installing the "track.war" Java Servlet

To build the "track.war" file, run the Ant build command as follows:

/zzz> cd $GTS_HOME

/usr/local/OpenGTS_1.2.3> ant track

(note, the "ant all" performed above also builds the "track.war" file)

The target "track" is a wrapper for ant targets "track.compile" and "track.war". The target "track.compile"

compiles all necessary classes and configuration files into the build directory "$GTS_HOME/build/track". The target

"track.war" then creates the 'web archive' file "$GTS_HOME/build/track.war". If any of the runtime

configuration files have changed, such as "private.xml", "reports.xml", "webapp.conf", or "common.conf" files

(or possibly any other "*.conf" of "*.xml" file), then the "track.war" file must be rebuilt and redeployed. A shortcut

to rebuilding the "track.war" file, if all source modules have already been compiled, is to issue the following

command:

/zzz> cd $GTS_HOME

/usr/local/OpenGTS_1.2.3> ant track.war

This will simply repackage the "track.war" file from the pre-built source modules, and changed runtime configuration

files. If everything has already been compiled, this command typically takes only a few seconds to complete.

OpenGTS Configuration and Installation Manual Page 18 of 60

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

Sem comentários

Sanav GC-101 Manual de Instalação Página 18