📄 readme_usearch.html
字号:
<!doctype html public "-//w3c//dtd html 4.0 transitional//en"><html><head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="Generator" content="Quadralay WebWorks Publisher 5.0.4"> <meta name="Page" content="Default"> <meta name="Title" content="Oracle Ultra Search 9.2.0.1 README"> <meta name="GENERATOR" content="Mozilla/4.77 [en] (Windows NT 5.0; U) [Netscape]"> <meta name="Author" content="Cindy Hsin"> <title>Oracle Ultra Search 9.2.0.1 readme</title></head><body bgcolor="#FFFFFF"><div CLASS="IND"><h1 CLASS="ProductTitle"><font face="Arial, Helvetica, sans-serif">Oracle Ultra Search 9.2.0.1 README</font></h1><div CLASS="BP">This document summarizes the differences between OracleUltra Search in Oracle9<i>i</i> Release 2 (9.2.0) andits documented functionality.</div><p><a NAME="999452"></a><p CLASS="BP">To view The Ultra Search documentation:<ul CLASS="LB1"><li CLASS="LB1" TYPE="DISC"><a NAME="999447"></a>View the documentation with a Web browser from theOracle documentation CD.</li><li CLASS="LB1" TYPE="DISC"><a NAME="999448"></a>View the complete Ultra Search Documentation at <tt>$ORACLE_HOME/ultrasearch/doc/help/toc</tt>.<tt>htm</tt>.</li><li CLASS="LB1" TYPE="DISC"><a NAME="999445"></a>View the documentation through the Oracle Ultra SearchAdministration Tool by clicking the Help icon.</li></ul><h2 CLASS="H1"><font face="Arial, Helvetica, sans-serif"><font color="#330099">1 Certificationand System Requirements</font></font></h2><p><a NAME="999595"></a><!--TOC=h3-"999595"--><h3 CLASS="H2"><a NAME="999017"></a><font face="Arial, Helvetica, sans-serif"><font color="#330099">1.1Ultra Search Installation</font></font></h3><!--/TOC=h2--><a NAME="999593"></a><p CLASS="H3">For installation documents within an Ultra Search installation,see $ORACLE_HOME/ultrasearch/doc/help/install.htm.<p><div CLASS="H3">The Ultra Search middle tier is compliant with Oracle J2EEcontainer (OC4J). Follow the instructions at $ORACLE_HOME/ultrasearch/doc/help/install_midtier.htmto configure the Ultra Search middle tier with OC4J.</div><p><div CLASS="H3">Ultra Search requires you to have either JRE or JDK onthe database host where you install the Ultra Search server component.By default, JDK 1.3.1 is installed by Oracle Universal Installer (OUI)during database installation under directory $ORACLE_HOME/jdk. If you usea different JDK, either create a soft link, or copy the files from thelocation where you install JDK to $ORACLE_HOME/jdk. Ultra Search is certifiedwith JDK 1.3.1.<h2 CLASS="H1"><font face="Arial, Helvetica, sans-serif"><font color="#330099">2 GeneralIssues and Workarounds</font></font></h2><!--/TOC=h1--><a NAME="999731"></a><!--TOC=h2-"999731"--></div><h3><font face="Arial, Helvetica, sans-serif"><font color="#330099"><font size=+1>2.1 New Features Addendum</font></font></font></h3>In addtion to new features covered in the Ultra Search online documentation,the following should be noted:<ul><a NAME="new_web"></a><li>Web data source model enhancement</li><br>There is no default Web data source in the 9.2.0 release. Users cancreate any number of Web data sources where each one is completely self-contained.In other words, its behavior is the same as any other type of data source.<br> <li>Improved query performance</li><br>A new Java API is provided for improved query performance. The methodsignature is public java.util.String compileForCount(). The complete methoddescription is in section 6.1.1.<br> <li>Web data source path inclusion/exclusion</li><br>Users can specify a URL path for crawler inclusion or exclusion. Thislets the crawler crawl a subset of a particular host.<br> <li>Mimetypes as a default search attribute</li><br>In addition to the author, description, subject, and title defaultsearch attributes, the mimetype search attribute has been added to let users restrict query resultsbased on document type.</ul><h3 CLASS="H3"><font face="Arial, Helvetica, sans-serif"><font color="#330099">2.2 Deprecated and Desupported Features</font></font></h3><div CLASS="H3">The following features have been deprecated or desupportedin Oracle Ultra Search release 2 (9.2.0):<ul><li>9.0.1 Query API Sample</li><br>Deprecated.<p><li>Running Ultra Search Middle-Tier Components on OSE (Oracle Servlet Engine)</li><br>OSE has been desupported by Oracle. Use <i>Oracle9i</i> ApplicationServer.<p><li>Default Web data source and Default schedule</li><br>Desupported due to web data source model change. Use the migrationscript to migrate to Ultra Search 9.2.0. For more information about the newweb data source model, refer to <a href="#new_web">Web data source modelenhancement</a> section.</ul></div><h2 class="H1"><font face="Arial, Helvetica, sans-serif"><font color="#330099">3 ConfigurationIssues and Workarounds</font></font></h2><!--/TOC=h1--><a NAME="996757"></a><p class="BP">This section describes Ultra Search configuration issuesand their workarounds.<h3><a NAME="999592"></a><!--TOC=h2-"999592"--></h3><h3 CLASS="H2"><font face="Arial, Helvetica, sans-serif"><font color="#330099">3.1 Settingup Ultra Search Sample Query Applications</font></font></h3><!--/TOC=h2--><a NAME="999593"></a><p CLASS="BP">In addition to the configuration steps described in <tt>$ORACLE_HOME/ultrasearch/doc/help/install_midtier</tt>.<tt>htm</tt>,you must also follow these steps in order for the Ultra Search sample query applications to function correctly.<br><a NAME="999594"></a><p CLASS="BP">To configure search.jsp and mail.jsp, you must manually editthe file common_customize_instance.jsp and change the values of the 'm_connection_string', 'm_instance_schema ', and 'm_instance_password' variables. The file common_customize_instance.jsp is in the $ORACLE_HOME/ultrasearch/sample/querydirectory.<div CLASS="BP"></div><p CLASS="BP">To configure usearch.jsp and tsearch.jsp, you must manuallyedit these files and change the variable settings for 'username', 'password',and 'jdbc_url'. The file usearch.jsp is in the $ORACLE_HOME/ultrasearch/sample/querydirectory, and tsearch.jsp is under the $ORACLE_HOME/ultrasearch/sample/query/tagdirectory.<div CLASS="BP"></div><p CLASS="BP">For detail information, see:<div CLASS="BP">$ORACLE_HOME/ultrasearch/sample/query/README.html,</div><div CLASS="BP">$ORACLE_HOME/ultrasearch/sample/query/README_complete.html,</div><div CLASS="BP">$ORACLE_HOME/ultrasearch/sample/query/tag/README.html</div><div CLASS="BP"></div><p><a NAME="999595"></a><!--TOC=h3-"999595"--><h4 CLASS="H3"><font face="Arial, Helvetica, sans-serif"><font color="#330099">3.1.1 Settingup 9.0.1 Query API Sample - Deprecated in 9.2.0</font></font></h4><!--/TOC=h3--><a NAME="999596"></a><p CLASS="BP">To configure <tt>gsearch</tt>.<tt>jsp</tt>, you must manuallyedit the file and change the values of the 'username' and 'password' variables,and then edit <tt>ultrasearch</tt>.<tt>properties</tt> to change the connectionstring. The file <tt>gsearch</tt>.<tt>jsp</tt> is in the <tt>$ORACLE_HOME/ultrasearch/sample/query/9i</tt>directory.<br><a NAME="999597"></a><p CLASS="BP">For editing the <tt>ultrasearch</tt>.<tt>properties</tt>,see <tt>$ORACLE_HOME/ultrasearch/doc/help/install_midtier</tt>.<tt>htm</tt>.<br><a NAME="999598"></a><p CLASS="BP">For detailed information, see: <tt>$ORACLE_HOME/ultrasearch/sample/query/9i/README</tt>.<tt>html</tt><br><a NAME="999072"></a><!--TOC=h2-"999072"--><h3 CLASS="H2"><font face="Arial, Helvetica, sans-serif"><font color="#330099">3.2 Runningthe Crawler</font></font></h3><!--/TOC=h2--><a NAME="999073"></a><p CLASS="BP">The Ultra Search Crawler is a Java process that runs on theserver tier when launched. Therefore, Ultra Search requires you to haveeither JRE or JDK installed on the database host where you install theUltra Search server component.<br><a NAME="999417"></a><center><table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="80%" CLASS="NoteAlso" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note" ><tr CLASS="NoteAlso"><td CLASS="NoteAlso"><a NAME="999429"></a><b><font face="Arial, Helvetica, sans-serif">SeeAlso:</font></b><a NAME="999421"></a><p CLASS="NB"><a href="#999017">"Ultra Search Installation"</a></td></tr></table></center><a NAME="999074"></a><!--TOC=h3-"999074"--><h4 CLASS="H3"><font face="Arial, Helvetica, sans-serif"><font color="#330099">3.2.1 Settingthe JOB_QUEUE_PROCESSES parameter</font></font></h4><!--/TOC=h3--><a NAME="999077"></a><p CLASS="BP">Oracle Ultra Search schedule launching uses the <tt>DBMS_JOB</tt>package. Therefore, the Oracle Ultra Search DBA must make sure that thereis least one SNP process running. In other words, the initialization parameterfile for the Oracle Ultra Search database instance should contain a linethat specifies the <tt>JOB_QUEUE_PROCESSES</tt> parameter to be at least2.<br><a NAME="999078"></a><!--TOC=h3-"999078"--><br><a NAME="999785"></a><!--TOC=h2-"999785"--><h3 CLASS="H2"><font face="Arial, Helvetica, sans-serif"><font color="#330099">3.3 GlobalizationSupport</font></font></h3><!--/TOC=h2--><a NAME="999786"></a><p CLASS="BP">Oracle Ultra Search, like any other application that usesthe database to store content, requires that the character set of the databasebe able to support the character set used at the application level. Forexample, if the application language is in Japanese, and if the databasecharacter set is SF7ASCII, then any data that the application attemptsto store will be corrupted, because the SF7ASCII character set does not supportAsian languages.<br><a NAME="999787"></a><p CLASS="BP">The <i>Oracle9i Globalization Support Guide</i> providesdetailed information on database character sets.<br><a NAME="999792"></a><center><table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="80%" CLASS="Note" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note" ><tr CLASS="Note"><td CLASS="Note"><hr><a NAME="999790"></a><b><font face="Arial, Helvetica, sans-serif">Note:</font></b><a NAME="999791"></a><p CLASS="NB">Universal Character Sets, such as UTF8, attempt to supportall languages of the world, including, but not limited to, Asian, European,and Middle Eastern languages.<hr></td></tr></table></center><h2 CLASS="H1"><font face="Arial, Helvetica, sans-serif"><font color="#330099">4 UsefulInformation</font></font></h2><!--/TOC=h1--><a NAME="999731"></a><!--TOC=h2-"999731"--><h3 CLASS="H3"><font face="Arial, Helvetica, sans-serif"><font color="#330099">4.1 VerifyingCrawler Progress</font></font></h3><!--/TOC=h3--><a NAME="999079"></a><p CLASS="BP">After you have configured the Oracle Ultra Search system,you can launch a crawler immediately from the Schedule screen.<br><a NAME="999080"></a><p CLASS="BP">View the Oracle Ultra Search crawler status by checking itsstate in the Oracle Ultra Search Administration Tool page.<br><a NAME="999081"></a><p CLASS="BP">Click the "Schedules" tab, and you will see a table that listsall schedules and their state.<br><a NAME="999082"></a><p CLASS="BP">When a schedule is launching, it is in the "LAUNCHING" state.During the launching state, URLs to be crawled are marked by a SQL update operation. The amount of time this processmay take depends on how many URLs are there for update. In cases such as maintenance crawling of the schedule, there canbe be millions of URLs to update. This may cause the schedule to remain in the "LAUNCHING"state for a very long time.<br><a NAME="999083"></a><p CLASS="BP">When a schedule has completed launching and the crawler hasbegun fetching pages, the state changes to "EXECUTING".<h3 CLASS="H2"><font face="Arial, Helvetica, sans-serif"><font color="#330099">4.2 PerformanceTuning</font></font></h3><h4 CLASS="H2"><font face="Arial, Helvetica, sans-serif"><font color="#330099">4.2.1 CrawlerPerformance Tuning</font></font></h4><!--/TOC=h2--><a NAME="999732"></a><p CLASS="BP">For Crawler performance tuning, see Step 5 in Configuringthe Oracle Server for Ultra Search at <tt>$ORACLE_HOME/ultrasearch/doc/help/configure_server</tt>.<tt>htm</tt>.⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -