Add v1.1.1 FGDC editor to a previous Geoportal release

The Geoportal Server version 1.1.1 release contains a new FGDC metadata editor based on the Geoportal XML Editor (GXE) engine. For those organizations that cannot upgrade to version 1.1.1 yet, this document outlines a procedure to incorporate GXE-based FGDC metadata editor from Geoportal Server version 1.1.1 into a previous Geoportal release.

Example Assumptions:

• System environment is Windows OS with Apache Tomcat as the web container
• Geoportal Server (pre-v1.1.1) deployed in a webapps folder

Procedure:

1. Download and unpack Geoportal Server v.1.1.1
   1. Download geoportal-1.1.1
   2. Unzip to folder geoportal-1.1.1
   3. Navigate to the sub-directory ..\geoportal-1.1.1\Web Applications\Geoportal
   4. Copy Geoportal.war and rename the file extension to .zip
   5. Unzip .zip to a folder
2. Stop the Tomcat service (from the services.msc control panel)
3. Add new GXE FGDC files from Geoportal - Copy" to the deployed geoportal
   1. Copy the fgdc folder from geoportal - Copy\WEB-INF\classes\gpt\gxe to the deployed geoportal gxe folder, webapps\geoportal\WEB-INF\classes\gpt\gxe
4. Add the new resource key-value pairs for the new FGDC editor
   1. Open the gpt.properties file from geoportal Copy in a text editor (in geoportal - Copy\WEB-INF\classes\gpt\resources)
   2. Copy the block of text pertaining to the GXE FGDC editor:
      1. Find the line starting # GXE FGDC Editor (line 3425)
      2. Use this as the start of the text block copy
      3. Find the line starting # end GXE FGDC timeinfo (line 3872)
      4. Use this as the end of the text block copy
      5. Copy the block of text into the clipboard
   3. Open the gpt.properties file from the deployed geoportal in a text editor (in webapps\geoportal\WEB-INF\classes\gpt\resources)
   4. Go to the end of the deployed gpt.properties and paste the block of text pertaining to GXE FGDC resources
   5. Save and close gpt.properties
5. Update the fgdc-definition file
   1. Go to the deployed geoportal webapps\geoportal\WEB-INF\classes\gpt\metadata\fgdc folder and rename fgdc-definition.xml to fgdc-definition-old.xml
   2. Copy the fgdc-definition.xml file from geoportal - Copy\WEB-INF\classes\gpt\metadata\fgdc to the deployed geoportal webapps\WEB-INF\classes\gpt\metadata\fgdc folder
6. Add the new GXE javascript functions
   1. Go to geoportal - Copy\catalog\js folder and copy the v1.1.1 folder
   2. Go to the deployed geoportal folder webapps\geoportal\catalog\js and paste the v1.1.1 folder
7. Update gxeEditorBody.jsp
   1. Go to the deployed geoportal folder webapps\geoportal\catalog\publication and edit gxeEditorBody.jsp in a text editor
   2. Find the line referencing gxe.js (line 49)
   3. Edit the path to the gxe.jsp to reference the new v1.1.1 folder: <script type="text/javascript" src="&lt;%=request.getContextPath()%">/catalog/js/v1.1.1/gxe.js"></script>
   4. Save and close the file
8. Test the new FGDC editor in your deployed geoportal
   1. Clear the logs by deleting all .log files in the Tomcat logs folder
   2. Start the Tomcat service from the services.msc control panel
   3. Wait for a minute
   4. Go to the Tomcat logs folder and open the gpt log file in a text editor
   5. Look for any ERROR messages
      1. If you see ERROR messages, something is wrong review all the previous steps
      2. If there are no ERROR messages, proceed to the next step
   6. Open the deployed geoportal in a web browser
   7. Log in as a publisher or administrator
   8. Go to the Administration tab and click on Add (next to Manage, under the main navigation bar)
   9. Select Use dedicated editor to create metadata manually and click Proceed button
   10. On the Create Metadata page, you should see an option for FGDC now, instead of FGDC Best Practice. (If you do not see this change, go back and double-check the steps pertaining to the fgdc-definition.xml file or gpt.resources)
   11. Select FGDC from the list and click the Proceed button
   12. On the Metadata Editor page, you should see the title FGDC under the Save as Draft and Save buttons, and you should see tabs for the FGDC CSDGM sections.
       1. If you get an error or do not see the CSDGM sections, go back and review the steps pertaining to gxe.js and the gxe files
       2. If you do see the FGDC CSGDM sections, then SUCCESS! ... Back up your deployed geoportal and enjoy using the GXE-based FGDC metadata editor.

---

Back to Customizations