Adding A New Managed Server R122

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 3
At a glance
Powered by AI
The key steps are to use the adProvisionEBS.pl script to add a new managed server, start it using admanagedsrvctl.sh, update the configuration files using txkSetAppsConf.pl script, and restart OHS if needed.

The steps are to use the adProvisionEBS.pl script to add it, start it using admanagedsrvctl.sh, perform dependency checks using txkChkEBSDependecies.pl, update other nodes' configuration using txkSetAppsConf.pl script.

The txkChkEBSDependecies.pl script performs dependency checks for the newly added managed server to ensure all required files are in place to avoid runtime errors.

Adding a New Managed Server in Oracle E-Business Suite R12.

2
Adding a new managed server

Addition of managed servers needs to be done on the run file system


Make Sure no active ADOP cycle.

During the next adop prepare, the Configuration Change Detector identifies that the addition has been
made and the managed servers are automatically synced up from the run file system to the patch file system.
The synchronization also gets done when fs_clone is executed.

Note: Managed server creation should be done only through the adProvisionEBS.pl script as mentioned in
this section. Managed servers should not be created from the WebLogic Server Administration Console.

To add a new managed server of a specific service type, perform the following steps on the run file
system:

1. Execute the following command to add a new managed server. This will create a managed server and
add a new entry to the context file for starting and stopping the new managed server via the adstrtal
and adstpall scripts:

Add managed server oacore_server2 with port 7213

[applcrp@oracrp01 ~]$ perl $AD_TOP/patch/115/bin/adProvisionEBS.pl ebs-create-managedserver -


contextfile=/d01/oracle/CRP/app/fs2/inst/apps/CRP_oracrp01/appl/admin/CRP_oracrp01.xml -
managedsrvname=oacore_server2 -servicetype=oacore -managedsrvport=7213 -
logfile=oadd_acore_server2.log
Enter the APPS Schema password:
Enter the WebLogic AdminServer password:

The logfile for this session is located at oadd_acore_server2.log


ManagedServer oacore_server2 created successfully.

2. Startup the managed server as follows:

[applcrp@oracrp01 ~]$ cd $ADMIN_SCRIPTS_HOME


[applcrp@oracrp01 scripts]$

[applcrp@oracrp01 scripts]$ sh admanagedsrvctl.sh start oacore_server2

You are running admanagedsrvctl.sh version 120.14.12020000.11

Enter the WebLogic Admin password:

Calling txkChkEBSDependecies.pl to perform dependency checks for oacore_server2


*** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS
*** Log File =
/d01/oracle/CRP/app/fs2/inst/apps/CRP_oracrp01/logs/appl/rgf/TXK/txkChkEBSDependecies_Thu_Nov_1
6_12_04_52_2017/txkChkEBSDependecies_Thu_Nov_16_12_04_52_2017.log
Perl script txkChkEBSDependecies.pl got executed successfully

Starting oacore_server2...
Server specific logs are located at
/d01/oracle/CRP/app/fs2/FMW_Home/user_projects/domains/EBS_domain_CRP/servers/oacore_server2/l
ogs

admanagedsrvctl.sh: exiting with status 0

admanagedsrvctl.sh: check the logfile


/d01/oracle/CRP/app/fs2/inst/apps/CRP_oracrp01/logs/appl/admin/log/adoacorectl.txt for more
information ...

3. Perform the following steps on all application tier nodes participating in the same cluster where this
managed server is added:

Source RUN File System:


[applcrp@oracrp01 app]$ . EBSapps.env

Execute the following command to add details of the newly added managed servers into the OHS
configuration files mod_wl_ohs.conf and apps.conf on the current node:

oacore_server2 has been added on host ' oracrp01' and domain 'depa.ae' with port 7213

[applcrp@oracrp01 ~]$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -


contextfile=/d01/oracle/CRP/app/fs2/inst/apps/CRP_oracrp01/appl/admin/CRP_oracrp01.xml -
configoption=addMS -oacore=oracrp01.depa.ae:7213
Enter apps schema password :
*** LOG FILE:
/d01/oracle/CRP/app/fs2/inst/apps/CRP_oracrp01/logs/appl/rgf/TXK/txkSetAppsConf_11161215.l
og ***

4. If Oracle HTTP Server is enabled on the node, restart it as follows:

[applcrp@oracrp01 scripts]$ adapcctl.sh stop

You are running adapcctl.sh version 120.0.12020000.6

Stopping OPMN managed Oracle HTTP Server (OHS) instance ...

adapcctl.sh: exiting with status 0

adapcctl.sh: check the logfile


/d01/oracle/CRP/app/fs2/inst/apps/CRP_oracrp01/logs/appl/admin/log/adapcctl.txt for more information
...

[applcrp@oracrp01 scripts]$ adapcctl.sh start

You are running adapcctl.sh version 120.0.12020000.6

Starting OPMN managed Oracle HTTP Server (OHS) instance ...


adapcctl.sh: exiting with status 0

adapcctl.sh: check the logfile


/d01/oracle/CRP/app/fs2/inst/apps/CRP_oracrp01/logs/appl/admin/log/adapcctl.txt for more information
...

[applcrp@oracrp01 scripts]$

Reference:

Managing Configuration of Oracle HTTP Server and Web Application Services in Oracle E-Business Suite
Release 12.2 (Doc ID 1905593.1)

You might also like