I am sure this procedure can be found all over the World Wide Web. However, I need to document it for myself here so I don’t have to search for it again.
Stop the Websphere application server.
Open the command prompt (in Windows) and browse to the Websphere home\bin\ directory. Issue ‘wsadmin.bat -conntype NONE’
This willÂ come upÂ with aÂ message “WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.”, which is pretty much confirming that the wsadmin is not connected to any server process.
Once launched issue ‘securityoff’ to the wsadmin console.
Restart the Websphere application server.