Вы находитесь на странице: 1из 15

Document 217368.

1 22/01/18 17(15

PowerView is Off Marcos Vinicius Martins Mana (Available) (0) Contact Us Help

Dashboard Knowledge Service Requests Patches & Updates 217368.1

Give Feedback... You have been directed to this document based on an ID match. Alternatively, click here to search on this phrase. Hide

Copyright (c) 2018, Oracle. All rights reserved.

Advanced Configurations and Topologies for Enterprise Deployments of E-Business Suite 11i To Bottom
(Doc ID 217368.1)

Checked for relevance on 17-DEC-2012 Was this document helpful?

Advanced Configurations and Topologies for Enterprise Deployments of E-Business Yes

Suite 11i No

This document contains information for using advanced configurations and topologies with Oracle E-Business Suite Release 11i.
The most current version of these notes is 217368.1 on Oracle MetaLink. This document used to be titled "Multi-Node Document Details
Configurations of iAS 1.0.2.2.2 for E-Business Suite 11i". There is a change log at the end of this document.

Chapter 1. Overview Type:


Status:
WHITE PAPER
Install and Patching Taxonomy Last Major PUBLISHED
Used Services Taxonomy Update: Aug 13, 2014
Advanced Configuration Topologies Last Aug 13, 2014
Update:
Nodes External to Oracle E-Business Suite
Network Configuration Requirements for Load-Balancers

Chapter 2. Configuring Load Balancing on Various Technology Layers Related Products

Option 2.1. DNS Layer Load Balancing Oracle E-Business Suite


Option 2.2. HTTP Layer Hardware Load Balancing Technology Stack
Option 2.3. Apache JServ Layer Load Balancing
Option 2.4. Forms Server / Metrics Layer Load Balancing Information Centers
Option 2.5. Concurrent Layer Load Balancing
Option 2.6. Database Layer Load Balancing Information Center: Using EBS
Technology Stack OID and SSO
[1461466.2]
Chapter 3. Adding Nodes
Information Center: Using EBS
Chapter 4. Configuring Demilitarized Zones Technology Stack - Framework
[1478640.2]
Appendices
Information Center: Overview
E-Business Suite Technology -
A. Setting up a load-balancer Forms [1411953.2]
B. Configurations not Supported for Load Balancing
C. Troubleshooting Apache JServ Layer Load Balancing Information Center: Using EBS
D. Configuring JVMs to Designate a Functionally Referenced Node Technology Stack Java
[1462269.2]
E. Configuring HTTP Load Balancers with Forms Metrics Server
F. Oracle Portal 3i Requirements With HTTP Load Balancer Information Center: Overview
EBS Technology Stack
Related Documentation Database and RAC
[1463217.2]
Chapter 1. Overview Show More

This document describes procedures for configuring complex configurations and topologies spanning multiple nodes for Oracle
Document References
E-Business Suite Release 11i environments that are managed by AutoConfig. For more information about AutoConfig, see
Migrating to AutoConfig to Manage System Configurations with Oracle Applications 11i (Oracle MetaLink Note 165195.1 ). No References available
for this document.
Required Patches
You must apply to all nodes Technology Stack patch 5478710 or higher before completing any of the following sections in your Recently Viewed
environment.
Advanced Configurations and
You must also apply to all nodes the Thin Client Framework (TCF) Rollup Patch B 3034091 or later. This will upgrade your TCF Topologies for Enterprise
server to be a servlet. Then follow the steps below: Deployments of E-Business
Suite 11i [217368.1]
1. On all nodes, run the AutoConfig Context Editor . Installing and Configuring Web
2. In the Context Detail screen, set the TCF Process Status context value (s_tcfstatus) to "disabled". Cache 10g and Oracle E-
TCF Process Status = disabled Business Suite 12 [380486.1]
3. Save your changes. Target CLONE Instance:
4. Generate new configuration files by running AutoConfig on all nodes. Adrelink Failed on FNDLIBR
With Error:
Additional patches required only for certain configurations, are listed within their respective sections. /usr/lib/gcc/x86_64-redhat-
linux/4.4.7/32/libgcc_s.so:
Concepts and Terminology undefined reference to
`__stack_chk_fail@GLIBC_2.4''
[2057857.1]
A "node" is a logical set of processes running on one hardware machine. Sometimes a node is also referred to as a "server" or
Actual Cost Process Program
an "instance". Each time you run the Rapid Install of E-Business Suite 11i, you create one node. You can create multiple nodes Completing In Error With
on one machine, or you can have nodes on various machines working together against one single E-Business Suite database. GMFACOST file not being
This creation of a "multi-node" E-Business Suite 11i instance is frequently done to lower cost of ownership (many small machines found [2187634.1]
are cheaper than one big one), increase fault tolerance (one machine fails, others do not), or scale the instance to support more Some Causes for Signal 11
users and load. error in ACP –Actual Cost

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 1 of 15
Document 217368.1 22/01/18 17(15

users and load. error in ACP –Actual Cost


Process, versions 11 & 12
A "service" is a functional set of processes running on one or more nodes. We will use this term to avoid confusion that stems [1451624.1]
from terms like "Forms server", which usually refers to a single node running the Forms service. But sometimes this term refers Show More
to the machine itself, or to the way a service is provided: via a Forms server listener process, versus a Forms servlet running in a
Java Virtual Machine (JVM) through an Apache web listener process.

A "farm" is a term used for a set of similar nodes (serving at least one same service), e.g. a Web Farm means a set of Web
Nodes. Nodes that are members of a large farm are usually identical except for their name (and IP address). Small farms
usually have machines serving multiple services, and belonging to multiple farms. When setting up load balancing, you should
first identify which nodes you want to load balance which services.

In addition, there might be machines running processes from code not installed by E-Business Suite. These nodes could have
other Oracle products or some third party products, and we refer to them as "external nodes". Examples of some frequently
used external nodes are hardware load-balancers, or the Oracle Internet Directory LDAP server. We contrast these to "internal
nodes" running parts of the E-Business Suite instance, which for simplicity we just call nodes.

This document discusses how to configure multiple nodes to work together, sharing the workload of one "multi-node" E-Business
Suite 11i instance. In production systems, only one node is present on each physical machine. To optimally utilize multiple
hardware machines, this document will also discuss configuring the distribution and balancing of the load.

There are different possible ways of classifying E-Business Suite nodes:

Install and Patching Taxonomy -- Used by AD Utilities and E-Business Suite Documentation
Used Services Taxonomy -- Used as shorthand in conversation

For the purposes of this document we will mostly use the Install and Patching taxonomy whenever the term for a type of Node is
used. Familiarity with all taxonomies is recommended. Within the context of this document, Multi-node refers to deployment
topologies where Web and Forms processes run on more than one physical application tier machine.

Install and Patching Taxonomy


At install time, each node is assigned a type: Web, Forms, Admin, Concurrent Processing, Database. One node can be of
multiple types at the same time. During installation, a single copy of the full E-Business file system is deposited on the storage
device. The configuration files are adjusted to represent which services should be started, and what the patching behavior
should be. When the same patch is applied to all nodes, it will have different effects on different nodes based on their (Install &
Patching) type. For more information see the Installation and AD Utilities documentation.

The Node type flag is set in the AutoConfig context file during Install time or Cloning time. The following table shows Node types
that are set in the Applications Context file.

Node type if
Node type
has a value
Flag
"Yes"
s_isAdmin Admin Node
s_isWeb Web Node
s_isForms Forms Node
Concurrent
s_isConc Processing
Node

Used Services Taxonomy


It is easy to imagine a node that was installed to be of various install and patching types, but is only used for one type of
functionality, one type of service. For example, a customer can initially install a single node that runs the web service, the Forms
service, the concurrent processing service, as well as the database service. Soon thereafter, the customer adds two more
identical machines: one to act as a Web server and the other as a Forms server. Both of the new machines are installed as
Web, Forms, Admin, and Concurrent Processing nodes.

And yet since one machine is configured to handle only Forms Server requests, some people would call it the Forms Server

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 2 of 15
Document 217368.1 22/01/18 17(15

And yet since one machine is configured to handle only Forms Server requests, some people would call it the Forms Server
node. The other machine could handle only Web requests (including both httpd and Apache JServ requests) so they would call it
the Web node. However, if the customer starts running Forms as a servlet through the web server, they would call that node both
a Web (Apache/httpd service) node and a Forms servlet node.

We believe this nomenclature is imprecise and causes confusion, but believe everyone should understand it as it is frequently
used for shorthand. For example, if Oracle Discoverer is the only functionality used from a node, then one could say that that
node is "a Discoverer node", vs saying the full precise term: "a Web (and maybe another Install type) node configured to provide
the Discoverer service by running the Apache, JVM, and Discoverer processes".

This shorthand nomenclature can also spread to dividing servers for specific E-Business Suite functionality. For example if all
requests to Human Resources services are routed to one node, we could call that node an "HR node". Yet another way to
distinguish nodes is due to their topology: we could refer to a node as a Demilitarized Zone (DMZ) node, or a load-balancer
node.

Here are some examples of Nodes within this taxonomy:

Forms Server node (this is same as Forms Node in Install and Patching taxonomy)
Forms Servlet node (this node is configured for Forms Servlet and is configured to run both the Forms servlet and Forms
runtime processes; this node is of Web and Forms type in the Install and Patching taxonomy)
Discoverer Servlet node (when this node is configured to serve all Discoverer requests)
Human Resources node

Advanced Configuration Topologies


When configuring various topologies, some nodes will need to be identified for special functions.

Web Entry Point Node

Web Entry Point node references the host name which is designated to be used by all the users to access Oracle E-Business
Suite 11i system. In the case where a load-balancer is being used, then the Web Entry Point becomes the load-balancer's host
name.

Primary Web Node

Within such a topology, this document distinguishes between a Primary Web Node and other web nodes within a farm of Forms
Nodes configured to be load balanced using Forms Metrics Server process.

Primary Web Node refers to the Web Node which is expected to be the initial target of all Forms requests. In the case
where a load-balancer is being used, Primary Web Node refers to the Web Node to which load-balancer sends all the
Forms request
The physical application tier server hosting the Primary Web Node must have a Forms Node.

This document introduces the concept of a Primary Forms Metrics Server Process.

The Forms Metrics Server Process running on the Primary Web Node is considered to be the Primary Forms Metrics
Server Process.
The Primary Forms Metrics Server Process is used to load balance Forms Clients transactions across other Forms
Servers in a Multi Node Configuration.

Nodes External to Oracle E-Business Suite

These nodes are not installed or configured by Oracle E-Business Suite but Oracle E-Business Suite can be configured to be
used with them. Examples of external nodes include multiple types of load-balancers which can be used with Oracle E-Business
Suite11i.

Session Persistent Load-Balancers

Load-balancers maintaining HTTP connections that maintain persistency of a single session. Session persistence is also
referred to as "stickiness." When a client's HTTP connection is directed to a particular server, then subsequent HTTP requests
from that client are directed to the same server.

Load-Balancers that Cannot Support Persistent Sessions

Load-balancers which use a round-robin way of balancing the incoming HTTP requests without maintaining session persistent
client connections.

Secure Socket Layer Accelerators

Secure Socket Layer (SSL) Accelerators can be used to reduce the SSL traffic and workload off the web servers. Usually SSL
accelerators are the primary targets for https requests from the user's desktop and thus are the initial target for all desktop client
communication. They are responsible for converting "https" SSL requests to non-SSL "http" requests, directing the request to the
http server which is running in non-SSL mode. Before sending the response back to the desktop they again convert the non-SSL

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 3 of 15
Document 217368.1 22/01/18 17(15

http server which is running in non-SSL mode. Before sending the response back to the desktop they again convert the non-SSL
requests to SSL requests.

Network Configuration Requirements for Load-Balancers


In a load-balanced configuration, a load-balancer device serves requests from clients and redirects them to multiple E-Business
Suite application tier servers. The load-balancer acts as a single entry point to the E-Business Suite environment. Two sets of
major requirements must be met to ensure successful configuration of hardware-based load-balancers with the E-Business
Suite:

1. Load-Balancer Requirements
2. DNS Resolution Requirements

1. Load Balancer Requirements

Virtual Servers and Port Configuration

It is possible to configure a single E-Business Suite environment to be accessed via multiple domain names, each
with its own pool of application tier servers. For details about these types of configurations, see Metalink Note
287176.1.

For example: A single E-Business Suite environment might have the following two domains:
partners.company.com, and employees.company.com. The partners.company.com domain uses a pool
of application servers (e.g. apptier1 and apptier2) secured and used exclusively for external access by partners
and supplies. The employees.company.com domain uses a different pool of application servers (e.g. apptier3
and apptier4) that may be used only by company employees. Both environments use the same E-Business Suite
database.

Depending on the load-balancer used, it is technically possible to use a single physical load-balancer to handle
client requests for both domains. To support this configuration, the load-balancer must:

Allow configuration of multiple virtual server names and multiple ports


Associate each virtual server name with its own IP address, each of which are accessible via your DNS
Allow clients to address the virtual server names, which the load-balancer uses to redirect traffic to the
appropriate pool of application tier servers

Note

Oracle E-Business Suite code running on the application tier servers may need to
establish connection to itself, external servers or to the database server for product
functionality and to meet high availability requirements. This requires the load
balancing device to accept connections from the application tier servers behind the
device and route the request to the appropriate server. In certain network
configurations, the load balancing device may not be configured/support such
connections and the request may either hang or be dropped. In such a scenario,
please contact your hardware load balancer vendor to discuss the feasibility of
reconfiguring the load balancer device to accept the connections originating from
the servers behind it or upgrades to devices that can support these types of
loopback connections. This is the recommended configuration.

Depending upon your networking device, it may be feasible to alias load-balancer


virtual host names directly to the IP addresses of specific application tier
servers. Such mappings may not be technically feasible in all
configurations. Oracle does not certify or recommend such configurations, but will
support them on a best-efforts basis, subject to available resources and
expertise. Although machine mappings may be supported, technical limitations
inherent in DNS layer devices may prevent port and protocol mappings.

For example, a load-balancer with SSL acceleration capabilities may be configured


to listen for HTTPS traffic on port 443, and forward unencrypted traffic to the pool of
application tier servers listening for HTTP traffic on port 8000. Mapping HTTPS
services to the application tier servers instead of the load-balancer/SSL accelerator
will result in failures, as the application tier servers: a) are not configured to handle
HTTPS traffic, and, b) will reject traffic for port 443.

Resource Monitoring, Port Monitoring & Process Failure Detection

Oracle recommends that the load-balancer be configured to detect service and node failures, through heartbeat
monitors, notification, or some other mechanism. If a node in the pool fails, the load-balancer must stop directing
traffic to the failed node.

Fail-Over Capabilities

It is possible to set up offsite fail-over environments that can be switched to if the primary environment fails. For
example, a load-balancer may be configured to direct E-Business Suite traffic to a primary pool of application
servers in Austin, Texas. If that primary site fails for some reason, the load-balancer should be able to detect the
failure and redirect all traffic to identically-named application tier servers running in an offsite disaster recovery site.

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 4 of 15
Document 217368.1 22/01/18 17(15

failure and redirect all traffic to identically-named application tier servers running in an offsite disaster recovery site.

Oracle recommends that load-balancers be configured to support fail-over configurations.

Returning Traffic on Failures

Oracle recommends configuring load-balancers to return immediately to the calling client when the application
server to which it forwards traffic is unavailable. This is preferred over the client disconnecting on its own after a
timeout based on the TCP/IP settings on the client machine.

2. DNS Resolution Requirements


All clients must be able to resolve the hostname of the load-balancer. In the case where a single load-balancer
hosts multiple virtual servers, clients must be able to resolve the hostname of each of the virtual server names.
Note that "clients" also include E-Business Suite application tier server nodes, which perform loopback queries to
the load-balancer's virtual server name.

You can perform the following tests from desktop clients and each application tier server node to ensure that DNS
resolution is working:

1. Use ping

>ping <LbrDeviceHostname>.<domain>

For example:

>ping employees.company.com

If successful, this command will return the IP address of the load-balancer, along with information about
ping latency and response times.

2. Use telnet

>telnet <LbrDeviceHostname>.<domain> [http/https port]

For example:

>telnet employees.company.com 443


>GET /OA_HTML/OAInfo.jsp

If successful, this command will connect to the load-balancer using the specified port and will return the
HTML output from OAInfo.jsp.

Chapter 2. Configuring Load Balancing on Various Technology Layers


This chapter contains detailed instructions for implementing load balancing for Oracle E-Business Suite Release 11i
environments. Depending on your requirements and existing networking infrastructure, you may need to implement one or more
of the following options:

Option 2.1 . Domain Name Server (DNS) Layer Load Balancing


Option 2.2 . HTTP Layer Load Balancing
Option 2.3 . Apache JServ Layer Load Balancing
Option 2.4 . Forms Server / Metrics Layer Load Balancing
Option 2.5 . Concurrent Layer Load Balancing
Option 2.6 . Database Layer Load Balancing

Note
Configuration steps for many of the above options have been
automated with the use of configuration wizards. You can follow
Oracle MetaLink Note 277574.1 titled "Running Configuration
Wizards from the Command Line in Oracle Applications 11i" to
learn more about configuration wizards.

Option 2.1. Domain Name Server (DNS) Layer Load Balancing


Domain Name Server (DNS) Layer load balancing solutions distribute end-user requests across multiple servers based on
dynamic assignments of IP addresses to a fully qualified domain name. The following diagram shows a typical configuration
using DNS layer load-balancer.

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 5 of 15
Document 217368.1 22/01/18 17(15

If you are using a Domain Name System (DNS) based Load Balancing solution, then you must do the following:

Step 2.1.1. Apply prerequisite patches

Apply the following prerequisite patches to all Web, Forms, Admin, and Concurrent Processing nodes:

Patch
Patch Description Comments
No
AutoConfig Rollup Patch Required templates for multi node
5478710
O (Dec 2006) configuration.
Framework patch for if you are using Framework version 5.7H
3077386
session consistency. (2771817 )or higher.
ORACLE
If you are using Oracle Configurator then
CONFIGURATOR
3209878 Configurator version should be
RUNTIME PATCH ( BLD-
11.5.9.19.66 or higher.
19-66 )

Step 2.1.2. Configure Web Nodes with DNS Load Balancer information

On each Web server node, run the AutoConfig Context Editor . In the Context Detail screen, set the following configuration
values:

1. "Web entry point Host" to the host name of the DNS-load balanced web node machine.
2. "Web entry point Domain" to the domain name of the DNS load-balanced web node machine.
3. "Web entry protocol" to the protocol value "http". If you have configured E-Business Suite 11i instance with SSL
then set this value to "https".
4. "Active Web Port" to the value of the "Web Port" of the DNS load-balanced web nodes.. You must ensure that the
value of "Web Port" is same across all Web Nodes.
5. "Login Page" to include <"Web entry protocol">://<"Web Host entry point">.<"Web domain entry point">:<"Active Web
Port">

Step 2.1.3. Enable Apache JServ Layer Load Balancing

DNS resolution has an expiration time which depends on the DNS solution implemented in a network. The
expiration times can vary and might cause session inconsistencies if the host serving a user session is switched
within a browser session past the DNS expiration time. Apache JServ uses session persistency and avoids this
problem, even if the DNS sends the request to another host. Complete the Apache JServ Layer Load Balancing
section of this document to enable this functionality.

Step 2.1.4. Implement Forms Listener Servlet (Recommended)

Complete the steps in Using Forms Listener Servlet with Oracle Applications 11i (MetaLink Note 201340.1 ) for
forms requests that are load balanced by the "Apache JServ Layer Load Balancing" .

If you choose to use Forms Listener Servlet, all Forms and Web Nodes must have the same directory structure.

Example: If the APPL_TOP on Web/Forms Node1 is located at /d1/applmgr/1159, then the APPL_TOP on
Web/Forms Node 2 must be located at /d1/applmgr/1159 as well.

Step 2.1.5. Set up Trusted OProcMgr nodes

On all Nodes: Use the AutoConfig Context Editor to update the following variables:

Add a comma separated list of IP addresses of all Web Nodes to the "OProcMgr Trusted Nodes" value

Option 2.2. HTTP Layer Hardware Load Balancing

Follow the steps in this section if you plan to use a load-balancer which accepts HTTP communication and forwards it to a farm.
The following diagram shows an example of a configuration where a load-balancer distributes load across two web nodes. While
Oracle E-Business Suite Release 11i is not certified / tested against specific load balancing solutions, we have tested both
hardware- and software based HTTP load-balancers and believe that our configurations should perform well.

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 6 of 15
Document 217368.1 22/01/18 17(15

Step 2.2.1. Configure HTTP Load-Balancer for session persistence

Hardware based HTTP Load-Balancers must be configured to ensure persistent session connections between clients and Web
Server Nodes in Oracle E-Business Suite Release 11i environments. Depending on the deployment architecture and capabilities
of the specific HTTP Load-Balancer in use a suitable option should be chosen to ensure that the load-balancer sends all the
requests from one client session to the same Web Server Node. Session persistency is also referred to as "stickiness". "Cookie
based" stickiness and "IP address based" stickiness are two of the available options to ensure connection persistency.

Refer to the third-party documentation for your HTTP load-balancer for details on configuring persistent session connections.

Step 2.2.2. Apply prerequisite patches

Apply the following prerequisite patches to all Web, Forms, Admin, and Concurrent Processing nodes:

Patch
Patch Description Comments
No
HTTP load-balancer Required templates for multi node
5478710
Patch. configuration.
Framework patch for if you are using Framework version 5.7H
3077386
session consistency. (2771817 )or higher.
ORACLE
If you are using Oracle Configurator then
CONFIGURATOR
3209878 Configurator version should be
RUNTIME PATCH ( BLD-
11.5.9.19.66 or higher.
19-66 )

Step 2.2.3. Configure Web Nodes with HTTP Load-Balancer information

On each Web server node, run the AutoConfig Context Editor . In the Context Detail screen, set the following configuration
values:

1. "Web entry point Host" to the HTTP load-balancer machine name


2. "Web entry point Domain" to the HTTP load-balancer domain name
3. "Web entry protocol" to the HTTP load-balancer protocol e.g. "http" or "https"
4. "Active Web Port" to the value of the HTTP load-balancer's external port
5. "Login Page" to include <"Web entry protocol">://<"Web Host entry point">.<"Web domain entry point">:<"Active Web
Port">

Note for using SSL Accelerator

Use SSL Accelerator (Conditional):

If either your configuration requires or you plan to use "cookie


based session persistence" at the HTTP Load Balancer level and
you plan to enable SSL for HTTP traffic at all middle tier Web
Nodes, then you have to use a SSL Accelerator as the Web
Entry Point Host. The reason being, HTTP Load Balancers can
not intercept the SSL encrypted communication between the
Client Browser and the middle tier Web Server to insert/delete
cookies to maintain session persistence. It is advantageous to
use SSL accelerators because it requires less maintenance since
none of the middle tier Web Nodes have to be configured for SSL
anymore.

Configure SSL Accelerator:

If either of the following conditions are true:

Your HTTP load-balancer also acts as a SSL Accelerator


You use an SSL Accelerator as your Primary Web Entry
point which is the initial target of interfacing client
communication

Then you must complete the following steps:

1. "Web entry point Host" to the SSL Accelerator


hostname.
2. "Web entry point Domain" to the SSL Accelerator
domain name
3. Set the "Web entry protocol" to "https".
4. Set the "Active Web Port" to the value of the SSL
Accelerator's external interfacing port.

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 7 of 15
Document 217368.1 22/01/18 17(15

Accelerator's external interfacing port.


5. Set the "Web SSL Port" to the same value as the
"Active Web Port".
6. "Login Page" to include "https://<'Web Host entry
point'>.<'Web domain entry point'>:<'Active Web Port'>"

Note for Oracle Configurator customers


If you are using Oracle Configurator then you must enable load balancing at
the Apache JServ layer even if your hardware load balancer is configured to
maintain session persistency.

Step 2.2.4. Ensure Uniformity Among Nodes (Recommended)

It is recommended that all load balanced nodes should be of uniform configuration i.e. all nodes should be
configured to have Web and Forms services.

Step 2.2.5. Forms Listener Servlet (Recommended)

It is strongly recommended that you implement Forms Listener Servlet for forms requests.

Complete the steps in Using Forms Listener Servlet with Oracle Applications 11i (MetaLink Note 201340.1 )
for forms requests.

If you choose to use Forms Listener Servlet, all Forms and Web Nodes must have the same directory
structure.

Example: If the APPL_TOP on Web/Forms Node1 is located at /d1/applmgr/1159, then the APPL_TOP
on Web/Forms Node 2 must be located at /d1/applmgr/1159 as well.

If you want to use Forms Metrics Server process to load balance forms requests then you can follow Appendix E.

Option 2.3. Apache JServ Layer Load Balancing


Oracle9i Application Server 1.0.2.2.2 introduces new capabilities for software-based load balancing of Apache JServ
transactions across multiple application-tier server nodes, increasing the fault-tolerance and scalability of large-scale Release 11i
environments. In addition, via mod_oprocmgr, 9iAS 1.0.2.2.2 provides JVM death detection and restart functionality across
multiple nodes.

For example, mod_oprocmgr may be configured to manage an Apache JServ load balancing server pool comprised of JVMs
running on two different Web Server nodes, as shown in the following diagram:

Step 2.3.1. Upgrade to Oracle 9i Application Server 1.0.2.2.2

If your Oracle E-Business Suite 11i instance is created using Rapid Install Oracle E-Business Suite 11i Releases
11.5.1 to 11.5.5 and you have not already migrated to Oracle 9i Application Server 1.0.2.2.2, then see Oracle
MetaLink Note 146468.1 , Installing Oracle9i Application Server 1.0.2.2.2 with Oracle Applications 11i to upgrade.

Note

Release 11.5.7 and 11.5.8 Rapid Install CD's already include Oracle9i
Application Server 1.0.2.2 Enterprise Edition. However, even if you installed
Oracle E-Business Suite using Release 11.5.7 or 11.5.8 Rapid Install, or
upgraded from Releases 10.7 or 11.0 using 11.5.7 or 11.5.8 Rapid Install, you
must upgrade to the latest patched iAS 1.0.2.2 by following Oracle MetaLink
Note 146468.1.

Step 2.3.2. Apply prerequisite patches

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 8 of 15
Document 217368.1 22/01/18 17(15

Step 2.3.2. Apply prerequisite patches

Apply the following prerequisite patches to all Web, Forms, Admin, and Concurrent Processing nodes:

Patch
Description Comments
No
3072811 iAS 1.0.2.2 Rollup 4 Includes OprocManager fix 2795224 .
OPROCMGR
3310149 REGISTERS WITH If you have standards compliant /etc/hosts
/ORPCOMGR- file, you do not need this patch.
SERVICE WITH A You need to have iAS 1.0.2.2 rollup 4 patch
DNS LOAD 3072811 before applying this patch.
BALANCER

6492873 OPM: FAILS TO This patch must be applied on top of iAS


KEEP SESSION 1.0.2.2.2 Rollup Patch 5 or higher.
USING DNS LBR
2655277 Application Object If you are using a load-balancer that does
Library 11i.FND.G not support persistent sessions, you must
apply this patch to switch your current
Login Page module to a servlet-based
Login Page.

Step 2.3.3. Configuring the Apache JServ Load Balancing Farm

Adding a Web Node to the Apache JServ Load Balancing Farm

Repeat this procedure on each Web Node to be added to the Multi-Node Apache JServ Load Balancing pool of
machines.

1. Run the AutoConfig Context Editor .


2. In the Context Detail screen, confirm that the OPROC Manager Port value is the same across all the load
balanced Web Farm Nodes.
3. In the Context Detail screen, confirm that the Local Domain Name value is the same across all the load
balanced Web Farm Nodes. If you plan to have servers with different domain names, see the Multi Domain
Support Appendix.
4. In the Context Detail screen, set the Configure Multi Web Node to "yes".
5. In the Context Detail screen, set the OA Core zone name to "root".
6. Run AutoConfig to generate Configuration files using AutoConfig.
7. Restart Oracle HTTP Server.

Note

If the node being added to the JServ Load Balancing Farm


is completely new to the Oracle E-Business Suite 11i, then
you need to re-generate the configuration files by running
AutoConfig on all other Web Nodes.

This has to be done since the new node was not


registered previously in "fnd_nodes" table in the database
at the time when the configuration files were generated on
all other Web Nodes. This is because the configuration
files on all other Web Nodes would not have contained any
information about the new node.

Removing a Web Server Node from the "Apache JServ Load Balancing" Server Pool

If you wish to remove a Web Server Node from the Multi-Node Apache JServ Load Balancing pool of servers:

On the Web Server Node to be removed from the Apache JServ Load balancing server pool:

1. Run the AutoConfig Context Editor .


2. In the Context Detail screen, set the Configure Multi Web Node to "no".
3. Run AutoConfig to generate configuration files.
4. Restart Oracle HTTP Server.

To Add Trusted Administration Nodes in the "Allow From" Directive for OProcMgr

If either of the following conditions apply, then you need to add the IP addresses of the trusted administration
nodes to the "Allow From" directive for OProcMgr.

You wish to add a list trusted administration nodes to the "Allow From" directive for OProcmgr
Your hostname resolves to two IP addresses (in the case of multiple Network Interface Cards in the same
host)

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 9 of 15
Document 217368.1 22/01/18 17(15

To add the trusted administration nodes IP addresses to the "Allow From" directive for OProcMgr, on each Web
node do:

1. Run the AutoConfig Context Editor .


2. In the Context Detail screen, set the following configuration values.
3. Add a comma separated list of fully qualified hostnames with domain names or IP addresses of all the
trusted administration nodes for "OProcMgr Trusted Nodes" .
4. Run AutoConfig to generate configuration files.

Configuring Apache JServ to Load Balance within Functionally Referenced Nodes

You may optionally distribute the load using weights within each group of functional nodes when using OProcMgr
to perform Apache JServ Load Balancing. See Appendix D for more information.

Option 2.4. Forms Server / Metrics Layer Load Balancing


You may choose between the following two options for load balancing Forms-based traffic:

Option 2.4.1 . Apache JServ Load Balancing when using a Forms Listener Servlet
Option 2.4.2 . Use Forms Metric Server

Option 2.4.1. Apache JServ Load Balancing when using a Forms Listener Servlet

Step 2.4.1.1. Implement Apache JServ Layer Load Balancing

Complete Option 2.3, Apache JServ Layer Load Balancing . Apache JServ Layer Load Balancing will be used by
the Forms Listener Servlet to serve forms requests.

Step 2.4.1.2. Implement Forms Listener Servlet Support

Complete Using Forms Listener Servlet with Oracle Applications 11i (MetaLink Note 201340.1 ).

If you are using the Forms Listener Servlet with Oracle Applications 11i:

Every Forms Node must have a Web Node on the same machine.
All Forms and Web Nodes must have the same directory structure.

Example: If the APPL_TOP on Web/Forms Node1 is located at /d1/applmgr/1159, then the


APPL_TOP on Web/Forms Node 2 must be located at /d1/applmgr/1159 as well.

Option 2.4.2. When using Forms Metric Server

Identify one web node to be the Primary Web Node which is distinct from the other web nodes.

Primary Web Node refers to the Web Server node which is expected to be the initial target of all client (desktop)
communication. In case of a HTTP Load Balancer (or Web Entry Point Node) Primary Web Node is the node to which
HTTP Load Balancer sends all the forms requests.
The physical application tier server hosting the Primary Web Node must have a Forms Node.

This document introduces the concept of a Primary Forms Metrics Server Process.

The Forms Metrics Server Process running on the Primary Web Node is considered to be the Primary Forms Metrics
Server Process.
The Primary Forms Metrics Server Process is used to load balance forms clients transactions across other Forms Servers
Multi Node Configuration.

Step 2.4.2.1. Configure Web Server Node to recognize Forms Server Node FND_TOP

This option configures one or more Web Server Nodes to recognize the Forms Server node. If the Web Server
Nodes are different from the Forms Server Nodes, perform the following additional steps on each Web Server
Node after the 9iAS 1.0.2.2.2 install:

1. On each Web server node, run the AutoConfig Context Editor .


2. In the Context Detail screen, set the Forms Server FND_TOP context value (s_formsfndtop in
$APPL_TOP/admin/<SID>.xml) to the location of FND_TOP on the Forms Server node(s).

For example, if the Forms Server is located on host formsnode.oracle.com, and the location of
$FND_TOP on the Forms Node is /u01/oracle/visappl/fnd/11.5.0, then

Forms Server FND_TOP = /u01/oracle/visappl/fnd/11.5.0

If you have multiple Forms Server nodes, they must all have the same directory structure.

Example: If the APPL_TOP on Web/Forms Node1 is located at /d1/applmgr/1159, then the APPL_TOP
on Web/Forms Node 2 must be located at /d1/applmgr/1159 as well.

3. Save your changes.


4. Generate new configuration files by running AutoConfig .
5. Regenerate your Applications jar files on the Web server node(s) by running adadmin and selecting

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 10 of 15
Document 217368.1 22/01/18 17(15

5. Regenerate your Applications jar files on the Web server node(s) by running adadmin and selecting
"Maintain Applications Files menu" followed by the "Generate Product JAR files" option.

Step 2.4.2.2. Configure the Web nodes to use Metrics Load Balancing

The Forms Metric Server method of load balancing forms client transactions identifies the physical server where
the Metric Server Load Balancing Service is running. All Forms Server Nodes will dynamically self-register as
Metric clients with the Metric Server.

If you have multiple Forms Server nodes in your configuration and you use the Primary Forms Metrics Server
Process and Forms Metrics Clients to do Forms Load Balancing, perform the following steps:

1. Execute the steps detailed in Option 1, above.


2. On each Web server node, run the AutoConfig Context Editor .
3. In the Context Detail screen, set the Metrics Server Load Balancing Host context value
(s_leastloadedhost in $APPL_TOP/admin/<SID>.xml) to %LeastLoadedHost%:

Metrics Server Load Balancing Host = %LeastLoadedHost%


4. In the Context Detail screen, set the Metrics Server Error URL context value (s_meterrorurl in
$APPL_TOP/admin/<SID>.xml) to your default Metrics Server error page, if any.

For example, if your Metrics Server error page is


http://webhost.oracle.com/OA_HTML/error.html, then

Metrics Server Error URL = http://webhost.oracle.com/OA_HTML/error.html


5. Save your changes.
6. Generate new configuration files by running AutoConfig as described in MetaLink Note 165195.1 .

Step 2.4.2.3. Set Metric Server Host

If you have multiple Forms Server nodes in your configuration and you use the Primary Forms Metrics Server
Process and Forms Metrics Clients to do Forms Load Balancing, perform the following additional steps on all
Forms and Web Server nodes.

1. On all Forms Metrics Client Nodes, run the AutoConfig Context Editor .
2. In the Context Detail screen, set the Metrics Server Host context value (s_methost in
$APPL_TOP/admin/<SID>.xml) to the hostname that runs the Primary Forms Metrics Server Process.

For example, if the Primary Forms Metrics Server Process is running on host "formsmetrics.oracle.com",
then
Metrics Server Host = formsmetrics.oracle.com
It is not mandatory to include the complete domain name as long as the Metrics Clients and Metrics Server
are in the same domain and the Metrics Clients can resolve the hostname of the Metrics Server.
3. Save your changes.
4. Generate new configuration files by running AutoConfig as described in MetaLink Note 165195.1

Known Issues with Multiple Forms Nodes


The Forms Metrics Server is started on all Forms nodes by the
adstrtall.sh (adstrtall.cmd on Windows) script. The
Forms Metric Server Process running on the Primary Web node
will be the Metrics Server that is used.

Option 2.4.3. Disabling Forms Metric Server

If you have multiple Forms Server nodes in your configuration and you use the Primary Forms Metrics Server
Process and Forms Metrics Clients to do Forms Load Balancing, and wish to disable this functionality perform the
following steps.

1. On all Forms Metrics Client Nodes, run the AutoConfig Context Editor .
2. In the Context Detail screen, set the Metrics Server Load Balancing Host context value
(s_leastloadedhost in $APPL_TOP/admin/<SID>.xml) to the value of "%s_hostname%"
context variable:

Metrics Server Load Balancing Host = myserver

[ where "myserver" is the name of this host and value of %s_hostname%. ]

3. Save your changes.


4. Generate new configuration files by running AutoConfig as described in MetaLink Note 165195.

Option 2.5: Concurrent Layer Load Balancing

Please refer "Oracle Applications System Administrators Guide" under section "Managing Concurrent Processing" for a detailed
overview of Parallel Concurrent Processing.

Option 2.6: Database Layer Load Balancing


You can achieve Database Layer Load Balancing by using Real Application Clusters (RAC). See Concurrent Manager Setup
and Configuration Requirements in an 11i RAC Environment (Oracle MetaLink Note 241370.1 ).

Chapter 3. Adding Nodes


In order to increase scalability or fault tolerance you can add a node to your farm of production servers. Adding a node is a two

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 11 of 15
Document 217368.1 22/01/18 17(15

In order to increase scalability or fault tolerance you can add a node to your farm of production servers. Adding a node is a two
step process, consisting of addition/installation followed by advanced configuration.

Step 3.1 : Addition of a New Node

Option 3.1.1 : Using Shared APPL_TOP

Shared APPL_TOP infrastructure can be used to add a node to an existing E-Business Suite 11i
system. Please follow Oracle MetaLink Note 233428.1 "Sharing an APPL_TOP in Oracle
Applications 11i" for instructions to migrate to a shared APPL_TOP infrastructure. This method of
adding a new node is recommended for the benefits described in the Oracle MetaLink Note
233428.1.

Option 3.1.2 : Using Cloning


The cloning process, as compared to an install process, allows you to avoid reapplying any patches
you have already applied on one "master copy" node. Please follow Oracle MetaLink Note 230672.1
"Cloning Oracle Applications Release 11i" to choose a method to clone an existing node. This
method of adding a new node can also be used when available.

Step 3.2 : Configuring the New Node

You must follow this document (217368.1) to set up the new node for Multi Node support. You should make sure
that the new node is configured correctly and is in line with the configuration of all the existing nodes in the farm.

Chapter 4. Configuring Demilitarized Zones


Please refer to Oracle MetaLink Note 287176.1 for DMZ configurations with Oracle E-Business Suite 11i.

Appendix A. Setting up an HTTP Layer Load-Balancer


There are two ways to set up a load-balancer to load balance requests for Oracle E-Business Suite 11i.

Option 1. Single Entry Point: URL Based Load Balancing (recommended)

Using this approach, the load-balancer distributes incoming requests based on URL. For example, all requests whose URLs
contain "/dev60cgi/f60cgi" will go to the Forms farm. This "single entry point" method is recommended since this does not
involve any extra manual configuration. This is the recommended configuration for Oracle E-Business Suite Release 11i
environments.

Appendix B. Configurations not Supported for Load Balancing


Multiple WebNodes on one single host are not supported for any layer Load Balancing.
Oracle E-Business Suite Release 11i has tested HTTP Load Balancing with a hardware load-balancer. Any other form of
HTTP Load Balancing is not consistently tested.
Oracle E-Business Suite Release 11i supports Apache JServ Load Balancing via "mod-oprocmgr" in Oracle 9i Application
Server 1.0.2.2.2. Previous versions of Oracle 9i Application Server e.g. "iAS10" and "iAS1021s" are not supported for
Load Balancing purpose. Load Balancing based on any manual redirections in the Apache JServ properties file is not
supported.
Apache JServ Load Balancing across multiple domains is not supported with Oracle E-Business Suite Release 11i.

Appendix C. Troubleshooting Apache JServ Load Balancing


Once you have configured for Apache JServ Load Balancing, you can use any of the following methods to determine whether
your Apache JServ Load Balancing is working correctly.

Method 1 : From Apache and Apache JServ Log files.

From the Apache and Jserv log files you can determine whether Apache JServ load balancing is being achieved. Apache log
files show the registration of OProcMgr service where as Apache JServ log files show the balancing of Apache JServ sessions.

Apache Log Files

When Apache service is started on each node, OProcMgr service on each node registers with OProcMgr service
on other nodes. This should be evident from the Apache log files in iAS 1.0.2.2.2 ORACLE_HOME i.e.
<IAS_ORACLE_HOME>/Apache/Apache/logs/access_log. Suppose you have three Web Nodes , Host1, Host2
and Host3, which are enabled for Apache JServ Load Balancing. After Apache service is started on all the nodes,
the Apache log files on Host1 will contain entries like:

Host2 - - [21/Jun/2004:16:17:53 -0700] "POST /oprocmgr-service HTTP/1.1" 200 15

Host3 - - [21/Jun/2004:16:17:53 -0700] "POST /oprocmgr-service HTTP/1.1" 200 15

Apache JServ Log Files

In the previous example, the Apache JServ log files i.e. <IAS_ORACLE_HOME>/Apache/Jserv/logs/mod_jserv.log,
on Host1 will contain entries like the following, once some users start accessing the E-Business Suite 11i pages.

[21/06/2004 23:50:29:805] (ERROR) balance: continuing session to Host2 : 16170

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 12 of 15
Document 217368.1 22/01/18 17(15

[ Note: The above "ERROR" string in the message is to be understood as "INFO" and this is not an ERROR
message. This is fixed in iAS 1.0.2.2.2 roll up patch 5. ]

Method 2 : Using a Servlet.

Step 1. Create the test servlet


Create a file called txkTestJservLoadBal.java under <iAS Home>/Apache/Jserv/servlets directory by copying the
following text:

import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;

public class txkTestJservLoadBal extends HttpServlet {

public static final String TITLE = "Testing JServLoad Balancing";

public void service (HttpServletRequest request, HttpServletResponse response)


throws ServletException, IOException
{
response.setContentType("text/html");

PrintWriter out = response.getWriter();

String serverName = request.getServerName();


out.println("Response from " + serverName );
}
}

Step 2. Compile the test servlet

Under directory <iAS Home>/Apache/Jserv/servlets compile the java program using the following command:

$AF_JRE_TOP/bin/javac -classpath <iAS_Home>/Apache/Jsdk/lib/jsdk.jar txkTestJservLoadBal.java

Step 3. Access the test servlet

Execute the compiled test servlet by accessing the following URL:


<web_entry_protocol>://<web_entry_point>.<web_entry_domain>:<web_entry_port>/servlets/txkTestJservLoadBal

This should show the "Response from <hostname>". If you click on the reload then you should see hostnames
of the other servers which participate in the Apache JServ Layer Load Balancing as well.

Appendix D. Configuring JVMs to Designate a Functionally Referenced Node


You can configure a node to serve as a particular "functionally referenced" node depending upon the requirements. For example,
you may want to configure a Web Node that serves only Discoverer requests or when using Forms Listener Servlet, a Forms
Node that serves only forms requests. You can do this by configuring the number of Java Virtual Machines (JVMs) for that
functional area or JVM group and further distribute the load within the set of functionally referenced nodes by defining the
weighting. Below is a table that describes the functional areas which are termed as Groups within Apache JServ, with the context
variables for configuring number of JVMs and defining weighting for each JVM Group.

JVM Group Context variable to Context variable to


name define the weight configure number of JVMs
Core group OACORE Node Weight OACORE JVM Processes
Disco group DISCO Node Weight Discoverer JVM Processes
Forms group FORMS Node Weight Forms Servlet JVM Processes
Web
Services XMLSVCS Node Weight XML Services JVM Processes
group

Here is a case study to show how to configure JVM groups to serve as a functionally referenced node. From the above table
there are four JVM Groups which can be configured to serve as these four functionally referenced nodes,

Forms Node
Discoverer Node
Self Service Node

Then your typical JVM configuration will look like this.

Forms Discoverer Self Service


Context Variable Setting
Node Node Node
OACORE JVM Processes 0 0 4
Discoverer JVM Processes 0 4 0
Forms Servlet JVM
4 0 0
Processes
XML Services JVM
0 0 4
Processes

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 13 of 15
Document 217368.1 22/01/18 17(15

0 0 4
Processes

Note
You must set the Applications Context variable "Forms Servlet Comment" to nothing
on all the nodes.

Distributing Load within a Farm


OProcMgr derives the weighting information from the configuration files in order to determine the load for the specific node. This
applies only to those environments which use OProcMgr to do the Apache JServ Load Balancing.

Extending the previous example, suppose you have 4 Forms Nodes in your Forms farm. And within these Forms Nodes, you
have two servers which are twice as fast as the other two or you want to load two servers twice as much as the other two. In this
case you may want to distribute the weighting as follows.

Context Variable Forms Forms Forms Forms


Setting Node1 Node 2 Node 3 Node 4
FORMS Node
2 2 1 1
Weight

Appendix E. Configuring HTTP Load Balancers with Forms Metrics Server

Important Note
This section has not been certified by Oracle Development
and is mentioned here for the purposes of possible
configuration choices. The recommended approach is to
use the certified Forms Listener Servlet configuration as
mentioned in Step 2.2.5.

Step 1 Implement Forms Metrics Server Option

Follow Option 2.4.2 to implement Forms Metrics Server.

Step 2 Direct All Forms Requests to Primary Web Node


In the case where a HTTP load balancer (Web Entry Point Node) is used, it is required to direct all the forms requests to the
Primary Web Node. You can achieve that by choosing an option below.

Option 1 Configure a Rule in HTTP Load Balancer


Define a rule in the HTTP Load Balancer (Web Entry Point Node) to direct all forms requests of type
(/dev60cgi/f60cgi) to Primary Web Node.

Option 2 Set ICX_FORMS_LAUNCHER Profile Option Value at Server Level

On all the Web Nodes, set the value of ICX_FORMS_LAUNCHER profile at server level to that of
Primary Web Node. You may need to apply the patch 4025399 to have the server level profile option
available to you. And you can refer the Readme of the patch 2917019 for more information regarding
server level profiles.

Appendix F. Oracle Portal 3i Requirements With HTTP Load Balancer


Oracle Portal 3i requires "cookie based session persistence" to be set at the HTTP Load Balancer. So, if Oracle E-Business
Suite 11i is configured to be used with Oracle Portal 3i and you plan to enable HTTP Load Balancing among the middle tier Web
Nodes, then you must follow Option 2.2. HTTP Layer Hardware Load Balancing and enable "cookie based session persistence"
on the HTTP Load Balancer. For more information about Oracle Portal 3i integration, please see Oracle MetaLink Note 146469.1
titled "Installing and Configuring Oracle Login Server and Oracle Portal 3i with Oracle Applications 11i".

Related Documentation
Installing Oracle Applications, Release 11i 11.5.7 (May 2002) (A92164-01) CR: 283557 (PDF, 1321 Kb)
Oracle9i Application Server (9iAS) with Oracle E-Business Suite Release 11i Documentation (Note 207159.1)
Installing Oracle9i Application Server with Oracle Applications 11i (Note 146468.1)
Using AutoConfig to Manage System Configurations with Oracle Applications 11i (Note 165195.1)
Load Balancing Implementation and Troubleshooting in 11.5.x using Metric Server (Note 148155.1)

Third Party Documentation

Deploying Big-IP System wirh Oracle E-Business Suite 11i

Change Log
Feb 29, 2008
Multiple entry point configuration removed as this was still under investigation for 11i release. Same functionality is
documented in the R12 load balancing note 380489.1
Mar 26, 2007
Chapter1, Required patches: Replaced patch 3029442 & 3104607 with patch 5478710
Mar 7, 2007:
Added "Network Configuration Requirements for Load-Balancers" to Chapter 1

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 14 of 15
Document 217368.1 22/01/18 17(15

Added "Network Configuration Requirements for Load-Balancers" to Chapter 1


Step 2.1.1, 2.2.2, Appendix A: Replaced patch 3175852 with patch 5478710
Sept 07, 2005
Implemented Remarks 45234.1. 45908.1, 60914.1, 58646.1. Also fixed gramatical errors as well as clarified
descriptions and instructions by rewording some of the text.
Aug 05,2005
Implemented Remarks in Section 2.2.1. Doc Bug# 4496674
Implemented Remarks in Section 2.3.2. Doc Bug# 4486756
Implemented Remarks in Section 2.3.1. Doc Bug# 4486736
Jul 05,2005
Added the following to the "Note for using SSL Accelerator" section
Conditional requirement of SSL Accelerator when using Cookie Based Persistence and SSL at the HTTP
layer
Modified the steps to refer to SSL Accelerator with new additional Step 5.
Appendix F added.
Apr 11, 2005:
Added reference to DMZ document.
Changed all references from "JServ" to "Apache JServ".
Removed Common Configuration section since it is not required.
Added a brief description for requiring Apache JServ load balancing for DNS load balancers
Added Appendix E and simplified description for Primary Web Node in Forms Metrics Server context vs Load
Balancer context.
Added Option 2.4.3. Disabling Forms Metric Server
Added a Note to section 2.3.3 to run AutoConfig when adding a Node conditionally
Added Third Party Documentation
Fixed broken links to 233428.1
Jun 23, 2004: Added use of shared APPL_TOP infrastructure to add new nodes and added confirming Apache JServ load
balancing from log files in Appendix C.
May 07, 2004: Added notes to update OA Core zone name to root for Apache JServ section and made changes to
Appendix D. Added configuration steps for DNS Load balancer section.
Feb 23, 2004: Added notes for Oracle Configurator.
Jan 26, 2004: Publishing updated version after an early adopter program.
Jan 24th, 2003:
Rearranged and renamed the sections so that it is easy to configure and understand.
Changed the Web/Forms node dependency for Forms Servlet configuration.

Copyright 2008 Oracle Corporation


MetaLink Note 217368.1
Last updated: November 27, 2008

Didn't find what you are looking for? Ask in Community...

Attachments
DNS Load Balancing Diagram (11.22 KB)
HTTP Load Balancing Diagram (11.93 KB)
JServ Pool Diagram (15.59 KB)
Terminology Diagram (15.29 KB)

Related
Products

Oracle E-Business Suite > Applications Technology > Technology Components > Oracle E-Business Suite Technology Stack > Advanced Configurations

Keywords
9IAS; AUTOCONFIG; JSERV; OHS; SCALABILITY; SERVLET; SIZING; TCF

Errors
HTTP-200

Back to Top
Copyright (c) 2018, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=210871230744835&id=217368.1&_adf.ctrl-state=o2qf54ptb_155 Page 15 of 15

Оценить