wiki:Release/2.6/Notes

Version 18 (modified by jng, 11 years ago) ( diff )

--

MapGuide 2.6 Release Notes

MapGuide Open Source 2.6 Beta 1 is now available

Table of Contents

  1. Installation
  2. Windows Compatibility
  3. Major New Items
    1. Fusion
    2. New schema revisions
    3. New/Changed APIs
    4. Other
  4. FDO Notes
  5. Installer notes
  6. Linux Notes
  7. Known Issues

Installation

Windows 32 bit installer:

Windows 64 bit installer:

Windows 32-bit MgInstantSetup bundle:

Windows 64-bit MgInstantSetup bundle:

Ubuntu 12.04 install script (32-bit):

CentOS 6.x Install Script:

Windows Compatibility

IMPORTANT: Due to upgrading to VS 2012 as the default compiler on Windows, MapGuide Open Source 2.6 will no longer support Windows XP or Windows Server 2003 in either IIS or Apache configurations. ​MapGuide Open Source 2.5 is the last release to support Windows XP and Windows Server 2003

32-bit64-bit
Windows VistaMaybe+Maybe+
Windows 7YesYes
Windows Server 2008Yes+Yes+
Windows Server 2008 R2N/AYes
Windows 8Yes1Yes1
Windows Server 2012N/AYes1
Windows 8.1Maybe1Maybe1

+ Not tested, but similar enough to Windows 7 to theoretically work

  • IIS configuration will probably not work. Apache config should work due to its self-contained nature

1 IIS/.Net successfully tested on Windows 8 64-bit and Windows Server 2012. Windows 8 32-bit is similar enough to theoretically work. Apache config untested

Windows RT (ie. Windows 8 on ARM devices) is not a supported platform for installing MapGuide Open Source

Major New Items

Fusion

  • OpenLayers upgraded to 2.13.1 (​MapGuide RFC 132)
  • ​TraceKit integration for better error handling
  • Templates now better handle display of Fusion errors.
  • ​Source map support for modern browsers allowing fusionSF-compressed.js to be "debugged" without any template modifications
  • QuickPlot now supports including a legend in the PDF plot and plot elements can be toggled on/off in its UI
  • New Geolocation widget for zooming/panning to the user's physical location via the HTML5 geolocation API
  • New CoordinateTracker widget for display mouse coordinates in various EPSG-based coordinate systems
  • Supports the new CREATERUNTIMEMAP operation for improved initial loading performance.
  • Supports the enhanced QUERYMAPFEATURES operation for improved selection performance with reduced AJAX round-tripping.
  • Redline enhancements
    • Redline Layers can now use ​Advanced Stylization, which allows for greater labelling flexibility
    • Widget now supports specifying desired data store format and available geometry types up-front, bypassing several user setup steps when creating a new redline layer.
    • Multiple redline objects can be selected/deleted/text updated at once

New schema revisions

New/Changed APIs

  • New CREATERUNTIMEMAP and DESCRIBERUNTIMEMAP operations in the mapagent that allow for a client application to create new MgMap instances and to be able to describe its layer/group structure over HTTP without needing to write any .net/PHP/Java code using the MapGuide Web API. (​MapGuide RFC 134 and ​MapGuide RFC 137)
  • New enhanced QUERYMAPFEATURES mapagent operation that allows for enhanced feature querying capabilities without the need for additional roundtrips to .net/PHP/Java web tier glue for missing information (​MapGuide RFC 126)
  • The EXECUTESQLQUERY mapagent operation has been removed from the mapagent and is no longer supported (​MapGuide RFC 136)
  • Selection rendering now respects the alpha component of the selection color you specify. However for compatibility purposes, an alpha component of FF will retain the old transparency override behavior.

Other

  • New Stylization Expression Functions for greater stylization flexibility (​MapGuide RFC 133)
  • New samples landing page and code samples demonstrating integration with the ​OpenLayers web mapping library.
  • Bundled PHP updated to 5.5.11 (​MapGuide RFC 138)
  • Bundled Apache updated to 2.4.9 (​MapGuide RFC 138)
  • Bundled versions of Apache and PHP use OpenSSL 1.0.1g that is not affected by the heartbleed security vulnerability.
  • Bundled Tomcat updated to 7.0.42 (​MapGuide RFC 138)

Please report any defects.

FDO Notes

MGOS 2.6 is compatible with FDO 3.9.

This release is built against the FDO 3.9 branch. The ArcSDE provider is included from the RC2 windows binary SDK.

Installer notes

Installing MGOS 2.6 (via the windows installer) alongside MGOS 2.5 or older releases is not a currently supported configuration. Consider using the MgInstantSetup bundle instead if you desire side-by-side installation

The installer does not currently support IIS Express as an IIS configuration option.

