Deploying rules

The planman deploy command is used in event management. You can use it to manually deploy all rules that are not in draft state (the isDraft property is set to NO in their definition). The command operates as follows:
  1. Selects all event rule definitions not in draft state from the HCL Workload Automation database.
  2. Builds event rule configuration files.
  3. Deploys the configuration files to the monitoring engines running on the HCL Workload Automation agents.
The new configuration files update the event rules running on each monitoring engine in terms of:
  • New rules
  • Changed rules
  • Rules deleted or set back to draft state

You can use this command in addition to, or in replacement of, the deploymentFrequency (df) optman configuration option, which periodically checks event rule definitions for changes to deploy (see Administration Guide for details on this option).

The changes applied to the event rule definitions in the database become effective only after deployment has taken place.

The command syntax is:

planman [connection_parameters] deploy [-scratch]

where:
connection_parameters
Defines the settings to use when establishing the connection using HTTP or HTTPS through WebSphere Application Server Liberty Base to the master domain manager. For more information refer to Planman command line.
-scratch
Without this option, the command affects only the rules that have been added, changed, deleted, or set back to draft state .

With this option, the command deploys all the non-draft rules existing in the database, including the ones that are already in deployment and have not changed.

Note that the deployment time increases proportionally with the number of active rules to deploy. If you need to deploy a large number of new or changed rules, run planman deploy with this option to reduce the deployment time.

Use of this option results in a complete reset of the event processor and should be used with caution. The command may cause the loss of any rule instances in progress at the time you issue it. The typical case is a sequential rule that has been triggered and is waiting for additional events to take place: if you use the option at this time, the event rule environment is reset and the tracked events are lost.

To run this command, you need build access on the prodsked file.