|
From: Brad T. <br...@ar...> - 2007-11-10 00:02:35
|
Hi Chris, If you've deployed the .war as "wayback-webapp-1.0.1.war" (on port 8080, for example) , and you define an AccessPoint named "8080:wayback", then you need to use the public access URL: http://yourhost.org:8080/wayback-webapp-1.0.1/wayback/ which would place subsequent queries at: http://yourhost.org:8080/wayback-webapp-1.0.1/wayback/query?... The fact that the wayback returns "normal" looking UI pages when users do not provide the "name" of the AccessPoint has been the source of a lot of confusion.. This should be addressed in the next release. Let me know if adding the AccessPoint name works for you, or if you're still having other problems, please forward on your wayback.xml configuration. Brad Chris Vicary wrote: > Hi, > > I'm having some difficulty configuring the newest version of wayback. > It is deployed in a non-ROOT webapp context (wayback-webapp-1.0.1, by > default) in tomcat 5.5.20 and configured for a localcdxindex > collection. Tomcat starts normally and I am able to access the wayback > search interface, but whenever I attempt a URL query, a 404 page is > returned with the description "The requested resource > (/wayback-webapp-1.0.1/query) is not available." There are no errors > reported in catalina.out. I'm guessing I missed something simple in a > configuration file, but not sure what. > > Thanks, > > Chris > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Archive-access-discuss mailing list > Arc...@li... > https://lists.sourceforge.net/lists/listinfo/archive-access-discuss > |