QUESTIONS & ANSWERS
-------------------

1. What is Ultra Search?

Oracle Ultra Search lets you index and search Web sites, database tables, files, mailing lists, Oracle9i Application Server (9iAS)
Portals, and user-defined data sources. As such, you can use Oracle Ultra Search to build different kinds of search applications. It centralizes the management, indexing, searching, and locating
of text based data. Ultra Search uses a crawler to index documents. The crawled data is used to build an index that is stored in an Oracle 9i database.

2. Where is the documentation for Oracle Ultra Search?

The Ultra Search online documentation is included with the generic online documentation set that is shipped with the 9i database software. Additionally, the Ultra Search documentation can be found on Oracle Technical Network (OTN):

http://otn.oracle.com/docs/products/ultrasearch/content.html

3. Who is the WKSYS user ?

WKSYS is a privileged Oracle user who owns the Ultra Search data dictionary and internal objects. Ultra Search uses the WKSYS user for storing Ultra Search packages and metadata. Other user defined objects or data should not be stored in the WKSYS schema.

By default, the account is locked. The default password is WKSYS. The password should be changed immediately for security purposes. To unlock and change the WKSYS user:
ALTER USER WKSYS ACCOUNT UNLOCK;
ALTER USER WKSYS IDENTIFIED BY ;

4. What are the WKADMIN and WKUSER role?

In 9.0.1.x, WKADMIN privilege gets created when Ultra Search is installed. This role allows users that have been granted it rights to perform all administrative duties on all instances for Ultra Search.

The WKUSER privilege will allow a user to modify general settings for the instance. These include: creating data sources, data groups, setting up a schedule, crawling.

The WKUSER role has the following privileges: execute on SYS.DBMS_LOCK to WKUSER, connect, create procedure, create trigger, create table, create type, create cluster.

In 9.2.0.x, the user tab in the Administration Tool allows the Ultra Search Administrator to grant either “super-user” or “general
administrative” roles to a user. The “Super-User” role is the same as WKADMIN. The “General Administrative” role is the same as WKUSER.

5. How does Ultra Search use Oracle Text features?

Ultra Search is uses the Oracle Text engine within the 9i DB to create and maintain the text indexes. Ultra Search adds the “crawler”
functionality, provides application and administration tools to setup and maintain the Ultra Search setup. The Ultra Search Administration
Tools and Query applications are easy to use and fully functional. No knowledge of Oracle Text is required to setup and use Ultra Search.

6. What is an Ultra Search Instance?

An Instance is where crawled data, schedule information, indexes, etc. are stored. Instances are logically separate which allows
the management of multiple Ultra Search instances for a given organization in a single database organization. For example, an organization's
marketing, human resources, and development portals can each have their own Ultra Search instances. All data belonging to an instance,
such as defined data sources, schedules, and index data, are entirely independent from data belonging to other Ultra Search instances.

Each Instance is associated with a database user schema.

7. What is the Ultra Search Universal Crawler?

The Oracle Ultra Search crawler is a shared server Java application that gathers documents from the data sources you specify during
configuration. When activated, the Crawler spawns processor threads that fetch documents from different data sources. The crawler
stores the documents in a local file system cache. With the cached data, Oracle Ultra Search creates the index required for querying. The crawler scans new, updated and/or deleted documents to index. This index is used for querying.

In addition, a remote crawler can be setup on a separate server to help enhance performance.

8. Can Ultra Search crawl data stored in proprietary systems?

The Ultra Search Crawler API can implement a crawler agent to crawl and index a proprietary document repository, such as Lotus Notes
or Documentum. In Ultra Search, the proprietary repository is called a user-defined data source. The module that enables the crawler to access the data source is called a crawler agent.
The agent collects document URLs and associated metadata from the user-defined data source and returns the information to the Ultra
Search crawler, which enques it for later crawling. The crawler agent must be implemented in Java using the Ultra Search crawler agent API.

9. Why would I want to crawl emails?
Email documents contain valuable information, but they are not structured to find specific relevant information easily. Oracle Ultra Search lets you retrieve and index emails on a server that supports the IMAP4 protocol.
An email source is a data source that derives its content from emails sent to a specific email address. When the Ultra Search crawler
searches an email source, the crawler collects all emails that have the specific email address in any of the "To:" or "Cc:" email header fields.
10. What is a data source?
A data source is a collection of documents. The data source is characterized by the properties of its location; such as a Web site or an email inbox. The Ultra Search crawler retrieves data from one or more data sources.
You can define one or more of the following data sources:
- Web sites
- Database tables
- Files
- Mailing lists
- Oracle9iAS Portal page groups
- User-defined data sources (requires crawler agent)

11. What is a data group and attribute?

A data group is a collection of data sources. The Ultra Search Administrator defines source groups through the Administration Tool. End users have the option to specify data groups to search via the Query Tool.

An attribute is metadata (information) about the document. Information comes from either a meta tag of a HTML document, an Oracle database column or email headers. An end user can refine their searches based on the attribute chosen at query time.

12. What is the Administration Tool used for?

The Ultra Search Administration Tool is a Java Server Page (JSP) Web application used to do the following:
- Define Ultra Search instances
- Manage administrative users
- Define crawler parameters, such as data sources
- Configure and schedule the Ultra Search crawler
- Set query options

13. What are the sample applications used for?

Ultra Search includes fully functional sample query applications to query and display search results. The query applications are written as Java server page (JSP) applications.
The sample query applications include a sample search portlet. The sample Ultra Search portlet demonstrates how to write a search portlet for use in Oracle 9iAS Portal.
If you do not want to use the Ultra Search sample query applications, you can build your own query application by directly invoking the Ultra Search Java Query API.

14. Can I write my own Ultra Search application?

Oracle Ultra Search provides a flexible, easy-to-integrate query framework as a query API. The API methods retrieve and display
query results. The API is written in Java. Therefore, it is compatible with a large spectrum of Web application servers that support any Java-based technology, such as Java server pages (JSP version 1.0 and higher).
Because the API is coded in Java, you can invoke the API methods from any Java-based application, such as from a Java servlet or
a Java server page (as in the case of the provided sample query applications). For rendering emails that have been crawled and indexed, you can also directly invoke the Ultra Search Java Email API methods.

15. How can I backup Ultra Search?

In 9.2.0.x, it is possible to create a read only snapshot of the master Ultra Search instance. This snapshot can be used as a backup. If the original instance becomes corrupted, the snapshot can be made updatable.

Another backup method is a cold backup of the system.

Additionally, export/import that could serve as a backup.

As with all backup plan, it is imperative to test the plan before the plan is

來自metalink.oracle.com