Tivoli Workload Automation, Version 8.6

switcheventprocessor

Switches the event processing server from the master domain manager to the backup master or vice versa.

Note that you can run the event processing server also on a workstation installed as a backup master that runs as a plain fault-tolerant agent.

Syntax

{switcheventprocessor | switchevtp} workstation

Arguments

workstation
Specifies the name of the master domain manager or of the backup master where you want to switch the event processing server. Wildcard characters are not permitted.

Comments

If you issue the command from a workstation other than the one where the event processor is configured, the command uses the command-line client, so the user credentials for the command-line client must be set correctly.

In case of backup masters the workstation must have the full-status attribute set to on.

Permission to start and stop actions on cpu objects is required in the security file to be enabled to run this command.

The correlation state of pending correlation rule instances is lost whenever the server is switched off or migrated. If caching of received events is enabled in the configuration file of the EIF listener, the cached events are lost after the event processor is switched.

Important:
  • Before running this command, run planman deploy as a precaution. Do this to make sure that your latest changes or additions to active event rules are deployed before the event processor is switched and so avoid the risk that, because of a time mismatch, the latest updates (sent automatically based on the setup of the deploymentFrequency global option) are received by the old event processor instead of the new one.
  • The master and backup masters designated to run the event processor should have their clocks synchronized at all times to avoid inconsistencies in the calculation of the time interval of running event rules. In fact, if the event processor is switched to a not-synchronized computer, timeout actions in the process of being triggered might undergo unexpected delays. Use a Network Time Protocol (NTP) server to keep all clocks synchronized.

See also

In the Tivoli® Dynamic Workload Console:
  1. Click Tivoli Workload Scheduler→Scheduling Environment→Monitor→Monitor Workstations
  2. Select All Workstations in plan or another predefined task name
  3. Choose an engine name, or specify connection properties, and click OK
  4. Select a workstation and click More Actions→Become Event Processor.