Understanding Component Search Options for Fluid Applications

For a fluid component, you have these options for providing search when a user accesses the component:

Fluid Component Search Option	Description
Real-time	Based on a pivot grid that builds a query against the component search record. See Setting up Real-Time Search for Fluid Components.
Keyword	Based on a search index created using the Search Framework and mapped to the fluid component. See Setting up Keyword Search for Fluid Components.
Configurable Search	Configurable search enables you to configure the presentation of your search page (standard or keyword) for an individual component or system wide. See Search Technology: Guidelines on Using Configurable Search for Fluid Components.

For any custom fluid component that you create, Oracle recommends that as part of the normal page and component development, you also create:

• A component-based pivot grid (for real-time component search).

• A search definition in the Search Framework for indexing the underlying application data (for keyword search).

A custom fluid component must employ at least one of the search options. You can employ both options. If neither search option is configured, you will need to bypass search completely using some other mechanism (for example, using SearchInit PeopleCode). Otherwise, the system displays an error, preventing access to the component.

When comparing one search option over the other, consider that the real-time search runs a search on all the data that is currently stored in the database while the keyword search may contain less current data. How current the data provided by the keyword search depends on how frequently the search indexes are updated. If you intend to employ only one of these search options, to ensure the best user experience, Oracle recommends employing the real-time search so the system reflects real-time data for end users.