When you disable a Crystal Enterprise server, you prevent it from receiving and responding to new Crystal Enterprise requests, but you do not actually stop the server process. This is especially useful when you want to allow a server to finish processing all of its current requests before you stop it completely.
For example, you may want to stop a Report Job Server before rebooting the machine it is running on. However, you want to allow the server to fulfill any outstanding report requests that are in its queue. First, you disable the Report Job Server so it cannot accept any additional requests. Next, go to the Crystal Management Console to monitor when the server completes the jobs it has in progress. (From the Servers management area, choose the server name and then the metrics tab). Then, once it has finished processing current requests, you can safely stop the server.
Note: The CMS must be running in order for you to enable and/or disable other servers.
The icon associated with each server identifies its status. In this example, the Event Server is disabled (but not stopped), and the remaining servers are running and enabled.
The Enable/Disable Servers dialog box appears.
This dialog box lists all of the Crystal Enterprise servers that are registered with your CMS, including servers running on remote machines. By default, servers running on remote machines are displayed as MACHINE.servertype. So, in this example, LCONNORS02.eventserver
is an Event Server running on a remote machine called LCONNORS02
. The server named Input
is the Input File Repository Server running on the local machine. In this example, all of the listed servers are currently enabled.
This example disables all servers running on LCONNORS02
.
Use the ccm.sh
script. For reference, see ccm.sh.
Crystal Decisions http://www.crystaldecisions.com/ Support services http://support.crystaldecisions.com/ |