Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 1 Controlling the iProcess Engine : Stopping iProcess Engine

Stopping iProcess Engine
The following sections explain how to stop the Windows (see below) and UNIX versions (see UNIX Version) of the iProcess Engine.
Windows Version
The iProcess Engine functions are provided by the iProcess nodename Process Sentinels service (where nodename is the name of your iProcess Engine installation).
You can stop the Process Sentinels service either:
Using the swstop.bat script located in the SWDIR\bin directory. For more information, see Using the swstop.bat Script.
Manually Stopping the iProcess Engine
To stop iProcess Engine:
1.
2.
From the Start menu, select Settings > Control Panel.
3.
Double-click the Administration Tools item.
4.
Double-click the Services item.The Services dialog appears.
5.
Select the iProcess Nodename Process Sentinels service item (where Nodename is the name of your iProcess Engine installation).
6.
Click the Stop button. This will stop the Process Sentinels service and the iProcess Engine server processes.
Using the swstop.bat Script
To stop iProcess Engine using the swstop.bat script located in the SWDIR\bin directory:
1.
2.
swstop
3.
swstop -p
UNIX Version
To stop iProcess Engine you must:
1.
2.
Stopping the Server Processes
Use the swstop script, which is located in the $SWDIR/bin directory to stop all the required server processes.
To stop the iProcess Engine server processes:
1.
2.
3.
Locate the SWDIR\bin directory, and enter the following command:
swstop
A summary of the shutdown process is displayed as the processes are stopped. The example is shown below.

 
 

 
 
Stopping Process Sentinels
You can also use the swstop script, which is located in the SWDIR\bin directory, to stop Process Sentinels.
To stop the Process Sentinels:
1.
2.
3.
Locate the SWDIR\bin directory, and enter the following command:
swstop -p
which displays the following message:
   Please wait, stopping process sentinels.
Forcing the iProcess Engine to Shutdown
Normally, when you want to shut down iProcess Engine, you must first get all users to log out of iProcess Suite.
However, you can force iProcess Engine to shut down, even if there are users logged in. There are two ways you can do this:
Using the swstop command from a command prompt. See below.
Using the swstop command from the Services dialog. For more information, see Enable Forced Shutdown from the Services Dialog.
Using the swstop Command
You can use the following command to force the iProcess Engine to shut down:
SWDIR\bin\swstop [-f [timeout]]
where:
-f issues a forced shutdown event to shutdown the iProcess Engine processes, whether or not there are users logged in.
timeout is the period, in seconds, to wait before shutting down iProcess Engine. If timeout is omitted, a default timeout value of 300 (5 minutes) is used. If a subsequent swstop -f timeout command is issued before the first timeout value has expired, the timeout will be reset to the new value if the new timeout value is smaller. You cannot increase the timeout period - a larger timeout value will be ignored.
Note that:
For example:
swstop -f
swstop -f 180
swstop -f 30
Enable Forced Shutdown from the Services Dialog
To force iProcess Engine to shut down from the Services dialog, you must:
Create a new string value called SERVICE_STOP_PARAMS in the Windows Registry and enter the swstop command as the string value data. For more information, see Creating the SERVICE_STOP_PARAMS String Value.
Once you have created the SERVICE_STOP_PARAMS string value, when you stop Process Sentinels from the Services dialog, the Process Sentinels are shut down using the swstop command with the parameters you specified. For more information, see Manually Stopping the iProcess Engine for more information.
To disable the forced shutdown from the Services dialog, either:
Delete the SERVICE_STOP_PARAMS string value from the Windows Registry, or
Delete the value data from the SERVICE_STOP_PARAMS string value in the Windows Registry.
Creating the SERVICE_STOP_PARAMS String Value
To create the SERVICE_STOP_PARAMS string value:
1.
From the Start menu, click the Run button. The Run dialog appears.
2.
In the Open: field, type regedit, and click the OK button. The Registry Editor window appears.
3.
Navigate to the registry list where the SERVICE_STOP_PARAMS string value is to be located, at:
   RegistryLocation\Staffware plc\Staffware Server\Nodes\nodename
where:
RegistryLocation is either \HKEY_LOCAL_MACHINE\SOFTWARE, if you are running the iProcess Engine on a 32-bit machine, or \HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node, if you are using a 64-bit machine.
nodename is the name of the iProcess Engine installation.
4.
From the Edit menu, select New > String Value. A new value named New Value #1 is created.
5.
Right-click the New Value #1 item and click the Rename button. Rename the New Value #1 item to the SERVICE_STOP_PARAMS item.
6.
Right-click the SERVICE_STOP_PARAMS item and click the Modify button. The Edit String dialog appears.
7.
swstop [-f [timeout]] [-n retries]
where:
-f issues a forced shutdown event to shutdown the iProcess Engine processes, whether or not there are users logged in.
timeout (optional) is the period, in seconds, to wait before shutting down the iProcess Engine. If timeout is omitted, a default timeout value of 300 seconds (5 minutes) is used. The timeout value can be a numeric value between 0 - 7200. If a value less than 0 is entered, the default value of 300 seconds (5 minutes) is used. If a value greater than 7200 is entered, the value of 7200 seconds is used.
-n retries (optional) is the maximum number of times the forced shutdown command will be retried, if required. The retries value can be a numeric value of 0 or greater. The re-issue of the forced shutdown command occurs if any of the processes have not shutdown. This overcomes the problem of an event being lost in the event system and the process not receiving the shutdown message.
If all the processes have still not completely shutdown after the number of retries then a final forced shutdown is issued.
If retries is omitted, (or if a value of less than 0 is entered), a default value of 0 is used. This means that a forced shutdown is issued after the timeout period and is not re-tried. Any processes that have not shutdown are forced to shutdown.
If all the processes have still not completely shutdown after the final forced shutdown is issued because, for example, a process has hung, then these processes will have to be shutdown manually through the Task Manager or by restarting the machine that is hosting iProcess Engine.
Note that:

 
Could not stop the iProcess nodename Process Sentinels service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion

 
where nodename is the name of your iProcess Engine installation. This is a warning only. Click the OK button, Process Sentinels continue to shutdown.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved