This article describes known and possibly blocking issues and their solution for the initial release of GeoMedia WebMap 2018 (version 16.5). The list will be ordered by date when the issue has been found.
Following statement in the installation guide may be confusing as it was not properly updated to 2018 release:
Be aware that some of the configuration elements prepared in the Administration Console, specifically “Maps & Workspaces” and “Search Configuration” may be lost when removing the Hexagon Geospatial 2015 (prior to EP06) products containing the Geospatial Portal component. Therefore before uninstalling the GeoMedia WebMap 2015 run the Administration Console 2015 Configuration Update executable and follow the instructions on the screen in order to preserve the configuration elements when upgrading to version 2016. After running the tool, you can proceed with the uninstallation the 2015 versions of software and install the 2016 release. The configuration elements will be preserved in the 2016 installation.
Interpret all versions 2016 occurences as 2018.
Administration Console 2015 Configuration Update mentioned can be downloaded here.
This problem consists of two parts:
There are two hotfixes available, please contact support in order to receive the patches.
For the issue# 1, there also exists a workaround, mentioned in this Community topic.
Although this problem can have various causes, one of them can be, that the WFS service was registered in the Administration Portal with URL having some default parameters such as service=WFS&request=GetCapabilities. In such case, the Administration Portal does not trim the standard OGC parameters from the URL and Consumer Portal sends redundant parameter/values pairs to the WFS service which leads to unexpected response.
Register a WFS service in the Administration Portal using only the base URL, e.g. http://myserver/WFS/service.svc/get
Consumer Portal will not load on a browser with default language set to Portuguese [pt].
There's missing JS file for the [pt] language code. To fix this, copy over './nls/pt-PT/ControlsOverride.js' to './nls/pt/ControlsOverride.js'. You can do this directly in the Consumer Portal template.