1 / 20

DiGIR

DiGIR. Portal Installation And Configuration. 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

maxine
Télécharger la présentation

DiGIR

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DiGIR Portal Installation And Configuration Schwartz GBIF Nodes III 29 April 2003

  2. 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 Schwartz GBIF Nodes III 29 April 2003

  3. 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…) Schwartz GBIF Nodes III 29 April 2003

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

  5. Installation Overview • Plan installation • Install Java 2 SDK • Install Apache Tomcat • Unpack environment zip (i.e. set up directory structure) • Unpack web application archives (.war files) • Edit configuration files • Test • Woo hoo! Schwartz GBIF Nodes III 29 April 2003

  6. 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 Schwartz GBIF Nodes III 29 April 2003

  7. 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:\ ) Schwartz GBIF Nodes III 29 April 2003

  8. Testing Tomcat Installation To check that Tomcat (and Java) were installed correctly… • Open a command prompt window • cd %CATALINA_HOME%/bin • startup • Check http://localhost:8080 in a web browser • Run a sample, assuming you installed them • shutdown • Woo hoo! Schwartz GBIF Nodes III 29 April 2003

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

  10. bin conf logs webapps work Directory Structure Everything in C:\DiGIR\ servlet.jar soap.jar uddi4j.jar xalan.jar xerces.jar logkit.jar DiGIR docs lib logs src engine tcinstance pres Schwartz GBIF Nodes III 29 April 2003

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

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

  13. 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 Schwartz GBIF Nodes III 29 April 2003

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

  15. 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 Schwartz GBIF Nodes III 29 April 2003

  16. Running the Engine • Open a command prompt window • cd %DIGIR_HOME%/tcinstance/engine/bin • startup_engine Schwartz GBIF Nodes III 29 April 2003

  17. Testing the Engine • Open a browser • Go to http://your.ip.or.domain:8080/portal/PortalServlet?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. Schwartz GBIF Nodes III 29 April 2003

  18. Running the Pres Layer • Open a command prompt window • cd %DIGIR_HOME%/tcinstance/pres/bin • startup_pres Schwartz GBIF Nodes III 29 April 2003

  19. Testing the Pres Layer • Open a browser • Go to http://your.ip.or.domain:10080/pres/PresentationServlet?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. Schwartz GBIF Nodes III 29 April 2003

  20. 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 Schwartz GBIF Nodes III 29 April 2003

More Related