3 Installing and Configuring Ultra Search

Installing As Part of Oracle Application Server Metadata Repository Creation

The Ultra Search backend is installed as part of the Oracle Application Server Metadata Repository (MR) creation. You can create the Metadata Repository using the Oracle Universal Installer (OUI), or you can create the MR on top of an existing customer database using RepCA (Repository Creation Assistant). For more information, refer to the Oracle9i Application Server Installation Guide and the Oracle Application Server Repository Creation Assistant guide, respectively.

IMPORTANT: If you are using RepCA to create the Metadata Repository, before you can use Ultra Search you need to perform the following post-install configuration steps:

1. If not already present, install JDK 1.4.1 or later on the system on which the MR was installed.

2. Go to the ultrasearch/admin directory of the RepCA CD. Then execute the wkrepca.sql script with SQL*Plus. You will have to connect as the wksys user and pass to the script the path to the JDK 1.4.1 or later Java executable. For example:

   sqlplus wksys/schema_password @repca_cd/ultrasearch/admin/wkrepca.sql
             /usr/local/jdk1.4/bin/java
   
   

   This will tell the Ultra Search backend where to find the Java executable.

Installing Into an Existing Database

Oracle Application Server MR can be installed on top of an existing database; this is the preferred way of installing Ultra Search into an existing database. Although doing so carries the overhead of installing every other Oracle Application Server component's schema, it does give you the benefits of Oracle Application Server infrastructure (well defined High Availability practices, automated IM integration and re-association, and so on). Nevertheless, you can install just Ultra Search into an existing database.

Let's assume ORACLE_HOME is where you want to install the Ultra Search backend. To install into an existing database, follow these steps:

1. If $ORACLE_HOME/ultrasearch already exists, back it up by renaming it (for example, $ORACLE_HOME/ultrasearch.old)

2. Copy repca_dir/ultrasearch to $ORACLE_HOME/ultrasearch, where repca_dir represents the topmost directory on the RepCA CD, containing the ultrasearch directory.

3. Change the current directory to $ORACLE_HOME/ultrasearch/admin.

4. If the Ultra Search schema, wksys, already exists on the target database, then uninstall it by executing:

   sqlplus /nolog @$ORACLE_HOME/ultrasearch/admin/wk0deinstall.sql "sys" syspw cstr
   
   

   Following is the meaning of each parameter:

5. Next, run the SQL*Plus script wk0setup.sql. For example:

   sqlplus /nolog @$ORACLE_HOME/ultrasearch/admin/wk0setup.sql $ORACLE_HOME
      cstr "sys" syspw "as sysdba" wksyspw tblspc tmptblspc "portal"
      cfs "oui" psep jdbcdrv jdbcnls jexec ctxhx jdbc_node 
      jdbc_all $ORACLE_HOME
   
   

   where the various parameters are as follows (parameters should be enclosed in quotes to avoid misinterpretation):

   • cstr—TNS alias preceded with '@' (for example, @inst1), this parameter can also be passed in as a single white space (' ')

   • syspw—password for the sys database user/schema

   • wksyspw—password to be used for the Ultra Search schema wksys

   • tblspc—tablespace for wksys

   • tmptblspc—temporary tablespace for wksys

   • cfs—if ORACLE_HOME is on a Cluster File System (CFS) then 'true'; else 'false'

   • psep—path separator (for example, on UNIX this is ':', on Windows it is ';')

   • jdbcdrv—path to JDBC drivers, classes12.zip (for example, $ORACLE_HOME/jdbc/lib/classes12.zip)

   • jdbcnls—path to nls_charset12.zip or orai18.jar (for example, $ORACLE_HOME/jdbc/lib/nls_charset12.zip)

   • jexec—Java executable path (for example, /packages/jdk1.4.1/bin/java). Note that this has to point to a JDK 1.4.1 or later installation

   • ctxhx—path to INSOFILTER, ctxhx (for example, $ORACLE_HOME/ctx/bin/ctxhx)

   • jdbc_node—thin JDBC connect string, and only the part after the '@' (for example, host:port:sid); note that in case of RAC, this connect string must be to the current node

   • dbc_all— same as JDBC_NODE, but in case of RAC with CFS true, this JDBC string should include all the RAC nodes (hint: use TNS syntax)

Enabling Ultra Search to Process Binary Files

