Indexing and Search Service Deployment Planning

Version 41 by sshenoy
on Nov 15, 2011 13:10.

compared with
Current by sshenoy
on Aug 12, 2014 23:10.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (5)

View Page History
Though you can deploy all components on a single host, or deploy a particular service's components on the same host, consider moving to a multi-host tiered architecture. A tiered architecture provides for more flexibility in tuning, upgrading, and expanding your deployment.

Indexing and Search Service requires specific versions of dependent component products. For information about the specific component product versions necessary to support ISS, see [Product Version Compatibility Requirements|CommSuite7U2:Communications Suite Component Products Requirements| Common Release Notes#Product Information for Communications Suite 7.0.6#Product Version Compatibility Requirements].

h3. Directory Server Considerations With ISS
In a multi-host architecture, where the web tier is running on separate systems from the indexing tier, Apache HTTP Server 2 must be installed on the systems in the indexing tier.

h2. Firewall Requirements

If you deploy a firewall between your Messaging Server and ISS Server, you need to open an additional port on the firewall for JMQ. That is, JMQ requires two ports. For more information, see [Connecting Through a Firewall|].

h2. Disk Space Requirements

ISS takes additional disk space to store its indexes. See [Memory and Disk Space Requirements|CommSuite7U2:Communications Suite Component Products Release Notes#Memory and Disk Space Requirements] for more information.
ISS takes additional disk space to store its indexes. See [Memory and Disk Space Requirements|Common Release Information for Communications Suite 7.0.6#Memory and Disk Space Requirements] for more information.

h2. ISS Logical Architecture

Indexing requires significant CPU resources, thus, it is best to install the indexing service on a separate host dedicated to an ISS single server installation. If this is not an option, then install ISS on the back-end host as a single server installation, and install GlassFish Server as well for ISS.

h2. ISS and High Availability

Indexing and Search Service provides the ability to make its search component highly available through the use of the Cluster Search Service and a highly available NFS, upon which you locate ISS indexes. When ISS search is unavailable from an ISS web node, the clients' search requests are redirected to another ISS web node that accesses the HA NFS and locates the appropriate index. Thus, the ISS search component can fail without an effective loss of the overall search functionality. Additionally, by using hardware load balancers in front of the ISS web nodes, you split the network load across these ISS front ends, increasing their availability to respond to client requests.

For more information, see [Configuring Indexing and Search Service for High Availability].

The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.