Mechanizations
Mechanizations is a standard configuration interface for adding, editing and removing MySQL stored procedures that are run at a scheduled time in Oracle Communications Unified Assurance. Default mechanizations include event correlation and deleting expired events.
For information about interacting with the grid and form, see Standard Configuration Interface in Unified Assurance Concepts.
This user interface calls REST methods from the api/event/mechanizations endpoints. See REST API for Unified Assurance Core for details.
To open this interface, from the main navigation menu, select Configuration, then Events, then Processing, and then Mechanizations.
Form Fields
-
Name: The name of the mechanization.
-
Description: The description of the mechanization.
-
Time fields: When you select the following fields, menus appear where you can select values. You can alternatively enter the values manually. The menus and field values are updated to match each other as you change them. See Configuring Mechanization Times for more information and examples of how the time fields interact.
-
Minutes: The minutes when the mechanization will run. Valid values are:
-
*: Run every minute.
-
A list of comma-separated numbers from 0 to 59: Run at the specified minutes.
-
*/N: Run every N minutes, where N is a number from 0 to 59. For example, set it to */5 to run every five minutes.
-
-
Hours: The hours when the mechanization will run. Valid values are:
-
*: Run every hour.
-
A list of comma-separated numbers from 0 to 23: Run at the specified hours.
-
*/N: Run every N hours, where N is a number from 0 to 23.
-
-
Days: The day of the month when the mechanization will run. Valid values are:
-
*: Run every day.
-
A list of comma-separated numbers from 1 to 31: Run on the specified days.
-
*/N: Run every N days, where N is a number from 1 to 31.
-
-
Months: The month when the mechanization will run. Valid values are:
-
*: Run every month.
-
A list of comma-separated numbers from 1 to 12: Run on the specified months.
-
*/N: Run every N months, where N is a number from 1 to 12.
-
-
WeekDays: The day of the week when the mechanization will run. Valid values are:
-
*: Run every day of the week.
-
A list of comma-separated numbers from 0 to 7: Run on the specified days of the week. Use 0 or 7 for Sunday, 1 for Monday, 2 for Tuesday, 3 for Wednesday, 4 for Thursday, 5 for Friday, and 6 for Saturday.
-
*/N: Run every N days of the week, where N is a number from 0 to 7.
-
-
-
Status - The status of the mechanization.
-
Stored Procedure - The actual code of the mechanization. Oracle recommends using MySQL cursors to reduce the likelihood of locking the database.
Filter Clause Toolbar
-
Line numbers: Show or hide line numbers.
-
Search: Search the code.
-
Previous: Go to the previous result for the current search.
-
Next: Go to the next result for the current search.
-
Replace One: Search and replace in the code, one result at a time:
-
Enter a value to search for and press Enter.
-
Enter a value to replace the result with, and press Enter.
The first result is highlighted.
-
Click one of the following:
-
Yes: Replaces the current result and moves to the next.
-
No: Does not replace the current result and moves to the next.
-
All: Replaces all results.
-
Stop: Exits the search and replace operation. You can also click anywhere else to exit.
-
-
-
Replace All: Search and replace all in the code:
-
Enter a value to search for and press Enter.
-
Enter a value to replace the result with, and press Enter.
All results are replaced.
-
Configuring Mechanization Times
Mechanizations use a cron-like syntax to determine when the mechanization is run. The scheduled time definition has fields for minutes, hours, days, months, and days of the week. You can set each of these fields to one or more literal values in a comma-separated list, or *, which is interpreted as every. The mechanization runs when the current time elements match the mechanization's scheduled time elements.
For example:
-
Set all time periods to * (every). The mechanization runs every minute, because the current time will always match the mechanization's scheduled time.
-
Set Minutes to 30 and all other time period to * (every). The current time will match the scheduled time once every hour, at thirty minutes past the hour. The mechanization runs once every hour, at 1:30, 2:30, 3:30, and so on.
-
Set Minutes to 59, Hours to 23, Days to 7, and Months and WeekDays to *. The mechanization runs at 23:59 on the 7th of every month, regardless of the day of the week the 7th falls on.
-
Avoid creating overly-complex schedules with time criteria that very seldom match. For example, by setting Minutes to *, Hours to *, Days to 26, Months to 1, and WeekDay to 1, the mechanization will only run when January 26 falls on a Monday. This means it would have run on January 26, 2015, and then not again until January 26, 2026.