The Ultra Search crawler uses the Oracle Text INSO filter, ctxhx, for processing of binary files. These are non text, non HTML files like PDF files, Microsoft Word files, and so on. For Ultra Search to be able to use the INSO filter, the shared library path environment variable must contain the $ORACLE_HOME/ctx/lib path.

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 $LD_LIBRARY_PATH environment variable to include $ORACLE_HOME/ctx/lib, and on Windows set the $PATH environment variable to include $ORACLE_HOME/bin.

Configure the Oracle Database for Ultra Search

After you have installed all Ultra Search components, you can optionally configure the Oracle database. See "Configuring the Oracle Server for Ultra Search" for more information.

Configure a Secure Ultra Search Installation

Step 1: Check the database version requirements and configure Oracle Identity Management.

Before you can set up a secure Ultra Search installation, you must do the following:

• Install or upgrade the Oracle database to 9.2.0.4 or higher. The middle tier and IM (identity management) version should be 9.0.4 or higher. If you have a 9.2.0.4 database, you can use RepCA to convert a 9.2.0.4 database to an Oracle Application Server 9.0.4 metadata repository.

• Install and configure the Oracle Internet Directory

  The middle tier and IM (identity management) version should be 9.0.4 or higher.

• Register the database to Oracle Internet Directory.

  You can use repCA to register the database to Oracle Internet Directory. After registration, you need to perform these manual steps:

  • Add the distinguished name of the database to the database server parameter file, as an RDBMS_SERVER_DN initialization parameter value.

  • Restart the database, so that the new initialization parameter takes effect.

• Configure the Oracle-Oracle Internet Directory SSL link. To establish a secure connection between database and Oracle Internet Directory, follow the instructions in the following books:

  • Configuring Oracle Internet Directory for SSL: "Chapter 13, Secure Sockets Layer (SSL) and the Directory," in the Oracle 9.2 release of the Oracle Internet Directory Administrator's Guide

  • Configuring the database for SSL: Chapter 15, "Managing Enterprise User Security" (Part II, Task 1 - Task 3), in the Oracle Database 9.2 release of the Oracle Advanced Security Administrator's Guide

Secure search functionality requires that the Ultra Search database is Oracle version 9.2.0.4 or higher and that the Ultra Search database is linked to a compatible instance of Oracle Internet Directory. This is necessary because Ultra Search utilizes XML DB functionality, which requires a certain version of Oracle. XML DB, in turn, requires a live link to Oracle Internet Directory, through which it retrieves all LDAP principal information. The Oracle-Oracle Internet Directory link must be running at all times for secure search to work. To set up this link, configure the Oracle Database to use Oracle Identity Management.

Step 2: Restart the Oracle listener.

In the previous step, you configured the Oracle Database to use Identity Management. That process involved configuring ORACLE_HOME for directory usage. You must make sure to restart the Oracle listener to inherit the changes made to ORACLE_HOME. Restart the listener, if you have not already done so.

Step 3: Install or upgrade Ultra Search, if necessary.

After you have configured the Ultra Search database to work with Oracle Internet Directory, you can install or upgrade the Ultra Search backend into the Oracle Server, if you have not already done so.

Step 4: Create the /sys/apps/ultrasearch folder.

Immediately after installation or upgrade, you must run a SQL script to create the /sys/apps/ultrasearch folder in the XML DB repository. This folder stores all Ultra Search ACLs in XML DB.

To create the /sys/apps/ultrasearch folder, do the following:

1. cd to $ORACLE_HOME/ultrasearch/admin

2. Login to the Ultra Search database using SQL*Plus as user WKSYS

3. Invoke the SQL script: @wk0prepxdb.sql

Upon termination, the wk0prepxdb.sql script lists all Ultra Search-related XML DB resources by running the following SQL:

SELECT any_path FROM resource_view WHERE any_path LIKE '%ultrasearch%';

Execution of that SQL statement must show two rows:

/sys/apps/ultrasearch
/sys/apps/ultrasearch_acl.xml

If you do not see this confirmation, then this step has failed, and you cannot proceed. Recheck that all previous steps were performed correctly.

Step 5: Turn on secure search functionality in Ultra Search.

Because there is currently no way to programatically verify a proper Oracle-Oracle Internet Directory installation, the secure search functionality in Ultra Search is turned off by default. You must explicitly turn on this feature after completing all previous steps.

Step 6: Turn On Secure Search in the Query Application.

To turn on secure search functionality in Ultra Search:

1. Login to the Ultra Search database using SQL*Plus as user WKSYS

2. Invoke the following PL/SQL API: exec WK_ADM.SET_SECURE_MODE(1)

