If you're developing applications for WAS and you're new to it, this is what you need to know:
$install_root/profiles/$profile_name/logs/$server_name. The default profile name is AppSrv01 and the default server name is server1. Example:
/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1. SystemOut.log is the file containing everything that was logged to standard out. Logs can also be viewed from the admin console by navigating to
Troubleshooting/Logging and Tracing/server_name/Runtime.
Server/Server Types/WebSphere application servers). Otherwise you have to do it from command line. Go to
./startServer.sh server_name, e.g.,
./startServer.sh server1(this assumes that your installation has only one profile defined, otherwise you may need to "cd" to the
profile_name/bindirectory). Make sure that you run all commands using the appropriate system account. To stop the server, run
./stopServer.sh server_name -username user_name -password password. user_name and password is the credentials of an admin account, typically the same one you use to login to the console.
Applications/Application Types/WebSphere enterprise applications, click on "Install new application", select "Fast path", accept all the defaults except that on "step 2" make sure that you targeted correct servers (if you have multiple servers/clusters in your environment). Note that you can deploy a WAR file directly, you don't have to build an EAR. In this case, make sure that you set a context root on "step 4" screen of the wizard.
Applications/Application Types/WebSphere enterprise applications/application_name/Context Root For Web Modulesin the console. Re-start the application after the change.
Applications/Application Types/WebSphere enterprise applications/application_name/Manage Modules/module_nameand make the appropriate selection in the "Class loader order" drop-down (this assumes you're doing it for a WAR module).
Server/Server Types/WebSphere application servers. You'll find the host name in the Host Name column. To find a port, click on your server, and expand Ports.
WC_defaulthostis the HTTP port and
WC_defaulthost_secureis the HTTPS port.
install_root/profiles/profile_name/logs/server_name, and kill the process ID contained in the file
server_name.pid. On Unix, you can simply do
kill -9 `cat server1.pid`(assuming
server1is your server name). Use task manager or
taskkill /PIDon Windows.
Buses/Your bus name/Destinations/Your destination/Queue points/Your queue point/Runtime/Messages.
This post is part of the series on WebSphere Application Server administration. Please subscribe to our blog if you'd like to receive updates.
We offer professional services in the area of WebSphere architecture, implementation and operations. If you're looking for help with any of these tasks, please let us know.
The tips are excellent. Thanks
It’s actually a nice and helpful piece of info.
I am satisfied that you shared this helpful info with us.
Please stay us informed like this. Thanks for sharing.