Installing Geoportal Server 2.6.4

The instruction for 2.6.4 is the same as 2.6.3.

Install Prerequisites

• Install AdoptOpenJDK 11

  • Download link: https://adoptopenjdk.net/.
  • Geoportal was tested with AdoptOpenJDK 11.

• Install Elasticsearch (6.x or higher)

  • Download link: https://www.elastic.co/downloads/elasticsearch
  • Geoportal was tested with Elasticsearch version 7.5.0.
  • Avoid Elasticsearch 7.8.0, it has a geometry related bug (see https://github.com/elastic/elasticsearch/pull/58786) that will cause issue with geoportal

• Install Tomcat 9.x

  • Download link: https://tomcat.apache.org/download-90.cgi
  • Installation guide: https://tomcat.apache.org/tomcat-9.0-doc/setup.html
  • Geoportal was tested with Tomcat 9.0.29.

We have built and tested Geoportal Server with the system environment above, it should work with other similar environments as well. It is found that the application does not work with Internet Explorer 11, please use newer versions or a different browser.

Deploy Geoportal Server

• Deploy geoportal.war to Tomcat (e.g. by copying geoportal.war file to the webapps folder).

• Quick updates of configuration

  • It is noticed that in some cases you need to update the nodes in app-context.xml in geoportal\WEB-INF\classes\config to the machine name to connect to Elasticsearch, e.g.

  		<beans:property name="nodes">
    		<beans:list>
    			<beans:value>gptsrv12r2</beans:value>
    		</beans:list>
    	</beans:property>
  

• Update your Geoportal essential configuration

  • Main configuration file
  • Security
  • Logging

• Restart Tomcat

• Run quick smoke test

  • Open geoportal web page (e.g. http://localhost:8080/geoportal)
  • Signin as gptadmin/gptadmin (top right)
  • Upload a few metadata records (top right)
  • Perform search (left panel), if search return the matching records, then the basic installation is working

• Perform additional configuration as necessary

Configure Geoportal Server

Main configuration file

The main configuration file for setting the cluster and node name(s) for Elasticsearch cluster is webapps/geoportal/WEB-INF/classes/config/app-context.xml. By default, Geoportal is configured to look on the localhost for a cluster named elasticsearch. If you need to change any of the Elasticsearch related configuration, please see Elasticsearch configuration.

Security configuration

You can configure various authentication options such as simple, LDAP, OAuth2 in Geoportal. The main configuration file for security is webapps/geoportal/WEB-INF/classes/app-security.xml.

• To configure geoportal to use simple authentication, see Security configuration simple
• To configure geoportal to use LDAP authentication, see Security configuration LDAP
• To configure geoportal to use ArcGIS authentication, see Security configuration ArcGIS

Logging

webapps/geoportal/WEB-INF/classes/log4j.properties Logging properties. You can modify the location of the log file by updating: log4j.appender.file.File

Elasticsearch mappings for the "metadata" index webapps/geoportal/WEB-INF/classes/config/elastic-mappings.xml Contains the Elasticsearch mappings for the "metadata" index, used when Geoportal auto-creates the "metadata" index. Whenever you create a "metadata" index within Elasticsearch, you'll need to include these mappings within your request "PUT" request.

Make additional metadata elements discoverable

Click here for details.

Customize search panel

Click here for details.

Add support for another language in the interface

Click here for details.

Note: There are many other configuration options in Geoportal Server, please visit the Configuration and Customization section of wiki home for more details.