How to add the manage server (oacore) in R12.2.4
I would be explaining what I learned from that experience and How to add the manage server in R12.2. I will particularly taking the example of oacore
1. Addition of managed servers needs to be done on the run file system when there is
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.
2. 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:
$ perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl \
ebs-create-managedserver -contextfile=<CONTEXT_FILE> \
-managedsrvname=<MANAGED_SERVER_NAME> -servicetype=<SERVICE_TYPE> \
-managedsrvport=<MANAGED_SERVER_PORT> -logfile=<LOGFILE>
For example, to add a managed server ‘oacore_server2’ of type ‘oacore’ with port 9705,
run the following command:
$ perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl \
ebs-create-managedserver -contextfile=<CONTEXT_FILE> \
-managedsrvname=oacore_server2 -servicetype=oacore \
-managedsrvport=9705 -logfile=<APPLRGF>/TXK/addMS_oacoreserver2.log
3) Start the newly created managed server
sh <ADMIN_SCRIPTS_HOME>/admanagedsrvctl.sh start <MANAGED SERVER NAME>
4) Perform the following steps on all application tier nodes participating in the same
cluster where this managed server is added:
Add the entry in OHS configuration file
a) Source the run file system.
b) 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:
$ perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl \
-contextfile=<CONTEXT_FILE> \
-configoption=addMS \
-oacore=<host>.<domain>:<port> \
-oafm=<host>.<domain>:<port> \
-forms=<host>.<domain>:<port> \
-formsc4ws=<host>.<domain>:<port>
where The argument context file accepts the complete path to the context file.
The arguments oacore, oafm, forms, formsc4ws accept a comma-separated list of managed server details in the following format:
<host>.<domain>:<port>
host and domain are the hostname and domain name of the newly added node
port is the port of the new managed server whose reference is to be added
For example, if the managed server oacore_server2 has been added on host ‘myserver’ and domain ‘go.com’ with port 9705, the following command should be executed:
$ perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl -contextfile=<CONTEXT_FILE> \
-configoption=addMS -oacore=myserver.go.com:9705
c) Restart the http server if it is present on that server
sh <ADMIN_SCRIPTS_HOME>/adapcctl.sh stop
$ sh <ADMIN_SCRIPTS_HOME>/adapcctl.sh start
OR
EBS R12.2 : add managed server oacore,oafm,forms,forms-c4ws..
By default there is single Web Application Services in EBS 12.2.4
If you want to increase number of server either oacore, oafm, forms or forms-c4ws then below instruction need to follow. In below example we are adding one more oacore server.
To check current edition:
echo $FILE_EDITION
Follow below steps to add oacore services
Step 1: Take backup of $CONTEXT_FILE from both edition
Step 2: Run script on run edition:
[applmgr@ebs122 ~]$ perl $AD_TOP/patch/115/bin/adProvisionEBS.pl ebs-create-managedserver
-contextfile=/apps01/applmgr/TEST/fs2/inst/apps/TEST_ebs122/appl/admin/TEST_ebs122.xml
-managedsrvname=oacore_server2 -servicetype=oacore -managedsrvport=7203 -logfile=/tmp/oacore2.log
Enter the APPS Schema password:
Enter the WebLogic AdminServer password:
The logfile for this session is located at /tmp/oacore2.log
Check the logfile for any error message.
[applmgr@ebs122 ~]$ vi /tmp/oacore2.log
Step 3: Run autoconfig on run edition
[applmgr@ebs122 ~]$ adautocfg.sh
Enter the APPS user password:
AutoConfig completed successfully.
Step 4: [applmgr@ebs122 ~]$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -ctxfile=$CONTEXT_FILE -outfile=/tmp/txkSetAppsConf.log
mod_wl_ohs.conf generated successfully
apps.conf generated successfully
Step 5: Stop/start http services on run edition
[applmgr@ebs122 ~]$ cd $ADMIN_SCRIPTS_HOME
[applmgr@ebs122 scripts]$ adapcctl.sh stop
You are running adapcctl.sh version 120.0.12020000.2
Stopping OPMN managed Oracle HTTP Server (OHS) instance ...
opmnctl stopproc: stopping opmn managed processes...
adapcctl.sh: exiting with status 0
[applmgr@ebs122 scripts]$ adapcctl.sh start
You are running adapcctl.sh version 120.0.12020000.2
Starting OPMN managed Oracle HTTP Server (OHS) instance ...
opmnctl start: opmn is already running.
opmnctl startproc: starting opmn managed processes...
adapcctl.sh: exiting with status 0
Now add oacore server info intoPATCH edition:
Step 6: Set patch edition env.
[applmgr@ebs122 ~]$ echo $FILE_EDITION
patch
Step 7:
Start up the WebLogic Administration Server of the PATCH file system by executing the below command on the PATCH file system
[applmgr@ebs122 scripts]$ adadminsrvctl.sh start forcepatchfs
You are running adadminsrvctl.sh version 120.10.12020000.2
Enter the WebLogic Admin password:
Enter the APPS Schema password:
Starting WLS Admin Server...
Refer /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/admin/log/adadminsrvctl.txt for details
adadminsrvctl.sh: exiting with status 0
adadminsrvctl.sh: check the logfile
/apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/admin/log/adadminsrvctl.txt for more information
Step 8: From Run Addition execute below script with service name and port number
[applmgr@ebs122 scripts]$ perl $AD_TOP/patch/115/bin/adProvisionEBS.pl ebs-create-managedserver
-contextfile=$CONTEXT_FILE -managedsrvname=oacore_server2 -servicetype=oacore -managedsrvport=7204 -logfile=\tmp\oacore2_2.log
Enter the APPS Schema password:
Enter the WebLogic AdminServer password:
Step 9:
[applmgr@ebs122 scripts]$ perl $AD_TOP/bin/adSyncContext.pl
-contextfile=/apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/appl/admin/TEST_ebs122.xml
Enter the APPS user password:
Enter the WebLogic AdminServer password:
The log file is /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/rgf/Sun_Jan_5_15_14_03_2014/adSyncContext.log
Step 10: Instantiate the fsclone_config.txt file on the PATCH file system of all Application tier nodes by running the following command after sourcing the RUN file system:
java oracle.apps.ad.autoconfig.InstantiateFile -e <PATCH_CONTEXT_FILE> -tmpl \
<PATCH_AD_TOP>/admin/template/fsclone_config_txt.tmp -out \
<PATCH_INST_TOP>/appl/admin/fsclone_config.txt
[applmgr@ebs122 scripts]$ java oracle.apps.ad.autoconfig.InstantiateFile -e /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/appl/admin/TEST_ebs122.xml -tmpl /apps01/applmgr/TEST/fs1/EBSapps/appl/ad/12.0.0/admin/template/fsclone_config_txt.tmp -out /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/appl/admin/fsclone_config.txt
Enter the APPS password : APPS
Step 11: Execute below script from RUN file system
On the node containing the Oracle HTTP Server, execute the following script from the RUN file system, passing the context file from the PATCH file system. This will update the Oracle HTTP Server configuration files on the PATCH file system with the new managed server port number.
[applmgr@ebs122 scripts]$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -ctxfile=/apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/appl/admin/TEST_ebs122.xml \
> -outfile=/tmp/oacore2_3.log
mod_wl_ohs.conf generated successfully
apps.conf generated successfully
Step 12: Stop weblogic services from PATCH file system:
[applmgr@ebs122 scripts]$ adadminsrvctl.sh stop
You are running adadminsrvctl.sh version 120.10.12020000.2
Enter the WebLogic Admin password:
Enter the APPS Schema password:
Stopping WLS Admin Server...
.Refer /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/admin/log/adadminsrvctl.txt for details
adadminsrvctl.sh: exiting with status 0
adadminsrvctl.sh: check the logfile
/apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/admin/log/adadminsrvctl.txt for more information
Step 13: Start newly added managed server from run edition:
admanagedsrvctl.sh start oacore_server2
Step 14: Check the status of server weblogic console:
I would be explaining what I learned from that experience and How to add the manage server in R12.2. I will particularly taking the example of oacore
1. Addition of managed servers needs to be done on the run file system when there is
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.
2. 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:
$ perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl \
ebs-create-managedserver -contextfile=<CONTEXT_FILE> \
-managedsrvname=<MANAGED_SERVER_NAME> -servicetype=<SERVICE_TYPE> \
-managedsrvport=<MANAGED_SERVER_PORT> -logfile=<LOGFILE>
For example, to add a managed server ‘oacore_server2’ of type ‘oacore’ with port 9705,
run the following command:
$ perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl \
ebs-create-managedserver -contextfile=<CONTEXT_FILE> \
-managedsrvname=oacore_server2 -servicetype=oacore \
-managedsrvport=9705 -logfile=<APPLRGF>/TXK/addMS_oacoreserver2.log
3) Start the newly created managed server
sh <ADMIN_SCRIPTS_HOME>/admanagedsrvctl.sh start <MANAGED SERVER NAME>
4) Perform the following steps on all application tier nodes participating in the same
cluster where this managed server is added:
Add the entry in OHS configuration file
a) Source the run file system.
b) 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:
$ perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl \
-contextfile=<CONTEXT_FILE> \
-configoption=addMS \
-oacore=<host>.<domain>:<port> \
-oafm=<host>.<domain>:<port> \
-forms=<host>.<domain>:<port> \
-formsc4ws=<host>.<domain>:<port>
where The argument context file accepts the complete path to the context file.
The arguments oacore, oafm, forms, formsc4ws accept a comma-separated list of managed server details in the following format:
<host>.<domain>:<port>
host and domain are the hostname and domain name of the newly added node
port is the port of the new managed server whose reference is to be added
For example, if the managed server oacore_server2 has been added on host ‘myserver’ and domain ‘go.com’ with port 9705, the following command should be executed:
$ perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl -contextfile=<CONTEXT_FILE> \
-configoption=addMS -oacore=myserver.go.com:9705
c) Restart the http server if it is present on that server
sh <ADMIN_SCRIPTS_HOME>/adapcctl.sh stop
$ sh <ADMIN_SCRIPTS_HOME>/adapcctl.sh start
OR
EBS R12.2 : add managed server oacore,oafm,forms,forms-c4ws..
By default there is single Web Application Services in EBS 12.2.4
If you want to increase number of server either oacore, oafm, forms or forms-c4ws then below instruction need to follow. In below example we are adding one more oacore server.
To check current edition:
echo $FILE_EDITION
Follow below steps to add oacore services
Step 1: Take backup of $CONTEXT_FILE from both edition
Step 2: Run script on run edition:
[applmgr@ebs122 ~]$ perl $AD_TOP/patch/115/bin/adProvisionEBS.pl ebs-create-managedserver
-contextfile=/apps01/applmgr/TEST/fs2/inst/apps/TEST_ebs122/appl/admin/TEST_ebs122.xml
-managedsrvname=oacore_server2 -servicetype=oacore -managedsrvport=7203 -logfile=/tmp/oacore2.log
Enter the APPS Schema password:
Enter the WebLogic AdminServer password:
The logfile for this session is located at /tmp/oacore2.log
Check the logfile for any error message.
[applmgr@ebs122 ~]$ vi /tmp/oacore2.log
Step 3: Run autoconfig on run edition
[applmgr@ebs122 ~]$ adautocfg.sh
Enter the APPS user password:
AutoConfig completed successfully.
Step 4: [applmgr@ebs122 ~]$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -ctxfile=$CONTEXT_FILE -outfile=/tmp/txkSetAppsConf.log
mod_wl_ohs.conf generated successfully
apps.conf generated successfully
Step 5: Stop/start http services on run edition
[applmgr@ebs122 ~]$ cd $ADMIN_SCRIPTS_HOME
[applmgr@ebs122 scripts]$ adapcctl.sh stop
You are running adapcctl.sh version 120.0.12020000.2
Stopping OPMN managed Oracle HTTP Server (OHS) instance ...
opmnctl stopproc: stopping opmn managed processes...
adapcctl.sh: exiting with status 0
[applmgr@ebs122 scripts]$ adapcctl.sh start
You are running adapcctl.sh version 120.0.12020000.2
Starting OPMN managed Oracle HTTP Server (OHS) instance ...
opmnctl start: opmn is already running.
opmnctl startproc: starting opmn managed processes...
adapcctl.sh: exiting with status 0
Now add oacore server info intoPATCH edition:
Step 6: Set patch edition env.
[applmgr@ebs122 ~]$ echo $FILE_EDITION
patch
Step 7:
Start up the WebLogic Administration Server of the PATCH file system by executing the below command on the PATCH file system
[applmgr@ebs122 scripts]$ adadminsrvctl.sh start forcepatchfs
You are running adadminsrvctl.sh version 120.10.12020000.2
Enter the WebLogic Admin password:
Enter the APPS Schema password:
Starting WLS Admin Server...
Refer /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/admin/log/adadminsrvctl.txt for details
adadminsrvctl.sh: exiting with status 0
adadminsrvctl.sh: check the logfile
/apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/admin/log/adadminsrvctl.txt for more information
Step 8: From Run Addition execute below script with service name and port number
[applmgr@ebs122 scripts]$ perl $AD_TOP/patch/115/bin/adProvisionEBS.pl ebs-create-managedserver
-contextfile=$CONTEXT_FILE -managedsrvname=oacore_server2 -servicetype=oacore -managedsrvport=7204 -logfile=\tmp\oacore2_2.log
Enter the APPS Schema password:
Enter the WebLogic AdminServer password:
Step 9:
[applmgr@ebs122 scripts]$ perl $AD_TOP/bin/adSyncContext.pl
-contextfile=/apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/appl/admin/TEST_ebs122.xml
Enter the APPS user password:
Enter the WebLogic AdminServer password:
The log file is /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/rgf/Sun_Jan_5_15_14_03_2014/adSyncContext.log
Step 10: Instantiate the fsclone_config.txt file on the PATCH file system of all Application tier nodes by running the following command after sourcing the RUN file system:
java oracle.apps.ad.autoconfig.InstantiateFile -e <PATCH_CONTEXT_FILE> -tmpl \
<PATCH_AD_TOP>/admin/template/fsclone_config_txt.tmp -out \
<PATCH_INST_TOP>/appl/admin/fsclone_config.txt
[applmgr@ebs122 scripts]$ java oracle.apps.ad.autoconfig.InstantiateFile -e /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/appl/admin/TEST_ebs122.xml -tmpl /apps01/applmgr/TEST/fs1/EBSapps/appl/ad/12.0.0/admin/template/fsclone_config_txt.tmp -out /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/appl/admin/fsclone_config.txt
Enter the APPS password : APPS
Step 11: Execute below script from RUN file system
On the node containing the Oracle HTTP Server, execute the following script from the RUN file system, passing the context file from the PATCH file system. This will update the Oracle HTTP Server configuration files on the PATCH file system with the new managed server port number.
[applmgr@ebs122 scripts]$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -ctxfile=/apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/appl/admin/TEST_ebs122.xml \
> -outfile=/tmp/oacore2_3.log
mod_wl_ohs.conf generated successfully
apps.conf generated successfully
Step 12: Stop weblogic services from PATCH file system:
[applmgr@ebs122 scripts]$ adadminsrvctl.sh stop
You are running adadminsrvctl.sh version 120.10.12020000.2
Enter the WebLogic Admin password:
Enter the APPS Schema password:
Stopping WLS Admin Server...
.Refer /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/admin/log/adadminsrvctl.txt for details
adadminsrvctl.sh: exiting with status 0
adadminsrvctl.sh: check the logfile
/apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/admin/log/adadminsrvctl.txt for more information
Step 13: Start newly added managed server from run edition:
admanagedsrvctl.sh start oacore_server2
Step 14: Check the status of server weblogic console:
No comments:
Post a Comment