The argument (1) indicates that you are turning on secure search.

After you have turned on secure search functionality, you can create Ultra Search instances that are secure search-enabled.

Ultra Search supports secure searches, which return only documents satisfying the search criteria that the search user is allowed to view. To turn on secure search in the query application, follow these steps:

1. Deploy Ultra Search query (ultrasearch_query.ear).

2. Edit the OC4J jazn.xml file to connect to Oracle Internet Directory. For example:

   <jazn provider="LDAP" default-realm="us" location="ldap://localhost:3060">
        <property name="ldap.user" value="orcladmin"/> 
        <property name="ldap.password" value="!welcome"/> 
        </jazn>
   
   

3. Restart OC4J.

4. Edit applications/ultrasearch_query/META-INF/orion-application.xml to turn on JAZN LDAP.

5. Edit applications/ultrasearch_query/query/WEB-INF/web.xml to enable login functionality in usearch.jsp. For example:

   <init-param> 
   <param-name>login enabled</param-name> 
   <param-value>true</param-value> 
   </init-param> 
   
   

6. Enable mod_osso in Apache.

7. Access http://hostname:port/ultrasearch/query/usearch.jsp to see the login function, and test secure search.

   
   

   See Also: "Secure Search"

Backend Reconfiguration After a Database Character Set Change

If the database character set has been changed after Ultra Search installation, you must reconfigure the Ultra Search backend so that it can adapt to the new character set.

Two SQL scripts (wk0prefcheck.sql and wk0idxcheck.sql), located in $ORACLE_HOME/ultrasearch/admin/, are used for this reconfiguration:

• wk0prefcheck.sql is invoked under wksys to reconfigure default cache character set and index preferences.

• wk0idxcheck.sql is needed for reconfiguring instance(s) created before the database character set change (for example, the default instance). This script must be invoked by the instance owner, and wk0prefcheck.sql must be run first, as it depends on reconfigured default settings generated by wk0prefcheck.sql.

  Running wk0idxcheck.sql also drops and recreates the Oracle Text index used by Ultra Search. If there are already data sources indexed, you must force a recrawl of all of the data sources.

  wk0idxcheck.sql must be run once for each instance. For example, if there are two instances, "inst1" and "inst2," owned by "owner1" and "owner2," respectively, then wk0idxcheck.sql should be run twice: once by "owner1" and once by owner2.

Configuring the Middle Tier with Oracle HTTP Server and OC4J

1. For OC4J configuration, modify the following OC4J configuration files: server.xml, application.xml, and default-web-site.xml in $ORACLE_HOME/j2ee/OC4J_Portal/config/. The configuration of OC4J works with Ultra Search J2EE applications.

   
   

   See Also: Oracle Application Server Containers for J2EE documentation for more information on deploying EAR and WAR applications and for the more advanced functionality of OC4J

   • For server.xml, under the <application-server> tag, add the following:

     <application name="UltrasearchAdmin" path="$ORACLE_HOME/ultrasearch/webapp/ultrasearch_admin.ear" /> 
     
     <application name="UltrasearchQuery" path="$ORACLE_HOME/ultrasearch/ultrasearch_query.ear" /> 
     
     <application name="UltrasearchPortlet" path="$ORACLE_HOME/ultrasearch/webapp/ultrasearch_portlet.ear" />
     

     
     

     Note: These lines let OC4J know that it must deploy the Ultra Search EAR file, as well as define where this EAR files is. Ultrasearch_admin.ear contains the Ultra Search administration tool Web application. The sample.ear file contains the sample query JSP pages. After OC4J deploys sample.ear, you can see the $ORACLE_HOME/ultrasearch/sample directory. Use the JSPs in this directory to create your own query Web pages. For more information on this directory, see "Testing the Ultra Search Sample Query Applications".

   • For application.xml, under the <orion-application> tag, add the following:

     <library path="$ORACLE_HOME/ultrasearch/lib/ultrasearch_query.jar" />
     <library path="$ORACLE_HOME/ultrasearch/webapp/config" />
     <library path="$ORACLE_HOME/jlib/uix2.jar" />
     <library path="$ORACLE_HOME/jlib/share.jar" />
     <library path="$ORACLE_HOME/jlib/regexp.jar" />
     <library path="$ORACLE_HOME/jdbc/lib/nls_charset12.zip" />
     <library path="$ORACLE_HOME/jlib/repository.jar"/>
     <library path="$ORACLE_HOME/jlib/ohw.jar"/>
     <library path="$ORACLE_HOME/jlib/ldapjclnt9.jar"/>
     <library path="$ORACLE_HOME/j2ee/home/jazn.jar"/>
     <library path="$ORACLE_HOME/portal/jlib/ptlshare.jar"/>
     <library path="$ORACLE_HOME/portal/jlib/pdkjava.jar"/>
     
     

     The preceding libraries are required for the Ultra Search administration tool and query Web applications to run.

     
     

     Note: $ORACLE_HOME/ultrasearch/webapp/config contains the ultrasearch.properties file. For more information, see "Editing the ultrasearch.properties File".

   • For default-web-site.xml

     Under <web-site> tag, add the following:

     <web-app application="UltrasearchQuery" name="query" 
          root="/ultrasearch/query" />
     <web-app application="UltrasearchQuery" name="welcome"
          root="/ultrasearch" />
     <web-app application="UltrasearchAdmin" name="admin"
          root="/ultrasearch/admin" />
     <web-app application="UltrasearchAdmin" name="admin_sso"
          root="/ultrasearch/admin_sso" />
     <web-app application="UltrasearchAdmin" name="ohw"
          root="/ultrasearch/ohw" />
     
     

     The preceding lines describe which Web application (WAR file) in the Ultra Search EAR files is deployed.

     • The application field describes the application name. It should match the application name in server.xml.

     • The name field describes the Web application name. This should match the WAR file name within the EAR file corresponding to the application.

     • For root, specify the virtual path for this Web application. The virtual path is the path under the URL. For the administrative Web application, access it using http://hostname.domainname:port/ultrasearch/admin/.

       
       

       Note: The virtual path for a particular Web application is defined in three files: default-web-site.xml, mod_oc4j.conf, and application.xml in the META-INF directory of the EAR file. (The META-INF is created by extracting the EAR file.) You must modify the root attribute of web-app in default-web-site.xml, and the value enclosed by tag context-root in application.xml to change the virtual path point to each Web application.

