1. SchwartzGBIF Nodes III29 April 2003 DiGIR Portal Installation And Configuration

2. SchwartzGBIF Nodes III29 April 2003 Portal Overview The entry point for a user Can make requests to N number of providers Communicates via protocol compliant messages only Can query registry for available providers Can determine, based on provider metadata, whether a provider should be queried

3. SchwartzGBIF Nodes III29 April 2003 Implementation Details Divided into two distinct applications –Portal Engine –Presentation Layer Portal Engine: –External network activity (registry calls, provider calls) –Threads provider calls for increased throughput –May limit provider calls based on metadata Presentation Layer (the UI): –Pages dynamically built off parsed schemas –Translates requests (from forms) to protocol request docs –Translates provider responses to various views (html, tab delimited, etc…)

4. SchwartzGBIF Nodes III29 April 2003 A Basic Architecture Portal Provider Register Provider Query Pres Layer Engine Matching Providers Registry Min Prov Info ( UDDI ) Resource Metadata XML over HTTP

5. SchwartzGBIF Nodes III29 April 2003 Installation Overview 1.Plan installation 2.Install Java 2 SDK 3.Install Apache Tomcat 4.Unpack environment zip (i.e. set up directory structure) 5.Unpack web application archives (.war files) 6.Edit configuration files 7.Test 8.Woo hoo!

6. SchwartzGBIF Nodes III29 April 2003 Planning Suitable hardware to run a server application Ample disk space (~150 Mb for *full* Java SDK and Tomcat installation) Open ports –Current engine port: 8080 and accompanying Tomcat administrative ports –Current presentation layer port: 10080 and accompanying Tomcat administrative ports Know namespaces and locations of schema and infodo documents Consider maintenance of log files

7. SchwartzGBIF Nodes III29 April 2003 Installation Assumptions Assume –Java 2 SDK installed JAVA_HOME environment variable is set PATH environment variable modified to contain %JAVA_HOME%/bin –Apache Tomcat installed CATALINA_HOME environment variable set –Windows OS –Single drive installation (i.e. C:\ )

8. SchwartzGBIF Nodes III29 April 2003 Testing Tomcat Installation To check that Tomcat (and Java) were installed correctly… 1.Open a command prompt window 2.cd %CATALINA_HOME%/bin 3.startup 4.Check http://localhost:8080 in a web browserhttp://localhost:8080 5.Run a sample, assuming you installed them 6.shutdown 7.Woo hoo!

9. SchwartzGBIF Nodes III29 April 2003 Environment Setup 1.Download the DiGIR environment zip file from: http://sourceforge.net/project/showfiles.php?group_id=38190 http://sourceforge.net/project/showfiles.php?group_id=38190 2.Unzip the file, preferably at C:\ 3.Set a DIGIR_HOME environment variable to the location of the install (e.g. C:\DiGIR )

10. SchwartzGBIF Nodes III29 April 2003 Directory Structure Everything in C:\DiGIR\ DiGIRdocs lib logs src tcinstance engine pres servlet.jar soap.jar uddi4j.jar xalan.jar xerces.jar logkit.jar bin conf logs webapps work

11. SchwartzGBIF Nodes III29 April 2003 Portal Engine Archive 1.Download the latest engine web application archive (.war) file from: http://sourceforge.net/project/showfiles.php?group_id=38190 http://sourceforge.net/project/showfiles.php?group_id=38190 2.If needed, rename the file back to.war (as.zip may have been appended upon download) 3.Place the.war file in %DIGIR_HOME%/tcinstance/engine/webapps 4.Unpack the file in the same directory: jar xvf DiGIR_Portal_Engine.war 5.Remove (or move) the.war file to prevent conflict

12. SchwartzGBIF Nodes III29 April 2003 Archive Contents The application.war file contains a WEB-INF directory of application files, libraries and configuration files… WEB-INF classes lib web.xml Java packages: org.calacademy.digir.common org.calacademy.digir.util org.calacademy.digir.engine org.calacademy.digir.presentation Web files:.jsp files.xsl files.js files.gif files.jpg files Presentation layer archive only

13. SchwartzGBIF Nodes III29 April 2003 Portal Engine Configuration Edit the portal.xml file found in %DIGIR_HOME%/tcinstance/engine/webapps/ WEB-INF/classes/org/calacademy/digir/engine logfileName – modify if DIGIR_HOME is not C:\ provider – set to the IP of your provider, include port contactEmail – change to your email Other parameters include: version, providerFilter, handlerPoolThreadMax, registry, providerCacheTimeout, xmlSchema, and protocolSchema

14. SchwartzGBIF Nodes III29 April 2003 Presentation Layer Archive 1.Download the latest presentation web application archive (.war) file from: http://sourceforge.net/project/showfiles.php?group_id=38190 http://sourceforge.net/project/showfiles.php?group_id=38190 2.If needed, rename the file back to.war (as.zip may have been appended upon download) 3.Place the.war file in %DIGIR_HOME%/tcinstance/pres/webapps 4.Unpack the file in the same directory: jar xvf DiGIR_Portal_Pres.war 5.Remove (or move) the.war file to prevent conflict

15. SchwartzGBIF Nodes III29 April 2003 Presentation Layer Config Edit the presentation.xml file found in %DIGIR_HOME%/tcinstance/pres/webapps/WEB-INF /classes/org/calacademy/digir/presentation logfileName – modify if DIGIR_HOME is not C:\ display – feel free to change if you like Other parameters include: dispatcher, xmlSchema, protocolSchema, and informationDomains

16. SchwartzGBIF Nodes III29 April 2003 Running the Engine 1.Open a command prompt window 2. cd %DIGIR_HOME%/tcinstance/engine/bin 3. startup_engine

17. SchwartzGBIF Nodes III29 April 2003 Testing the Engine 1.Open a browser 2.Go to http://your.ip.or.domain:8080/portal/PortalS ervlet?action=getProviders http://your.ip.or.domain:8080/portal/PortalS ervlet?action=getProviders Keep an eye on the logfile %DIGIR_HOME%/logs/portal_services.log and the console window that appears when you run the startup script. Be on the look out for errors and exceptions.

18. SchwartzGBIF Nodes III29 April 2003 Running the Pres Layer 1.Open a command prompt window 2. cd %DIGIR_HOME%/tcinstance/pres/bin 3. startup_pres

19. SchwartzGBIF Nodes III29 April 2003 Testing the Pres Layer 1.Open a browser 2.Go to http://your.ip.or.domain:10080/pres/Presenta tionServlet?action=home http://your.ip.or.domain:10080/pres/Presenta tionServlet?action=home Keep an eye on the logfile %DIGIR_HOME%/logs/presentation.log and the console window that appears when you run the startup script. Be on the look out for errors and exceptions.

20. SchwartzGBIF Nodes III29 April 2003 More Information DiGIR http://digir.sourceforge.net Portal Install Guide http://digir.sourceforge.net/port/digir_portal_install.html Portal Develop Setup http://digir.sourceforge.net/port/digir_portal_dev_setup.html