Dave, Your best bet is to have a, say Windows 7 / IIS, set-up that was configured by the installer as a reference. The MapGuide documentation used to have a section for manual config but it has not been updated for a while so while the theory is there the exact steps will not be. You also need to have a knowledge of IIS configuration but it's something along the lines of the list below. If anyone could correct any terminology or enhance the list please feel welcome!
-1) Ensure that .NET, IIS and the management console features are all installed on your VM. For Azure services you also need to add an HTTP endpoint. As these are not MapGuide config specific I'm not going into those generic details for running an IIS server on Azure here. 0) Install MapGuide 2.4 with the .NET following the install wizard and selecting manual configuration. 1) Create a new "mapguide" application pointing to [INSTALL_DIR]\MapGuide\Web\www 2) I would recommend creating a dedicated application pool for this 3) Within the "mapguide" application also create applications from the "mapagent" and "mapviewernet" folders 4) If required by your solution create a "mapviewerajax" application pointing in parallel to the "mapviewernet" folder 5) Within the "mapagent" application add a hander mapping for "mapagent.fcgi" as an IsapiModule pointing to [INSTALL_DIR]\MapGuide\Web\www\mapagent\isapi_MapAgent.dll 6) If you need PHP \mapadmin access add a handler mapping for "*.php" as a FastCgiModule pointing to [INSTALL_DIR]\MapGuide\Web\Php\php-cgi.exe Test with http:\\localhost\mapguide\mapagent\index.html - goto "other" and "create session" If I missed anything please post back! Crispin -- View this message in context: http://osgeo-org.1560.n6.nabble.com/MapGuide-2-4-on-Azure-Windows-Server-2012-NET-4-5-tp5007390p5018596.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
