---Adding Secondary Node in EBS R12.2.

Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1)

Section 5: Advanced Cloning Options

5.3 Adding a New Application Tier Node to an Existing System

1. OS version should be same

2. Directories should be same are primary
3. Create oraInventory Directory as in primary node and put oraInventory Entry in /etc/oraInst
from root user.
4. Execute adpreclone on primary app and db and create application fs1/EBsapps backup of
running file edition
5. Cope application backup to secondary node
6. Start patch admin managed server on primary before starting adcfgclone.pl script
./adadminsrvctl.sh start forcepatchfs

*****Adding Secondary Node Steps

7. Cd /u02/opt/oracle/PROD/fs1/EBSapps/comn/clone/bin
8. perl adcfgclone.pl appsTier dualfs
Enter the APPS password :

Enter the Weblogic AdminServer password :

Do you want to add a node (yes/no) [no] : yes

Verifying: Run file system AdminServer is running

Verifying: Patch file system AdminServer is running

Running: Context clone...

Log file located at

/u02/opt/oracle/PROD/fs1/EBSapps/comn/clone/bin/CloneContext_0204173655.log

Target System Hostname (virtual or normal) [erpuat] : erpuat

Target System Base Directory set to /u02/opt/oracle/PROD

Target System Current File System Base set to /u02/opt/oracle/PROD/fs1
Target System Other File System Base set to /u02/opt/oracle/PROD/fs2
Target System Fusion Middleware Home set to /u02/opt/oracle/PROD/fs1/FMW_Home
Target System Other File System Fusion Middleware Home set to
/u02/opt/oracle/PROD/fs2/FMW_Home
Target System Web Oracle Home set to /u02/opt/oracle/PROD/fs1/FMW_Home/webtier
Target System Other File System Web Oracle Home set to
/u02/opt/oracle/PROD/fs2/FMW_Home/webtier
Target System Appl TOP set to /u02/opt/oracle/PROD/fs1/EBSapps/appl
Target System Other File System Appl TOP set to /u02/opt/oracle/PROD/fs2/EBSapps/appl
 Target System COMMON TOP set to /u02/opt/oracle/PROD/fs1/EBSapps/comn
Target System Other File System COMMON TOP set to
/u02/opt/oracle/PROD/fs2/EBSapps/comn

Target System Instance Home Directory [/u02/opt/oracle/PROD] : /u02/opt/oracle/PROD

Target System Current File System Instance Top set to
/u02/opt/oracle/PROD/fs1/inst/apps/EBSMOCK_erpuat
Do you want to preserve the Display [ebsuat:0.0] (y/n) : n
Target System Display [erpuat:0.0] : enter
Target System Root Service [enabled] : enter
Target System Web Entry Point Services [enabled] :
Target System Web Application Services [enabled] :
Target System Batch Processing Services [enabled] : disabled --if you disable conc on this
then put disabled. Conc manager service will be not start on this node. Like wise for web
application services too.
Target System Other Services [disabled] : enter
Do you want the target system to have the same port values as the source system (y/n)
[y] ? : y
Validating if the source port numbers are available on the target system..
Complete port information available at
/u02/opt/oracle/PROD/fs1/EBSapps/comn/clone/bin/out/EBSMOCK_erpuat/portpool.lst

UTL_FILE_DIR on database tier consists of the following directories.

1. /usr/tmp
2. /tmp
3. /zfs/T24env/DB/ebsmock/12.1.0/ebs_home/appsutil/outbound/EBSMOCK_dreddbadm01
4. /usr/tmp
Choose a value which will be set as APPLPTMP value on the target node [1] : 1

The new APPL_TOP context file has been created :

/u02/opt/oracle/PROD/fs1/inst/apps/EBSMOCK_erpuat/appl/admin/EBSMOCK_erpuat.xml
Check Clone Context logfile
/u02/opt/oracle/PROD/fs1/EBSapps/comn/clone/bin/CloneContext_0204173655.log for details.

Creating Patch file system context file.....

Log file located at /u02/opt/oracle/PROD/fs1/EBSapps/comn/clone/bin/CloneContextPatch_0204174505.log

Target System Other File System Instance Top set to

/u02/opt/oracle/PROD/fs2/inst/apps/EBSMOCK_erpuat
Validating if the source port numbers are available on the target system..
Complete port information available at
/u02/opt/oracle/PROD/fs1/EBSapps/comn/clone/bin/out/EBSMOCK_erpuat/portpool.lst
The new APPL_TOP context file has been created :
/u02/opt/oracle/PROD/fs2/inst/apps/EBSMOCK_erpuat/appl/admin/EBSMOCK_erpuat.xml
Check Clone Context logfile
/u02/opt/oracle/PROD/fs1/EBSapps/comn/clone/bin/CloneContextPatch_0204174505.log for details.

