Implementing Shared APPL_TOP or Application Tier

Lets continue with how to configure shared Application Tier ( Earlier used to called as shared APPL_TOP) .

If you have reached here via search engine & haven’t read overview of shared APPL_TOP or shared application tier then I’ll recommend you go through it at mentioned at end of this post in related posts heading.

From now onwards I’ll discuss shared application tier & shared APPL_TOP interchangeably.

There are two scenarios in which you want to configure Shared Application tier like
1. You want to configure shared APPL_TOP at install time itself (During Initial Build/Fresh Install)
2. You already have multi node Installation and want to configure Shared APPL_TOP.

In case of fresh Install or configure shared application tier via Installer
You first find a file system & share it across all servers ( Usually ask unix team to do so). Lets assume you want to configure shared appl_top on machine 1, 2 and 3 . Assume you have file system /u01/shared/appl_top, /u01/shared/comn_top, /u01/shared/ora_top local to any of these servers or on any file server like SAN or NAS , then mount it to all these three servers with same mount points assume in our case we mounted like
/u01/shared/appl_top, /u01/shared/comn_top, /u01/shared/ora_top
Then when rapid installer asks for mount points give shared mount points from all three or more machines. Rest Leave on Installer 🙂

In case to configure shared Application Tier on already installed multiple node
1. There is some minimum software version for some component you need , make sure you have appropriate version if not upgrade them . For version check metalink Note referenced at bottom of this in Related links section.
2. Then you need to enable Autoconfig if you already don’t have Autoconfig enabled : To check more on Autoconfig visit http://teachmeoracle.com/autoconfig.html
3. If your exisiting xml file ( CONTEXT file) is of format SID.xml then you need it in format SID_HOSTNAME.xml ( This way each server will recognize its xml/context file ) . You can do same by perl script adclonectx.pl
4. Shared file system across all machine with same mount point as done above
5. You then finally run autoconfig to configure shared application tier

About the Author Atul Kumar

Oracle ACE, Author, Speaker and Founder of K21 Technologies & K21 Academy : Specialising in Design, Implement, and Trainings.

follow me on:

Leave a Comment:

5 comments

sandeep_dba says March 26, 2008

”
4. Shared file system across all machine with same mount point as done above
5. You then finally run autoconfig to configure shared application tier
”

The REAL steps for shared application tier configuration lie between these two points(Running txkSOHM.pl).You haven’t written anything about it.

sandeep_dba says March 26, 2008

Only running autoconfig wont configure the shared application tierYou need to define which node is your primary and which secondary.Also need to specify location for configuration files.

amit says March 29, 2008

Hi Sandeep,

Script txkSOHM.pl that you will run will create tnsname.ora,apachec configuration files,Jserv file related to soap,oem configuration files. Basically it is crating files related to Tech Stack Oracle Home.

Let me know if this helps

Amit

Muthu says January 4, 2011

Hi,
I have configured the 2 Application tier for Active Active mode (R12.1.1).everything is completed but primary url only working .if i enter secondary url means it will redirecting to Primary Url .I need Multiple Url .Please Help me .

Atul Kumar says January 4, 2011

@ Muthu,
On second node set s_webentryhost, s_webentrydomain, s_external_url , s_active_webport, s_webentryurlprotocol, s_login_page to second machine and run autoconfig

Also check 380490.1 Oracle E-Business Suite R12 Configuration in a DMZ (This is not exact match but will give you idea)

Add Your Reply