| Oracle® Collaboration Suite Release Notes Release 2 (9.0.4.1) for AIX-Based Systems Part Number B12205-02 |
|
|
View PDF |
| Oracle® Collaboration Suite Release Notes Release 2 (9.0.4.1) for AIX-Based Systems Part Number B12205-02 |
|
|
View PDF |
This chapter summarizes release note issues associated with Oracle Ultra Search.
The following sections are included in the chapter:
Oracle Ultra Search is a high-level search component supplied with the Oracle Collaboration Suite that you can use to search across other Oracle Collaboration Suite components, corporate Web servers, databases, mail servers, file servers, and Oracle9iAS Portal instances. It uses information you provide to crawl through the various disparate repositories of information in your company searching for documents according to your search criteria. Oracle Ultra Search searches over 150 proprietary document types.
This release of Ultra Search includes the following features:
Support for new attribute types, including date ranges and list-of-values (LOV)
Improved Query APIs and new support for JSP tags
Integration with 9iASPortal - native crawling of Portal instances
The Crawler Extensibility API - this is a Java API to adapt the Ultra Search crawler to index and search data sources
Relevance boosting - this adjusts the ranking of search results
Display URL support - this renders the results of database crawls in a Web screen
|
See Also: Oracle Ultra Search User's Guide |
The Ultra Search welcome page is now at the following location:
http://host:port/ultrasearch/welcome/
In previous releases, it was at the following location:
http://host:port/ultrasearch/
The Ultra Search installer creates a default Ultra Search instance based on the default Ultra Search test user, so users can test Ultra Search functionality based on the default instance after installation.
The default instance name is WK_INST. It is created based on the database user WK_TEST. In other words, WK_TEST is the instance administrator for WK_INST. The default user password is WK_TEST.
For security purposes, WK_TEST is locked after the installation. You must login to the database as DBA role, unlock the user, then change the password. (The password expires after the installation.) Make sure to update the cached schema password using the administration tool Edit Instance page after you change the password in the database.
The default instance is also used by the Ultra Search sample application. You must update the data-sources.xml file, as described in the 'Configuring the Middle Tier Component' section of the Oracle Ultra Search User's Guide.
You can override the search results and influence the order that documents are ranked in the query result list with document relevancy boosting. This can promote important documents to higher scores and make them easier to find.
Relevancy boosting has the following limitations:
Comparison of the user's query against the boosted queries uses exact string match. This means that the comparison is case-sensitive and space-aware. Therefore, a document with a boosted score for "Ultra Search" is not boosted when user enters "ultrasearch".
Relevancy boosting requires that the query application pass in the search term in the Query API getResult() method call. The sample applications are designed to pass the basic search terms as the boost term. Advanced search criteria based on search attributes are ignored.
The Ultra Search Complete Sample Query Application is translated into the same set of languages supported in Oracle Collaboration Suite Release 2.
|
See Also: Oracle Collaboration Suite Installation and Configuration Guide for the list of languages |
For Web data sources, there is a new option to index or not index dynamic pages. The default value is Yes, so dynamic URLs are crawled and indexed.
For data sources already crawled with this option, setting Index Dynamic Page to No and recrawling the data source removes all dynamic URLs from the index.
Some dynamic pages appear as multiple search hits for the same page, and you may not want them all indexed. Other dynamic pages are each different and need to be indexed. You must distinguish between these two kinds of dynamic pages. In general, dynamic pages that only change in menu expansion without affecting its contents should not be indexed. Consider the following three URLs:
http://itweb.oraclecorp.com/aboutit/network/npe/standards/naming_convention.html http://itweb.oraclecorp.com/aboutit/network/npe/standards/naming_convention.html?nsdnv=14z1 http://itweb.oraclecorp.com/aboutit/network/npe/standards/naming_convention.html?nsdnv=14
The question mark ('?') in the URL indicates that the rest of the strings are input parameters. The duplicate hits are essentially the same page with different side menu expansion. Ideally, the same query should yield only one hit:
http://itweb.oraclecorp/com/aboutit/network/npe/standards/naming_convention.html
Dynamic page index control applies to the whole data source. So, if a Web site has both kinds of dynamic pages, then you need to define them separately as two data sources in order to control the indexing of those dynamic pages.
If you register authentication information for a data source, then the Ultra Search administration tool automatically turns on cookie support. You can override this and turn cookies support off.
During crawling, documents are stored in the cache directory. Every time the preset size is reached, crawling stops and indexing starts. In previous releases, the cache file was always deleted when indexing was done. You can now specify not to delete the cache file when indexing is done. This option applies to all data sources. The default is to delete the cache file after indexing.
The Ultra Search crawler uses the Oracle Text INSO filter ctxhx, which requires that your shared library path environment variable contain the $ORACLE_HOME/ctx/lib/ path. Without that, filtering fails for any binary document.
At installation, the Oracle Installer automatically sets the variable to include $ORACLE_HOME/ctx/lib/. However, if, after the installation, you restart the database, then you must manually set your shared library path environment variable to include $ORACLE_HOME/ctx/lib/ before starting the Oracle process. You must restart the database to pick up the new value for filtering to work.
For example, on UNIX set the LIBPATH environment variable to include $ORACLE_HOME/ctx/lib, and on Windows set the $PATH environment variable to include $ORACLE_HOME/bin.
Table 6-1 lists known bugs for Oracle Ultra Search.
Table 6-1 Oracle Ultra Search Known Bugs
| Bug Number | Description | Action |
|---|---|---|
| 2881313 | Web Provider Error
This error is received when registering the Ultra Search portlet. |
For the latest information on this bug, contact your Oracle Support Representative.
Update Change the value of |
| 3483945 | The WKPROXY user does not have the super-user privilege.
When using the WK_INST instance created during installation, scheduling and running a job work properly. However, if the instance is recreated or a new instance is created, scheduling does not work. |
For the instance to work properly, apply the following workaround.
Grant WKPROXY the super-user privilege, as follows:
Log in to the Infrastructure database as exec wk_adm.use_instance(your_instance_name)select ji_id from wk$job_info where ji_type=1;exec wk_job.disable_job(ji_id)exec wk_job.enable_job(ji_id) Note: Every job for the instance needs to be disabled and enabled. Resume the schedule, as follows:
|
