Activating, Deactivating and Terminating Client Processes During a Simulation

Once you have started a distributed processing simulation, you can choose to activate an inactive Client process (e.g., if a machine becomes available) or deactivate a Client process that is currently active (e.g., if a user requires the machine for other work, or the machine’s performance is not sufficient).

You activate an inactive Client process by simply clicking on the Active checkbox. The Controller will automatically try to connect to the Client, and if successful, will begin to send it realizations.

You can deactivate or terminate an active Client process by clearing the Active checkbox. The Controller will redirect the realization that the Client process was working on to another Client process, and will send no additional realizations to the Client process (unless it is subsequently reactivated).

Similarly, if a Client process is terminated during a simulation (i.e., if the Client process is closed, or if the machine hosting the process is turned off or rebooted), the Controller will redirect the realization that that Client process was working on to another Client process, and will send no additional realizations to the terminated process.

Note: If an active Client process is terminated (by first deactivating the Client in the Controller and then closing the Client dialog or turning off the Client machine) and then restarted during a simulation, the Controller will not automatically reconnect to the Client process and start to use it again. To reestablish the connection, you must check the Active checkbox for that Client process in the Controller dialog.