Upload
vuongdien
View
219
Download
2
Embed Size (px)
Citation preview
Software installation manualWeb application URBAN SMS suite
January, 2012
URBAN SMS Soil Management Strategy
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 1 / 60
Urban SMS WP4
Urban SMS Tools
Installation Guide
CGS Plus d.o.o.
Technical training version
Saved: Friday, January 27, 2012 Print: Sunday, 29 January 2012
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 3 / 60
Content Urban SMS.............................................................................................................................................................. 1 WP4 ........................................................................................................................................................................ 1 Urban SMS Tools .................................................................................................................................................... 1 Installation Guide ................................................................................................................................................... 1 Content................................................................................................................................................................... 3 1 Hardware requirements ................................................................................................................................. 5 2 Software requirements .................................................................................................................................. 7 2.1 Important software ................................................................................................................................ 7 2.1.1 IIS 6 ................................................................................................................................................. 7 2.1.2 Message queue............................................................................................................................... 7 2.1.3 Grass GIS software.......................................................................................................................... 8 2.1.4 MapGuide Maestro software ......................................................................................................... 8 2.1.5 MapGuide software........................................................................................................................ 9
3 UrbanSMS web application (CD) .................................................................................................................. 11 3.1 Urban SMS ‐ CD content....................................................................................................................... 11
4 Installation of Grass GIS engine.................................................................................................................... 11 5 Configuration settings of the Message Queue............................................................................................. 17 5.1 Verify Grass installation........................................................................................................................ 17
6 Installation of MapGuide open source, version 2.1.0 .................................................................................. 18 7 Installation of the Mapguide Maestro 2.1................................................................................................... 24 7.1 Setup of MapGuide Maestro web service ............................................................................................ 26
8 Map admin set packages .............................................................................................................................. 47 9 Configuring the UrbanSMS web application ................................................................................................ 49 9.1 Setting up the Web.config file .............................................................................................................. 49 9.2 IIS settings............................................................................................................................................. 51 9.3 Security ................................................................................................................................................. 54 9.4 Create folder and copy data ................................................................................................................. 55 9.5 Batch files ............................................................................................................................................. 55 9.5.1 Settings the BATCH file for GRASS................................................................................................ 55
9.6 Troubleshooting the Web Application ................................................................................................. 56 10 Create database........................................................................................................................................ 56 11 MapGuide settings ................................................................................................................................... 58
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 5 / 60
About a task Project Urban SMS
http://www.urban‐sms.eu
WP4 Soil Manager Suite
WP responsible:
dr. Borut Vrščaj, Agricultural Institute of Slovenia, Hacquetova 17, SI1000 Ljubljana, Slovenia
Contact: [email protected]
Subcontractor:
CGS plus, Innovative IT and Environmental Technologies, d.o.o.
Brnčičeva ulica 13, SI1000 Ljubljana, Slovenia
http://www.cgsplus.com/
Tool programming team:
Msc.Matjaž Ivačič, univ.dipl.ing.geod. Msc. Dejan Gregor, univ.dipl.ing. Mr. Dejan Kos Mr. Andrej Beden, Dr. Alenka Šajn‐Slak
Contact: [email protected]
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 6 / 60
About a document
This document presents the Urban SMS software installation manual.
Document stage: Final version, December 2011
Authors:
Msc.Matjaž Ivačič, univ.dipl.ing.geod. Msc. Dejan Gregor, univ.dipl.ing. Mr. Dejan Kos Mr. Andrej Beden, Dr. Alenka Šajn‐Slak
Contact: [email protected]
Abstract This document represents all steps for successful Urban SMS software installation. It describes basic software as well as hardware requirements, system configuration of data and user web application. The document describes step by step steps for successful installation and suggests the basic settings to enable the effective use.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 7 / 60
1 Hardware requirements Minimum Server, processor 1,8 GHZ (dual core), 2 GB ram, 80GB disk
2 Software requirements The following software is required to run the Urban SMS Tools:
‐ Microsoft server 2003 Service pack 2 o IIS 6 o Message queue
‐ Microsoft SQL server 2008 ‐> all version ‐ .NET Framework 2.0, 3.5 ‐ Grass GIS ‐ MapGuide OpenSource ‐ MapGuide Maestro
2.1 Important software
2.1.1 IIS 6 You must have install IIS 6.
Check Internet information services (IIS)
2.1.2 Message queue You must have install Message queue.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 8 / 60
Check Message Queuing and click “Details” and check “Triggers”
2.1.3 Grass GIS software Geographic Resources Analysis Support System, commonly referred to as GRASS GIS, is a Geographic Information System (GIS) used for data management, image processing, graphics production, spatial modelling, and visualization of many types of data. It is Free (Libre) Software/Open Source released under GNU General Public License (GPL). GRASS is official project of the Open Source Geospatial Foundation.
Main Grass web page:
Link to GRASS information site:
http://grass.osgeo.org
Link to setup file with WinGrass 6.4
http://grass.osgeo.org/grass64/binary/mswindows/native/WinGRASS‐6.4.0RC6‐1‐Setup.exe or FTP
Other useful Grass information:
http://grass.itc.it/
To download Grass reference manuals please visit:
http://grass.itc.ireference t/grass65/manuals/html65_user/index.html
2.1.4 MapGuide Maestro software MapGuide Maestro Open Source is a web‐based platform that enables users to develop and deploy web mapping applications and geospatial web services.
Main MapGuide Maestro project open source hope web page:
http://mapguide.osgeo.org/
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 9 / 60
Download MapGuide Maestro software
http://download.osgeo.org/mapguide/maestro/MapGuide%20Maestro%202.0.msi or ftp
To download MapGuide Maestro manuals please visit:
http://trac.osgeo.org/mapguide/wiki/maestro/UserGuide
2.1.5 MapGuide software http://download.osgeo.org/mapguide/releases/2.1.0/MapGuideOpenSource‐2.1.0.4283‐Final.exe or ftp
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 11 / 60
3 UrbanSMS web application (CD)
3.1 Urban SMS CD content For a successful software use, the following software should be downloaded in further six steps:
1.) Install Grass 2.) Config Message Queue 3.) Install MapGuide (server) 4.) Config Message Queue 5.) Install MapGuide maestro 6.) Config Database 7.) Config UrbanSMS web application
a. Web config
4 Installation of Grass GIS engine When entering the Grass download page, please follow step ‐ by‐ step Grass installation procedure:
Step 1: Run Grass Setup
Click Next
Step 2: Accept Grass License Agreement.
Click Next
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 12 / 60
Step 3: Accept Grass License Agreement.
Select the Grass folder. To avoid possible difficulties it is suggested that you change location to C:/Grass.
Click Next
Step 4: Select Components to install.
There is no need to install demo datasets.
Click Install (installation might take a few minutes)
Click Next when completed
Step 5: When the installation is complete
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 13 / 60
Now tick Launch GRASS GIS and click Finish
Grass is now installed; please tick Launch GRASS GIS and click Finish.
Step 6: Run the Grass application and start with Grass configuration
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 14 / 60
Point 1: Click Browse
In point 1 click browse and select map where will you have saved data and write project location in point 2. Important project location can be only one word or phrase.
Point 2: Click the location wizard
In point 1, please select your location and then click next. (Point 2). Please choose arbitrary non‐earth coordinate system (XY), if you are not fully familiar with other options.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 15 / 60
Click finish (point 1)
In warning window you only click OK. (V redu in Slovenian)
Point 3:
Type in the name of your mapset and click OK:
Click OK (V redu)
Now Grass is installed and configured with all basic settings.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 17 / 60
5 Configuration settings of the Message Queue Go to: Start/Control Panel/ Administrative Tools/Computer Management.
Right click on Private Queues and select new ‐> Private Queue
Set the name for Queue and select Transactional
Potential problems:
Message Queue may have problems with executing of the batch file, so it’s necessary to set the rights (permissions) for the implementation of the Message Queue.
5.1 Verify Grass installation Run Grass from Start‐> All Programs‐> Gras‐64‐>Grass 6.4. ORC6
After successful installation, Grass is started showing the following window on the screen:
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 18 / 60
6 Installation of MapGuide open source, version 2.1.0 Step 1: Installation starts with the following window. Please click Next:
Click Next
Step 2: To move forward, you should agree with the license agreement
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 19 / 60
You must accept the terms in the License Agreement and then click Next
Step 3: Select your server
Select IIS Configuration and then click Next
Step 4: Select the technology on which you wish to run the software
Select .NET and then click Next
Step 5: Create the application pool
You can change the application pool or only click next.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 20 / 60
Click next
Step 6: The IP address for MapGuide server should be provided
It is recommended not to change the IP address. Please click Next
Step 7: Select the path for your installation
Click Next
Step 8: MapGuide component
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 21 / 60
Click Next
Step 9: Start installation
Click Install
Step 10: Please click Finish to complete the installation
Click Finish
Step 11: To be able to use the software, the system must be restarted.
Click Yes
MapGuide Open Source 2.1.0 is now installed on your computer/server.
Step 12: Check if you have Allowed ASP.NET
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 22 / 60
Click Allow
Step 13: You must have selected right ASP.NET version 2.0.59727
Select 2.0.59727
Step 14: In tab Directory Security browse for admin user on your server. To execute all operation application need full access. You must also check “Integrated Windows authentication”
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 23 / 60
Browse admin user
Step 15: In application pool you need to change Identity to “Local System”
In application pool identity select “Local System”
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 24 / 60
7 Installation of the Mapguide Maestro 2.1
Important: Before installing Mapguide Maestro, IIS6 needs to be installed first on your computer/server.
Step 1: Please open the Mapguide Maestro download page and click Next to start the installation sequence
Click Next
Step 2: Please accept the license agreement
Click Next
Step 3: Select the desired components to be installed
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 25 / 60
Click Next
Step 4: To start the installation of the MapGuide Maestro, please click Install
Click Next
Step 5: Installation is now finish
Click Next
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 26 / 60
7.1 Setup of MapGuide Maestro web service Mapguide Open Source is now installed. The next step is to connect to the mapagent trough the MapGuide Maestro. To do that, we need to config the input data path first.
1.) Please select your data path, username and password
Click Next
2.)
Click »Create a new resource«
3.)
Select »Folder«
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 27 / 60
4.)
Select the folder name (e.g. UrbanSMS)
5.)
Click with right mouse button on folder name (in our case UrbanSMS) and then select New ‐‐> Folder
It is very important that the following file structure is used:
‐ Data
‐ Layers
‐ Layouts
‐ Maps
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 28 / 60
6.)
Then right click on Data folder and then select New‐>Dataconnection
Then select the data provider for your connection from the list.
Select provider and then click OK
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 29 / 60
7.)
Please Note: You can select different providers (please see the following examples):
a) GDAL
Configuration data connection
Point 1: Copy the physical path:
C:\Data\urbansms\GISData\12.5\USMS\ToolData\gOM\
Point 2: Test the connection to make sure everything is in order (»Provider reports no errors«)
Point 3: Select the coordinate system
Then click »Add a new coordinate system override«
Click on Source »…«
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 30 / 60
Select the coordinate Category:
And then coordinate system:
Finish selection with OK.
Click OK and repeat this procedure also for Target
Point 4: Save Data connection
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 31 / 60
Program will probably ask you if you want to save the Data connection regardless the warnings reported. You can click Yes.
b.) SHAPE
Point 1: Copy the physical path where source is Example: C:\Data\urbansms\GISData\12.5\USMS\ToolData\gOM\
Point 2: Tooltip can show user data with some parameters.
Point 3: You can change visibility of data from the table with selection on checkbox visible.
Point 4: You can add role:
Point 5: You can delete role:
Point 6: Type in the rule:
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 32 / 60
By clicking on the Properties, you can view the shapes.
Example for role:
AS_<20
And then click Ok.
Point 7: You can change the colour of the typed role. Point 8: It is almost the same to the Tooltip, you can add the label on the selected role (with your data). Example: CONCAT ( AS_ , 'As mg/kg' ) Point 9: All roles you can also add to the legend with some short description.
8.)
Please select the folder Data and type in the »Resource name« without a special character. Then click OK.
9.)
We have now created the DataConnection.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 33 / 60
The next step is to create the Layer.
Right click on the folder Layer and then select New‐‐>Layer
10.)
Click on »…«
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 34 / 60
11.)
Select the Data connection from the folder Data.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 35 / 60
12.)
On each layer you can change several properties. For example; the visibility settings determine the scales on the web page from which the layer will be visible (Zooming in and out).
Click Save for save properties of this layer.
13.)
Select the folder Layer and type in the mane for »Resource name«. NOTE: please do not use special characters. To finish, click OK.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 36 / 60
14.)
Right click the folder Maps, then select New and then Map
15.)
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 37 / 60
Point 1: Select »…«
Point 2: Select Coordinate Category
Point 3: Coordinate System
Point 4: Click OK
Point 5: In description, type in the project name (Example: UrbanSMS)
16.)
In the »Layers by group« tab click on the icon that stands for »Add a new group«.
On the right side, you can then change the layer’s properties (name and legend label) of this added group.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 38 / 60
The following Layer groups are suggested:
17.)
In »Layers by group« click on »Add a new layer to the map«
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 39 / 60
18.)
Select the folder Layers and then layers which you would like to show on the map. Then click OK.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 40 / 60
19.)
This is an example for the added layers.
Point 1: You can change the properties of these added layers.
Point 2: You can change the properties, for added/selected layers which are present/visible on left side of the web page. If this is ticked this means true, otherwise it is false.
Point 3: Save maps
Important: Layer name in Name box MUST be identical!
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 41 / 60
Select the folder Layer and type in the »Resource name« without special characters. Then click OK.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 42 / 60
20.)
In the tab “Layer by drawing order” you can change the priority by which the layers will be shown on
the web page.
21.) The data layers as seen in the “Data” and “Layer” folders
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 43 / 60
Data
Layers
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 44 / 60
22.)
Right click the Layouts and then select the New‐>Layout
23.)
Insert the title name. (Example: UrbanSMS: Celje)
Insert Select »…« (Please see the next picture)
Insert the initial task in taskpane. Then insert "../../urbansms/SoilManagenmentTools.aspx"
Note; please insert the initial task in taskpane. Then save Layouts (see next picture)
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 45 / 60
Select the folder Maps and select created map.
Select the folder Layouts and type in the »Resource name« without special characters. Then click OK.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 46 / 60
On Layouts you can also change the default menu. It is suggested use the following (depends on the user’s needs).
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 47 / 60
8 Map admin set packages domain /mapguide/mapadmin/
• Default username: Administrator • Default password: admin • Map admin Login
Type in the username and password
Import packages
To make the packages you must type in the name of library (E.g. Library://UrbanSMS/ and custom name (for example; urbanSMS_2010). This saves all settings from Maestro to *.mgp
If you have more versions/data you can dynamically load them with a command “Load Package”.
Select/tick and load the desired package
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 49 / 60
On CD you have test data. Please copy Test_UrbanSMS.mgp to “C:\Program Files\OSGeo\MapGuide\Server\Packages” and then find category “Load Packega” in click “Load Package”.
9 Configuring the UrbanSMS web application
9.1 Setting up the Web.config file Web.config is a settings file, which is located on the same place as the application.
URL path from UrbanSMS web application <add key="urlPage" value="http://localhost/UrbanSMSWeb/"/>
Root URL path from domain <add key="urlRoot" value="http://localhost/"/> Layouts from MapGuide maestro <add key="webLayout" value="Library://UrbanSMS/Layouts/layout_UrbanSMS.WebLayout"/> User from MapGuide maestro <add key="defaultUser" value="Administrator"/> Password from MapGuide maestro <add key="defaultPassword" value="admin"/> Map name which use MapGuide maestro <add key="mapName" value="map_UrbanSMS"/> Grass Work space which was setup <add key="grassWorkSpace" value="@celje"/> Result name should be the same as in Maestro in folder map (layer name) <!‐‐ TOOLS 1 ‐‐> <add key="tools1result" value="esq_result"/> <!—END TOOLS 1 ‐‐> <!‐‐ TOOLS 2 ‐‐> <add key="tools2result" value="gNS_result"/> <!‐‐ END TOOLS 2 ‐‐> <!‐‐ TOOLS 3 ‐‐> <add key="tools3result" value="gSC_result"/> <!‐‐ END TOOLS 3 ‐‐> <!‐‐ TOOLS 4 ‐‐> <add key="tools4result" value="asq_result"/> <!‐‐ END TOOLS 4 ‐‐> <!‐‐ TOOLS 5 ‐‐> <add key="tools5result" value="asq_result"/>
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 50 / 60
<!‐‐ END TOOLS 5 ‐‐> <!‐‐ TOOLS 6 ‐‐> <add key="tools6result" value="asq_result"/> <!‐‐ END TOOLS 6 ‐‐> <!‐‐ TOOLS 7 ‐‐> <add key="tools7result" value="asq_result"/> <!‐‐ END TOOLS 7 ‐‐> <!‐‐ TOOLS 8 ‐‐> <add key="tools8result" value="asq_result"/> <!‐‐ END TOOLS 8 ‐‐> <!‐‐ TOOLS 9 ‐‐> <add key="tools9result" value="asq_result"/> <!‐‐ END TOOLS 9 ‐‐> If you have any problems, you can enable logging in the UrbanSMS application; <!‐‐ 0 ‐ NO 1 ‐ YES ‐‐> <add key="EnableLoging" value="0"/> Path for logo which is present in the PDF report; <add key="pdfHead" value="E:\projekti\test\UrbanSMS_solution\UrbanSMSWeb\images\urbansms_central_logos_euro.jpg"/> Geometry doesn’t change; <add key="Geometry" value="Geometry"/> Name of the message queue; <add key="MessageQueueName" value="UrbanSMS"/> Please do not change; <add key="customPolygonLayerName" value="Customlayers"/> Application’s ID from your application (in aspnet_Applications tabel ) <add key="applicationID" value="CA67C06E‐FF7B‐4B2B‐A733‐CB5C15FF1CBD"/> Path for Grass colour path; <add key="color_grass_path" value="C:\Program Files (x86)\GRASS‐64\etc\colors\"/> Physical path for the application; <add key="pathAppliaction" value="E:/projekti/test/UrbanSMS_solution/UrbanSMSWeb/"/> Defualt Grass layer for projection; <add key="defaultGrassName" value="gNS_K"/>
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 51 / 60
Time delay in milliseconds – time between execution report . If you have slow server increase number. (delay for all tools and for delayLsr for LSR tools) <add key="delay" value="10000"/> <add key="delayLsr" value="20000"/>
9.2 IIS settings Project UrbanSMS needs permissions for work in IIS. So it’s very importent that we set all settings in IIS.
Step 1: Add urbanSMS map in virtual directory. Go to wwwroot find map urbansms, right click select properties, go to taw “Web Sharing” and check Read, Write and Execute.
Step 2: Set directory Securuity on IIS to special user with administration permission and check “Integrated Windows authentication”.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 52 / 60
Step3: Go to Services and find “ASP.NET State Service”, set Startup Type to Automatic in start him.
Step 4: Instal MSChart which you can found on your CD.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 53 / 60
Click Next
Now you must accept license term and click Next
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 54 / 60
If was MSChart successfully install, then you get message “The software update has been installed successfully”.
And now restart your server.
9.3 Security The web application crates files in different folders. It is that for important to set the correct permission on the folder:
‐ Path: web application/BatchFile/ ‐ Path: web application/BatchFile/rule/ ‐ Path: web application/images/chart/ ‐ Path: web application/Log/ ‐ Path: web application/BatchFile/ ‐ Path: web application/Report/ ‐ Path: web application/Report/picture ‐ Path: web application/Report/txtResult ‐ Path: Grass path/etc/colors
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 55 / 60
Set “Ful Control”
9.4 Create folder and copy data Crate folder in C: (C:/Data/urbansms/GISData/) and then extract file from CD “UrbanSMS‐CE‐demoDATA_5m_V6.0.ZIP” and copy in this folder.
This is result: C:\Data\urbansms\GISData\5\USMS\
9.5 Batch files Path: web application/BatchFile/
9.5.1 Settings the BATCH file for GRASS The Web application holds the BatchFile folder (GrassSettings.bat), which must be replaced with your data from the GRASS. Run Grass from your desktop and then write in the CMD (in GRASS) :
‐ »set«. Edit GrassSettings.bat and change path from different folder to your path. (what you get in Grass only copy) . When this is done, please save your settings.
‐ r.in.poly ‐‐overwrite input="c:\Inetpub\wwwroot\urbansms\init_mask.txt" output=init_mask (c:\Inetpub\wwwroot\urbansms\ ‐> root path from your urbansms application)
Init_mask.txt file consists coordinates of Lower Left and Upper Right box for project area. Please be careful with data format.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 56 / 60
Sample of init_mask.txt
9.6 Troubleshooting the Web Application Web application can sometimes report errors. To overcome this and solve the problem, there are several scenarios:
‐ Web application Go to the webaplication/web.config and find the position <add key="EnableLoging" value="0"/>. Change the value to 1 . Looking at the webaplication/Log/log.data you view the error message and also other information.
‐ MapGuide Check the log from the MapGuide. Go to C:\Program Files\OSGeo\MapGuide\Server\Logs.txt. Exploring the logs you can make sure if something is wrong with the MapGuide.
‐ Report If the report is empty, this means there is a problem with the GRASS. Then you must restart server.
Some typical problems:
‐ Going into selected tool, the Required Dataset Availability usually holds some information. In case this is empty, it probably means that the name in the web application is different from the name in Maestro.
o Error in the webaplication/Log/log.data setLayerVisible ‐ Napaka: OSGeo.MapGuide.MgObjectNotFoundException: The specified object was not found. ‐ GetItem() line 117 file c:\osgeo\mapguide_21\mgdev\common\foundation\Data/NamedCollection
Solution: The data layer name in Maestro and web application must be identical. Please make sure this is true and correct the layer names.
10 Create database UrbanSMS application use data from database, for this reason we must crate database in SQL Server 2005 or 2008. You can use existing SQL server or install now. (SQL Server 2008 R2 Express)
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 57 / 60
Type name for database
For access from urbanisms application to database you have 2 option, you can use special user, or use network services. For bout case you must add permission on database. Go to Securty‐>Login‐>right click and find the user.
Search the user for login
The some procedure is for add new user in database Urban_SMS and give him owner permission.
Now you can execute SQL script which can you find on CD. (urban_sms.sql)
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 58 / 60
11 MapGuide settings
The default location for the MapGuide Open source:
C:\Program Files\OSGeo\MapGuide .
In the setup file you can find the ZIP file; www.zip, which must be copied to the C:\Program Files\OSGeo\MapGuide\Web\www\viewerfiles (this is one of the file settings for MapGuide)
Copy “webconfig.ini” from c:\Program Files\OSGeo\MapGuide\Web\www\ to c:\Inetpub\wwwroot\urbansms\.
Copy “serverconfig.ini” from CD to C:\Program Files\OSGeo\MapGuide\Server\bin\ and replace older “serverconfig.ini”. (if you have default installation, but first make backup)
Default login:
Username: Administrator
Password: admin007$
12 Administration of users Administrator can add, delete and edit all users in “User” tab.
Administrator can add new user with following next rules:
User name is customized, but ppassword must consist Letters (abc…),Numbers (123…) and Special characters(&%$#...) . For example:
abc123$
All together password should not be shorter than 6 characters together.
User can be deleted only at first setup, before start to use UrbanSMS application. If you want to disable login for specific user you just set value in field “IsLockedOut” to true.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 59 / 60
When user types wrongly his password more than three(3) times, password is locked and only Administrator can change “IsLockedOut” back to false.
13 Administration of SMS tools
When you finished with installation procedure you have to go to Administrative Modul and for each tool complete the following:
For NS tool the procedure is as follows:
Go to http://“domain”/urbansms/Admin/DetailData.aspx?toolid=2
(Domain in Celje case is for example: urbansms.celje.si:8000)
Step 1.
Open “Edit” under “Edit Input Data Nutrient Status (NS)” and confirm the settings with “Update”. It is enough to update first raw in a table only.
Step 2.
Open Edit” under “Data interpretation & legend” and confirm the settings with “Update”. It is enough to update first raw in a table only.
Step 3.
When finish step 1. and 2. you have to check the results with click on “Save and test” under “Tool Algorithms”.
Please see the picture and step numbers bellow.
Interreg CENTRAL Urban SMS
WP4 Soil Manager Suite
Page: 60 / 60
When you successfully finished “Save and test” button you should get (in case of NS tool for Celje) the following message
Successfully saved and tested! | Range of data: min = 3.666667 max = 5.000000 |)
Now you are sure that input data, equation and legend settings are correct for use in the Urban SMS application.
URBAN SMS Soil Management Strategy
This project is implemented through the CENTRAL EUROPE Programmeco-financed by the ERDF.
The paper in hand reflects the author‘s views and the Managing Authority of the INTERREG IV B CENTRAL Programme is not liable for any use that may be made of the information contained therein.
www.urban-sms.eu
This paper belongs to the following section of URBAN SMS work plan: WP4 Soil manager suite / 4.4 update according local tests / 4.4.4 soil manager suite
Contact details of project partner commissioning / responsible for this paper:
Borut Vrščaj, Agricultural Institute of Slovenia, Hacquetova 17, SI1000 Ljubljana, SI, [email protected]