Overview
ArcGIS Server Geoportal Extension 9.3.1 SP1 requires certain software to be setup on the environment in which the Geoportal extension 9.3.1 SP1 will be installed. Please refer to each section below to verify that your environment meets the particular system requirement before proceeding with a Geoportal extension 9.3.1 SP1 installation.
-
Operating System
-
Database
-
Java
-
Web Server/Servlet Engine or Application Server
-
Browser Support
-
ESRI Software
-
Mail Server Access
-
Directory Server
Operating System
The following operating systems are supported for the Geoportal extension 9.3.1:
- RedHat Enterprise Linux AS/ES 5
- Windows XP SP2
- Windows 2003 Server SP2
- Windows 2008 Server Standard
- Windows 2003 Server 64-bit*
- Windows 2008 Server Standard 64-bit*
*Note: When installing any of the Geoportal Extension components on a 64-bit system, they must be installed into the "Program Files (x86)" directory.
Database
Geoportal extension 9.3.1 supports the following databases:
- Oracle 9i (9.2.0.7)
- Oracle 10g (10.2.0.4)
- Oracle 11g (11.1.0.7)
- Microsoft SQL Server 2005 SP2
- Microsoft SQL Server 2008
- PostgreSQL 8.3
Java
A full Java JDK is required. The following versions of Java are supported (both are available at http://java.sun.com/products/archive):
Servlet Container
The Geoportal extension web applications are based on Java Servlet technology and therefore require the use of a Servlet container.
The following software provide Java Servlet support and have been tested and verified to run the Geoportal extension 9.3.1 web applications:
- Apache Tomcat 5.5.x (requires Java JDK 5)
- Apache Tomcat 6.0.x (requires Java JDK 6)
- Oracle WebLogic 10 MP1 and 10.3
- Sun GlassFish 2.1
- Servlet Exec AS 6.0
*Note: Exposing the Geoportal extension 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.
Browser Support
The Geoportal extension has been tested for use on the following browsers.
- Internet Explorer 6.0*
- Internet Explorer 7.0
- Internet Explorer 8.0
- Mozilla Firefox 2.0
- Mozilla Firefox 3.0
*Note: Internet Explorer 6.0 is not able to display RSS. The Geoportal extension contains functionality for displaying search results in GeoRSS format. If you use the Internet Explorer 6.0 web browser, the Geoportal's GeoRSS display functionality will not work as expected.
ESRI Software
The following ESRI software is required before installing the Geoportal extension 9.3.1, service pack 1:
- ArcGIS Server 9.3.1 Standard Enterprise, service pack 1. It does not need to be installed on the same machine as the Geoportal web application, but the Geoportal web application should be able to consume the ArcGIS Server services.
- Microsoft .NET Framework 2.0 or higher should be installed on the machine hosting the Geoportal Harvesting Tool and the Harvesting Service. The machine hosting Desktop Tools does not need to be the same machine hosting the Geoportal, ArcGIS Server services, or database.
The following ESRI software is optional for the Geoportal extension 9.3.1:
- ArcGIS Desktop 9.3.1, service pack 1 (highly recommended).
*Note: ArcGIS Desktop .NET Framework must be enabled during installation of ArcGIS Desktop on any machine that will be using the Geoportal extension Clients. Screenshot below shows enabling .Net Framework during ArcGIS Desktop installation:
- ArcSDE 9.3.1, service pack 1. Only required if upgrading from a GPT 9.3 geoportal implementation or a Geoportal extension 9.3.1 impelmentation using the SDE-enabled database model.
In addition, Geoportal extension 9.3.1 requires the following:
- An ArcGIS Server Map Service, with a REST URL endpoint.
- 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:http://sampleserver1.arcgisonline.com/ArcGIS/rest/services/Locators/ESRI_Geocode_USA/GeocodeServer
- 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:http://sampleserver1.arcgisonline.com/ArcGIS/rest/services/Geometry/GeometryServer
For help on how to create Map services, Geocode services to be used for the Locator, and Geometry services, refer to the ArcGIS Server Help for each at:
*Note: Geoportal extension 9.3.1 service pack 1 does not use ArcIMS and deploys its own servlet web application for connecting to ArcCatalog. If you do not uninstall ArcIMS, the Geoportal extension 9.3.1 servlet.war cannot be deployed. If you plan to implement the Geoportal with the MetadataServer and ArcSDE, then you must uninstall ArcIMS and verify that the ArcIMS servlet web application is no longer present in the <Tomcat>\webapps folder before proceeding. If you are implementing the Geoportal without the MetadataServer and ArcSDE, then you have the option to leave ArcIMS installed. If you leave ArcIMS and the ArcIMS servlet application installed, then the only functionality that will be affected is the Geoportal extension's Publish Client desktop tool for ArcCatalog, which requires the Geoportal extension sevlet web application.
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 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 extension 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.