NaturalOracle DataGaurd tutorial Series Coming Soon!! Natural
For Any queries, please mail us at support@funoracleapps.com

Adding and Deleting Managed Server in Oracle Apps R12.2

No comments

Adding a New Managed Server

The below steps needs to be executed on 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.

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:

Step 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 /patch/115/bin/adProvisionEBS.pl \
ebs-create-managedserver -contextfile= \
-managedsrvname= -servicetype= \
-managedsrvport= -logfile=


For example, to add a managed server 'oacore_server2' of type 'oacore' with port 7203, run the following command:

$ perl /patch/115/bin/adProvisionEBS.pl \
ebs-create-managedserver -contextfile=$CONTEXT_FILE \
-managedsrvname=oacore_server2 -servicetype=oacore \
-managedsrvport=7203 -logfile=$APPLRGF/TXK/addMS_oacoreserver2.log

Note:
The managed server name must be of the form _server, where n is an integer.
As well as being free, the port number for each managed server must be unique: no two managed servers across the run and patch file systems can have the same port number.

Step 2:

Startup the managed server as follows:


On Unix:
$ sh /admanagedsrvctl.sh start

Example:

$ sh /admanagedsrvctl.sh start oacore_server2

Step 3: 

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 /patch/115/bin/txkSetAppsConf.pl \
-contextfile= \
-configoption=addMS \
-oacore=.: \
-oafm=.: \
-forms=.: \
-formsc4ws=.:

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 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 /patch/115/bin/txkSetAppsConf.pl -contextfile=$CONTEXT_FILE \
-configoption=addMS -oacore=testserver.example.com:7205

Step 4:

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

On UNIX:
$ sh /adapcctl.sh stop
$ sh /adapcctl.sh start



Removing a Managed Server

The below steps needs to be executed on run file system when there is no active ADOP cycle. 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.
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.

Step 1:

If the managed server to be deleted is running, shut it down as follows:

On Unix:

$ sh /admanagedsrvctl.sh stop

For example, before deleting a managed server 'oacore_server2', execute the following command to shut it down.
$ sh /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 /patch/115/bin/adProvisionEBS.pl \
ebs-delete-managedserver \
-contextfile= -managedsrvname= \
-servicetype= -logfile=

For example, for deleting a managed server 'oacore_server2' of type 'oacore', execute the following command:
$ perl /patch/115/bin/adProvisionEBS.pl \
ebs-delete-managedserver \
-contextfile= -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 /patch/115/bin/txkSetAppsConf.pl \
-contextfile= \
-configoption=removeMS \
-oacore=.: \
-oafm=.: \
-forms=.: \
-formsc4ws=.: \
-ekanban=.:
-accessgate=.: \
-yms=.:

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 and port are the hostname, domain and port of the managed server whose reference is to be deleted.

For 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 /patch/115/bin/txkSetAppsConf.pl -contextfile= \
-configoption=removeMS -oacore=testserver.example.com:7205

Step 4:

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

On UNIX:
$ sh /adapcctl.sh stop
$ sh /adapcctl.sh start


Reference:

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

No comments :

Post a Comment

How to Create New Application user from an existing user in Oracle Apps R12

No comments
In this post I am going to share the steps to create an application user from an exiting user.
This can be used to create a user in same EBS instance or any other EBS instance.


I am creating a  new user with name john.cena  from existing user himanshu.singh . This I am doing on the same EBS instance. This will bring all responsibility also to user. 

SOURCE USER : himanshu.singh
TARGET USER : john.cena

To find the responsibilities of source user:
set pages 1200
set lines 200
SELECT frt.RESPONSIBILITY_NAME, furg.end_date
FROM
fnd_user_resp_groups furg,
FND_RESPONSIBILITY fr,fnd_responsibility_tl frt,fnd_user fu
WHERE fu.user_name = '&username'
AND   fu.user_id = furg.user_id
AND   furg.responsibility_id = fr.RESPONSIBILITY_ID
AND   frt.responsibility_id = fr.RESPONSIBILITY_ID
ORDER BY 1;

STEP 1: Use FNDLOAD to download user himanshu.singh from source instance:

FNDLOAD apps/apps 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct  user_metadata.ldt FND_USER USER_NAME=himanshu.singh

STEP 2: Modify the ldt file (himanshu.singh_USER.ldt for the example above):

Change the line to


BEGIN FND_USER “john.cena”
OWNER = “APPSMGR”
LAST_UPDATE_DATE = “2014/01/06”
START_DATE = “1951/01/01”

In case you are doing in other instance transfer the to other instance using scp or some other command.

STEP 3: Use FNDLOAD to upload new user to target instance:

FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct  user_metadata.ldt  FND_USER   USER_NAME=john.cena

STEP 4: Change the password of the new user from application front end,email and other details as required.

No comments :

Post a Comment