Is there a difference between using "conman stopappserver" and "stopWas.sh" to stop WebSphere on Tivoli Workload Scheduler (TWS)?   Additionally, is there any difference in using "conman startappserver" and "startWas.sh" to start WebSphere on TWS?  YES.


Use the "startappserver" and "stopappserver" to start and stop the application server and appservman.

To stop and restart the application server, for example to implement a change in the application server configuration, use the following conman commands:

stopappserver[domain!]workstation [;wait]

This command stops the application server and appservman. 
You can optionally stop the application server on a remote workstation. 
The optional ;wait parameter tells conman to suspend processing until the command reports that   both the application server and the service have stopped.

startappserver[domain!]workstation [;wait]

This command starts the application server and appservman. 
You can optionally start the application server on a remote workstation. 
The optional ;wait parameter tells conman to suspend processing until the command reports that both the application server and the service are running.

Use the startappserver and stopappserver commands to start or stop the embedded version of the WebSphere Application Server version 6.1.

These commands also stop appservman, the service that monitors and optionally restarts the application server.

**************
NOTE:  If you do not want to stop appservman, you can issue startWas or stopWas, supplying the -direct argument

The full syntax of startWas and stopWas is as follows: 

UNIX

Start the application server 

	   startWas.sh [-direct] 

Stop the application server

	   stopWas.sh -user <user_ID> -password <password> [-direct]


Windows

Start the application server 

	startWas.bat [-service <service_name>] [-options <parameters>] [-direct] 

Stop the application server 

	stopWas.bat [-service <service_name>] [-wasHome <installation_directory>] [-options <parameters>] [-direct]