Please observe the updated software requirements if you are using .net and/or IIS configuration:

  • IIS (all versions) require FastCGI for IIS to be installed. For IIS7 and above, you can install FastCGI by enabling the CGI feature of your IIS installation. See ​this link for more information.
  • The supported .net Framework version for the MapGuide .net API is 4.0. You must have this version of the .net Framework installed before proceeding with installation.

Java configuration requires Java 6 (1.6.0) or higher.

The MgInstantSetup bundles only work with IIS7 or higher if you choose to use this web server. You must still satisfy the .net and FastCGI software requirements required for this configuration.

To assist new MapGuide users and developers, the installer also now bundles the following optional components:

  • .net/PHP/Java viewer samples
  • MapGuide Developer's Guide in HTML format with updated content
  • .net/PHP/Java Developer's Guide Samples

All bundled samples require the ​Sheboygan dataset to be loaded into the MapGuide Server.

A restart of Apache and/or IIS may be required for PHP to work.

For the InstantSetup bundles, the MgInstantSetup utility requires .net Framework 4.0 to run. This is in addition to whatever existing software requirements imposed by this release of MapGuide Open Source.

For Tomcat configuration, the installer currently does not install Tomcat as a service (#953). You will have to do this manually post-installation.

Also ensure that you install the JVM of the same bitness as your installation of MapGuide. For example, you will get a java.lang.UnsatisfiedLinkError if you attempt to run a Tomcat from a 32-bit MapGuide installation on a 64-bit JVM. If you have both 32 and 64-bit JVMs installed, you must ensure that the Tomcat bundled with MapGuide is using the correct one. Tomcat will generally use the one indicated by the JAVA_HOME environment variable, so this may have to be set and/or overridden. up

Note that upgrading Apache from 2.2.x to 2.4.x has introduced changes to some configuration directives. If you have any custom httpd directives defined in your current MapGuide installation, please consult the ​upgrade notes for any changes you have to do when migrating/upgrading your Apache-based MapGuide installation to this release.

If you have PHP-based MapGuide applications, consult the ​5.3 to 5.4 migration guide and ​5.4 to 5.5 migration guide for any API and compatibility issues that may be present in your MapGuide application as a result of moving to PHP 5.5

Linux Notes

For the CentOS build of MapGuide, the xerces-c library used has been built to use the iconv transcoder (instead of the default GNU iconv transcoder). This is to ensure a workable MapGuide build for CentOS. Any side-effects as a result of this change are currently not known and users are encouraged to report any issues that may be a result of this change.

Known Issues

  • Fusion: Bing/VirtualEarth commercial layers may conflict with Google layers if they are both specified in a Flexible Layout. If you have a Bing/VirtualEarth layer as the default, switching to a Google layer in your Fusion application will cause the Google layer to be displaced and vice versa.
  • #2252: It is not possible to call MgFeatureService::UpdateFeatures() with a NULL MgTransaction in the PHP API
  • #2441: v2.6 QUERYMAPFEATURES may not return attributes of selected points when selection is done at the edge of the point.
  • Installer may generate a providers.xml entry for the ArcSDE provider if all providers are enabled in the "Feature Selection" dialog even if the installer does not actually bundle the ArcSDE provider. You can simply remove this entry from providers.xml after installation if this is the case.
  • CentOS: mgserver may throw double-free errors on service startup or server shutdown. Should not affect server behaviour.
  • The Performance Profiler on Linux may not work due to insufficient permissions to save the generated report files. To fix this, ensure the directory /usr/local/mapguideopensource-2.6.0/webserverextensions/www/mapadmin/profilingmapxml on linux has sufficient write permissions for the user account that the PHP executable runs under.
  • For an InstantSetup-based install with an Apache configuration, the Performance Profiler is ​hard-coded to always use mapviewerjava if it exists for displaying the map viewer for capturing extents for profiling. If you did not choose a Java configuration you will get the ajaxviewer.jsp source instead of the expected map viewer. To resolve this, delete the mapviewerjava directory
  • Uninstallation can leave "ghost" IIS virtual directories behind, which currently is any virtual directory / application you create inside the mapguide virtual directory that was not created by the installer These "ghost" directories may impact on future installations. To ensure these "ghost" directories are completely gone after uninstallation, use the appcmd.exe utility to remove these virtual directories. You can find out what virtual directories are still there by running

appcmd.exe list vdir

  • PHP Viewer and Developer's Guide samples will not work if the PHP viewer feature is not enabled. Likewise for .net and Java. Nothing in the installer will prevent you from making such a choice.
  • For the IIS configuration or Apache configuration with a custom http port, you will have to update the WFS and WMS server name configuration properties via the MapGuide Site Administrator after installation if you intend to use such features. This is currently set to localhost:8008 for both.
Note: See TracWiki for help on using the wiki.