Skip To Content

Post-Deployment Actions

Out-of-the-box, the Geoportal will be implemented with default values. It is strongly recommended that all users make modifications to their Geoportal instance prior to going live on a production system. Some of the most important post-deployment actions are provided below.

Customize the User Interface for your Organization's Look and Feel

It is important to customize your geoportal to distinguish it from the default look and feel, and integrate with the other web pages in your organization. For detailed information on customizing the geoportal user Interface, please refer to the section on Geoportal Customizations.

Modify Default Usernames and Passwords

If you followed the installation guide closely during your Geoportal setup, you are likely using default usernames and passwords as outlined in the installation guide or defaulted in the gpt.xml configuration file. If you do not change the defaults, your Geoportal is vulnerable for manipulation by anyone who also has a Geoportal instance, since they are knowledgeable about the default username and password settings. It is therefore strongly recommended that once your Geoportal goes into production, you reset the default usernames and password. It is also recommended to encrypt passwords in your Geoportal configuration files. To encrypt passwords please see Encryption Concepts.

Schedule Synchronization

A production geoportal likely will connect to other metadata repositories for synchronizing resources in the geoportal catalog. When you deploy the geoportal, it is important to make a plan for which repositories will be synchronized, how often, and what other network resources should be registered and synchronized. See How to Publish Resources for more information on synchronizing resources.

Register the Geoportal Sitemap with Search Engines

The Geoportal automatically provides a sitemap file for your organization's deployed Geoportal. A sitemap is an xml file that shows the structure of a website, and provides additional information on the pages within the site. If a sitemap is submitted to search engines - such as Google, Yahoo!, or Microsoft - users may be able to find records from the Geoportal by using these search engines directly. has a helpful page on how to submit your sitemap. You can see your default geoportal sitemap by pasting the following in a web browser, replacing the host with your web server's name, port with your servlet engine port number, and contextPath with the name of your geoportal web application (geoportal by default):


Only resources that have their access level set to public are included in the sitemap.

After accessing this url, register the response with a search engine of your choice. You can modify the following sitemap settings in the \\geoportal\WEB-INF\classes\gpt\config\gpt.xml file. More details for each of these parameters are found in the comments within the gpt.xml file.
  • sitemap.baseUrl: the base URL for sitemap files
  • sitemap.documentUrlPattern: the URL pattern referencing documents within a sitemap
  • sitemap.urlsPerIndexFile: the maximum number of sitemap files to be referenced within the sitemap index file
  • sitemap.urlsPerSitemapFile: the maximum number of documents to be referenced within an individual sitemap file
  • sitemap.namespaceUri: the sitemap namespace URI, default =
  • sitemap.changefreg: the change frequency to be listed per document reference
  • sitemap.priority: the priority to be listed per document reference, 0.0 -> 1.0

Expose the Geoportal to OpenSearch

The Geoportal is exposed through OpenSearch, which means that certain browsers - such as Mozilla Firefox 3 and Internet Explorer 7 - will support searching the Geoportal as a search provider directly from the browser. For more information on Geoportal OpenSearch, see Add the Geoportal Search to a List of Search Providers. Because users may have many search providers registered with their browser, the name of your Geoportal search provider should be distinguishable. To change the name that will appear in the list of search providers from the default, do the following:

  1. Navigate to the \\geoportal\WEB-INF\classes\gpt\resources folder.
  2. Open the file in a text editor.
  3. Find the line that reads OpenSearch resources.
  4. In the catalog.openSearch.shortName parameter, change the associated Geoportal Search text to read something specific to your organization. This is the name that will appear in the list of search providers in the browser interface by default. For example, a good shortName parameter may include the name of your organization.
  5. You can also change the text associated with the catalog.openSearch.description parameter to match a description specific to your organization.
  6. Save the file.
  7. Restart the geoportal web application.

Update the CS-W Service Provider Information

When you first access your Geoportal's CS-W service through the GetCapabilities request - sample shown below - you will see a list of the capabilities of the service.

