Information:
The following steps should be executed in order to delete a managed server from the domain. As in the case of managed server addition, deletion of managed servers should be done on the run file system, with synchronization between the run and the patch file systems subsequently being performed automatically during adop prepare execution or during fs_clone.
Note: Managed server deletion should be done only through the adProvisionEBS.pl script as mentioned in this section. Managed servers should not be deleted from the WebLogic Server Administration Console.
Step 1:
To delete a managed server of a specific service type, perform the following steps on the run file system:
Perform the following steps on the application tier where the managed server resides.
If the managed server to be deleted is running, shut it down as follows:
On Unix:
$ sh <ADMIN_SCRIPTS_HOME>/admanagedsrvctl.sh stop <MANAGED SERVER NAME>
Example:
$ sh <ADMIN_SCRIPTS_HOME>/admanagedsrvctl.sh stop oacore_server2
Step 2:
Run the command below on the application tier node where the managed server resides. This will delete the managed server, and also update the respective context variables that contain references to the deleted managed server.
$ perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl \
ebs-delete-managedserver \
-contextfile=<CONTEXT_FILE> -managedsrvname=<MANAGED_SERVER_NAME> \
-servicetype=<SERVICE_TYPE> -logfile=<LOGFILE>
Example,
For deleting a managed server ‘oacore_server2’ of type ‘oacore’, execute the following command:
$ perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl \
ebs-delete-managedserver \
-contextfile=<CONTEXT_FILE> -managedsrvname=oacore_server2 \
-servicetype=oacore -logfile=<APPLRGF>/TXK/delMS_oacoreserver2.log
Step 3:
Perform the following steps on all application tier nodes participating in the same cluster as the deleted managed server:
Source the run file system.
If the deleted managed server is part of the cluster configuration defined on the current node, execute the following command to delete details of the managed server from 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=removeMS \
-oacore=<host>.<domain>:<port> \
-oafm=<host>.<domain>:<port> \
-forms=<host>.<domain>:<port> \
-formsc4ws=<host>.<domain>:<port> \
-ekanban=<host>.<domain>:<port> \
-accessgate=<host>.<domain>:<port> \
-yms=<host>.<domain>:<port>
where
The argument contextfile accepts the complete path to the context file.
The arguments oacore, oafm, forms, formsc4ws, ekanban, accessgate and yms accept a comma-separated list of managed server details in the following format:
<host>.<domain>:<port>
host, domain and port are the hostname, domain and port of the managed server whose reference is to be deleted.
Example:
To remove references of the deleted managed server oacore_server2 with port 7205 on host ‘testserver’ and domain ‘example.com’, the following command should be executed:
$ perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl -contextfile=<CONTEXT_FILE> \
-configoption=removeMS -oacore=testserver.example.com:7205
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
Once you performed the above step when you login to weblogic console you will see the respective service has been removed from the system.
