Reset the WebLogic administration password (if locked or forgotten):

Previously,  discussed about changing the weblogic password of EBS WebLogic Domain  R12.2 if password is known.

Here, we are going to discuss when Reset the WebLogic administration password (if locked or forgotten):

1.Shut down all running services. Since the AdminServer password is not known, the servers cannot be stopped from the console and so must be killed as follows.

(i)Connect to the Oracle E-Business Suite instance and source the application tier environment file.


(ii)Identify the PIDs of Node Manager, AdminServer, and all running Managed
Servers:
$ ps -ef | grep "NodeManager"
$ ps -ef | grep "weblogic.Name=AdminServer"
$ ps -ef | grep "weblogic.Name=forms-c4ws_server"
$ ps -ef | grep "weblogic.Name=forms_server"
$ ps -ef | grep "weblogic.Name=oafm_server"
$ ps -ef | grep "weblogic.Name=oacore_server"


(iii)Kill all these processes, starting with Node Manager and followed by the
Managed Servers.

2. Back up these folders, and then delete them:
<EBS_DOMAIN_HOME>/security/ DefaultAuthenticatorInit.ldift
<EBS_DOMAIN_HOME>/servers/<server_name>/data/ldap
<EBS_DOMAIN_HOME>/servers/<server_name>/security/boot.properties
<EBS_DOMAIN_HOME>/servers/<server_name>/data/nodemanager/boot.properties

Where:
• <EBS_DOMAIN_HOME> is the absolute path of the EBS WebLogic domain
• <server_name> is the name of the server directory under <EBS_DOMAIN_HOME>.

If the password is not reset correctly, the backed up files and folders can be restored.

3. Set up a new environment to change the WLS AdminServer password.
(i) Start a new session and connect to the Oracle E-Business Suite instance.
(ii) Do not source the application tier environment file.
(iii) Run the following command to source the WebLogic Server domain environment:
$ cd <EBS_DOMAIN_HOME>/bin
$ source setDomainEnv.sh
(iv)Run the following commands:
$ cd <EBS_DOMAIN_HOME>/security
$ java weblogic.security.utils.AdminAccount <wls_adminuser> <wls_admin_new_password>

Where:
• <wls_adminuser> is the same as the value of context variable
s_wls_admin_user
• <wls_admin_new_password> is the new WLS AdminServer password you
wish to set.

4. Start AdminServer from the command line. You will be prompted for the WebLogic
Server username and password, so that the AdminServer boot.properties file
can be generated.
(i) Go to the EBS Domain Home:
$ cd <EBS_DOMAIN_HOME>
(ii) Start AdminServer:
$ java <s_nm_jvm_startup_properties> -Dweblogic.system.StoreBootIdentity=true -Dweblogic.Name=AdminServer weblogic.Server

Where:
• <s_nm_jvm_startup_properties> is the same as the value of context variable ss_nm_jvm_startup_properties
The above command prompts for the WebLogic Server username and password:
Enter username to boot WebLogic server:
Enter password to boot WebLogic server:
Provide the same credentials as you provided in Step 3.

5. Change the Node Manager password.
(i)Log in to the WebLogic Administration console.
(ii)Click the 'Lock & Edit' button.
(iii)In the left panel, click on the EBS Domain link.
(iv)Select the 'Security' tab
(v) Click on the 'Advanced' link.
(vi)  Edit the 'Node Manager password' field and set it to the new WebLogic Server password. The password should be same as set in Step 3.
(vii)  Edit the 'Confirm Node Manager Password' field and set it to the new WebLogic Server password. The password should be same as set in Step 3.
(viii) Save and activate the changes.

6. The first time, AdminServer has to be stopped from the Admin console. Follow
these steps:
(i) Log in to the WebLogic Administration console.
(ii) Shut down AdminServer.

7. Set up your environment to start AdminServer again. AdminServer should now be started using the normal AD script, which will also start Node Manager using the new password.
(i)Launch a new session and connect to the Oracle E-Business Suite instance.
(ii) Source the application tier environment file.
(iii) Start AdminServer with the following command:
$ $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

8. Start the Managed Servers. For the first time, all Managed Servers should be started from the WebLogic Server Admin console. This step will create boot.properties files for the respective Managed Servers. Follow these steps:
(i) Log in to the WebLogic Server Administration Console.
(ii) Start all Managed Servers, one at a time.

9. Shut down all the Managed Servers. This is so the new credentials will be picked up at the next startup. Follow these steps:
(i) Log in to the WebLogic AdminServer console.
(ii) Shut down all Managed Servers.
(iii) Shut down AdminServer.

10. Shut down Node Manager using the normal AD script.
$ $ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop

11. Copy the boot.properties file for each Managed Server. WebLogic Server native scripts use the boot.properties file. The above steps have created the boot.properties file under
<EBS_DOMAIN_HOME>/servers/<Managed Servername>/data/nodemanager, which is used by Node Manager. For each Managed Server, copy the newly-generated boot.properties file from
<EBS_DOMAIN_HOME>/servers/<Managed Servername>/data/nodemanager to <EBS_DOMAIN_HOME>/servers/<Managed Server name>/security.
The EBS WebLogic Server domain password has now been changed, and all servers can now be started using the normal AD scripts.
To start AdminServer:
$ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start
To start the Managed Servers:
$ $ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start <managed_server_name>

