The WAS graphical programs which every WAS Administrator should know.
This is the Administrative Gui for WAS 5.0. If you are running the default instance of a default setup of WAS on your local computer, you can access the Admin Console by using a browser to go to http://localhost:9090/admin.
In general, go to /admin on the host name, with the Administrative HTTP port.
Normally, you can use any username to gain access. If global security is turned on, you may need to enter a valid local OS account username and password, or a username and password from some LDAP database.
Most of the data displayed is cached. If you want to see changes made by other Administrators using Admin Consoles or wsadmin, you have to use the Logoff menu item then log back in again.
See the Deployment section below.
IBM likes to call this AAT (stands for Application Assembly Tool). Run it like
assembly.sh > /dev/null 2>&1 &
since the program isn't smart enough to go into the background by itself.
Notice that the stderr and stdout output are thrown away.
Unlike IWS's deploytool, I don't know of any problems with assembly.sh where
stderr output is needed for troubleshooting.
The validation feature is moderately useful. It misses many obvious errors which will get caught during deployment. It constantly reports an internal error and says to see the log file (there is no log file).
It is usually easier to use the JTree in the left pane to add/remove items (usually by right-clicking and picking "Add something" or "New").
When asked for "Module Visibility", choose "COMPATIBILITY".