|
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 administrative console. Other times, after
making configuration changes, you may wish to re-enable security without
having to start WebSphere Application Server, enable security, then stop
and start WebSphere Application Server again for security changes to 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 administrative server must still be restarted for changes to
take effect.
The script assumes the DB2 database is named "WAS" and the
install_root directory is C:\WebSphere\AppServer. Modify
the following variables in the script file to change these variables to
match your environment:
SET DB=WAS
SET WAS_HOME=C:\WebSphere\AppServer
Tool:
Suggest dragging a shortcut to wassec.bat file to desktop, then
modify the shortcut properties to pass in one of the parameters.
Invoke the script using: 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 wassec.bat
file to enable WebSphere security.
|
|
|
|
|
|
|