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.

This entry was posted on Thursday, January 28th, 2010 at 9:14 am and is filed under Administration. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.