12. The above steps have changed the Oracle WebLogic AdminServer password on the run file system. You now need to perform an fs_clone operation, to change the WebLogic EBS Domain password on the patch file system:
(i) Launch a new session and connect to the Oracle E-Business Suite instance.
(ii)Source the application tier environment file.
(iii) Run the command:
$ adop phase=fs_clone

Change or Reset The WebLogic Administration Password In 12.2:

Changing the WebLogic administration password (if password is known):

The Oracle WebLogic Server domain EBS_domain_<SID> uses Node Manager to control the Administration Server and the managed servers. For this domain, the Node Manager and Oracle WebLogic Server Administration User passwords must be same or the AD control scripts will not work properly.

Important: If you need to change the Administration User password,you must change the Node Manager password first. If you do not do this, the WebLogic Server configuration change will not be detected and the next online patching cycle may fail.

The password-changing instructions that follow should be performed on the run file system. The password change will be automatically propagated to the patch file system during the next adop prepare phase or fs_clone operation.


Shut down all application tier services except the Admin Server:

On the primary node, run the command:
 $ <ADMIN_SCRIPTS_HOME>/adstpall.sh -skipNM -skipAdmin

 On all secondary nodes, run the command:
 $ <ADMIN_SCRIPTS_HOME>/adstpall.sh

Change the Oracle WebLogic Server Administration User password by performing the following steps as applicable.
1. Source the environment on the run file system.
2. Run the commands appropriate for your platform:

$ perl $FND_TOP/patch/115/bin/txkUpdateEBSDomain.pl -action=updateAdminPassword

start all services on all nodes using command :

$ <ADMIN_SCRIPTS_HOME>/adstrtal.sh

The above command is available only if TXK 7 is applied.

If that is not the case, the password need to changed from Console and few steps need to be performed.

Steps for Changing  the weblogic password pre TXK 7:

1)  Access Administrative console
2) Login using the current weblogic admin username and  password.
3) Select the lock and edit button and click domain
4) Click on Security TAB and then click on advanced tab
5) Provide the new password which you want to configure for weblogic admin user   in the node manager password field
6) Click on “save” and Verify settings updated successfully and then click on “Activate changes”
7) Now click on “Security Realms” and Click on “myrealm”
8)select “users and groups” and select weblogic User and then provide the new password for the weblogic user
9) Make sure the settings has been updated successfully

After this we need to edit the configuration file “boot.properties” for all managed and admin server  using text editor and update the password field with the above configured password ( new password)

a) take  backup of the below files

$FMW_HOME/user_projects/domains/EBS_domain/servers/AdminServer/security/boot.properties
$FMW_HOME/user_projects/domains/EBS_domain/servers/forms-c4ws_server1/data/nodemanager/boot.properties
$FMW_HOME/user_projects/domains/EBS_domain/servers/forms_server1/data/nodemanager/boot.properties
$FMW_HOME/user_projects/domains/EBS_domain/servers/oacore_server1/data/nodemanager/boot.properties
$FMW_HOME/user_projects/domains/EBS_domain/servers/oafm_server1/data/nodemanager/boot.properties

b) Update the password in password field and restart the application services using adstpall.sh and adstrtal.sh scripts.

Difference between R12.1 and R12.2

Difference between  R12.1 and R12.2 technology stack:


>>The most substantial difference is the inclusion of weblogic server in place of 10.1.3 Oracle home .

The 10.1.3 Application server is replaced by FMW_HOME.
The major change in R12.2 is involvement of Weblogic server to manager all the forms,oacore servers.

Replacing Oracle Containers for Java (OC4J) 10g with WebLogic Server 11g EBS 12.2 will use WebLogic Server from Fusion Middleware 11g in place of OC4J 10g as part of the release’s internal technology stack.  Other additional new Fusion Middleware 11g components used will include WebLogic JSP and UIX 11g.

>>In R12.2 we have two filesystems fs1(run filesystem) and fs2(patch filesystem), where as In R12.1.3 we only one application filesystem.


>>In 12.1.3 we have adpatch utility for patching, In R12.2.4 we have adop(online patching) utility patching.

Online Patching support via 11gR2 Edition-Based Redefinition.EBS 12.2 will use the 11gR2 Database’s Edition-Based Redefinition features to provide support for Online Patching.

>>A new “EBSenv.env” is introduced to select RUN/PATCH file system.

>>How to change apps user password in R12.2.4


All the services are started from Weblogic home.

Difference:

Replacing Oracle Containers for Java (OC4J) 10g with WebLogic Server 11g
Online Patching support via 11gR2 Edition-Based Redefinition
adpatch is replaced with adop.

Differe in R12.1 and R12.2 services:

The OPMN only manages Oracle HTTP Serve.

•        The run and patch file system, here each use a different s_port_pool.

•        In which few ports are same for both fs1 & fs2.   

    For example: s_webport, s_rpcport, s_java_object_cache_port