Many thanks for visiting my Blog..!!Please share this blog using below share buttons and leave your Comments/Feedback/Appreciations on Tab: Feedback
Share This Blog..!!

Wasadmin Password Change using security.xml file

    Wasadmin password changing options or Open websphere without prompting the password : If you forgot the password for websphere console or not able to stop services tire due to wasadmin password change. then you can follow, below option to rest your password.DK®



You can disable security by modifying the security.xml file(s).DK®
If you are running the based edition of IBM WebSphere Application Server only:
You can Change wasadmin password
cd 
/opt/IBM/InformationServer/ASBServer/bin/./AppServerAdmin.sh -was -user -password 
and restart the websphere services.

If this will not work then
There is only one security.xml file to change if you are running the base Application Server alone.
The security.xml file is located under  

WAS_install_root/profile/profile_name/config/cells/cellname

Always store a copy of the security.xml file in a temporary directory before making any changes.
To disable security:
Open the security.xml file and search for the very first occurrence of enabled="true". This is located inside the tag.
Change enabled="true" to enabled="false", then save the file.
You must restart the server for the change to take effect.
Restart WebSphere using:
cd /etc/rc2.d

./S85ISFServer stop

./S85ISFServer start

If you are running a Deployment Manager
There are two security.xml files you need to change:
WSAS_install_root/profiles/node_profile/config/cells/cellname/security.xml
WSAS_install_root/profiles/dmgr_profile/config/cells/cellname/security.xml
Always store a copy of the security.xml file in a temporary directory before making any changes.
Open each security.xml file and search for the very first occurrence of enabled="true". This is located inside the tag.
Change enabled="true" to enabled="false", then save the file.
You must restart the Deployment Manager, the nodegent and then the Application Servers, in that order.

If are receiving security errors when trying to stop the WebSphere processes, then you will need to manually stop the Java processes.

No comments:

Post a Comment

disqus