wiki:Release/3.1/Notes

Version 1 (modified by jng, 6 years ago) (diff)

--

MapGuide 3.1 Release Notes

MapGuide Open Source 3.1 Beta 1 is now available

Installation

Windows 32 bit installer:

  • [TBD]
    • Size: TBD
    • md5: TBD

Windows 64 bit installer:

  • [TBD]
    • Size: TBD
    • md5: TBD

Windows 32-bit MgInstantSetup bundle:

  • [TBD]
    • Size: TBD
    • md5: TBD

Windows 64-bit MgInstantSetup bundle:

  • [TBD]
    • Size: TBD
    • md5: TBD

Ubuntu 12.04 install script (32-bit):

  • [TBD]
    • Size: TBD
    • md5: TBD
  • Uninstall script: [TBD]
    • Size: TBD
    • md5: TBD

Ubuntu 12.04 install script (64-bit):

  • [TBD]
    • Size: TBD
    • md5: TBD
  • Uninstall script: [TBD]
    • Size: TBD
    • md5: TBD

CentOS 6.x install script (32-bit):

  • [TBD]
    • Size: TBD
    • md5: TBD
  • Uninstall script: [TBD]
    • Size: TBD
    • md5: TBD

CentOS 6.x install script (64-bit):

  • [TBD]
    • Size: TBD
    • md5: TBD
  • Uninstall script: [TBD]
    • Size: TBD
    • md5: TBD

Sample Data

This release includes a new version of the Sheboygan Sample data set demonstrating features introduced in this and recent versions of MapGuide

  • [TBD]
    • Size: TBD
    • md5: TBD

Extra Files

The install packages for this release of MapGuide omit several USA-specific CS-Map grid data files which are only required if your spatial data uses a coordinate system that involves an NSRS datum. See CS-Map RFC 7 for more information.

As a result, our installation packages are now up to 150 MB lighter as a result of this omission.

Should you require these grid data files, you can download them here:

  • [TBD]
    • Size: TBD
    • md5: TBD

To install these files, unzip them into the Usa directory of your CS-Map installation (eg. C:\Program Files\OSGeo\MapGuide\CS-Map\Dictionaries\Usa) and restart your MapGuide Server

Fusion build tools

Fusion build tools is a zip file containing the build.xml and associated build tools required to "re-compile" fusionSF.js and fusionSF-compressed.js on a production fusion installation.

Use the Fusion build tools if you have made patches and/or modifications to your fusion installation, and you need to build a new fusionSF.js and/or fusionSF-compressed.js

In order to use the Fusion build tools, you need to have Apache Ant installed.

  • [TBD]
    • Size: TBD
    • md5: TBD

To use the Fusion build tools, extract the zip file contents into your fusion directory and navigate to this directory in the command prompt and execute the following command:

ant compress

This will re-build fusionSF.js and fusionSF-compressed.js under fusion\lib

Due to the default installation location (under Program Files), you may need to do this under a UAC-elevated command prompt or fix the directory permissions so that normal users can create/modify files.

Windows Compatibility

32-bit64-bit
Windows 10Yes+Yes+
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

MapGuide

  • New Layer Definition cache for faster Layer Definition access MapGuide RFC 151
  • Web Tier component updates MapGuide RFC 155
    • PHP updated to 5.5.33
    • Apache updated to 2.4.18
    • Tomcat updates to 7.0.68

Fusion

  • TBD

New schema revisions

  • None

New/Changed? APIs

  • None

Other

Please report any defects.

FDO Notes

MGOS 3.1 is compatible with FDO 4.1

This release is built against the FDO 4.1 branch

Installer notes

Installing MGOS 3.1 (via the windows installer) alongside any older release 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 by grabbing the tomcat windows service installer from the Tomcat download site

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

Should you choose to uninstall the Linux build of this release at any time, download and the respective uninstaller script. This ensures that any proper service un-registration is also performed.

Known Issues

  • On Ubuntu, bash needs to be the default shell due to bash-isms in the service control scripts (#2497)
  • Installing msttcorefonts for your specific distro is strongly recommended to avoid the case of "hieroglyphic" labels. You can specify the path of your msttcorefonts installation in serverconfig.ini to have MapGuide load these fonts in on startup.
  • Using the Linux builds of MapGuide on distributions they were not built for is not supported. If you want to run MapGuide on:
    • Versions of Ubuntu newer than 12.04
    • CentOS 7 or higher
    • A different Linux distribution

Then consider running MapGuide in a docker container that is based on Ubuntu 12.04 or CentOS 6.x. This installation method is not supported and is only mentioned here for informational purposes.

  • The following FDO providers may or may not not be functional in 64-bit Linux builds of MapGuide
    • SHP (spatial indexing code not working properly in 64-bit, will cause incorrect spatial queries. Workaround: Use OGR provider)
    • MySQL (un-tested, please provide feedback)
    • PostgreSQL (un-tested, please provide feedback)
    • King.Oracle (un-tested, please provide feedback)
    • WFS (un-tested, please provide feedback)
    • WMS (un-tested, please provide feedback)
  • The following FDO providers have been validated in a 64-bit Linux environment by their respective FDO unit test suites (ie. All tests pass). Feedback on these providers in 64-bit Linux still welcome/appreciated:
    • SDF
    • SQLite
    • GDAL
    • OGR
  • 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
  • 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-3.1.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.