Starting, stopping, and restarting servers are common actions that you perform when you configure servers or take them offline for other reasons. The remainder of this section tells you when a certain configuration change requires that you first stop or restart the server. However, because these tasks appear frequently, the concepts and differences are explained first, and the general procedures are provided for reference.
For example, if you want to change the name of a CMS, or if you want to configure the WCS to support NT Single Sign On, then you must first stop the server. Once you have made your changes, you start the server again to effect your changes.
Tip: When you stop (or restart) a server, you terminate the server's process, thereby stopping the server completely. If you want to prevent a server from receiving requests without actually stopping the server process, you can also enable and disable servers. We recommend that you disable Report Job Servers and Program Job Servers before stopping them so that they can finish processing any jobs they have in progress before stopping. For details, see Enabling and disabling servers.
Note: You cannot stop the CMS or the WCS over the Web. You must use the CCM instead. See Stopping a Crystal Management Server for more information.
A list of servers appears. The icon associated with each server identifies its status:
In this example, the Page Server is stopped, and the remaining servers are running and enabled.
You may be prompted for network credentials that allow you to start and stop services running on the remote machine.
Toolbar Icon | Action |
---|---|
You may be prompted for network credentials that allow you to start and stop services running on the remote machine.
The CCM performs the action and refreshes the list of servers.
Use the ccm.sh
script. For reference, see ccm.sh.
Crystal Decisions http://www.crystaldecisions.com/ Support services http://support.crystaldecisions.com/ |