You will also see information about the service, such as what organization is providing the service and keywords. To customize this to reference information for your organization, navigate to the \\geoportal\WEB-INF\classes\gpt\metadata directory on your Geoportal server and edit the cswCapabilities.xml file accordingly. Restart the geoportal web application, and the next time you access the GetCapabilities request, you should see your updated provider information in the response.

Mulitlingual Support in the CS-W Capabilities Document

To enable meeting INSPIRE requirements for the Discovery service metadata and multilingual support, you will need to make further modifications to your geoportal cswCapabilities.xml file. Navigate to the \\geoportal\WEB-INF\classes\gpt\metadata\ directory, and open the cswCapabilities.xml file. This file contains additional information including the language for free text elements and an OGC-compliant Capabilities section called ExtendedCapabilities. The OGC CSW getCapabilities operation is extended to support an additional LANGUAGE parameter (only for HTTP GET binding) accepting 3-letter language codes as described in ISO 639-2/T.

Notice that free text elements have an xml:lang attribute. This is used by the Geoportal to determine which description corresponds to a specific language. To add more language-specific elements, you will create XML elements with the xml:lang attribute that indicate the language for the element values. The cswCapabilities.xml contains an example of Italian GetCapabilities, and the example XML elements are commented out as default. To see how the Italian example works, uncomment the XML elements.

The following XML fragment illustrates how to describe title and abstract in English and Italian:

< ows:ServiceIdentification >
 < ows:Title xml:lang =" eng "> This is a Geoportal exposing INSPIRE Discovery service metadata capabilities </ ows:Title >
< ows:Title xml:lang =" ita "> Questo Geoportale espone un servizio di Discovery per INSPIRE </ ows:Title >
< ows:Abstract xml:lang =" eng "> A catalogue service that conforms to the HTTP protocol binding of the OpenGIS Catalogue
Service ISO Metadata Application Profile specification (version 2.0.2) </ ows:Abstract >
< ows:Abstract xml:lang =" ita "> Un servizio di catalogo che si conforma al protocollo del servizio di catalogo di OpenGIS (versione 2.0.2) </ ows:Abstract >
 <!-- .... -->

The additional elements you need to fill in the ExtendedCapabilities section are defined accordingly with the INSPIRE Discovery Services Technical Guidance Version 3.1. The fragment relevant for multilingual support is the one defining the supported languages; an example declaring English (default language) and Italian follows:

< inspire_ds:Languages >
< inspire_ds:Language default =" true "> eng </ inspire_ds:Language >
< inspire_ds:Language > ita </ inspire_ds:Language >
 </ inspire_ds:Languages >

An example of a getCapabilities request asking for a response in Italian is shown below:

If the Italian (code: ita) language is supported the Geoportal, the catalog will return a capabilities document with Italian title and abstract; otherwise the title and abstract will be returned in the default language.

Multilingual Support in the CSW Exceptions

To support multiple languages in the CSW Exception report, you will need to create language-specific files for each supported language. The language-specific files should be placed under \\geoportal\WEB-INF\classes\gpt\resources directory.

The Geoportal detects and uses a language-specific file by looking at its file name to see if the file name has a language code. The naming convention for a language properties file is similar to the convention used for Localization of the Geoportal interface text: csw_{language code}.properties, except that the file name will use a three-letter language code. For example, if you add Italian as a supported language in your CS-W properties, name the file

The best way to create a language-specific file is to copy that exists in the resource folder, and name it to follow the above naming convention. Then, open the file and find the section titled "CSW exception codes". Translate string values for the exception codes into a target language. An example is shown below.

# CSW exception codes
catalog.csw.exceptionCode.InvalidFormat = [Italian] Invalid format
catalog.csw.exceptionCode.InvalidParameterValue  = [Italian] Invalid parameter value
catalog.csw.exceptionCode.MissingParameterValue =  [Italian]Missing parameter value
catalog.csw.exceptionCode.NoApplicableCode = [Italian]An exception occurred with no applicable code
catalog.csw.exceptionCode.OperationNotSupported = [Italian] Operation not supported
catalog.csw.exceptionCode.ResourceNotFound = [Italian] Resource not found
catalog.csw.exceptionCode.VersionNegotiationFailed = [Italian] Version negotiation failed