EBS 12.2 : How to set Admin Password of an EBS WebLogic Domain is lost OR forgotten

0 Comments

5
(1)

EBS 12.2 : How to set Admin Password of an EBS WebLogic Domain is lost OR forgotten


Taken from Oracle E-Business Suite Setup Guide  Part No. E22953-31. January 2020 … Fundamental Oracle E-Business Suite Setup Tasks 1-11 … Oracle WebLogic Server 11g Administration Console.


AS we know EBS WebLogic Domain uses Node Manager to control the startup of the AdminServer and Managed Servers. For the EBS WebLogic domain, the Node Manager and WebLogic AdminServer passwords must be the same. In some, if situation if we lost or forget the password then we will not able to start-stop the WebLogic console manual or using AD scripts.



We can follow the below steps to reset the password if we don’t know the password or somehow we lost it.


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.


1A. Connect to the Oracle E-Business Suite instance and source the application tier environment file.

1B. 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

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


Note: 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.


3A. Start a new session and connect to the Oracle E-Business Suite instance.

3B. Do not source the application tier environment file.

3C. Run the following command to source the WebLogic Server domain environment:

$ cd <EBS_DOMAIN_HOME>/bin
$ source setDomainEnv.sh


4. 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.


Note: Do not omit the trailing period (‘.’) in the above command: it is needed to specify the current domain directory.


5. 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.


5A. Go to the EBS Domain Home:

$ cd <EBS_DOMAIN_HOME>


5B. Start AdminServer:

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


6. Change the Node Manager password.

6A. Log in to the WebLogic Administration console.

6B. Click the ‘Lock & Edit’ button.

6C. In the left panel, click on the EBS Domain link.

6D. Select the ‘Security’ tab.

6E. Click on the ‘Advanced’ link.

6F. Edit the ‘Node Manager password’ field and set it to the new WebLogic Server.

6G. 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.


7A. Launch a new session and connect to the Oracle E-Business Suite instance.

7B. Source the application tier environment file.

7C. 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:
1. Log in to the WebLogic Server Administration Console.
2. 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:

1. Log in to the WebLogic AdminServer console.
2. Shut down all Managed Servers.
3. 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 
3-50 Oracle E-Business Suite Setup Guide
have created the boot.properties file under
<EBS_DOMAIN_HOME>/servers/<Managed Server
name>/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 Server
name>/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.


11A. To start AdminServer:

$ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start


11B. 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 a fs_clone operation, to change the WebLogic EBS Domain password on the patch file system:


12A. Launch a new session and connect to the Oracle E-Business Suite instance.

12B. Source the application tier environment file.

12C. Run the following command:

adop phase=fs_clone

This document is only for learning purpose and always validate in the LAB environment first before applying in the LIVE environment.


Hope so you like this article
!
Please share your valuable feedback/comments/subscribe and follow us below and don’t forget to click on the bell icon to get the latest update. Click here to know more about our pursuit.

 1,476 Total Views,  1 Views Today

How useful was this post?

Click on a star to rate it!

Average rating 5 / 5. Vote count: 1

No votes so far! Be the first to rate this post.

As you found this post useful...

Follow us on social media!

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Spread the Knowledge!

Leave a Reply

Your email address will not be published. Required fields are marked *

3 × two =

Open chat
1
Contact Us:
Hi,

Greetings of the day! How can we help you?

Thanks.
Team DBsGuru
Direct Call:+91-9310167776
Email: info@dbsguru.com

Share Learn Grow!


Click on the below technical group to join us to share expertise in PostgreSQL and MySQL on WhatsApp group. The purpose of this group is only help to the DBA community.

PostgreSQL Technical Group.

MySQL technical Group.

Technical Links Powered by DBsGuru.

Thanks.
Team DBsGuru.