November 2010 - IPT - lists.gbif.org

Open call for testing of the IPT 2.0RC1
by Tim Robertson 13 Dec '10

13 Dec '10

Dear all, The IPT development team are pleased to invite you to participate in the testing of the re-engineered and simplified IPT. The revised IPT is the result of a re-engineering effort of the 1.0 version of the IPT, specifically to: - Reduce the server requirements significantly - Increase the data import performance by removing the embedded database - Remove the dependency on heavy libraries and tools such as Geoserver - Remove all data interfaces that are not necessary for data publication through GBIF - Improve the robustness of the tool The result is an IPT that: - is less than 12MB - starts in only a few seconds - supports fast import (1 million records in 15 seconds or so) - includes an expanded metadata profile - supports the importing of DwC Archives - allows multiple organisation support (an IPT may be installed by an institution, but the resource associated with a different institution) We would like to thank those early testers who have helped us, over the last 5 weeks, identify and address some 81 issues and enhancements already (http://code.google.com/p/gbif-providertoolkit/issues/list?can=1&q=Milestone… ). All reported defects have been addressed, and therefore we have indicated this is a version that is a candidate for being a formal release and therefore labelled IPT 2.0RC1. Issues are actively being tracked, monitored and will be prioritised and addressed, and I ask that you use this utility to record any issues that you come across: http://code.google.com/p/gbif-providertoolkit/issues/list The user manual and engineering documentation drafting are under way and expected to be finished by the end of 2010 prior to the general availability (IPT 2.0GA) release. The IPT 2.0GA release is targeted by the end of the 2010 but will only be made available following a successful community test phase. The IPT 2.0RC1 for this test can be downloaded: http://gbif-providertoolkit.googlecode.com/files/ipt-2.0RC1.war The IPT 2.0RC1 is restricted for use to the GBIF development registry at this stage and therefore can not be used for publication onto the GBIF network during this testing phase. Please find attached some basic guideline information for testers in the absence of the user manual. Thank you once again to all IPT contributers. Best wishes, Tim

5 4

v2.0 release timeline?
by Bruce Wilson 18 Nov '10

18 Nov '10

Hi All. Does an timeline exist for deployment of the v2.0 IPT package? I've been moving slowly on publishing via the v1.0-RC3 package anticipating the release of v2.0. Bruce Wilson - UVSC Department of Chemistry | Mail Stop 179 | UVU | 800 W University Parkway, Orem UT 84058 (801)863-7138 | bruce.wilson(a)uvu.edu | http://science.uvu.edu/wilson

2 1

Notes on configuring RHEL to run IPT (ipt-2.0-SNAPSHOT-r2482)
by Matt 17 Nov '10

17 Nov '10

Hi all, Some notes on my recent effort to get IPT running on RHEL- at minimum they'll help me remember howto repeat this for real in the future. Special thanks to Tim for the very speedy help. One quick question now- if I configure everything is it easy to save the configuration file, then wipe the install, then toss the config back in? Cheers, Matt --- Running RHEL (Realm Linux flavour), see http://www.linux.ncsu.edu/realm_linux/. Did (all) this as a su. Yum installed packages of note (I'm not sure if these were all required or not, it's just the overall configuration): java-1.4.2-gcj-compat.x86_64 java-1.4.2-gcj-compat-devel.x86_64 java-1.6.0-openjdk.x86_64 java-1.6.0-openjdk-devel.x86_64 java_cup.x86_64 xalan-j2.x86_64 xalan-j2-xsltc.x86_64 xerces-j2.x86_64 xerces-j2-scripts.x86_64 tomcat5.x86_64 tomcat5-common-lib.x86_64 tomcat5-jasper.x86_64 tomcat5-jsp-2.0-api.x86_64 tomcat5-server-lib.x86_64 tomcat5-servlet-2.4-api.x86_64 tomcat5-webapps.x86_64 I answered y to all the dependency questions on yum installs. It took me a bit to figure out that the the webapps folder linked at /usr/share/tomcat5/webapps or /var/lib/tomcat5/webapps After cding there I grabbed the files wget http://gbif-providertoolkit.googlecode.com/files/ipt-2.0-SNAPSHOT-r2482.war wget http://gbif-providertoolkit.googlecode.com/files/ipt-geoserver-1.0-RC3.zip Then I chowned/chgrped them to user 'tomcat' and did 'service tomcat5 restart'. After you hit http://your.site.com:8080/ipt-2.0-SNAPSHOT-r2482 you'll have a ipt-2.0-SNAPSHOT-r2482 folder back in webapps. Went there, and edited webapps/ipt/WEB-INF/classes/log4j.xml changing the log lines to: <param name="file" value="/tmp/debug.log "/> <param name="file" value="/tmp/admin.log "/> Note that the Issue 451 fix describing this problem doesn't include the slash preceding tmp in the steps body but the attached file does (the latter is correct). The last trick was to: cd /var/lib/tomcat5/common/endorsed and do a number of "rebuild-jar-repository" rebuild-jar-repository /var/lib/tomcat5/common/endorsed xalan-j2-serializer.jar rebuild-jar-repository /var/lib/tomcat5/common/endorsed xalan-j2.jar rebuild-jar-repository /var/lib/tomcat5/common/endorsed xerces-j2.jar ... and some others The end product of the endorsed folder looks like this: [jaxp_parser_impl].jar -> /usr/share/java/jaxp_parser_impl.jar [xalan-j2-2.7.0].jar -> /usr/share/java/xalan-j2-2.7.0.jar [xalan-j2].jar -> /usr/share/java/xalan-j2.jar [xalan-j2-serializer].jar -> /usr/share/java/xalan-j2-serializer.jar [xerces-j2-2.7.1].jar -> /usr/share/java/xerces-j2-2.7.1.jar [xerces-j2].jar -> /usr/share/java/xerces-j2.jar [xml-commons-apis].jar -> /usr/share/java/xml-commons-apis.jar The xalan-j2-serializer.jar was definitely needed as including this link ultimately resolved the problem. I'm not sure which others were required. After all this (and at various points in the debugging) a "service tomcat5 restart" and the site was live.

2 1

Configuring IPT for RHEL/Centos?
by Matt 17 Nov '10

17 Nov '10

Hi All, Trying to get IPT running. I assume it's possible to do on linux? Is it possible to configure remotely (i.e. not going the localhost route as per the docs)? I think I'm configured thus far correctly since I can see /geoserver fine. I tried both the 1.0 RC3 and the 2.0 invite versions. Present error is a 404, resource () not found. Running Apache Tomcat/5.5.23 installed via yum. Any thoughts? I'd be happy to document the process if I can get something running. Thanks in advance, Matt

3 3