® Application Server involves starting and stopping other server components such as the Deployment Manager and the node agent. Unless your LDAP directory runs on
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 components, 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 machine or on multiple machines that are not clustered.
Starting and stopping the Deployment Manager
The Deployment Manager manages the Sametime System Console and all Sametime Server cells.
Starting the Sametime System Console
When started, the Sametime System Console runs as a task in the WebSphere
Application Server administrative console.
Logging in to the console
Use the Sametime
System Console and its underlying WebSphere
Application Server Integrated Solutions Console to prepare for server installations and configure and administer servers running on WebSphere
Application Server after installation.
Running Sametime as services on Linux or Windows
Newly installed Sametime servers running on WebSphere Application Server on Linux or Microsoft Windows can be started from the Services panel. When install completes, verify that services are created properly and for Windows, that dependencies are set to avoid problems when the system restarts.
Starting and stopping WebSphere Application Servers on Windows
Use the Start Programs menu in Microsoft
® to start or stop any Sametime
servers running on WebSphere
Command reference for starting and stopping servers
You may use a command window to start and stop Sametime
components running on WebSphere
Application Server. To stop servers, you will supply the WebSphere
Application Server administrator password that was established when you installed the server.