Tomcat Decommissioning: What Should I-Share Libraries Do?

After June 30, 2011, CARLI will no longer support the Tomcat (version 7) WebVoyage interface to the public catalog. Most I-Share libraries will be unaffected by this change. To see whether your library’s instance of Tomcat WebVoyage has received any traffic in recent months, consult the usage statistics reports named 2011-mm-Raw-tc.txt at https://i‑share.carli.illinois.edu/acrlstats/ .

All I‑Share libraries should ensure that no library web page links or search widgets point to the Tomcat interface, that no external services such as link resolvers or federated search systems point to the Tomcat interface and, to the extent possible, that no bookmarks or other stored references point to the Tomcat interface. Specific information follows about what will happen and what libraries should do.

What will happen:

At 5PM on Thursday, June 30, 2011 CARLI will associate the name i-share7.carli.illinois.edu with the server that runs Classic WebVoyage. After 5PM, users who still point to the simple address https://i‑share7.carli.illinois.edu will be taken to the catalog selection page at https://i‑share.carli.illinois.edu/ilcso/cgi‑bin/welcome, where the default database will be determined by their IP address and where they may choose between the Classic WebVoyage and the VuFind interfaces.

Users who point specifically to https://i-share7.carli.illinois.edu/xxx, where xxx is the three-letter code for a particular I-Share library, will wind up on the page at
https://i‑share.carli.illinois.edu/xxx/webvoy.htm, which for most I-Share libraries performs an automatic javascript forward to the default search page in the Classic WebVoyage interface:
https://i‑share.carli.illinois.edu/xxx/cgi‑bin/Pwebrecon.cgi?PAGE=First&DB=local.

Users who point to an elaborated Tomcat URL (that is, a URL with anything after the "/xxx," like, for instance, https://i-share7.carli.illinois.edu/xxx/vwebv/searchBasic) will wind up at something like https://i‑share.carli.illinois.edu/xxx/vwebv/searchBasic, which will generate an error message. CARLI will not attempt to redirect elaborated Tomcat URLs back to their Classic counterparts.

A very small number of users had used the “Save Search” feature of Tomcat WebVoyage. If the library has the “Save Search” feature enabled in Classic WebVoyage, the Tomcat searches will display in the user’s MySearches list, but will not re-execute successfully and will need to be re-saved. If the library does not have the “Save Search” feature enabled in Classic WebVoyage, the Tomcat searches will not be available to the user but, on request from the user, CARLI can retrieve and convert the searches to “canned searches” that the user can store outside of WebVoyage.

What libraries should do:

Check to see if there’s still any traffic on your library’s Tomcat WebVoyage instance. Usage statistics are available at https://i-share.carli.illinois.edu/acrlstats/ ; any Tomcat usage will be reported in the files named 2011-mm-Raw-tc.txt, where mm is the number for the month.
Correct all links to the Tomcat WebVoyage interface so that they point instead to Classic WebVoyage or to VuFind. The CARLI URL Builder may be helpful: http://auth.carli.illinois.edu/cgi‑bin/buildlink/index.cgi .
Correct all search boxes incorporated into library web pages so that they submit searches via Classic WebVoyage or VuFind rather than Tomcat WebVoyage. The CARLI Search Box Builder may be helpful: http://www.carli.illinois.edu/mem‑prod/I‑Share/opac/opac_search_box_builder_wv7.php .
Configure WorldCat/SILC to link to Classic WebVoyage or to VuFind rather than to Tomcat WebVoyage.
Correct other third-party pointers to the OPAC, such as link resolvers’ target definitions, A&I databases’ links-to-holdings configurations, federated search systems’ target definitions, etc., so that they connect to Classic WebVoyage or VuFind instead of to Tomcat WebVoyage.
If users contact the library about searches they had saved in Tomcat WebVoyage, contact CARLI for assistance.