Managing Managed Server Configurations:

 By default,application tier will have only a single instance of the oacore, oafm, forms and forms-c4ws services.

To increase the Web logic performance, we need to add up managed servers.

Filesystem: to be used run

There should  not be any active ADOP cycle.

Managed server additionbe removal  should be done only through scripts: adProvisionEBS.pl and txkSetAppsConf.pl 

Never use WebLogic Administration Console.

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

$ 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>

$ perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl \

ebs-create-managedserver -contextfile=<CONTEXT_FILE> \

-managedsrvname=oacore_server2 -servicetype=oacore \

-managedsrvport=7203 -logfile=<APPLRGF>/TXK/addMS_oacoreserver2.log

After completed scripts it’s created new oacoreserver2

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

Source the run file system.

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 contextfile 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 'testserver' and domain 'example.com' with port 7205, the following command should be executed: 

$ perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl -contextfile=<CONTEXT_FILE> \

-configoption=addMS -oacore=testserver.example.com:7205

3.perl $AD_TOP/bin/adSyncContext.pl contextfile=$CONTEXT_FILE

This script is used to explicitly pull the values of the WebLogic Server and Oracle HTTP Server configuration parameters and synchronize the corresponding context variable values accordingly.

4.Startup the New  managed server

$ sh <ADMIN_SCRIPTS_HOME>/admanagedsrvctl.sh start <MANAGED SERVER NAME>

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

On UNIX:

$ sh <ADMIN_SCRIPTS_HOME>/adapcctl.sh stop

$ sh <ADMIN_SCRIPTS_HOME>/adapcctl.sh start

6.Run fs_clone :

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.