文件列表:

OpenGTS_2.2.7 (0, 2010-09-11)
OpenGTS_2.2.7\.RELEASE_2.2.7 (0, 2010-09-11)
OpenGTS_2.2.7\bin (0, 2010-09-11)
OpenGTS_2.2.7\bin\admin.bat (3685, 2009-12-30)
OpenGTS_2.2.7\bin\admin.pl (3796, 2009-12-30)
OpenGTS_2.2.7\bin\admin.sh (3508, 2009-12-30)
OpenGTS_2.2.7\bin\checkInstall.bat (3382, 2010-05-24)
OpenGTS_2.2.7\bin\checkInstall.sh (7670, 2010-06-30)
OpenGTS_2.2.7\bin\common.bat (2277, 2009-06-30)
OpenGTS_2.2.7\bin\common.pl (11035, 2010-05-29)
OpenGTS_2.2.7\bin\common.sh (2464, 2009-12-28)
OpenGTS_2.2.7\bin\dbAdmin.pl (13220, 2010-03-13)
OpenGTS_2.2.7\bin\dbConfig.bat (876, 2009-03-09)
OpenGTS_2.2.7\bin\exeJava (3765, 2010-01-25)
OpenGTS_2.2.7\bin\exeJava.bat (661, 2009-03-05)
OpenGTS_2.2.7\bin\getFile.sh (2354, 2009-05-28)
OpenGTS_2.2.7\bin\gtsdb.sh (1025, 2009-03-22)
OpenGTS_2.2.7\bin\initdb.bat (1091, 2009-03-09)
OpenGTS_2.2.7\bin\initdb.pl (2081, 2009-03-09)
OpenGTS_2.2.7\bin\initdb.sh (1597, 2009-12-19)
OpenGTS_2.2.7\bin\parseFile.sh (789, 2009-05-06)
OpenGTS_2.2.7\bin\psjava (8490, 2009-12-22)
OpenGTS_2.2.7\bin\rgTest.sh (2100, 2010-06-28)
OpenGTS_2.2.7\bin\runserver.bat (1452, 2010-04-30)
OpenGTS_2.2.7\bin\runserver.pl (7519, 2010-05-02)
OpenGTS_2.2.7\bin\runserver.sh (6281, 2010-06-09)
OpenGTS_2.2.7\bin\serverList (1427, 2010-07-19)
OpenGTS_2.2.7\bin\startServers.sh (5014, 2010-04-14)
OpenGTS_2.2.7\build.properties (1760, 2010-01-04)
OpenGTS_2.2.7\build.xml (70871, 2010-08-08)
OpenGTS_2.2.7\build_custom.xml (694, 2009-02-11)
OpenGTS_2.2.7\CHANGELOG.txt (65120, 2010-09-11)
OpenGTS_2.2.7\common.conf (8964, 2010-08-13)
OpenGTS_2.2.7\config.conf (8266, 2010-09-11)
OpenGTS_2.2.7\config.conf.original (8266, 2010-08-05)
OpenGTS_2.2.7\custom.conf (620, 2010-05-17)
OpenGTS_2.2.7\dcservers.dtd (1755, 2010-06-28)
OpenGTS_2.2.7\dcservers.xml (6719, 2010-08-21)
OpenGTS_2.2.7\default.conf (843, 2009-10-30)
OpenGTS_2.2.7\jlib (0, 2010-09-11)
... ...

