Starting and stopping the Dynamic Workload Console

To start and stop the Dynamic Workload Console or an engine, you must start and stop the application server instance it is installed on.

Embedded WebSphere Application Server on a Tivoli Integrated Portal in a Tivoli Workload Automation instance

If you installed the Dynamic Workload Console on the embedded WebSphere Application Server, you can start and stop the server as follows:

Windows operating system:

To stop: install_dir\wastools\stopWas.bat

To start: install_dir\wastools\startWas.bat

UNIX and Linux operating systems:

To stop: install_dir/wastools/stopWas.sh

To start: install_dir/wastools/startWas.sh

WebSphere Application Server on a Tivoli Integrated Portal outside a Tivoli Workload Automation instance

If you are using an external instance of WebSphere Application Server, use the following WebSphere Application Server scripts to start and stop an application server instance.

Note:

These scripts can also be used to start and stop embedded WebSphere Application Server, although it is suggested that you use the method described above.

Windows operating system:

ewas_install_dir\bin\stopServer.bat app_server
-user user_id -password user_id_pw

ewas_install_dir\bin\startServer.bat app_server

UNIX and Linux operating systems:

ewas_install_dir/bin/stopServer.sh app_server
-user user_id -password user_id_pw

/ewas_install_dir/bin/startServer.sh app_server

where:

ewas_install_dir

Is the directory where the WebSphere Application Server is installed.

|app_server

|Is the server name specified in the Tivoli Integrated Portal profile related to |the Dynamic Workload Console or to the engine. The default is server1.

user_id

Is the administrator user ID specified when installing the Dynamic Workload Console or the engine.

user_id_pw

Is the administrator user ID password specified when installing the Dynamic Workload Console or the engine.