Set the timeout for seedlist requests
We can set the default timeout for seedlist requests by creating an IBM WAS environment variable and specifying the required value of the timeout.
By default, seedlist requests time out after 240 seconds. This default setting overrides the timeout for server-to-server requests defined in LotusConnections-config.xml, which is 60 seconds. We can override the default seedlist request timeout by creating a WAS variable named SEARCH_SEEDLIST_TIMEOUT and setting the required value of the timeout in milliseconds.
- Use an administrator ID to log in to the WAS Integrated Console associated with the profile to which you installed IBM Connections. If we installed the applications to multiple WAS profiles, log in to the console associated with the appropriate profile.
- Expand Environment and click WebSphere variables.
- Select the relevant cell from the Scope drop-down list and click New.
- Enter SEARCH_SEEDLIST_TIMEOUT in the Name field.
- Enter a value in milliseconds in the Value field.
- Enter a description of the variable in the Description field, and then click OK.
- Stop the affected servers and start those servers again to put the variable configuration change into effect. If the change you made affects a node, we must stop and restart all of the servers on that node. Similarly if the change you made affects a cell, we must stop and restart all of the servers in that cell.
For a high-availability deployment, stop and start the servers in turn to ensure the Search application is still available to the users.
Parent topic:
Manage the Search application
Related:
Change WAS environment variables
Related reference: