DOYENSYS Knowledge Portal

We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal

Tuesday, March 27, 2012

To configure Load Balancer in Oracle E-Business Suite R12

Load Balancing configuration for R12:


For overview and various options for High Availability (at application tier level) follow Metalink (Oracle My Support) note 380489.1 Using Load-Balancers with Oracle E-Business Suite Release 12
Configuration steps mentioned are based on following assumptions

1.E-Business Suite (Apps) is installed and accessible using at least one apps server via web server port (assume port pool 0 i.e. 8000) i.e.

2. There is hardware load balancer available with port translation (8000 to 80) – (Optional and required only if you want port translation or URL on non default port)
Note: If your load balancer does not have port translation feature and you would like to use standard HTTP(s) port i.e. 80 or 443 then additional steps are required to reconfigure EBS on 80/443

3. If you want URL to be SSL/HTTPS (port 443) then Load Balancer should have capability to SSL encryption/decryption (In this case SSL will terminate at Load Balancer and from Load Balancer to Web/Apps Tier configure is HTTP)
Note: If you want SSL to be configured all the way till Web/Apps Tier then additional steps are required to re-configure EBS on 443

4. EBS R12 supports multiple URLs pointing to same application. (For this setup you need minimum 2 apps tier + additional profile option configuration)
Follow section 2.2 Using Hardware Load Balancer with Multiple Web Entry Points of Note # 380489.1
5. Session Persistence is configured at Load Balancer (Mandatory if you have multiple middle/apps tier)

Configuration below are based on following setup (change values where required)

1. There are two application tier ( and with web port as 8000

2. Load Balancer URL after setup is (listening on port 80)

3. Load Balancer is configured with entry forwarding request to & (with session stickiness)
Step to follow to re-configure Oracle Apps to use Load Balancer

1. Update following five values in Context File ($CONTEXT_FILE)  (Context file is at $INST_TOP/appl/admin) of application tier.

a) s_webentryhost – To load balancer  URL i.e. mylbr (Do not enter full name with domain)
b) s_active_webport -to load balancer port i.e. 80 (For SSL use 443)
c) s_login_page – Full URL pointing to Load Balancer http://loadbalancer.domain:port/OA_HTML/AppsLogin i.e. (For SSL use https and port as 443)
d) s_external_url – Load Balancer URL http://loadbalancer.domain:port  i.e. (For SSL use https and port as 443)
e) s_webentryurlprotocol – http  (Change to https if using SSL)
f) s_webentrydomain – Load Balancer Domain i.e.

2. Run Autoconfig on application tier

