Script To Disable (or enable) WebSphere Security

Technote (FAQ)
Problem
There may be times, while testing with WebSphere security, or perhaps recreating customer problems, or any other reason, that you may need to disable security without going through the admin console.

Example, if locked out of the admin console). Other times, after making config changes, you may wish to re-enable security without having to start WAS, enable security, and recycle WAS again to have security enabling take effect.
Solution
Instead of having to update the DB2 database and modifying the sas.server.props manually, just run the attached bat file.

Note: The admin server must still be restarted for changes to take effect.

Assumes the DB2 database is named WAS and WebSphere's install directory is C:\WebSphere\AppServer. If this is not the case, modify the following variables in the bat file.


SET DB=WAS
SET WAS_HOME=C:\WebSphere\AppServer



Suggest dragging a shortcut to bat file to desktop, then modify the shortcut properties to pass in one of the parameters.
i.e. C:\wassec.bat -d

Double clicking the shortcut icon on you desktop will cause the bat file to disable WebSphere security.

Similarly, specifying -e option will cause the bat file to enable WebSphere security.












Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Security
Operating system(s): Windows 2000, Windows NT
Software version: 3.5, 4.0
Software edition: Advanced
Reference #: 1177018
IBM Group: Software Group
Modified date: 2004-08-15