Untitled Document

RIMapper deployed in Tomcat

After successfull deployment in Tomcat the minimal setup (there could be additional files) should be inside the Tomcat webapplications root {eg "C:\Program Files\Apache Software Foundation\Tomcat 5.0\webapps"}, as follows:

RIMapper
\|– \|	-- admin -	––––––	---	----	----	DefineWMSInstance.html wms_instance.jsp	web-app to set wms_instance.xml
\|– \| \| \|	-- js -----	––––––	---	----	----	gui.js anim_gui.js helper_functions.js mapapp.js	javascript code for the GUI same for animation GUI helper class for GUI (by Carto:Net) helper class for GUI (by Carto:Net)
\|–	META-INF
\|–	WEB-INF
\|	\|––––	classes
\|	\|	\|–	nl
\|	\|		\|–	itc
\| \| \|	\| \| \|			\|–	rimapper		various JAVA classes that parse XML files, convert data to SVG, handles exceptions, etc. See the JavaDoc for more information.
\|	\|––––	––––––	––	–––	lib -	––––––––––––––––––––––––	Java libraries needed for the project
\| \|–	–––––––	––––––	––	–––	–––	CapabilitiesTemplate.xml wms_instance.xml testURL.html WMS_exception_1_1_1.dtd WMS_MS_Capabilities.dtd	template for generating GetCapabilities response xml configuration stating SFServer, username and password to connect to DB and the name of the database, that defines the WMS instance. start page to test sending WMS requests OGC schema definition for exceptions OGC schema definition for Capabilities response

Barend Köbben - last changes February 22, 2013
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 2.5 License.