----------------------------------------------------------------------------------- Project: OpenGTS - Open GPS Tracking System URL : http://www.opengts.org File : README.txt ----------------------------------------------------------------------------------- Notes: 1) Please refer to the included "OpenGTS_Config.pdf" file for all installation and configuration information for the OpenGTS system. 2) When updating to a newer version of OpenGTS, it is highly recommended that the following command be run to update the database with the latest table/column changes: > bin/dbAdmin.pl -tables=ca 3) On Windows 7, IE 8, if you receive the error "Error [jsMapInit:[object error]" then you may need to enable "Active Scripting" in security tab. 4) A listing of the database tables and fields can be found in the file "SCHEMA.txt" in the OpeNGTS installation diretory. 5) Documentation is now available online at the following link: http://www.opengts.org/documentation.html 6) This open-source version of OpenGTS includes support for the following GPS tracking devices: - Aspicore GSM Tracker (Nokia, Sansung, Sony Ericsson phones) - Sanav GC-101, MT-101, and CT-24 Personal Tracker (HTTP-based protocol) - Sanav GX-101 Vehicle Tracker (HTTP-based protocol) - V-Sun 3338 Personal Tracker - iCare G3300 Personal Tracker - Various Boost Mobile phones (OpenDMTP compliant) - HP hw6965 Windows/CE phone (OpenDMTP compliant) - Mologogo capable phoes - "GPSMapper" capable phones. - "NetGPS" capable devices. Please let us know if you find any issues with this release. ----------------------------------------------------------------------------------- Visit the following link for additional downloadable documentation and add-ons for OpenGTS: http://www.geotelematic.com/download.html ----------------------------------------------------------------------------------- Updating existing Geozone table entries (only required when upgrading from versions previous to v1.9.3): If you have existing Geozone table entries, they will need to be updated to include Bounding-Box information used to optimize Geozone lookups. This update process is done automatically with the following steps: 1) Update the new Geozone bounding-box table fields: > bin/dbAdmin.pl -tables=ca 2) For each account having Geozone entries, run the following command (replace "" with the appropriate account-IDs for each account which has Geozone entries): > bin/admin.pl Geozone -account= -list -update The update process should now be complete. ----------------------------------------------------------------------------------- This package may contain one or more of the following source modules which contain copyrights from their respective authors. Please review these source modules for their copyright and license information: war/track/js/mapstraction/mapstraction.js war/track/js/mapstraction/mapstraction-geocode.js war/track/js/mapstraction/labeledmarker.js war/track/js/sorttable/sorttable.js ----------------------------------------------------------------------------------- Contributors: See the following link for a list of contributors: http://www.opengts.org/info.html ----------------------------------------------------------------------------------- Sample data: Additional documentation for installing sample 'demo' data into the database can be found in the "README.txt" file in the "sampleData" directory at sampleData/README.txt ----------------------------------------------------------------------------------- Boost Mobile Motorola phones: For information regarding support for various Boost Mobile Motorola phones, please see the document at MotoDMTP/MotoDMTP.txt ----------------------------------------------------------------------------------- Sanav GC-101 GPS Tracking Device Support: Additional documentation for installing and configuring the GC-101 server within OpenGTS can be found in the "README.txt" file in the "gc101" source directory at src/org/opengts/war/gc101/README.txt See the following link for manufacturer's product information: http://www.sanav.com ----------------------------------------------------------------------------------- ICare G3300 Personal GPS Tracking Device Support: Support for the ICare G3300 GPS tracking device is included in this release. This server uses the raw-socket mode device communication server based on the example 'template' server. The "icare.jar" server jar file can be built with the command: > ant icare And can be started in the same manner that other servers are started using the "runserver.pl" command as follows: > $GTS_HOME/bin/runserver.pl -s icare See the following link for manufacturer's product information: http://www.i-care.net.tw ----------------------------------------------------------------------------------- Runtime config file property key references (for *.conf files, such as 'default.conf', 'common.conf', 'webapp.conf, ...): - Previously defined property keys may be referenced by placing them in ${...} brackets, such as ${log.name}. Environment variables may also be referenced in this manner, as in ${GTS_HOME}, or ${CATALINA_HOME}. - A default value may be specified for referenced property keys which have not been defined. For instance ${OUTPUT_DIR=/tmp} would resolve to "/tmp", if the property OUTPUT_DIR is not defined (as an environment variable, or otherwise), or will resolve to the value specified on the OUTPUT_DIR property (or environment variable) if it is defined. - Recursive propery key references may also be specified. For instance, the specification ${THIS_DIR=${THAT_DIR=/tmp}} will first attempt to resolve the value for "THIS_DIR", if not found, then value of THAT_DIR will be returned. If THAT_DIR is not defined, then finally the specification will resolve to "/tmp". - Property reference specifications for which the property is not defined, and there is no specified default value will resolve to the literal "${var}" string. That is, if "var" is not defined, then ${var} will resolve to the literal string "${var}". - Property reference specifications are only resolved at the time a property value is requested, not at the time the property key=value line is parsed (ie. lazy resolution). For instance, in the property specification below, "var_a" will resolve to "test", even though "var_b" is not defined until after "var_a": var_a=${var_b} var_b=test This means that if "var_b" should ever change, the resolved value of "var_a" will also change accordingly. [ie. "var_a" will only be resolved at the time a call to an RTConfig property value retrieval method is called - such as RTConfig.getString("var_a")]. Write-only (assignable) property keys (ie. %log, %include) are the only exception to this rule. Since their assigned behavior is executed at the time they are parsed ('%log' prints a log message, and '%include' includes a file), write-only property keys must be assigned values that can be fully resolved at the time their values are assigned. - Property keys may be re-assigned. Property keys take on their last assigned value. For instance, the following will display "Hello", then display "World": test=Hello %log=${test} test=World %log=${test} The following are reserved read-only constant property keys: %version returns the current version, as in "2.0.4" %contextName returns the context 'name' (name of the servlet context, or main class name) %contextPath returns the context 'path' (path to the servlet context, or $GTS_HOME) %configURL returns the URL for the loaded config file The following are reserved write-only (assignable) constant property keys: %log displays the specified value to the log output %include includes the config at the value URL (URL must exist, error otherwise) %include? includes the config at the value URL (URL may exist, otherwise ignored) (The included URL protocol must be one of "file" or "http".) The following are available within a PrivateLabel session context: session.name The PrivateLabel Domain name session.locale The PrivateLabel Domain locale ----------------------------------------------------------------------------------- Contact Info: Please feel free to contact us regarding questions on this package. Thanks, Martin D. Flynn devstaff@opengts.org

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：