RunMechanizations

The Oracle Communications Unified Assurance Event Mechanizations Runner will run mechanizations (MySQL stored procedures). The default job configuration is to run this every minute, but the actual mechanizations run will depend on their own scheduling which is independent of the job.

You can run this application as a scheduled job using the Jobs UI.

Mechanizations Runner Setup

  1. Add a new Mechanization(s) or modify an existing Mechanization(s):

    Configuration -> Events -> Processing -> Mechanizations

  2. Enable the default Job, unless a specific configuration option is needed.

    Configuration -> Broker Control -> Jobs

Default Scheduled Job

The following table shows the settings for the default job. Actual values are in bold, descriptions of values are in plaintext.

Field Value
Package coreProcessing-app
Name Event Run Mechanizations
Program bin/core/processing/RunMechanizations
Arguments This field is blank. There is no default value.
Description Run Mechanization Stored Procedure in DB
Failover Type Standalone (Supported: Standalone, Primary, Redundant/Backup)
Status Disabled
Privileged This option is selected.
Minutes *
Hours *
Days *
Months *
WeekDays *

See Jobs in Unified Assurance User's Guide for general information about the settings for jobs.

See Using Application Primary/Backup Failover for more information about the different failover types.

Default Configuration

The following table shows the default configurations for the application. Actual values are in bold, descriptions of values are in plaintext.

Name Default Value Possible Values Notes
LogFile logs/EventMechRunner.log Text, 255 characters The relative path to the log file.
LogLevel ERROR OFF, FATAL, ERROR, WARN, INFO, DEBUG The logging level for the application.
ShardID 1 An integer Database shard to be used.

Best Practices

Administration Details

The following list shows the technical details you will need for advanced administration of the application: