locked
use FSIS connect to ESP, but "The web request timed out" RRS feed

  • Question

  • hi, i just install FSIS and esp.5.3.sp3.slipstream.win32 on two servers.

    then i build a sample ims workflow (validate ok), and run the sample.

    http://localhost:81/Samples/ServerControls/ServerControlsApp1.aspx

    search input: test

    but no result and the debug trace as below:

    Ims.Trace constructor called
    Ims.Trace constructor exits
    Ims.Trace.initialize() called.
    Ims.Trace._toggleTrace() called
    Ims.Trace._toggleTrace() returns
    WARN: Ims.HitList(HitList): Error: function() { return this._failure; }
    ERROR: Ims.Search.SearchExecutor(SearchExecutor): The web request timed out.

    but i can search some result from FAST ESP 15100 port with the input 'test' and the same search profile

    How can i fix it?

    Friday, December 3, 2010 8:56 AM

Answers

  • Hi,

    This can be a challenging issue that may be best handled by our Technical Support department.   We would need to know what has been configured in the IMS flow you created, and confirm it is configured correctly.  Additionally, we would want to confirm you modified the web.config for the IMS Toolkit sample apps properly as well.

    Regarding your workflow validating okay, generally speaking, the validation just insures that the operators are configured properly to the lowest degree.  It doesn’t actually validate that the configuration is necessarily “correct” in the context that it does what the customer was intending.  I recommend that you set up a very simlpe flow such as with just a FlowInput>ESPLookup>FlowOutput operator to just get started and see if you can get that to work.  For example:

    1.       Choose the Flow Input operator from the Interaction Management section of the toolbox and drag it to your canvas.
    2.       Double click on FlowInput.  Enter “Input” in the Input name field and switch to the Schema view.  Under Name enter “ContextObject” and set Type to “ContextObject”.  (Note: When working with IMS Flows, the input name will always be “Input”.)
    3.       Drag the ESP Lookup operator to the canvas and create a connection from FlowInput to ESPLookup.
    4.       Open the configuration screen for ESPLookup and configure the entries as follows:
               Qr server - [qrserver_FQDN]:15100
               Search View - xmldata
               Search XPath - /context:context/ims:imsSearch
               Results XPath - /context:context
               Results name  - results
    5. Add the Flow Output operator and connect it to ESPLookup
    6.  Save the flow.  The configuration for this flow is complete.

    Testing the flow using the IMS UI Toolkit samples
    1.       Open a new instance of Visual Studio
    2.       Go to File > Open > Web Site…
    3.       Open the IMS Toolkit - may be found in c:\Program Files\FAST Search Server 2010 for Internet Sites\IMS Toolkit
    4.       Choose Website > Start Options…
    5.      Click the Use custom server radio button and enter the sitename - example:  “http://fsis1.company.com/”.
    6.       Click ok. 
    7.       Open web.config and locate the <flowAliases> section.
    8.       The next line below <flowAliases> should contain the esp key.  Set the value to “IMSFlows.ESPFlow”.
    9.       Save web.config.  (If you do not have permissions to save web.config, browse to your FSIS folder - example: C:\Program Files\FAST Search Server 2010 for Internet Sites, and grant the user account full control over the IMS Toolkit directory and all subfolders and files.)
    10.      In the right window browse to Samples > SearchApp.  Right click on SearchApp1.aspx and choose View in Browser.
    11.    Search for your desired terms and verify that you receive results (Note: The first time you use a flow after adding it or starting the Interaction Engine, the search may fail due to a timeout before the flow is activated.  The second search should succeed.)
    12.    Close the Internet Explorer window.
    13.    Save the new Visual Studio project.

    If even a simple flow does not work, we likely would need to view the IMS flow files, and this may requrie that you open a service request with our Technical Support team.

    Thanks!
    Rob Vazzana | Microsoft | Enterprise Search Group | Senior Support Engineer |http://www.microsoft.com/enterprisesearch

    • Proposed as answer by Rob Va - MSFT Thursday, December 30, 2010 6:12 PM
    • Marked as answer by Rob Va - MSFT Wednesday, August 24, 2011 5:13 PM
    Thursday, December 30, 2010 6:12 PM

