none
FS4SP Rest API RRS feed

  • Question

  • Hi.

    We have legacy ASP code that runs REST queries against Fast ESP (it parses XML results from plain HTTP requests against ESP query server at, say, "http://fastesp:15100/cgi-bin/xsearch?query=testquery").

    Now we are moving to FS4SP. The same kind of XML result can be seen when we run queries locally at FS4SP servers (http://localhost:13280/cgi-bin/xsearch?offset=0&hits=10&query=testquery). The TCP port has changed but the XML seems to be the same. The problem is that this URL this is not available for remote HTTP clients anymore.

    Should I port the code or can I expose this URL to my old ASP clients?

    Thursday, May 24, 2012 2:51 PM

Answers

  • Hi,

    In order to get results from FS4SP you should query via SharePoint. This ensures that security trimming takes place. The QR server is only available on localhost, and not from an external server which means you cannot expose it.

    As for getting XML back, you can use the RSS endpoint (http://server/[site collection/]_layouts/srchrss.aspx), or create your own handler to output XML in the format you would like. I recommend going the RSS route. (But this won't allow using FQL).

    The RSS endpoint takes just about the same parameters as the default search page does.

    Thanks,
    Mikael Svenson


    Search Enthusiast - SharePoint MVP/MCT
    http://techmikael.blogspot.com/
    Author of Working with FAST Search Server 2010 for SharePoint

    Friday, May 25, 2012 8:18 AM
  • Hi,

    I haven't tried to mess with the configs in order to expose the QR server directly as work with SharePoint in conjunction with FS4SP.

    I mean, why go for FS4SP and not just stay with FAST ESP when you want to access the QR server directly?

    And the reverse proxy things was a smart move :)

    Thanks,
    Mikael Svenson


    Search Enthusiast - SharePoint MVP/MCT
    http://techmikael.blogspot.com/
    Author of Working with FAST Search Server 2010 for SharePoint

    Friday, May 25, 2012 8:27 PM

All replies

  • Hi,

    In order to get results from FS4SP you should query via SharePoint. This ensures that security trimming takes place. The QR server is only available on localhost, and not from an external server which means you cannot expose it.

    As for getting XML back, you can use the RSS endpoint (http://server/[site collection/]_layouts/srchrss.aspx), or create your own handler to output XML in the format you would like. I recommend going the RSS route. (But this won't allow using FQL).

    The RSS endpoint takes just about the same parameters as the default search page does.

    Thanks,
    Mikael Svenson


    Search Enthusiast - SharePoint MVP/MCT
    http://techmikael.blogspot.com/
    Author of Working with FAST Search Server 2010 for SharePoint

    Friday, May 25, 2012 8:18 AM
  • Thanks, Mikael.

    The problem with this approach is that I would have to rewrite my legacy ASP code. No need for security here, since all content is public. If I were starting from scratch I'd go the RSS way too, but this is not the case. I need this old solution to keep working without rewriting it.

    Funny thing is that I changed the "qr_server" entry in %FASTSearch%\bin\QRProxyService.exe.config from "localhost" to the real IP address, but it seems that qrproxy ignores it and only accepts "localhost" connections. Should this entry work?

    I actually managed to make it work by configuring IIS as a reverse proxy (using ARR), so qrproxy "thinks" connections are coming from localhost. Messy, but ARR is lightweight enough - I can live with that.


    Friday, May 25, 2012 1:02 PM
  • Hi,

    I haven't tried to mess with the configs in order to expose the QR server directly as work with SharePoint in conjunction with FS4SP.

    I mean, why go for FS4SP and not just stay with FAST ESP when you want to access the QR server directly?

    And the reverse proxy things was a smart move :)

    Thanks,
    Mikael Svenson


    Search Enthusiast - SharePoint MVP/MCT
    http://techmikael.blogspot.com/
    Author of Working with FAST Search Server 2010 for SharePoint

    Friday, May 25, 2012 8:27 PM
  • Hi Andre,

    What about a client-server application?

    A server application on the FAST server which accepts incoming string (such as your old HTTP request) and will query the localhost, and a client application which will accept the XML from the server. You'll need the server to handle multi-threading.

    You'll probably have to disable the security trimming feature for it, but I don't see a reason for it not to work well.

    Amir

    Monday, May 28, 2012 6:44 AM