Skip To Content

Preinstallation requirements

There are two parts to a Esri Geoportal Server. The first part is the system hosting the Geoportal end point 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.

Geoportal host system requirements

The Geoportal host environment requires an operating system, a database, a full Java JDK, a web application server, and map services for the search, preview, and metadata editor maps. The Geoportal connects to an organization's LDAP structure and thus needs access to a directory server.

Refer to each subsection below to verify that your environment meets the particular system requirements before proceeding with a Geoportal installation.


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

Operating system

The following operating systems are supported for the Geoportal:

  • Red Hat Enterprise Linux AS/ES 5
  • Windows 2003 Server SP2
  • Windows 2008 Server Standard
  • Windows 2003 Server 64 bit
  • Windows 2008 Server Standard 64 bit
  • Windows 7 Ultimate, Professional Edition 32 bit
  • Windows Server 2008 R2
  • Windows Server 2012 Standard
  • Windows Server 2012 R2

When installing any of the Geoportal components on a 64-bit system, they must be installed into the Program Files (x86) directory.


Geoportal supports the following databases. The Geoportal database can be deployed on the same server or a different server than the geoportal web application:

  • Oracle 10g
  • Oracle 11g
  • PostgreSQL 8.4 (32 and 64 bit)
  • PostgreSQL 9.1 (32 and 64 bit)
  • MySQL 5.5
  • Microsoft SQL Server 2005 SP2 and SP3
  • Microsoft SQL Server 2008


The Geoportal source code is based on Java 6, but it has been tested to run on Java 7 as well. Java JDK 6 (32 or 64 bit) or Java JDK 7 (7 if you're using Tomcat 7.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. The following software provide Java Servlet support and have been tested and verified to run the Geoportal web application:

  • Apache Tomcat 6.0.32 and higher and Tomcat 7.0.x
  • Oracle WebLogic 11g
  • GlassFish 3.1 and GlassFish 3.1.2

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 (for example, port 8080). In those cases, a redirect from a web server (for example, 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 Geoportal 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 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 an 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 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.

ArcGIS Server Standard (optional)

ArcGIS Server does not need to be installed on the same machine as the Geoportal web application, but the Geoportal web application will need to consume a map service for the search, preview, and metadata editor maps, a locator service, and a geometry service. These are described below. A user should be able to consume the ArcGIS Server services hosted by your organization. The Geoportal requires the following services:

  1. A service for the basemap. The basemap can be an ArcGIS Server Map Server REST end point, or it can also be a WMS end point, a WMTS end point, or the OpenStreetMap service.
  2. An ArcGIS Server Locator Service. If you do not have the means to create a locator service, you may use the publicly available one at
  3. An ArcGIS Server Geometry service. If you do not have the means to create a geometry service, you may use the publicly available one at
For help on how to create map services, geocode services to be used for the locator, and geometry services, refer to About publishing services.

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 on an intranet system where the JavaScript API online cannot be referenced, 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 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
  • //webapps/geoportal/widgets/example.jsp
  • //webapps/geoportal/widgets/searchjs.jsp

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 has been tested for use on the following browsers:

  • Internet Explorer 7.0, 8.0 (Note: For correct display of the Geoportal Search page map and Preview maps, verify that you are running Internet Explorer 8 in Compatibility Mode), 9.0, 10, and 11.
  • Mozilla Firefox 3.0, 3.5, and later
  • Google Chrome
  • Apple Safari

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 plug-ins available for the browsers for viewing XML.

ArcGIS Desktop

ArcGIS Desktop is required for using the CSW clients, publish client, and WMC client. The Geoportal clients allow users to connect to the Geoportal from within ArcGIS Desktop to publish and search.


The ArcGIS Desktop .NET Framework option must be enabled during installation of ArcGIS Desktop on any machine that will be using the clients.