This section addresses prerequisites and preliminary configuration procedures that must be followed before installing Oracle ATG Web Commerce Search.
If you are installing on AIX and must run Search using
sudo, note that for security reasons, AIX removes theLIBPATHenvironment variable when usingsudo. To resolve this potential problem you can either setLIBPATHas root before running Search, or set theLIBPATHin the application server’s startup script.Note that running any Oracle ATG Web Commerce application as root is not recommended. If at any time you run Search as root or using
sudo, the file permissions in the installation change to root. Therefore, you must either continue running Search as root or usingsudo, or reset the file permissions.If you are installing on a UNIX or Linux variant, you must increase the number of open files permitted. The default setting is too low to support high network traffic, and can result in a “too many open files” error under load. Symptoms include Routing having problems communicating with the engine or logging an error.
Set the number of open files permitted to 10,000 or higher on all machines running Search, including the Routing instances and remote search engines.
If you are installing on a UNIX variant (such as Solaris or AIX) and there is any chance that your content includes filenames with non-English characters, make sure that your system locale is set to use UTF-8 encoding.
Note: If you are using multi-byte languages, Search Administration may incorrectly calculate length limits for fields such as content set names, based on your database capabilities. If your database limits the number of bytes stored in string columns, set the
maxLengthEncodingproperty of the/atg/searchadmin/adminui/validator/Validatorcomponent to your database encoding. The default setting is UTF-8. If your database correctly limits string column length based on character encoding, you can set the property to null or leave it empty.For any installation in which you are planning to run Search Administration, before you install Search, install your application server and the Oracle ATG Web Commerce platform. If you are only planning to run a standalone search engine, you do not need the platform or an application server.
You will need a scalable, shared network drive where indexes are initially created and from which they can be retrieved by the search engines. This directory is called the deployment share. All search engines and Search Administration instances must have access to this directory. Indexes can take up a great deal of disk space, so be sure the directory selected has sufficient space (at least 100 GB, more if your index is large or you plan to archive old indexes). This directory must be writable. In a production environment, this directory should be located on a dedicated, high-performance machine. Make sure to secure this shared drive against unauthorized access, just as you would any sensitive part of your network.
Note: The deployment share must be created and configured as a shared folder prior to installing Search.