3. Repeat step 1 & 2 on all nodes running Web Server. (To check which servers are running as Web Nodes, login to database as user apps and run query “select node_name from fnd_nodes where SUPPORT_WEB=’Y';”)

4. Test load balancer configuration by accessing load balancer URL i.e.

5. If you get page not found error then check if request is coming from load balancer to Web Server access logs at $LOG_HOME/ ora/10.1.3/ access_log.NNNNNNNN (sort access log based on time stamp “ls -ltr access_log*”)

Monday, March 26, 2012

Profile Options that are used commonly by APPS DBA’s

Concurrent Related Profile Options

Concurrent: Active Request Limit  
Value: Numeric
This profile options will restrict the number of concurrent requests that may be run simultaneously by each user. If we do not specify a limit, then there will be no limit .

Concurrent: Hold Requests
Values: YES/NO
This option use to automatically place requests on hold after submission.

Concurrent: Report Access Level
This option determines the access privileges to report output files and log files generated by a concurrent program. This option can be set by a system administrator or by any apps user.

Concurrent: Report Copies
Values: Numeric
This option is used to find out the number of default copies that print for each submitted concurrent request.

Concurrent: Request priority
Values: Numeric
Concurrent requests in Oracle Applications are first queued. Requests normally run according to a start time on a first submitted, first run basis. Priority overrides this request start time. A higher priority request starts before an earlier request. This option displays the default priority for concurrent requests. Only a system administrator can change your request priority.

Concurrent: Concurrent:OPP Process Timeout
Values: Numeric
This profile option specifies the amount of time the manager waits for the OPP to actually process the request.

Concurrent: OPP Response Timeout
Values: Numeric
This profile option specifies the amount of time a manager waits for the OPP to respond to its request for post processing.

Concurrent: GSM Enabled
Values: YES/NO
Use this profile option to enable Generic Service Management. GSM will manages all the concurrent manager services.

FND:Debug Log Module
Values: YES/NO
The Logging Service can filter out debugging messages depending on their module. Module names are unique across applications and coding languages. If a module is specified for this profile option, then only messages for that module will be written to the log file. If this profile option is left blank then messages for all modules will be written to the log file.

FND: Debug Log Level

The Logging Service can filter out debugging messages depending on their priority level.. There are five levels of the Debug/Trace Service:. In order from highest priority to lowest priority, they are: Errors, Exceptions, Events, Procedures, and Statements. The Debug Log Level is the lowest level that the user wants to see messages for.. The possible profile option values are Null (which means off), and the five priority levels above. For instance, if the “FND: Debug Log Level” profile is set to “EVENT”, then the file will get the messages that the programmer had marked as “EVENT”, “EXCEPTION”, or “ERROR”.

FND: Debug Log Filename for Middle-Tier
The file name for the file to hold debugging messages used in the Logging Service. If the value of this profile option is null, then the Logging Service is turned off.

FORMS/Reports Related Profile Options

ICX            : Discoverer Launcher
ICX            : Forms Launcher
ICX            : Report Launcher
ICX            : Session Timeout
These profile options are used by the Oracle Applications Personal Homepage.
Set the site level value of each of these profile options to the base URL for launching each application. The profile option value should be sufficient to launch the application, but should not include any additional parameters which may be supplied by the Personal Homepage.

RRA          : Delete Temporary Files
Values                : YES/NO

When using a custom editor to view a concurrent output or log file from the front end, the Report Review Agent will make a temporary copy of the file on the client. Set this profile to “Yes” to automatically delete these files when the user exits Oracle Applications.
Only the System Administrator can update this profile option.

RRA          : Enabled
Values    : YES/NO
Set this user profile to Yes to use the Report Review Agent to access files on concurrent processing nodes.

RRA          : Maximum Transfer Size

Specify, in bytes, the maximum allowable size of files transferred by the Report Review Agent, including those downloaded by a user with the “Copy File…” menu option in the Oracle Applications Report File Viewer and those “temporary” files which are automatically downloaded by custom editors. For example, to set the size to 64K you enter 65536. If this profile is null, there is no size limit.

Viewer:Default Font Size

Using this new profile option, you can set the default font size used when you display report output in the Report Viewer.
The valid values for this option are 6, 8, 10, 12, and 14.

Java Color Scheme

If the Java Look and Feel profile option is set to Oracle, the Java Color Scheme can be specified as follows:
Swan (default)

The Java Color Scheme profile has no effect if the Java Look and Feel is set to Generic.
Attention: Setting the Java Color Scheme profile option to a value other than ‘swan’ (the default value) can have a considerable impact on forms user response time performance.

Sign-On   : Audit Level

Sign-On:Audit Level allows you to select a level at which to audit users who sign on to Oracle Applications. Four audit levels increase in functionality: None, User, Responsibility, and Form.
None is the default value, and means do not audit any users who sign on to Oracle Applications.

Signon Password Failure Limit

Values: Numeric
The Signon Password Failure Limit profile option determines the maximum number of login attempts before the user’s account is disabled.

Signon Password Hard to Guess

Values    : YES/NO
The Signon Password Hard to Guess profile option sets rules for choosing passwords to ensure that they will be hard to guess. A password is considered hard-to-guess if it follows these rules:
The password contains at least one letter and at least one number.
The password does not contain the username.
The password does not contain repeating characters.

Signon Password Length

Values: Numeric
Signon Password Length sets the minimum length of an Applications signon password. If no value is entered the minimum length defaults to 5.

Signon Password No Reuse

Values: Numeric
This profile option specifies the number of days that a user must wait before being allowed to reuse a password.

Signon Password Case

Values    : YES/NO
sitive  Passwords are stored and compared as they are, with the password case preserved. During validation, the entered password must match the decrypted version otherwise an error message is displayed. With Release 12, this option is the default behavior. All newly created or changed passwords are treated as case sensitive.

Site Name

The Site Name appears in the title of the MDI window. If you want additional information on your installation to appear in the title, for example, Test or Production, you can add that information here.

You can select the printer which prints your reports. If a printer cannot be selected, contact your system administrator. Printers must be registered with Oracle Applications.