Thunderstone Support Forums

Best Bets are included in the XML backup. Underneath each <Profile> element should be a <BestBets> element, which contains <BestBetGroup> elements, each of which has one or more <BestBet>. If a profile doesn't have any best bets, then the <BestBet> won't be there.

Are any of those elements present in your backup?

There is an additional feature that was missing from the original 27.1.0 changelog. This is not a change to the release itself. Anyone who already applied 27.1.0 already has this feature, and the same 27.1.0 update is still available to apply.

• Revamped Best Bet Clicks Query Log report. Now groups by best bet keywords, allows viewing individual click queries, shows logs of now-deleted best bets, and works with large numbers of best bets

DBWalker-1.5.0 is now available for Gen3 and Gen4 appliances (see System->Information->System Information, "General" tab for generation)

* Added DBCP connection pooling to DBWalker

* Updated postgreSQL JDBC driver to v42.2.5, requires PostgreSQL 8.2 (from Dec 2006) or newer

* Fixed DBWalker not showing some content with accented characters correctly


Download and install updates by visiting the System->System Setup->Update Software page on the appliance. After installing the update, Disable and re-Enable DBWalker to make use of the new functionality.

Ok, if you have ASP.NET installed the Handler Mapping configuration will be written to web.config in the target location, and multiple /texis applications pointing to the same target location don't need to re-do the "Apply proxyModule.dll as a Wildcard Application Map" step.

Strangely, my IIS Administration UI prevented me adding a duplicate "Thunderstone Proxy Module" in the first place, rather than allowing it to be added and blowing up the IIS configuration.

Given that the manager itself balks at the existing redundant configuration, you can delete the "INSTALLDIR/etc/ISAPI-virtualdir/web.config" file, and redo the Handler Mapping configuration once.

These /texis and /webinator applications can be manually recreated for other sites. Our Search Appliance docs describe how to do this, but it's not totally accurate for how Webinator would need it. While I fix up the docs, I'll include the instructions here. You'll be doing this once for each site you want to have /texis accessible.

----------------------
Add the /texis application

• Open the Internet Information Services (IIS) Manager
• Right click on the web site you want to use and select Add Application...
• In the Alias box, enter texis.
• In the Application pool box, select ThunderstonePool.
• In the Physical Path box, browse to the INSTALLDIR/etc/ISAPI-virtualdir folder.
• Click OK to complete the wizard and return to the IIS Manager window.

Apply proxyModule.dll as a Wildcard Application Map

• In IIS Manager, click the newly created texis application, and double-click Handler Mappings in the center list.
• Choose Add Wildcard Script Map on the right.
• For the name, enter Thunderstone Proxy Module.
• Set the executable to INSTALLDIR/etc/proxyModule.dll.
• When you hit OK to close that window, you'll be prompted with Do you want to allow this ISAPI Extension? Choose Yes.
• In IIS8, an additional step is required:
  • Right click on the new handler mapping, choose Edit...
  • Click the Request Restrictions button that wasn't present before.
  • Uncheck Invoke handler only if request is mapped to: box and click OK, and accept allowing the extension again.

Add the /webinator virtual directory

• Right click on the web site and select Add Virtual Directory...
• In the Alias box, enter webinator.
• In the Physical Path box, browse to the INSTALLDIR/htdocs/webinator folder.
• Click OK to complete the wizard and return to the IIS Manager window.

And that should do it. This will provide the exact same webinator interface as any other site, so you'll want to choose the appropriate profile when searching.

Old webinator sets the login cookie via a <meta> html tag instead of a HTTP header, which modern browsers no longer support. So after you log in you see a successful page, and your browser doesn't keep the cookie around for the next request - which tells you to log in again.

Using IE for the admin interface is a fine workaround, or you can update to the latest version which has this fixed.

They're designed to work together. DBWalker only provides a html interface to your databases, it doesn't do any "search" on its own. Webinator takes care of that for you, so Webinator will always be the "front end" for any searches that are done.

We'd like to get more details about your setup, please submit a support request at https://www.thunderstone.com/tech-support/ and let us know:

* What version of postgres you're using
* the schema for this postgres table
* which field have you set as the keyfield in this DBWalker Config
* a couple example URLs that are showing the 500 error

and we'll help troubleshoot this scenario.
Thanks!

Also, modern scripts have many new features; if you upgrade, it would be worthwhile discussing with Thunderstone what changes you're trying to implement and see if it's possible nowadays without modifying the scripts yourselves.

For anyone curious, the "infield operators" documentation has details on this and the other operators available:

https://docs.thunderstone.com/site/psap ... ators.html