All replies

  • Hi,

    This can be a challenging issue that may be best handled by our Technical Support department.   We would need to know what has been configured in the IMS flow you created, and confirm it is configured correctly.  Additionally, we would want to confirm you modified the web.config for the IMS Toolkit sample apps properly as well.

    Regarding your workflow validating okay, generally speaking, the validation just insures that the operators are configured properly to the lowest degree.  It doesn’t actually validate that the configuration is necessarily “correct” in the context that it does what the customer was intending.  I recommend that you set up a very simlpe flow such as with just a FlowInput>ESPLookup>FlowOutput operator to just get started and see if you can get that to work.  For example:

    1.       Choose the Flow Input operator from the Interaction Management section of the toolbox and drag it to your canvas.
    2.       Double click on FlowInput.  Enter “Input” in the Input name field and switch to the Schema view.  Under Name enter “ContextObject” and set Type to “ContextObject”.  (Note: When working with IMS Flows, the input name will always be “Input”.)
    3.       Drag the ESP Lookup operator to the canvas and create a connection from FlowInput to ESPLookup.
    4.       Open the configuration screen for ESPLookup and configure the entries as follows:
               Qr server - [qrserver_FQDN]:15100
               Search View - xmldata
               Search XPath - /context:context/ims:imsSearch
               Results XPath - /context:context
               Results name  - results
    5. Add the Flow Output operator and connect it to ESPLookup
    6.  Save the flow.  The configuration for this flow is complete.

    Testing the flow using the IMS UI Toolkit samples
    1.       Open a new instance of Visual Studio
    2.       Go to File > Open > Web Site…
    3.       Open the IMS Toolkit - may be found in c:\Program Files\FAST Search Server 2010 for Internet Sites\IMS Toolkit
    4.       Choose Website > Start Options…
    5.      Click the Use custom server radio button and enter the sitename - example:  “http://fsis1.company.com/”.
    6.       Click ok. 
    7.       Open web.config and locate the <flowAliases> section.
    8.       The next line below <flowAliases> should contain the esp key.  Set the value to “IMSFlows.ESPFlow”.
    9.       Save web.config.  (If you do not have permissions to save web.config, browse to your FSIS folder - example: C:\Program Files\FAST Search Server 2010 for Internet Sites, and grant the user account full control over the IMS Toolkit directory and all subfolders and files.)
    10.      In the right window browse to Samples > SearchApp.  Right click on SearchApp1.aspx and choose View in Browser.
    11.    Search for your desired terms and verify that you receive results (Note: The first time you use a flow after adding it or starting the Interaction Engine, the search may fail due to a timeout before the flow is activated.  The second search should succeed.)
    12.    Close the Internet Explorer window.
    13.    Save the new Visual Studio project.

    If even a simple flow does not work, we likely would need to view the IMS flow files, and this may requrie that you open a service request with our Technical Support team.

    Thanks!
    Rob Vazzana | Microsoft | Enterprise Search Group | Senior Support Engineer |http://www.microsoft.com/enterprisesearch

    • Proposed as answer by Rob Va - MSFT Thursday, December 30, 2010 6:12 PM
    • Marked as answer by Rob Va - MSFT Wednesday, August 24, 2011 5:13 PM
    Thursday, December 30, 2010 6:12 PM
  • Any luck with this issue? I am facing the same problem.
    Tuesday, August 2, 2011 5:09 PM
  • Try the above steps to get a simple flow to work.  If even a simple flow does not work, we would need to view the IMS flow files, and this may requrie that you open a service request with our Technical Support team.

    Thanks!
    Rob Vazzana | Microsoft | Enterprise Search Group | Senior Support Engineer |http://www.microsoft.com/enterprisesearch

    Tuesday, August 2, 2011 5:29 PM