Skip to content

Preinstallation 1.2.8

Jump to bottom
zguo edited this page Oct 13, 2017 · 3 revisions

There are two parts to a Geoportal Server system. The first part is the system hosting the geoportal endpoint and web application itself. The second part is the end user system made up of the machines that access the deployed geoportal. System requirements differ between the two parts, and are described in the sections below.

Table of Contents

Geoportal host system requirements

The geoportal host environment requires an operating system, a database, a full Java JDK, a web application server, and access to ArcGIS Server services (ArcGIS Server map, locator, and geometry services for the geoportal search map and place finder). The geoportal connects to an organization's LDAP structure, and thus needs access to a directory server.

Please refer to each subsection below to verify that your environment meets the particular system requirement before proceeding with a Geoportal Server installation.

Note: System configurations not listed in this topic may work for your implementation; however, ones listed here were tested and any compatibility issues were documented or resolved, whereas deploying the Geoportal Server in an unlisted system configuration may result in unknown issues.

Operating System

The following operating systems are supported for the Geoportal Server:

  • RedHat Enterprise Linux AS/ES 5
  • Windows 7 Ultimate, Professional Edition 32-bit, 64-bit
  • Windows 10 Home, Pro and Enterprise
  • Windows 2008 Server Standard
  • Windows 2008 Server Standard 64-bit
  • Windows Server 2008 R2
  • Windows Server 2012 Standard
  • Windows Server 2012 R2
Note: When installing any of the Geoportal Server desktop components on a 64-bit system, they must be installed into the Program Files (x86) directory.

Database

The Geoportal Server supports the databases below, if you have a slightly different version, most time it should work as well even though not supported. The Geoportal Server database can be deployed on the same server or a different server than the geoportal web application:

  • Oracle 11g
  • Oracle 12c
  • PostgreSQL 9.2.14 (32 and 64 bit)
  • PostgreSQL 9.3.10 (32 and 64 bit)
  • PostgreSQL 9.4.5 9.4.8
  • Microsoft SQL Server 2012
  • Microsoft SQL Server 2014
  • MySQL 5.6.x

Java

The Geoportal source code is based on Java 6, it works with Java 7 and Java 8 as well. Java JRE/JDK 6 (32 or 64 bit), Java JRE/JDK 7 (7 if you're using Tomcat 7.x), or JRE/JDK 8 (8 if you're using Tomcat 8.x) is required on the server hosting the geoportal web application.

Servlet Container

The geoportal web application is based on Java Servlet technology and therefore requires the use of a Servlet container. Most of the Geoportal Server development and testing was on Apache Tomcat environment. The following software provide Java Servlet support to run the geoportal web application.

Note: Exposing the geoportal web applications on port 80 (the default Http port) will require planning and coordination with your organization's IT and network staff. For example, Tomcat can be configured as a web container to support network requests on port 80. However in most cases, Tomcat is configured to respond to requests on a port different than port 80 (e.g. port 8080). In those cases, a redirect from a web server (e.g. IIS or Apache HTTP) or from a reverse-proxy server will be required to send URL requests for a geoportal web application to Tomcat for handling. In the case of WebLogic and GlassFish, they are application servers that also provide web server support. WebLogic or GlassFish may be configured to provide front-end port 80 Http support for the geoportal web applications. Alternatively, a reverse proxy may be used to provide URL redirection requests for a geoportal web application to either the web application's Http web server or to the Servlet container.

Mail Server Access

A Mail server is necessary for the following notification functionality:

  • Feedback function to contact geoportal administrators.
  • Data download notification functionality
  • Harvesting Notifications
If a mail server with a network accessible URL is not available, the features listed above will not work correctly.

Directory Server and LDAP

For full functionality of user-based roles, an LDAP-enabled Directory Server is required for the authentication. You may use an existing Directory Server that supports LDAP v.3, if you already have one in your organization. If you currently do not have a LDAP Directory Server, and you wish to have user-based role functionality, you will need to install a Directory Server. Instructions for installing Apache Directory Server (an open source directory server) are available in the Geoportal Server installation guide.

