-
Notifications
You must be signed in to change notification settings - Fork 62
Installing Geoportal Server 2.0.0
Urban MacGillivray edited this page Sep 6, 2016
·
4 revisions
- Install Elasticsearch (2.3.1 or higher, this will only work with a 2.X version of Elasticsearch)
- Install Tomcat 8
- Deploy geoportal.war to Tomcat.
- Update your Geoportal essential configuration
- Restart Tomcat
- Run quick smoke test
- Open geoportal web page (e.g. http://localhost:8080/geoportal)
- Signin as gptadmin/gptadmin (top right)
- Upload a few metadata records (top right)
- Perform search (left panel), if search return the matching records, then the basic installation is working
- Perform additional configuration as necessary
[Tomcat8]/webapps/geoportal/WEB-INF/classes/config/app-context.xml
Set the cluster and node name(s) for Elasticsearch cluster, e.g.:
<beans:bean id="elasticContext" class="com.esri.geoportal.db.elastic.ElasticContext">
<beans:property name="clusterName" value="elasticsearch" />
<beans:property name="nodes">
<beans:value>host1</beans:value>
<beans:value>host2</beans:value>
</beans:list>
</beans:property>
</beans:bean>
[Tomcat8]/webapps/geoportal/WEB-INF/classes/app-security.xml
- configure various authentication options such as simple, LDAP, OAuth2.
[Tomcat8]/webapps/geoportal/WEB-INF/classes/log4j.properties Logging properties. You can modify the location of the log file by updating: log4j.appender.file.File
Elasticsearch mappings for the "metadata" index [Tomcat8]/webapps/geoportal/WEB-INF/classes/config/elastic-mappings.xml Contains the Elasticsearch mappings for the "metadata" index, used when Geoportal auto-creates the "metadata" index. Whenever you create a "metadata" index within Elasticsearch, you'll need to include these mappings within your request "PUT" request.