All data that is collected and processed as part of crawling and indexing is stored in this user's schema.Īs a general guideline, create the tablespace as large as the total amount of data that you want to index.

The Ultra Search instance user is a database user that you must explicitly create. As a general guideline, create a TEMPORARY tablespace as large as possible, depending on the RAM on your host.ĭisk space for the Ultra Search instance user's tablespace. However, as a general guideline, the minimal requirements are as follows:Īpproximately 3GB of disk space for the OracleAS infrastructure or database and the Ultra Search backend (server component).ġ5MB of disk space for the Ultra Search middle tier on top of the Web server’s disk requirements.įor each remote crawler host, the same amount of disk space as needed to install the Ultra Search backend.ĭisk space for a large TEMPORARY tablespace. Allocate enough memory for the HTTP Server as well as the JDK that runs the J2EE engine.īecause customer requirements vary widely, Oracle cannot recommend a specific amount of disk space. Oracle recommends using the Oracle HTTP Server with the Oracle J2EE container. Regardless of your choice, allocate enough memory for the J2EE engine. However, you might want to install and run this on the same host as the Ultra Search backend.

Therefore, it can be installed and run on a separate host from the Ultra Search backend (server component). The Ultra Search administration tool is a J2EE 1.2 standard Web application. When crawling very large amounts of data, these values might need to be adjusted. Out of the box, when the crawler is launched, the JVM is configured to start with 25MB and grow to 256MB. The Ultra Search crawler is a pure Java program. See Also: Oracle Text Application Developer's Guide and Oracle9i Database Performance Tuning Guide and ReferenceĪlong with the resource requirements for the database and the Text indexing engine, also consider the memory requirements of the Ultra Search crawler.

Ultrasearch