Starting and stopping servers running on WebSphere Application Server

Starting and stopping IBM® Sametime® servers that run on WebSphere® Application Server involves starting and stopping other server components such as the deployment manager and the node agent. Unless your LDAP directory runs on Domino®, there is no dependency between servers running on WebSphere Application Server and those that run on Domino, such as the Sametime Community server. You can use a command window to start and stop IBM Sametime components running on IBM WebSphere Application Server. To stop servers, you must supply the WebSphere Application Server administrator password that was established when you installed the server.

Sequence for starting and stopping servers

Follow this sequence when starting or stopping servers associated with a Sametime server.

Start server sequence

Start the deployment manager.
If you installed a server using a cell profile, the deployment manager is installed on the same computer as the Sametime server. If you installed a server as a cluster member, the deployment manager is probably on the same computer as the primary node, or on a separate computer.
Start the node agent.
Start the Sametime server.

Stop server sequence

Stop the Sametime server.
Stop the node agent.
Stop the deployment manager.
If you installed a server in a cell profile, the deployment manager is on the same computer as the Sametime server. If you installed a server in a cluster, the deployment manager is probably not on the same computer.

Where to run server commands

Open a command window on the computer where the server is installed, and navigate to the appropriate /bin directory shown in the following table.

Table 1. Server command directories
Type	Directory to run commands
Sametime System Console	`stSSC_profile_root`/bin
Sametime Meeting Server	`stM_profile_root`/bin
Sametime Proxy Server	`stP_profile_root`/bin
Sametime Media Manager	`stMS_profile_root`/bin
Sametime Gateway Server	`profile_root`/bin
Sametime Advanced Server	`stAdv_profile_root`/bin

Tip: For information about default paths, see Directory conventions.

Server commands to start and stop the deployment manager

Use these commands to start or stop the deployment manager. Navigate to the was_install_root/profiles/DeploymentManagerName/bin directory for the deployment manager you want to start.

Table 2. Start and stop commands for the deployment manager
Operating system	Commands
AIX® or Linux	./startmanager.sh ./stopManager.sh -username `admin_user` -password `admin_password`
Windows	startmanager.bat stopManager.bat -username `admin_user` -password `admin_password`

Server commands for AIX or Linux

Note: The deployment manager must be running before you start a server, and the server name is case sensitive.

Table 3. Start server commands for AIX or Linux
Type	Commands
Sametime System Console	`./startNode.sh` `./startServer.sh STConsoleServer`
Sametime Meeting Server	`./startNode.sh` `./startServer.sh STMeetingHttpProxy` `./startServer.sh STMeetingServer`
Sametime Proxy Server	`./startNode.sh` `./startServer.sh STProxyServer`
Sametime Media Manager	Linux only: `./startNode.sh` `./startServer.sh STMediaServer`
Sametime Gateway Server	`./startNode.sh` `./startServer.sh RTCGWServer`
Sametime Advanced Server	`./startNode.sh` `./startServer.sh STAdvancedServer`

Note: Stop the deployment manager last, after you have stopped the server. The server name is case sensitive.

Table 4. Stop server commands for AIX or Linux
Type	Commands
Sametime System Console	`./stopServer.sh STConsoleServer -username username -password password` `./stopNode.sh -username username -password password`
Sametime Meeting Server	`./stopServer.sh STMeetingServer -username username -password password` `./stopServer.sh STMeetingHttpProxy -username username -password password` `./stopNode.sh -username username -password password`
Sametime Proxy Server	`./stopServer.sh STProxyServer -username username -password password` `./stopNode.sh -username username -password password`
Sametime Media Manager	`./stopServer.sh STMediaServer -username username -password password` `./stopNode.sh -username username -password password`
Sametime Gateway Server	`./stopserver.sh RTCGWServer -username username -password password` `./stopNode.sh -username username -password password`
Sametime Advanced Server	`./stopServer.sh STAdvancedServer -username username -password password` `./stopNode.sh -username username -password password`

Server commands for Windows

The Start Programs menu is also a convenient way to start and stop Sametime servers running on WebSphere Application Server.

Note: The deployment manager must be running before you start a server.

Table 5. Start server commands for Windows
Server	Commands
Sametime System Console	`startNode.bat` `startServer.bat STConsoleServer`
Sametime Meeting Server	`startNode.bat` `startServer.bat STMeetingHttpProxy` `startServer.bat STMeetingServer`
Sametime Proxy Server	`startNode.bat` `startServer.bat STProxyServer`
Sametime Media Manager	`startNode.bat` `startServer.bat STMediaServer`
Sametime Gateway Server	`startNode.bat` `startServer.bat RTCGWServer`
Sametime Advanced Server	`startNode.bat` `startServer.bat STAdvancedServer`

Note: Stop the deployment manager last, after you have stopped the server.

Table 6. Stop server commands for Windows
Server	Commands
Sametime System Console	`stopServer.bat STConsoleServer -username username -password password` `stopNode.bat -username username -password password`
Sametime Meeting Server	`stopServer.bat STMeetingServer -username username -password password` `stopServer.bat STMeetingHttpProxy -username username -password password` `stopNode.bat -username username -password password`
Sametime Proxy Server	`stopServer.bat STProxyServer -username username -password password` `stopNode.bat -username username -password password`
Sametime Media Manager	`stopServer.bat STMediaServer -username username -password password` `stopNode.bat -username username -password password`
Sametime Gateway Server	`stopserver.bat RTCGWServer` `stopNode.bat -username username -password password`
Sametime Advanced Server	`stopServer.bat STAdvancedServer -username username -password password` `stopNode.bat -username username -password password`

How installing cell profiles affects starting and stopping servers
If you chose the configuration type "Cell Profile" when you installed a Sametime Proxy Server, Sametime Media Manager, or a Sametime Meeting Server, you installed a self-contained set of WebSphere Application Server components for each server. You have this configuration type if you installed different Sametime servers on the same computer or on multiple computers that are not clustered.
Starting and stopping the Sametime Video Manager
For the IBM Sametime Video Manager, the sequence for starting and stopping server components is very important.
Creating or removing a node agent service on Windows or Linux
By default, the node agent is not registered as a service when it is installed on Microsoft Windows or Linux using the Primary Node configuration profile, so you must register it manually.

Parent topic: Starting and stopping servers in a Sametime deployment