Basic WebSphere commands

Even you are not the infrastructure support guy, but you develop code for Websphere you need to know "emergency" commands for your WebSphere environment/

Several tips

Tip #1: If you install WebSphere in Windows OS, give the name of root folder without space, example "WAS".

Tip #2: Your log file is located C:\WAS\WebSphere\AppServer\profiles\AppSrv01\logs\server1 and SystemOut is a main log file.

Tip #3: If you need to install application you may use administrator console. But you can do it manually as well.

wsadmin -host serverB.host.com -port serverBRMIPortNumber -c '$AdminApp install /path/to/localfile.ear {...options...}'

Running command line tools on the Microsoft Windows Vista or later Microsoft operating system: On the Windows Vista, Windows Server 2008, and Windows 7 operating systems, you can install WebSphere Application Server as either Administrator or non-Administrator. When it is installed as Administrator, certain operations (such as those involving Windows Services) require Administrator privileges. To ensure that WebSphere Application Server command-line tools have sufficient privileges, run them with elevated administrator authority on systems that have the Windows User Account Control (UAC) Run all administrators in Admin Approval Mode policy enabled. When you run these command-line tools from a Command Prompt, run them from a Command Prompt window that is launched by performing the following actions:

Right-click a Command Prompt shortcut.

Click Run As Administrator.

When you open the Command Prompt window as Administrator, an operating-system dialog appears that asks you if you want to continue. Click Continue to proceed.

Examples of these tools are the startServer command, stopServer command, startManager command, stopManager command, startNode command, stopNode command, firststeps command, and the Profile Management Tool