2. Modify modOC4J configuration files. Add the following to $ORACLE_HOME/Apache/Apache/conf/mod_oc4j.conf:

   Oc4jMount /ultrasearch/             OC4J_Portal 
   Oc4jMount /ultrasearch/*            OC4J_Portal 
   Oc4jMount /ultrasearch/query        OC4J_Portal 
   Oc4jMount /ultrasearch/query/*      OC4J_Portal 
   Oc4jMount /ultrasearch/ohw          OC4J_Portal 
   Oc4jMount /ultrasearch/ohw/*        OC4J_Portal 
   Oc4jMount /ultrasearch/admin_sso    OC4J_Portal 
   Oc4jMount /ultrasearch/admin_sso/*  OC4J_Portal 
   Oc4jMount /ultrasearch/admin        OC4J_Portal 
   Oc4jMount /ultrasearch/admin/*      OC4J_Portal 
   
   

3. Ultra Search sample pages require JDBC connections to the database as the instance owner. Due to JServ limitations in the Oracle9i release, the user name, password and connection string used to create the JDBC connection are hard-coded inside the sample JSP code. To configure the JSP to query a specific instance, edit the JSP source code, and replace the user name, password, and connection string values. All sample JSP source code is in the OC4J applications directory.

   The following files contain user name, password, and connection string values:

   • 9i/gsearch.jsp

   • 9i/display.jsp

   • 9i/gsearchf.jsp

   • 9i/gutil.jsp

   • 9i/mail.jsp

     
     

     Note: The Oracle9i JSP files are being deprecated. It is not necessary to configure them if you do not plan to use them.

Configuring the Administration Tool with Single Sign-On Server

To configure the Ultra Search administration tool with the Oracle Single Sign-On (SSO) server, you must also follow these steps in addition to the configuration in "Configuring the Middle Tier with Oracle HTTP Server and OC4J".

1. For OC4J configuration, modify the following OC4J configuration files: application.xml and default-web-site.xml in $ORACLE_HOME/j2ee/OC4J_Portal/config/.

   • For application.xml, under <orion-application> tag, add the following:

     <library path="$ORACLE_HOME/jlib/repository.jar" />
     <library path="$ORACLE_HOME/jlib/jndi.jar" />
     <library path="$ORACLE_HOME/jlib/ldapjclnt9.jar" />
     <library path="$ORACLE_HOME/j2ee/home/jazn.jar" />
     <library path="$ORACLE_HOME/j2ee/home/jaas.jar" />
     
     

   • For default-web-site.xml, under <web-site> tag, add the following:

     <web-app application="UltrasearchAdmin" name="admin" root="/ultrasearch/admin_sso" /> 
     
     

2. Modify modOC4J configuration files. Add the following to mod_oc4j.conf:

   Oc4jMount /ultrasearch/admin_sso/*  OC4J_Portal 
   
   

3. Confirm the following:

   • $ORACLE_HOME/Apache/Apache/conf/httpd.conf includes oracle_apache.conf

   • $ORACLE_HOME/Apache/Apache/conf/oracle_apache.conf includes ultrasearch.conf

   • $ORACLE_HOME/ultrasearch/webapp/config/ultrasearch.conf has the following content:

     # add alias for ultra search online help and welcome page

     Alias /ultrasearch/doc/ "/private/nli/ora9ias/ultrasearch/doc/"

     Alias /ultrasearch/ "/private/nli/ora9ias/ultrasearch/sample/"

     <IfModule mod_osso.c>
       <Location /ultrasearch/admin_sso>
          require valid-user
          authType Basic
       </Location>
     </IfModule>
     

Deploying the Ultra Search EAR File on a Third Party Middle Tier

Because Ultra Search EAR files contain only Web applications (WAR files), they can be made to deploy on any J2EE 1.2 container. To do so, you must know the Ultra Search WAR file name, the predefined URL root, and the Java library required. The following section explains the Ultra Search EAR files that you deploy in a standard J2EE 1.2 container. It does not contain information on the configuration of each J2EE 1.2 container.

jar -tvf ultrasearch_admin.ear 
          META-INF/ 
          META-INF/application.xml 
          META-INF/orion-application.xml 
          admin.war 
          admin_sso.war 
          ohw.war 

jar tf ultrasearch_query.ear 

   META-INF/application.xml 
   META-INF/orion-application.xml 
   query.war 
   welcome.war 
   rewriter/SampleRewriter.java 
   agent/SampleAgent.java 
   agent/README.html 

$ORACLE_HOME/ultrasearch/webapp/config 
$ORACLE_HOME/jdbc/lib/classes12.jar 
$ORACLE_HOME/jdbc/lib/nls_charset12.zip 
$ORACLE_HOME/ldap/jlib/ldapclnt9.jar 
$ORACLE_HOME/lib/xmlparserv2.jar 
$ORACLE_HOME/lib/activation.jar 
$ORACLE_HOME/lib/mail.jar 

jar -xvf ultrasearch_portlet.ear

ultrasearch_portlet.ear 
            META-INF/ 
                      application.xml 
            query.war 
            agent/ 
            index.html

$ORACLE_HOME/jdbc/lib/classes12.jar
$ORACLE_HOME/jdbc/lib/nls_charset12.zip
$ORACLE_HOME/lib/xmlparserv2.jar
$ORACLE_HOME/lib/activation.jar
$ORACLE_HOME/lib/mail.jar

Editing the data-sources.xml File

<data-source 
   class="oracle.jdbc.pool.OracleConnectionCacheImpl" 
   name="UltraSearchDS" 
   location="jdbc/UltraSearchPooledDS" 
   username="username" 
   password="password" 
   url="jdbc:oracle:thin:@database_host:oracle_port:oracle_sid"
/> 

Where username and password are the Ultra Search instance owner's database user name and password, database_host is the host name of the back end database computer, oracle_port is the port to the user's Oracle database, and oracle_sid is the SID of the user's Oracle database. In addition to user name, password, and JDBC URL, data-sources.xml also allows configuration of the connection cache size, as well as the cache scheme.

The following tag specifies the minimum and maximum limits of the cache size, the inactivity time out interval, and the cache scheme.

If you are adding the data source for the default Ultra Search instance user wk_test, then make sure to unlock wk_test first.

<data-source 
   class="oracle.jdbc.pool.OracleConnectionCacheImpl" 
   name="UltraSearchDS" 
   location="jdbc/UltraSearchPooledDS" 
   username="wk_test" 
   password="wk_test" 
   url="jdbc:oracle:thin:@localhost:1521:isearch" 
   min-connections="3" 
   max-connections="30" 
   inactivity-timeout="30">
 <property name="cacheScheme"  value="1"/>
</data-source>

There are three types of caching schemes:

• DYNAMIC_SCHEME = 1

• FIXED_WAIT_SCHEME = 2

• FIXED_RETURN_NULL_SCHEME = 3

  
  

  See Also: Oracle9iAS Containers for J2EE Security Guide

Oracle Database

The data-sources.xml file is located in the $ORACLE_HOME/oc4j/j2ee/OC4J_SEARCH/config directory.

Editing the ultrasearch.properties File

The $ORACLE_HOME/ultrasearch/webapp/config/ultrasearch.properties file contains configuration information used by Ultra Search middle tier. You do not need to edit this file, because it is automatically configured by the Oracle installer.

Here is an example of the ultrasearch.properties file:

connection.driver=oracle.jdbc.driver.OracleDriver
connection.url=jdbc:oracle:thin:@ldap://dlsun8888.cn.oracle.com:3060/iasdb,cn=oraclecontext
oracle.net.encryption_client=REQUESTED
oracle.net.encryption_types_client=(RC4_56,DES56C,RC4_40,DES40C)
oracle.net.crypto_checksum_client=REQUESTED
oracle.net.crypto_checksum_types_client=(MD5)
oid.app_entity_cn=m16bi.sgtcnsun03.cn.oracle.com
domain=us.oracle.com

Where

• connection.driver specifies the JDBC driver you are using.

• connection.url specifies the database to which the middle tier connects. Ultra Search supports following formats:

  • host:port:SID (where host is the full host name of the Oracle base instance running Ultra Search, port is the listener port number for the Oracle Database instance, and SID is the Oracle Database instance ID)

  • HA-aware string (for example, TNS keyword-value syntax)

  Here is an example connection.url string:

  connection.url=jdbc:oracle.thin:@ultrasearch.us.oracle.com:1521:myInstance
  
  

• oracle.net.encryption_client, oracle.net.encryption_types_client, oracle.net.crypto_checksum_client, and oracle.net.crypto_checksum_types_client control the properties of the secure JDBC connection made to the database. See Oracle Database JDBC Developer's Guide and Reference for more information.

• oid.app_entity_cn specifies the Ultra Search middle tier application entity name.

• domain specifies the common domain for the IM (identity management) machine and the Ultra Search middle tier machine. This enables delegated administrative service (DAS) list of values to work with Internet Explorer. For example, if the Ultra Search middle tier in us.oracle.com and the IM machine is uk.oracle.com, then the common domain is oracle.com. Add the following line in ultrasearch.properties: domain=oracle.com

Starting the Web Server

With the Oracle Application Server release, start the Web server using the Oracle Enterprise Manager Application Server Control.

With the database release, do the following:

java -jar $ORACLE_HOME/oc4j/j2ee/home/oc4j.jar -config 
$ORACLE_HOME/oc4j/j2ee/OC4J_SEARCH/config/server.xml

Testing the Ultra Search Administration Tool

Check that the Web Server is running.

Test your changes by attempting to log on to the administration tool:

• Visit: http://hostname.domainname:port/ultrasearch/admin/index.jsp

  where hostname.domainname is the full name of the host where you have installed the Ultra Search middle tier, and port is the default Web server port.

• During the installation of the Ultra Search backend, a new ultrasearch instance owner, WK_TEST is created. Log on to the Ultra Search administration tool by entering the Ultra Search instance owner's database user name and password.

• The nature of JSP pages is such that the first time any page is accessed, it takes a few seconds to compile. Subsequent accesses are much faster.

• If you log on to the Ultra Search administration tool successfully, then you have completed the Ultra Search administration tool configuration process.

Testing the Ultra Search Sample Query Applications

After you verify that the Ultra Search administration tool is working, you should be able to run the Ultra Search sample query applications.

To test the Ultra Search sample query applications, do one of the following:

• Visit http://hostname.domainname:port/ultrasearch/query/search.jsp

• Follow the links in the Ultra Search welcome page: http://hostname.domainname:port/ultrasearch/index.html

  
  

  See Also: "Configuring the Middle Tier with Oracle HTTP Server and OC4J" for information about configuring the JSP to query a specific instance

Locations for sample query applications are listed in the following section. Access the sample query source code by going to the directories list. You can also see a working demo of each sample query JSP page with the URL root, and you can append the correct JSP file name at the end of the URL root.

The sample query application is shipped as $ORACLE_HOME/ultrasearch/ultrasearch_query.ear.

The URL root for the query is http://hostname.domainname:port/ultrasearch/query/.

The URL root for the Oracle Application Server query is in http://hostname.domainname:port/ultrasearch/query/.

Portlet is shipped as $ORACLE_HOME/ultrasearch/webapp/ultrasearch_portlet.ear.