FMW Pre-requisite check log file location :

/u02/opt/oracle/PROD/fs1/EBSapps/comn/clone/FMW/logs/prereqcheck.log
Running: FMW pre-req check...
Configuring: Run file system....
 LogFile located at
/u02/opt/oracle/PROD/fs1/inst/apps/EBSMOCK_erpuat/admin/log/clone/run/RCloneApplyAppstier_0204174
5.log
Configuring: Patch file system....
LogFile located at
/u02/opt/oracle/PROD/fs1/inst/apps/EBSMOCK_erpuat/admin/log/clone/patch/RCloneApplyAppstier_02041
758.log
Do you want to startup the Application Services for
EBSMOCK? (y/n) [n] : n
Services not started

4. Register the new topology from the newly added application tier node. Do not execute/follow
this step

9. On secondary node cd to below directory

/u02/opt/oracle/PROD/fs2/FMW_Home/webtier/instances/EBS_web_EBSMOCK_OHS1/config/OHS/EBS_web_EBSMOCK

9. update mod_wl_ohs.conf file and remove reference of primary managed server from all file

LoadModule weblogic_module "${ORACLE_HOME}/ohs/modules/mod_wl_ohs.so"

<IfModule mod_weblogic.c>

DynamicServerList OFF

<Location /OA_HTML>

SetHandler weblogic-handler

WebLogicCluster erpuat.kb.com.pk:7211,ebsuat.kb.com.pk:7211

To

WebLogicCluster erpuat.kb.com.pk:7211

10. on secondry node update apps.conf file also in same directory and remove url of primary server
from all file
<Location /OA_MEDIA>
ProxyPass balancer://oacorecluster_oamedia
ProxyPassReverse balancer://oacorecluster_oamedia
</Location>
<Proxy balancer://oacorecluster_oamedia>
BalancerMember http://erpuat.kb.com.pk:7211/OA_HTML/media
BalancerMember http://ebsuat.kb.com.pk:7211/OA_HTML/media
</Proxy>

To
<Location /OA_MEDIA>
ProxyPass balancer://oacorecluster_oamedia
ProxyPassReverse balancer://oacorecluster_oamedia
</Location>
<Proxy balancer://oacorecluster_oamedia>
BalancerMember http://erpuat.kb.com.pk:7211/OA_HTML/media
</Proxy>
11. Run autoconfig on both primary and secondary
12. Reload the application tier TNS Listener (FNDFS listener) as follows:
$ lsnrctl reload APPS_EBSMOCK
 13. If the Node Manager service is up on the Patch Edition File System of the newly added application tier node, shut it
down 
14. Check sqlnet.ora in TNS_ADMIN and add Validate Node entry if not available.
15. After adding new nodes, refer to My Oracle Support Knowledge Document 1375686.1, Using Load-Balancers with
Oracle E-Business Suite Release 12.2, for details on how to set up load balancing.
16. Configure URL for both nodes on OTD by system Team.

2.4: Using Domain Name Server (DNS) Load Balancing with Single Web Entry
Point

2.4.3: Update Applications Context File

17. Update both node context file with Load Balance Name

Context Variable Context Variable

Old Context Value New Context Value
Name Description
Protocol that desktop
s_webentryurl clients use to communicate http http
protocol with the web entry point
server
Name of the host that appstier1 on Application Server 1
s_webentryhost receives the first HTTP ebsof
request from the desktop
client appstier2 on Application Server 2

Domain name of the host

s_webentrydomain that receives the first HTTP example.com example.com
request from the desktop
client
Port on the web server
s_active_webport or load balancer tha 8051 8051
t listens for HTTP requests
http://appstier1.example.com:8050

/OA_HTML/AppsLogin 

on Application Server 1
s_login_page URL used to access the https://dnslbr.example.com/
Applications logon page http://appstier2.example.com:8050
OA_HTML/AppsLogin

/OA_HTML/AppsLogin

 on Application Server 2

URL that third party tools

use
to connect to the E-
s_external_url Business
Suite System. This is used
only by the Oracle Web
Services product.
http://appstier1.example.com:8050/ on
Application Server 1
https://dnslbr.example.com/
http://appstier2.example.com:8050/ on
Application Server 2

After completing the changes shown above, do the following:

1. Run the AutoConfig utility on all the application tier servers.
2. Restart application server processes.
3. Test sign on from the web entry point.
4. Check application availability be shutting down application one by one.