|
| Problem | Situations in which security is enabled but something has changed such that they have no way of accessing WebSphere. | | | | Solution | This is an addendum to Technote #1000037, which only deals with DB2 database modifications. This Technote addresses how to perform the same functions with Oracle on AIX:AIX Instructions: From a UNIX command line, "su" to the oracle instance userid (Make sure all WebSphere processes are stopped). =>su - oracle (or whatever your oracle instance userid is named) Then run the following commands: oracle:>sqlplus ejsadmin/ejsadmin (or whatever userid/pw is used for db access)SQL:>update EJSADMIN.SECURITYCFG_TABLE set SECURITYENABLED=0;SQL:>exit (if it doesn't exit automatically) Before restarting, ensure security is turned off in the sas.server.props file, and that the sas.server.future file is deleted.
Return to root and restart all WebSphere processes. | |
| |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Security Operating system(s): Multi-Platform Software version: 3.5, 4.0 Reference #: 1050200 IBM Group: Software Group Modified date: 2004-08-28
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|