Bill has documented a solution to this problem. Basically, he ran wsadmin in local mode--which lets wsadmin run without a running app server to connect to--and then disabled security. Pretty clever.
But wait a second: Anyone can just turn off global security? That seems like a bit of a security hole! Turns out this isn't as bad as it might seem.
When you run
wsadminin local mode, you basically get a fancy editor for modifying the WAS configuration files (a glorified Notepad or vi/emacs). Like with a text editor, you must have OS permissions to edit the files. Normally, you install WAS as root (on Unix/Linux), so the files are owned by root, so you have to be logged in as root to modify the files.
So to run and use
wsadminin local mode, you must be logged in as a user which has OS permissions to edit the configuration files, which basically means you must be logged in as root. And if you're root, you control the machine, including WAS. Therefore, this isn't really a security hole after all. Interesting, huh?