Run process workflow action to perform event-driven reconciliation


Apart from running reconciliation jobs manually or by scheduling them, you can use a run process action with an active link, filter, or escalation. This is one method of performing event-driven reconciliation.

The Application-Command Reconciliation command enables you to run jobs from the command line.

You can use the command parameters to dynamically substitute datasets or qualifications as described in Dynamic dataset and qualification values in event-driven reconciliation jobs.

Use the following syntax:

Application-Command Reconciliation <action> -o "<job_name>" -l "-c
<classID> -q <qualification>"
;[...];"-w <workingDatasetName> -d
<definedDatasetName>"
;[...];

The <action> initiated by the command can be:

  • Trigger-Job — Starts the specified job.
  • Cancel-Job — Cancels the specified job if it is running.
  • Pause-Job — Pauses the specified job if it is running.
  • Resume-Job — Resumes the specified job if it is paused.

The following table describes the parameters used with the Application-Command Reconciliation command.


Application-Command Reconciliation command parameters

For example, to start a job named Merge Datasets, use the following command:


Application-Command Reconciliation Trigger-Job -o "Merge Datasets"

You can enter multiple class-qualification pairs and dataset pairs. For example, if the Merge Datasets job is defined to merge the BMC Configuration Import dataset into the BMC Asset dataset but you want to run it using the TestSource and TestTarget datasets, respectively, you would use the following command:

Application-Command Reconciliation Trigger-Job -o "Merge Datasets" -l "-w TestSource
 -d BMC Configuration Import;-w TestTarget -d BMC Asset"

Qualifications must be specified in  internal representation. To convert a qualification string into an internal representation, you can use the Application-Parse-Qual-L Run Process command.

For more information about dynamic dataset or qualification substitution, see Dynamic dataset and qualification values in event-driven reconciliation jobs. For more information about Run Process commands, see Using Run Process and $PROCESS$ commands in the  online documentation.

Note

When you start a job using a Run Process action, the Last Activity Time is neither read nor updated. This means that you cannot use this method to perform an incremental merge.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*