Post Deployment Actions
When the geoportal web application is first deployed per the installation guide, it will be configured with default values. It is strongly recommended that you make certain modifications to the geoportal instance prior to going live on a production system. Some of the most important post-deployment actions are provided in this topic.
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.
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 the Encryption Concepts section in the Security Concepts topic.
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.
The geoportal web application 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. Sitemap.org 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): http://host:port/contextPath/sitemap
Note: 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 = http://www.sitemaps.org/schemas/sitemap/0.9
- 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
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:
- Navigate to the \\geoportal\WEB-INF\classes\gpt\resources folder.
- Open the gpt.properties file in a text editor.
- Find the line that reads OpenSearch resources.
- 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.
- You can also change the text associated with the catalog.openSearch.description parameter to match a description specific to your organization.
- Save the gpt.properties file.
- Restart the geoportal web application.
When you first access your geoportal's CS-W service through the GetCapabilities request - sample shown here - you will see a list of the capabilities of the service. http://serverName:portNumber/geoportal/csw/discovery?Request=GetCapabilities&Service=CSW&Version=2.0.2
You will also see information about the service, such as what organization is providing the service and keywords. To customize this to reference 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.
When testing, you may discover that your metadata records are receiving validation errors when you attempt to publish them to your Geoportal. In this case, you have two choices if you want the metadata to pass validation: 1) update the metadata with the required missing information, or 2) adjust the Geoportal's validation rules for that metadata standard/profile. To do the latter, see Customize Metadata Validation. Note that if you are publishing metadata by harvesting a THREDDS server, you will likely need to change the validation rules for the iso-19115-2-definition.xml file to be less stringent.
Next to Customizations