By executing Federated Query Server (usually by submitting a form in an HTML search page) and specifying the search criteria in form variables.

Federated Query Server is a piece of search middleware that takes a user's query, translates and broadcasts it to multiple HTTP-enabled content repositories, reformats, sorts, merges and clusters the query results, and returns them to the user in a single HTML page.

Federated Query Server runs under Windows NT 4.0 Server (SP3, SP5 or SP6a), Windows 2000 Server, Windows Server 2003, Solaris 7+, HP-UX 11+ and Suse Linux 9+. It requires a CGI-compatible Web server.

Federated Query Server has no specific hardware requirements. It should be run on a machine that is more than capable of running the particular Web server that is in use. In particular, a fast Internet connection (T1 recommended), and a reasonable amount of free memory after the Web server has started, will help obtain the best performance from Federated Query Server.

unlimited number of sort levels may be specified. Each level may sort on one of the following elements of a result - URL, title, summary, relevance score, date, size, language, author, category, image URL, image ALT, reference string, type string, reference number, type number, content repository name, or any one of 10 user defined elements. Usually, the first level sort is by relevance score, as this is the order in which results are normally returned from content repositories.

Duplicate query result removal is optional. If it is enabled, query results that are the same (you can choose which comparison method to use) are merged into a single result, the relevance score of the merged result being the average of the relevance scores of the original duplicate results.

Any Tucana Knowledge Server may issue a query to any other server, where the from clause of a select command names the required models on one or more servers (using their URL). The Knowledge Server supports a naming service (similar to DNS), that informs a server of the other servers in a federation and the models they hold.

Federated Query Server requires a content repository to have the following features and characteristics: The results are returned as a list of uniformly formatted items, each with a URL that links to the result document Any content repository that meets the above conditions is likely to be compatible with Federated Query Server.

The text of each Boolean operator, and the characteristics of the language, make up a language configuration. Federated Query Server has one language configuration for the user interface (i.e. for queries specified on the search form) and one language configuration for each content repository. Any operators that are found in the query text are translated from the user interface language to the languages of the content repositories.

Federated Query Server accepts queries using the GET or POST method, and can broadcast queries using HTTP/1.0 or HTTP/1.1 requests that again use either the GET or POST method. The version and method used is specifiable on a per content repository basis.

Federated Query Server supports Basic, NTLM, Kerberos, Negotiate and delegated HTTP authentication. It can also access content repositories that require a user to log-in via a Web form. Credentials can be stored in the Federated Query Server configuration file, specified on the search form, or obtained from the Web server. Additionally, Federated Query Server can pass cookies between the browser and a content repository, in either or both directions.

Federated search is a technology that allows multiple searches to be done at the same time. It presents a single search interface to the user and acts as an intermediary to other databases. AFX utilizes connectors to "talk" to these other databases. The search term is sent simultaneously via connectors to all search sources. The searches are deployed, responses are collated, and returned to the user in a single list.

I'm doing a transfer using the SQL EM transfer tool, and not only is it not transferring the objects.

You simply click on a search result row and this takes you to the full table display with a template query which you can modify.

When you view your ticket, you will see near the top the Ticket Status of your ticket, whether it is Open or Close. If you are satisfied that your question has been answered fully, then you simply click on the "Close" link. That will close your ticket. You are free to open a new ticket in case you have another question or problem.

quot;OR" and "AND" are valid query symbol in the bizForm query. Please see the sample below

Oxford DRS titles currently support meta-search and can be accessed by meta search software via HTTP request. You should use method="get" using the site's base url (eg, http://www.oxford-britishliterature.com/) followed by 'search?' and the 'q=' parameter to signify the query. For example, the following URL...

Yes. The Query Cache operates on the server level, caching complete result sets matched with the original query string. If an exactly identical query is made (which often happens, particularly in web applications), no parsing or execution is necessary; the result is sent directly from the cache. Various tuning options are available. See Section 5.14, "The MySQL Query Cache".

You can search and query any ODBC compatible relational database (e.g. SQL Server, DB2/UDB, Oracle, MySQL, Sybase, etc.). You cannot search and query legacy databases such as IBM’s IMS and VSAM, object-oriented databases such as POET, or XML databases (although MetaTrieve will process XML data types stored in a relational database as tables and columns).

No, you can go directly to a query by selecting the “Query” menu option, or by clicking on “Search” without entering a search term.

Yes, you can save the results sheet as test or as a spreadsheet and open it later for further querying. You can also save the data results of a query as text or Excel sheet or Microsoft Access table (if displayed in Excel or Access).

My Body Weight chart WAS looking cool, but then the weight range (the values on the y axis) changed for no reason. The weight goes all the way down to zero now and the graph looks almost like a flat line even though I’ve lost 50 pounds. I’ve seen that other members have the same issue, while others graphs look fine. I would change the weight range myself, but I don’t see anyway to do that. Also, My bodyfat graph, my benchpress graph . .

There are two ways: You can use the Search function to search by topic, or you can click on Browse Our eLibrary in the left column of the homepage and search by issue. However, you must be a current subscriber and be registered to access the articles.

You can use the X-Force search engine at http://xforce.iss.net/xforce/search.php, or you can use your favorite search engine. Your choice of keywords makes a big difference in the success of finding the information you want. For example, searching on Microsoft will result in hundreds of results, but searching on MS04 may narrow your search to Microsoft security bulletins for 2004.

The Query property of the component retrieves a Message object. When you do a call for any property of the Message object, the components builds and sends the query to the name server.

Federated committees deal with issues that apply to a specific membership division. Federated committees perform duties necessary to the ongoing operation of that division and are comprised only of members from that division.

Federated identity allows a set of service providers to agree on a way to refer to a single user, even if that user is known to the providers in different guises. Most commonly, federated identity is achieved through the linking together of the user's several accounts with the providers. This allows the user to get more personalized service without centrally storing personal information.

The ~ operator does regular expression matching, and ~* does case-insensitive regular expression matching. The case-insensitive variant of LIKE is called ILIKE. Case-insensitive equality comparisons are normally expressed as: SELECT * FROM tab WHERE lower(col) = 'abc'; This will not use an standard index.

For example: if a mountain's name is Mount Zester and another mountain is named Mount Abraham, ideally Mount Zester would show up alphabetically with the "Z" words and Mount Abraham would show up with the "A" words. However, if the query names are listed as "Mount Zester" and "Mount Abraham" then they will both show up with the "M" words.

Create a form named "Search Form" with simple text fields that will be used to refer to the Notes fields of the documents in the "Search View" below. Name these fields form_Field1 and form_Field2 which correspond to Notes fields named Field1 and Field2. Add a field named "SaveOptions" with a default value of "0" (with the quotes) so the form is not saved when submitted.