Simple authentication option: When no LDAP Directory Server is available, the geoportal may be configured for a single administrative account. This is a quick option for an introductory setup, but is not recommended for production environments. Users wishing to use simple authentication need not install additional directory server software. Setting up simple authentication can be achieved solely via the geoportal configuration file and is described in detail in the installation guide.

A Map Service

The geoportal will reference a map service for its Search page search map. The geoportal web application may consume ArcGIS Server services (hosted by your or another organization), a WMS service, or the OpenStreetMap web map for the geoportal search page.

For help on how to create Map services, refer to the ArcGIS Server Help for each at:

ArcGIS Server Locator and/or Geometry services (optional)

These will also be used in your search map - the locator service is necessary if you want to use the gazetteer drop-a-point-on-the-search-map functionality. The geometry service projects the bounding boxes of the metadata search results upon the search map.

For help on how to create Geocode services to be used for the Locator, and Geometry services, refer to the ArcGIS Server Help for each at:

Esri JavaScript API

By default, the geoportal will reference the JavaScript API available online to render the geoportal Search Page search map, the Preview Page map, the Search Widget for HTML Sample, and the map used to render the footprint of the metadata on the Details page. If you are deploying the Geoportal Server on an intranet system where the JavaScript API online cannot be referenced, then you can reference a locally installed instance of the JavaScript API instead. Instructions for installing the JavaScript API locally are part of the ArcGIS JavaScript API product. The following Geoportal Server files will need to be updated with the local JavaScript API reference:

  • //geoportal/WEB-INF/classes/gpt/config/gpt.xml
  • //geoportal/catalog/skins/lookAndFeel.jsp
These files contain the reference, but only as a sample and thus don't need to be updated for regular functioning of the geoportal:
  • //geoportal/widgets/example.jsp
  • //geoportal/widgets/searchjs.jsp
  • //geoportal/catalog/publication/arcgised.jsp

A note about ArcIMS

The Geoportal Server uses its own servlet web application for allowing ArcGIS Desktop 9.3.x instances to connect through the Geoportal Publish Client. You must uninstall ArcIMS on the machine hosting the geoportal's servlet.war file, as ArcIMS has its own servlet.war file and this will conflict with the geoportal's. If you do not uninstall ArcIMS and delete the ArcIMS servlet.war file, users will not be able to publish to your geoportal using the Publish Client in an ArcGIS Desktop 9.3.x environment.

ArcGIS WebAppBuilder

The GeoportalSearch and AddToMap widgets requires ArcGIS WebAppBuilder 2.0 or above.

Geoportal end user system requirements

The supported browser and Esri software requirements are recommended for users to connect to and use the deployed geoportal. These browsers and Esri software are not required for the system hosting the geoportal, but instead for the user environments connecting to it.

Browser Support

The Geoportal Server are supported on the following browsers:

  • Internet Explorer 11 and above.
  • Mozilla Firefox 32 and above
  • Google Chrome 32 and above
  • Apple Safari
Note: Chrome and Safari browsers parse out the XML tags when viewing raw XML. This will affect the ability to view the raw metadata in the geoportal, as users only see text and not the associated metadata parameter tags. This behavior is a Web Browser behavior not geoportal behavior. The workaround to view raw metadata XML is to view the metadata XML page's source, or install appropriate plugins available for the browsers for viewing XML.

ArcGIS Desktop

The Geoportal Clients allow users to connect to the geoportal from within ArcGIS Desktop to publish and search. You can use the Geoportal Clients for ArcGIS 10.5.1 with ArcGIS 10.5.1. Caution: The ArcGIS Desktop .NET Framework option must be enabled during installation of ArcGIS Desktop on any machine that will be using the Geoportal Clients.

Return to Installation

Clone this wiki locally