Using Scheduled Workflows
if ((state = get('state')) != clustered) {
audit('state is ' + state + '; aborting');
return;
}
if ((state = get('peer_state')) != clustered) {
audit('peer state is ' + state + '; aborting');
return;
}
run('cd /');
run('confirm maintenance system reboot');
}
};
Using Scheduled Workflows
Workflows can be started via a timer event by setting up a schedule for them. The property
scheduled has to be added to the Workflow Object and needs to be set to true. Schedules can
either be created via the CLI once a workflow is loaded into the appliance or an array type
property named schedule can be added to the Object Workflow.
Each schedule entry consists of the following properties:
TABLE 134
Workflow Schedule Properties
Property Type Description
NAME
String Name of the schedule, system
generated
frequency
String minute,halfhour,hour,day,week,
month
day
String Specifies specific day and can be set
to: Monday, Tuesday,Wednesday,
Thursday,Friday,Saturday or Sunday.
Can be set when frequency is set to
week or month
hour
String 00-23, Specifies the hour part of the
schedule and can be specified when
the frequency is set to a day,week or
month.
minute
String 00-59, Specifies the minute part of
the schedule.
600 Oracle ZFS Storage Appliance Administration Guide, Release OS8.6.x • September 2016