This line was removed.
This word was removed. This word was added.
This line was added.
Changes (4)View Page History
h3. Directory Server Considerations With ISS
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|http://docs.oracle.com/cd/E19226-01/821-0027/gcuhq/index.html].
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].