The Job name space contains commands for modifying jobs created in the individual job name spaces (for example, SnapshotJob, , AuditJob, , or DeployJob, ). Using these commands, you can modify includes, add and remove schedules, and add and remove servers and groups.
When working with the Jobs name space, be aware of the following:
Variable Name | Variable Type | Description |
---|---|---|
visitor | com.bladelogic.om.infra.ast.visitor.condition.ConditionASTNodeVisitor | no description |
Variable Name | Variable Type | Description |
---|---|---|
visitor | com.bladelogic.om.infra.ast.visitor.conditionresult.ConditionResultASTNodeVisitor | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobAssetClass | com.bladelogic.om.infra.model.base.SJobAssetClass | no description |
Adds a component to the job.
<b>boolean</b> - returns true if this operation modified the job component list.Variable Name | Variable Type | Description |
---|---|---|
jobComponent | com.bladelogic.om.infra.model.base.SJobComponent | - the component to add. |
Adds a component group to this job.
<b>boolean</b> - returns true if this operation modified the job component group list.Variable Name | Variable Type | Description |
---|---|---|
group | com.bladelogic.om.infra.model.base.SJobComponentGroup | - the component group. |
Variable Name | Variable Type | Description |
---|---|---|
jobDepotObjectGroup | com.bladelogic.om.infra.model.base.SJobDepotObjectGroup | no description |
Variable Name | Variable Type | Description |
---|---|---|
x | com.bladelogic.om.infra.model.base.SJobDevice | no description |
Adds a server group to this job.
<b>boolean</b> - returns true if this operation modified the job server group list.Variable Name | Variable Type | Description |
---|---|---|
group | com.bladelogic.om.infra.model.base.SJobDeviceGroup | - the server group. |
Variable Name | Variable Type | Description |
---|---|---|
x | com.bladelogic.om.infra.model.base.SJobMasterComponent | no description |
Adds a master device to the job.
<b>boolean</b> - returns true if this operation modified the job master device list.Variable Name | Variable Type | Description |
---|---|---|
jobMasterDevice | com.bladelogic.om.infra.model.base.SJobMasterDevice | - the SJobMasterDevice object to add. |
Adds a master snapshot to the job.
<b>boolean</b> - returns true if this operation modified the job master snapshot list.Variable Name | Variable Type | Description |
---|---|---|
masterSnapshot | com.bladelogic.om.infra.model.base.SJobMasterSnapshot | - the master snapshot to add. |
Variable Name | Variable Type | Description |
---|---|---|
x | com.bladelogic.om.infra.model.base.SJobSnapshot | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobTargetJob | com.bladelogic.om.infra.model.base.SJobTargetJob | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobTargetJobGroup | com.bladelogic.om.infra.model.base.SJobTargetJobGroup | no description |
Adds a template to a job.
<b>boolean</b> - returns true if this operation modified the job template list.Variable Name | Variable Type | Description |
---|---|---|
template | com.bladelogic.om.infra.model.base.SJobTemplate | - the component template. |
Adds a template group to the job.
<b>boolean</b> - returns true if this operation modified the job template group list.Variable Name | Variable Type | Description |
---|---|---|
group | com.bladelogic.om.infra.model.base.SJobTemplateGroup | - the template group. |
Variable Name | Variable Type | Description |
---|---|---|
x | com.bladelogic.om.infra.model.notification.Notification | no description |
Adds approval to a given schedule
Variable Name | Variable Type | Description |
---|---|---|
scheduleId | Integer | id the schedule which requires approval |
approvalId | Integer | approval id |
Command | Input | Return value stored name |
---|---|---|
Job.addApprovalRequestToSchedule-api | $scheduleId$ $approvalId$ | - |
Adds approval to a given schedule
Variable Name | Variable Type | Description |
---|---|---|
scheduleId | Integer | id the schedule which requires approval |
approvalId | Integer | approval id |
This command adds a daily schedule to a job. This command is not supported when the approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a daily schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS.
This command does not send a job notification. To add a schedule that includes notifications, see the Job addDailyScheduleWithSNMPNotification or Job addDailyScheduleWithEMailNotification commands.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Daily schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
The following example shows how to add a daily run at 11:35 PM to a job:
DATE_STRING="2005-01-01 23:35:00" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addDailySchedule $JOB_KEY "$DATE_STRING"` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 2 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a daily schedule to a job and, depending on the resulting status of the job run, issues an email notification. This command is not supported if the approval is enabled for the job type
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a daily schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS.
The recipient argument identifies the receiver of the email that this command generates. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Daily schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
recipient | String | Receiver of the email notification. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
The following example shows how to add a daily run at 11:35 PM to a job. Email will be sent on success, failure, or cancel.
RECIPIENT="datacenteradmin@anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addDailyScheduleWithEMailNotification $JOB_KEY "$DATE_STRING" $RECIPIENT $NOTIFICATION_STATUS` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 1 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 2 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a daily schedule with specified priority to a job and, depending on the resulting status of the job run, issues an email notification. This command is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a daily schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS.
The recipient argument identifies the receiver of the email that this command generates. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Set priorityString to one of the following priorities:
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Daily schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
recipient | String | Receiver of the email notification. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
priorityString | String | Priority of daily schedule to be added. |
The following example shows how to add a daily run at 11:35 PM to a job. Email will be sent on success, failure, or cancel.
RECIPIENT="datacenteradmin@anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
PRIORITY_STRING="HIGH" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addDailyScheduleWithEMailNotificationAndPriority $JOB_KEY "$DATE_STRING" $RECIPIENT $NOTIFICATION_STATUS $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 1 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 2 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a daily schedule to a job. This command is not supported when approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a daily schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS. The priorityString argument sets the priority of the schedule.
Set priorityString to one of the following priorities:
This command does not send a job notification. To add a schedule that includes notifications, see the Job addDailyScheduleWithSNMPNotificationAndPriority or Job addDailyScheduleWithEMailNotificationAndPriority commands.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Daily schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
priorityString | String | Priority of daily schedule to be added. |
The following example shows how to add a HIGH priority daily run at 11:35 PM to a job:
DATE_STRING="2005-01-01 23:35:00" |
PRIORITY_STRING=HIGH |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addDailyScheduleWithPriority $JOB_KEY "$DATE_STRING" $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 2 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a daily schedule to a job and, depending on the resulting status of the job run, issues an SNMP notification.This command is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a daily schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS.
The recipient argument identifies the SNMP listener. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Daily schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
recipient | String | SNMP listener. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
The following example shows how to add a daily run at 11:35 PM to a job. An SNMP trap will be generated on success, failure, or cancel.
RECIPIENT="snmpsystem.anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addDailyScheduleWithSNMPNotification $JOB_KEY "$DATE_STRING" $RECIPIENT $NOTIFICATION_STATUS` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 3 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 2 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a daily schedule with specified priority to a job and, depending on the resulting status of the job run, issues an SNMP notification.This command is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a daily schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS.
The recipient argument identifies the SNMP listener. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Set priorityString to one of the following priorities:
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Daily schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
recipient | String | SNMP listener. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
priorityString | String | Priority of daily schedule to be added. |
The following example shows how to add a daily run at 11:35 PM to a job with HIGH Priority. An SNMP trap will be generated on success, failure, or cancel.
RECIPIENT="snmpsystem.anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
PRIORITY_STRING="HIGH" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addDailyScheduleWithSNMPNotificationAndPriority $JOB_KEY "$DATE_STRING" $RECIPIENT $NOTIFICATION_STATUS $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 3 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 2 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a daily schedule to a job in a time zone. This command is not supported when the approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a daily schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS.
For a list of valid Time Zone ids, use the Schedule listValidTimeZones command.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Daily schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
timeZoneId | String | Time zone to be used for the one-time schedule to be added. |
The following example shows how to add a daily run at 11:35 PM to a job in the UTC time zone:
DATE_STRING="2005-01-01 23:35:00" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addDailyScheduleWithTimeZone $JOB_KEY "$DATE_STRING" UTC` |
Command | Input | Return value stored name |
---|---|---|
Schedule.findTimeZoneById | $timeZoneId$ | timeZone |
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 2 | - |
JobSchedule.setRecurringTimeZone | NAMED_OBJECT=timeZone | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
key | com.bladelogic.om.infra.model.base.keys.SDepotObjectKey | no description |
depotObjectTypeId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
key | com.bladelogic.om.infra.model.base.keys.SDepotObjectKey | no description |
depotObjectTypeId | Integer | no description |
assocType | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
l | java.util.List | no description |
Variable Name | Variable Type | Description |
---|---|---|
depotObjectKey | DBKey | no description |
partId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
depotSoftware | com.bladelogic.om.infra.model.depot.DepotObject | no description |
Adds the list of devices to the job. The list should contain Integer items.
Variable Name | Variable Type | Description |
---|---|---|
deviceList | java.util.List | - the List of devices. |
This command adds an interval schedule to a job. This command is not supported if the approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
This command takes 5 arguments: DBKey of a job, a date/time formatted string indicating the start time of the first occurrence of the job, the interval in days, in hours and in minutes.
This command does not send a job notification. To add a schedule that includes notifications, see the Job addIntervalScheduleWithSNMPNotification or Job addIntervalScheduleWithEMailNotification commands.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Start date for the schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
days | Integer | Number of days in the interval. |
hours | Integer | Number of hours in the interval. |
mins | Integer | Number of minutes in the interval. |
The following example shows how to add an interval schedule every 1 day 10 hours and 12 minutes to a job, starting at 2005-01-01 23:35:00:
DATE_STRING="2005-01-01 23:35:00" |
DAYS="1" |
HOURS="10" |
MINS="12" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addIntervalSchedule $JOB_KEY "$DATE_STRING" "$DAYS" "$HOURS" "$MINS"` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setStartTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setIntervalDay | $days$ | - |
JobSchedule.setIntervalHour | $hours$ | - |
JobSchedule.setIntervalMinute | $mins$ | - |
JobSchedule.setSchedFreqTypeId | 5 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds an interval schedule to a job and, depending on the resulting status of the job run, issues an email notification.This command is not supported if the approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a start time for the schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS.
The days, hours, and mins arguments let you specify the interval in days, in hours and in minutes.
The recipient argument identifies the receiver of the email that this command generates. The statusType argument indicates the statuses for which you want to issue a notification. The possible statuses have the following values:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Start time of the schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
days | Integer | Number of days in the interval. |
hours | Integer | Number of hours in the interval. |
mins | Integer | Number of minutes in the interval. |
recipient | String | Receiver of the email notification. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
The following example shows how to add an interval schedule to a job, starting at 11:35 PM. Email will be sent on success, failure, or cancel.
RECIPIENT="datacenteradmin@anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
DAYS="1" |
HOURS="10" |
MINS="12" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addIntervalScheduleWithEMailNotification $JOB_KEY "$DATE_STRING" "$DAYS" "$HOURS" "$MINS" $RECIPIENT $NOTIFICATION_STATUS` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 1 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setStartTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setIntervalDay | $days$ | - |
JobSchedule.setIntervalHour | $hours$ | - |
JobSchedule.setIntervalMinute | $mins$ | - |
JobSchedule.setSchedFreqTypeId | 5 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds an interval schedule to a job and, depending on the resulting status of the job run, issues an SNMP notification. This command is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a start time for the schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS.
The days, hours, and mins arguments let you specify the interval in days, in hours and in minutes.
The recipient argument identifies the SNMP listener. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses have the following values:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Start time of the schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
days | Integer | Number of days in the interval. |
hours | Integer | Number of hours in the interval. |
mins | Integer | Number of minutes in the interval. |
recipient | String | SNMP listener. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
The following example shows how to add an interval schedule to a job, starting at 11:35 PM. An SNMP trap will be generated on success, failure, or cancel.
RECIPIENT="snmpsystem.anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
DAYS="1" |
HOURS="10" |
MINS="12" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addIntervalScheduleWithSNMPNotification $JOB_KEY "$DATE_STRING" "$DAYS" "$HOURS" "$MINS" $RECIPIENT $NOTIFICATION_STATUS` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 3 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setStartTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setIntervalDay | $days$ | - |
JobSchedule.setIntervalHour | $hours$ | - |
JobSchedule.setIntervalMinute | $mins$ | - |
JobSchedule.setSchedFreqTypeId | 5 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds an interval schedule in a time zone to a job. This command is not supported when the approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
This command takes 6 arguments: DBKey of a job, a date/time formatted string indicating the start time of the first occurrence of the job, the interval in days, in hours and in minutes and time zone.
For a list of valid Time Zone ids, use the Schedule listValidTimeZones command.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Start date for the schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
days | Integer | Number of days in the interval. |
hours | Integer | Number of hours in the interval. |
mins | Integer | Number of minutes in the interval. |
timeZoneId | String | Time zone to be used for the one-time schedule to be added. |
The following example shows how to add an interval schedule every 1 day 10 hours and 12 minutes to a job with time zone, starting at 2005-01-01 23:35:00:
DATE_STRING="2005-01-01 23:35:00" |
DAYS="1" |
HOURS="10" |
MINS="12" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addIntervalScheduleWithTimeZone $JOB_KEY "$DATE_STRING" "$DAYS" "$HOURS" "$MINS" UTC` |
Command | Input | Return value stored name |
---|---|---|
Schedule.findTimeZoneById | $timeZoneId$ | timeZone |
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setStartTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setIntervalDay | $days$ | - |
JobSchedule.setIntervalHour | $hours$ | - |
JobSchedule.setIntervalMinute | $mins$ | - |
JobSchedule.setSchedFreqTypeId | 5 | - |
JobSchedule.setRecurringTimeZone | NAMED_OBJECT=timeZone | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a monthly schedule to a job. This command is not supported if the approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a monthly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS. Use the dayOfMonth argument to specify the day when the job executes.
This command does not send a job notification. To add a schedule that includes notifications, see the Job addMonthlyScheduleWithSNMPNotification or Job addMonthlyScheduleWithEMailNotification commands.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Monthly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
dayOfMonth | Integer | Calendar day of the month to execute the job. |
The following example shows how to add a monthly run to a job. The job runs at 11:35 PM on the 25th day of the month.
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_MONTH=25 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addMonthlySchedule $JOB_KEY "$DATE_STRING" $DAY_OF_MONTH` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 4 | - |
JobSchedule.setSubScheduleTypeId | 0 | - |
JobSchedule.setDayOfMonth | $dayOfMonth$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a monthly schedule to a job with support for all schedule choices (specific day of a particular week of every month, particular day of every month or last day of every month). This command is not supported if the approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
There are three types of monthly schedules that are supported. The command requires specifying one of the types listed below to add appropriate schedule to the job.
The dateString argument defines a monthly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS.
Use the dayOfWeekOrMonth argument to specify the day when the job executes. For last day of month schedule (scheduleType=2) this argument gets ignored and you may specify -1 as its value. For specific day of month schedule (scheduleType=0), this specifies actual calendar day (1-31) and for specific day of a week schedule (scheduleType=1) it provides the actual day of the week based on the following scheme.
Use the weekOfMonth argument for specific day of a week schedule (scheduleType=1), to select the week in which the job will execute. Set value to -1 to execute the job in last week of every month. Please note any value entered gets ignored for all other type of schedules (scheduleType=0 or scheduleType=2).
This command does not send a job notification. To add a schedule that includes notifications, see the Job addMonthlyScheduleWithSNMPNotification or Job addMonthlyScheduleWithEMailNotification commands.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
scheduleType | Integer | Type of monthly schedule. Valid types are listed above. |
dateString | String | Monthly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
dayOfWeekOrMonth | Integer | Day of the week or month to execute the job depending on the type of schedule. Refer command description for more details as values differ based on the type. |
weekOfMonth | Integer | Specific week of the month to execute the job. Only applicable for day of week schedule and any provided value will be ignored for other types. |
The following example shows how to add a monthly run to a job. The job runs at 11:35 PM on the second Tuesday of every month.
SCHEDULE_TYPE=1 |
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_WEEK=4 |
WEEK_OF_MONTH=2 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addMonthlySchedule $JOB_KEY $SCHEDULE_TYPE "$DATE_STRING" $DAY_OF_WEEK $WEEK_OF_MONTH` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 4 | - |
JobSchedule.setSubScheduleTypeId | $scheduleType$ | - |
JobSchedule.setDayOfMonth | $dayOfWeekOrMonth$ | - |
JobSchedule.setDaysOfWeek | $dayOfWeekOrMonth$ | - |
JobSchedule.setWeekOfMonth | $weekOfMonth$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a monthly schedule to a job and, depending on the resulting status of the job run, issues an email notification. Monthly schedule with email notification is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a monthly schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS. Use the DayOfMonth argument to specify the day when the job executes.
The recipient argument identifies the receiver of the email that this command generates. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Monthly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
dayOfMonth | Integer | Calendar day of the month to execute the job. |
recipient | String | Receiver of the email notification. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
The following example shows how to add a monthly run to a job. The job runs at 11:35 PM on the 25th day of the month. Email will be sent on success, failure, or cancel.
RECIPIENT="datacenteradmin@anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_MONTH=25 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addMonthlyScheduleWithEMailNotification $JOB_KEY "$DATE_STRING" $DAY_OF_MONTH $RECIPIENT $NOTIFICATION_STATUS` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 1 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 4 | - |
JobSchedule.setSubScheduleTypeId | 0 | - |
JobSchedule.setDayOfMonth | $dayOfMonth$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a monthly schedule to a job with support for all schedule choices (specific day of a particular week of every month, particular day of every month or last day of every month) and, depending on the resulting status of the job run, issues an email notification. Monthly schedule with email notification is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
There are three types of monthly schedules that are supported. The command requires specifying one of the types listed below to add appropriate schedule to the job.
The dateString argument defines a monthly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS.
Use the dayOfWeekOrMonth argument to specify the day when the job executes. For last day of month schedule (scheduleType=2) this argument gets ignored and you may specify -1 as its value. For specific day of month schedule (scheduleType=0), this specifies actual calendar day (1-31) and for specific day of a week schedule (scheduleType=1) it provides the actual day of the week based on the following scheme.
Use the weekOfMonth argument for specific day of a week schedule (scheduleType=1), to select the week in which the job will execute. Set value to -1 to execute the job in last week of every month. Please note any value entered gets ignored for all other type of schedules (scheduleType=0 or scheduleType=2).
The recipient argument identifies the receiver of the email that this command generates. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
scheduleType | Integer | Type of monthly schedule. Valid types are listed above. |
dateString | String | Monthly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
dayOfWeekOrMonth | Integer | Day of the week or month to execute the job depending on the type of schedule. Refer command description for more details as values differ based on the type. |
weekOfMonth | Integer | Specific week of the month to execute the job. Only applicable for day of week schedule and any provided value will be ignored for other types. |
recipient | String | Receiver of the email notification. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
The following example shows how to add a monthly run to a job. The job runs at 11:35 PM on the second Tuesday of every month. Email will be sent on success, failure, or cancel.
RECIPIENT="datacenteradmin@anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
SCHEDULE_TYPE=1 |
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_WEEK=4 |
WEEK_OF_MONTH=2 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addMonthlyScheduleWithEMailNotification $JOB_KEY $SCHEDULE_TYPE "$DATE_STRING" $DAY_OF_WEEK $WEEK_OF_MONTH $RECIPIENT $NOTIFICATION_STATUS` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 1 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 4 | - |
JobSchedule.setSubScheduleTypeId | $scheduleType$ | - |
JobSchedule.setDayOfMonth | $dayOfWeekOrMonth$ | - |
JobSchedule.setDaysOfWeek | $dayOfWeekOrMonth$ | - |
JobSchedule.setWeekOfMonth | $weekOfMonth$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a monthly schedule with specified priority to a job and, depending on the resulting status of the job run, issues an email notification. Monthly schedule with email notification is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a monthly schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS. Use the DayOfMonth argument to specify the day when the job executes.
The recipient argument identifies the receiver of the email that this command generates. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Set priorityString to one of the following priorities:
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Monthly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
dayOfMonth | Integer | Calendar day of the month to execute the job. |
recipient | String | Receiver of the email notification. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
priorityString | String | Priority of monthly schedule to be added. |
The following example shows how to add a monthly run with high priority to a job. The job runs at 11:35 PM on the 25th day of the month. Email will be sent on success, failure, or cancel.
RECIPIENT="datacenteradmin@anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_MONTH=25 |
PRIORITY_STRING=HIGH |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addMonthlyScheduleWithEMailNotificationAndPriority $JOB_KEY "$DATE_STRING" $DAY_OF_MONTH $RECIPIENT $NOTIFICATION_STATUS $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 1 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 4 | - |
JobSchedule.setSubScheduleTypeId | 0 | - |
JobSchedule.setDayOfMonth | $dayOfMonth$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a monthly schedule with specified priority to a job with support for all schedule choices (specific day of a particular week of every month, particular day of every month or last day of every month) and, depending on the resulting status of the job run, issues an email notification. Monthly schedule with email notification is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
There are three types of monthly schedules that are supported. The command requires specifying one of the types listed below to add appropriate schedule to the job.
The dateString argument defines a monthly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS.
Use the dayOfWeekOrMonth argument to specify the day when the job executes. For last day of month schedule (scheduleType=2) this argument gets ignored and you may specify -1 as its value. For specific day of month schedule (scheduleType=0), this specifies actual calendar day (1-31) and for specific day of a week schedule (scheduleType=1) it provides the actual day of the week based on the following scheme.
Use the weekOfMonth argument for specific day of a week schedule (scheduleType=1), to select the week in which the job will execute. Set value to -1 to execute the job in last week of every month. Please note any value entered gets ignored for all other type of schedules (scheduleType=0 or scheduleType=2).
The recipient argument identifies the receiver of the email that this command generates. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Set priorityString to one of the following priorities:
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
scheduleType | Integer | Type of monthly schedule. Valid types are listed above. |
dateString | String | Monthly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
dayOfWeekOrMonth | Integer | Day of the week or month to execute the job depending on the type of schedule. Refer command description for more details as values differ based on the type. |
weekOfMonth | Integer | Specific week of the month to execute the job. Only applicable for day of week schedule and any provided value will be ignored for other types. |
recipient | String | Receiver of the email notification. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
priorityString | String | Priority of monthly schedule to be added. |
The following example shows how to add a monthly run with high priority to a job. The job runs at 11:35 PM on the second Tuesday of every month. Email will be sent on success, failure, or cancel.
RECIPIENT="datacenteradmin@anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
SCHEDULE_TYPE=1 |
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_WEEK=4 |
WEEK_OF_MONTH=2 |
PRIORITY_STRING=HIGH |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addMonthlyScheduleWithEMailNotificationAndPriority $JOB_KEY $SCHEDULE_TYPE "$DATE_STRING" $DAY_OF_WEEK $WEEK_OF_MONTH $RECIPIENT $NOTIFICATION_STATUS $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 1 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 4 | - |
JobSchedule.setSubScheduleTypeId | $scheduleType$ | - |
JobSchedule.setDayOfMonth | $dayOfWeekOrMonth$ | - |
JobSchedule.setDaysOfWeek | $dayOfWeekOrMonth$ | - |
JobSchedule.setWeekOfMonth | $weekOfMonth$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a monthly schedule with specified priority to a job. This command is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a monthly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS. Use the dayOfMonth argument to specify the day when the job executes.
This command does not send a job notification. To add a schedule that includes notifications, see the Job addMonthlyScheduleWithSNMPNotificationAndPriority or Job addMonthlyScheduleWithEMailNotificationAndPriority commands.
Set priorityString to one of the following priorities:
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Monthly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
dayOfMonth | Integer | Calendar day of the month to execute the job. |
priorityString | String | Priority of monthly schedule to be added. |
The following example shows how to add a monthly run with high priority to a job. The job runs at 11:35 PM on the 25th day of the month.
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_MONTH=25 |
PRIORITY_STRING=HIGH |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addMonthlyScheduleWithPriority $JOB_KEY "$DATE_STRING" $DAY_OF_MONTH $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 4 | - |
JobSchedule.setSubScheduleTypeId | 0 | - |
JobSchedule.setDayOfMonth | $dayOfMonth$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a monthly schedule to a job with support for all schedule choices (specific day of a particular week of every month, particular day of every month or last day of every month) and with specified priority to a job. This command is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
There are three types of monthly schedules that are supported. The command requires specifying one of the types listed below to add appropriate schedule to the job.
The dateString argument defines a monthly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS.
Use the dayOfWeekOrMonth argument to specify the day when the job executes. For last day of month schedule (scheduleType=2) this argument gets ignored and you may specify -1 as its value. For specific day of month schedule (scheduleType=0), this specifies actual calendar day (1-31) and for specific day of a week schedule (scheduleType=1) it provides the actual day of the week based on the following scheme.
Use the weekOfMonth argument for specific day of a week schedule (scheduleType=1), to select the week in which the job will execute. Set value to -1 to execute the job in last week of every month. Please note any value entered gets ignored for all other type of schedules (scheduleType=0 or scheduleType=2).
This command does not send a job notification. To add a schedule that includes notifications, see the Job addMonthlyScheduleWithSNMPNotificationAndPriority or Job addMonthlyScheduleWithEMailNotificationAndPriority commands.
Set priorityString to one of the following priorities:
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
scheduleType | Integer | Type of monthly schedule. Valid types are listed above. |
dateString | String | Monthly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
dayOfWeekOrMonth | Integer | Day of the week or month to execute the job depending on the type of schedule. Refer command description for more details as values differ based on the type. |
weekOfMonth | Integer | Specific week of the month to execute the job. Only applicable for day of week schedule and any provided value will be ignored for other types. |
priorityString | String | Priority of monthly schedule to be added. |
The following example shows how to add a monthly run with high priority to a job. The job runs at 11:35 PM on second Tuesday every month.
SCHEDULE_TYPE=1 |
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_WEEK=4 |
WEEK_OF_MONTH=2 |
PRIORITY_STRING=HIGH |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addMonthlyScheduleWithPriority $JOB_KEY $SCHEDULE_TYPE "$DATE_STRING" $DAY_OF_WEEK $WEEK_OF_MONTH $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 4 | - |
JobSchedule.setSubScheduleTypeId | $scheduleType$ | - |
JobSchedule.setDayOfMonth | $dayOfWeekOrMonth$ | - |
JobSchedule.setDaysOfWeek | $dayOfWeekOrMonth$ | - |
JobSchedule.setWeekOfMonth | $weekOfMonth$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a monthly schedule to a job and, depending on the resulting status of the job run, issues an SNMP notification. Monthly schedule with SNMP notification is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a monthly schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS. Use the DayOfMonth argument to specify the day when the job executes.
The recipient argument identifies the SNMP listener. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Monthly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
dayOfMonth | Integer | Calendar day of the month to execute the job. |
recipient | String | SNMP listener. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
The following example shows how to add a monthly run to a job. The job runs at 11:35 PM on the 25th day of the month. An SNMP trap will be generated on success, failure, or cancel.
RECIPIENT="snmplistener.anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_MONTH=25 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addMonthlyScheduleWithSNMPNotification $JOB_KEY "$DATE_STRING" $DAY_OF_MONTH $RECIPIENT $NOTIFICATION_STATUS` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 3 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 4 | - |
JobSchedule.setSubScheduleTypeId | 0 | - |
JobSchedule.setDayOfMonth | $dayOfMonth$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a monthly schedule to a job with support for all schedule choices (specific day of a particular week of every month, particular day of every month or last day of every month) and, depending on the resulting status of the job run, issues an SNMP notification. Monthly schedule with SNMP notification is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
There are three types of monthly schedules that are supported. The command requires specifying one of the types listed below to add appropriate schedule to the job.
The dateString argument defines a monthly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS.
Use the dayOfWeekOrMonth argument to specify the day when the job executes. For last day of month schedule (scheduleType=2) this argument gets ignored and you may specify -1 as its value. For specific day of month schedule (scheduleType=0), this specifies actual calendar day (1-31) and for specific day of a week schedule (scheduleType=1) it provides the actual day of the week based on the following scheme.
Use the weekOfMonth argument for specific day of a week schedule (scheduleType=1), to select the week in which the job will execute. Set value to -1 to execute the job in last week of every month. Please note any value entered gets ignored for all other type of schedules (scheduleType=0 or scheduleType=2).
The recipient argument identifies the SNMP listener. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
scheduleType | Integer | Type of monthly schedule. Valid types are listed above. |
dateString | String | Monthly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
dayOfWeekOrMonth | Integer | Day of the week or month to execute the job depending on the type of schedule. Refer command description for more details as values differ based on the type. |
weekOfMonth | Integer | Specific week of the month to execute the job. Only applicable for day of week schedule and any provided value will be ignored for other types. |
recipient | String | SNMP listener. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
The following example shows how to add a monthly run to a job. The job runs at 11:35 PM on second Tuesday of every month. An SNMP trap will be generated on success, failure, or cancel.
RECIPIENT="snmplistener.anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
SCHEDULE_TYPE=1 |
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_WEEK=4 |
WEEK_OF_MONTH=2 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addMonthlyScheduleWithSNMPNotification $JOB_KEY $SCHEDULE_TYPE "$DATE_STRING" $DAY_OF_ WEEK $WEEK_OF_MONTH $RECIPIENT $NOTIFICATION_STATUS` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 3 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 4 | - |
JobSchedule.setSubScheduleTypeId | $scheduleType$ | - |
JobSchedule.setDayOfMonth | $dayOfWeekOrMonth$ | - |
JobSchedule.setDaysOfWeek | $dayOfWeekOrMonth$ | - |
JobSchedule.setWeekOfMonth | $weekOfMonth$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a monthly schedule with specified priority to a job and, depending on the resulting status of the job run, issues an SNMP notification. Monthly schedule with SNMP notification is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a monthly schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS. Use the DayOfMonth argument to specify the day when the job executes.
The recipient argument identifies the SNMP listener. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Set priorityString to one of the following priorities:
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Monthly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
dayOfMonth | Integer | Calendar day of the month to execute the job. |
recipient | String | SNMP listener. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
priorityString | String | Priority of monthly schedule to be added. |
The following example shows how to add a monthly run with high priority to a job. The job runs at 11:35 PM on the 25th day of the month. An SNMP trap will be generated on success, failure, or cancel.
RECIPIENT="snmplistener.anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_MONTH=25 |
PRIORITY_STRING=HIGH |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addMonthlyScheduleWithSNMPNotificationAndPriority $JOB_KEY "$DATE_STRING" $DAY_OF_MONTH $RECIPIENT $NOTIFICATION_STATUS $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 3 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 4 | - |
JobSchedule.setSubScheduleTypeId | 0 | - |
JobSchedule.setDayOfMonth | $dayOfMonth$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a monthly schedule with specified priority to a job with support for all schedule choices (specific day of a particular week of every month, particular day of every month or last day of every month) and, depending on the resulting status of the job run, issues an SNMP notification. Monthly schedule with SNMP notification is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
There are three types of monthly schedules that are supported. The command requires specifying one of the types listed below to add appropriate schedule to the job.
The dateString argument defines a monthly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS.
Use the dayOfWeekOrMonth argument to specify the day when the job executes. For last day of month schedule (scheduleType=2) this argument gets ignored and you may specify -1 as its value. For specific day of month schedule (scheduleType=0), this specifies actual calendar day (1-31) and for specific day of a week schedule (scheduleType=1) it provides the actual day of the week based on the following scheme.
Use the weekOfMonth argument for specific day of a week schedule (scheduleType=1), to select the week in which the job will execute. Set value to -1 to execute the job in last week of every month. Please note any value entered gets ignored for all other type of schedules (scheduleType=0 or scheduleType=2).
The recipient argument identifies the SNMP listener. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Set priorityString to one of the following priorities:
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
scheduleType | Integer | Type of monthly schedule. Valid types are listed above. |
dateString | String | Monthly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
dayOfWeekOrMonth | Integer | Day of the week or month to execute the job depending on the type of schedule. Refer command description for more details as values differ based on the type. |
weekOfMonth | Integer | Specific week of the month to execute the job. Only applicable for day of week schedule and any provided value will be ignored for other types. |
recipient | String | SNMP listener. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
priorityString | String | Priority of monthly schedule to be added. |
The following example shows how to add a monthly run with high priority to a job. The job runs at 11:35 PM on second Tuesday of every month. An SNMP trap will be generated on success, failure, or cancel.
RECIPIENT="snmplistener.anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
SCHEDULE_TYPE=1 |
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_WEEK=4 |
WEEK_OF_MONTH=2 |
PRIORITY_STRING=HIGH |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addMonthlyScheduleWithSNMPNotificationAndPriority $JOB_KEY $SCHEDULE_TYPE "$DATE_STRING" $DAY_OF_WEEK $WEEK_OF_MONTH $RECIPIENT $NOTIFICATION_STATUS $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 3 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 4 | - |
JobSchedule.setSubScheduleTypeId | $scheduleType$ | - |
JobSchedule.setDayOfMonth | $dayOfWeekOrMonth$ | - |
JobSchedule.setDaysOfWeek | $dayOfWeekOrMonth$ | - |
JobSchedule.setWeekOfMonth | $weekOfMonth$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a monthly schedule to a job for a specific time zone. This command is not supported if the approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a monthly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS. Use the dayOfMonth argument to specify the day when the job executes.
For a list of valid Time Zone ids, use the Schedule listValidTimeZones command.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Monthly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
dayOfMonth | Integer | Calendar day of the month to execute the job. |
timeZoneId | String | Time zone to be used for the one-time schedule to be added. |
The following example shows how to add a monthly run to a job. The job runs at 11:35 PM on the 25th day of the month in UTC.
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_MONTH=25 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addMonthlyScheduleWithTimeZone $JOB_KEY "$DATE_STRING" $DAY_OF_MONTH UTC` |
Command | Input | Return value stored name |
---|---|---|
Schedule.findTimeZoneById | $timeZoneId$ | timeZone |
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 4 | - |
JobSchedule.setSubScheduleTypeId | 0 | - |
JobSchedule.setDayOfMonth | $dayOfMonth$ | - |
JobSchedule.setRecurringTimeZone | NAMED_OBJECT=timeZone | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
l | java.util.List | no description |
This command adds a one-time schedule to a job.If approval is enabled for the job type, use the addOneTimeScheduleWithApproval command instead.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a one-time schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS.
This command does not send a job notification. To add a schedule that includes notifications, see the Job addOneTimeScheduleWithSNMPNotification or Job addOneTimeScheduleWithEMailNotification commands.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | One-time schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
The following example shows how to add a schedule to a job for a single run on the 1st of January 2005 at 11:35 PM.
DATE_STRING="2005-01-01 23:35:00" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addOneTimeSchedule $JOB_KEY "$DATE_STRING"` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ false | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setOnceDateTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 1 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a one-time schedule to a job. The job waits until the approval is received and then runs. If the approval does not come on time, the schedule is marked as expired and the approval system closes the change ticket.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a one-time schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS.
This command does not send a job notification. To add a schedule that includes notifications, see the Job addOneTimeScheduleWithSNMPNotificationAndWithApproval or Job addOneTimeScheduleWithEMailNotificationAndWithApproval commands.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | One-time schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
approvalId | Integer | Approval ID to be attached to the job. |
The following example shows how to add a schedule to a job for a single run on the 1st of January 2005 at 11:35 PM.
DATE_STRING="2005-01-01 23:35:00" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_APPROVAL_ID=`blcli Job createApproval 2 2 "My change" 2 3 "" ""` |
JOB_KEY=`blcli Job addOneTimeScheduleWithApproval $JOB_KEY "$DATE_STRING" $JOB_APPROVAL_ID` |
Command | Input | Return value stored name |
---|---|---|
Utility.stringToDate | $dateString$ | scheduleDate |
ApprovalRequest.findById | $approvalId$ | approvalRequest |
Schedule.isApprovalRequestAlreadyUsed | $approvalId$ | - |
Job.checkApprovalAccess | NAMED_OBJECT=approvalRequest | - |
Job.findByDBKey | $jobKey$ | job |
Job.isApprovalEnabled | NAMED_OBJECT=job NAMED_OBJECT=approvalRequest | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setOnceDateTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 1 | - |
JobSchedule.setApprovalRequestAPI | NAMED_OBJECT=approvalRequest | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a one-time schedule to a job and, depending on the resulting status of the job run, issues an email notification. If approval is enabled for the job type, use the addOneTimeScheduleWithEMailNotificationAndWithApproval command instead.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a one-time schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS.
The recipient argument identifies the receiver of the email that this command generates. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | One-time schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
recipient | String | Receiver of the email notification. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
The following example shows how to add a schedule to a job for a single run on the 1st of January 2005 at 11:35 PM. Email will be sent on success, failure, or cancel.
RECIPIENT="datacenteradmin@anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addOneTimeScheduleWithEMailNotification $JOB_KEY "$DATE_STRING" $RECIPIENT $NOTIFICATION_STATUS` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ false | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 1 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setOnceDateTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 1 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a one-time schedule to a job with specified priority and, depending on the resulting status of the job run, issues an email notification. If approval is enabled for the job type, use the addOneTimeScheduleWithEMailNotificationAndWithApproval command instead.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a one-time schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS.
The recipient argument identifies the receiver of the email that this command generates. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Set priorityString to one of the following priorities:
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | One-time schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
recipient | String | Receiver of the email notification. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
priorityString | String | Priority of one-time schedule to be added. |
The following example shows how to add a schedule with high priority to a job for a single run on the 1st of January 2005 at 11:35 PM. Email will be sent on success, failure, or cancel.
RECIPIENT="datacenteradmin@anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
PRIORITY_STRING=HIGH |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addOneTimeScheduleWithEMailNotificationAndPriority $JOB_KEY "$DATE_STRING" $RECIPIENT $NOTIFICATION_STATUS $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ false | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 1 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setOnceDateTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 1 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a one-time schedule to a job. The job waits until the approval is received and then runs. Depending on the resulting status of the job run, the command issues an email notification. If the approval does not come on time, the schedule is marked as expired and the change ticket is closed by the approval system.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a one-time schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS.
The recipient argument identifies the receiver of the email that this command generates. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | One-time schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
recipient | String | Receiver of the email notification. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
approvalId | Integer | Approval ID to be attached to the job. |
The following example shows how to add a schedule to a job for a single run on the 1st of January 2005 at 11:35 PM. Email will be sent on success, failure, or cancel.
RECIPIENT="datacenteradmin@anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_APPROVAL_ID=`blcli Job createApproval 2 2 "My change" 2 3 "" ""` |
JOB_KEY=`blcli Job addOneTimeScheduleWithEMailNotificationAndWithApproval $JOB_KEY "$DATE_STRING" $RECIPIENT $NOTIFICATION_STATUS $JOB_APPROVAL_ID` |
Command | Input | Return value stored name |
---|---|---|
Utility.stringToDate | $dateString$ | scheduleDate |
ApprovalRequest.findById | $approvalId$ | approvalRequest |
Schedule.isApprovalRequestAlreadyUsed | $approvalId$ | - |
Job.checkApprovalAccess | NAMED_OBJECT=approvalRequest | - |
Job.findByDBKey | $jobKey$ | job |
Job.isApprovalEnabled | NAMED_OBJECT=job NAMED_OBJECT=approvalRequest | - |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 1 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setOnceDateTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 1 | - |
JobSchedule.setApprovalRequestAPI | NAMED_OBJECT=approvalRequest | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a one-time schedule with specified priority to a job. If approval is enabled for the job type, use the addOneTimeScheduleWithApproval command instead.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a one-time schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS.
Set priorityString to one of the following priorities:
This command does not send a job notification. To add a schedule that includes notifications, see the Job addOneTimeScheduleWithSNMPNotificationAndPriority or Job addOneTimeScheduleWithEMailNotificationAndPriority commands.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | One-time schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
priorityString | String | Priority of one-time schedule to be added. |
The following example shows how to add a schedule with high priority to a job for a single run on the 1st of January 2005 at 11:35 PM.
DATE_STRING="2005-01-01 23:35:00" |
PRIORITY_STRING=HIGH |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addOneTimeScheduleWithPriority $JOB_KEY "$DATE_STRING" $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ false | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setOnceDateTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 1 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a one-time schedule to a job and, depending on the resulting status of the job run, issues an SNMP notification. If approval is enabled for the job type, use the addOneTimeScheduleWithSNMPNotificationAndWithApproval command instead.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a one-time schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS.
The recipient argument identifies the SNMP listener. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | One-time schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
recipient | String | SNMP listener. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
The following example shows how to add a schedule to a job for a single run on the 1st of January 2005 at 11:35 PM. An SNMP trap will be generated on success, failure, or cancel.
RECIPIENT="snmplistener.anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_MONTH=25 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addOneTimeScheduleWithSNMPNotification $JOB_KEY "$DATE_STRING" $RECIPIENT $NOTIFICATION_STATUS` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ false | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 3 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setOnceDateTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 1 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a one-time schedule with specified priority to a job and, depending on the resulting status of the job run, issues an SNMP notification. If approval is enabled for the job type, use the addOneTimeScheduleWithSNMPNotificationAndWithApproval command instead.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a one-time schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS.
The recipient argument identifies the SNMP listener. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Set priorityString to one of the following priorities:
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | One-time schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
recipient | String | SNMP listener. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
priorityString | String | Priority of one-time schedule to be added. |
The following example shows how to add a schedule with high priority to a job for a single run on the 1st of January 2005 at 11:35 PM. An SNMP trap will be generated on success, failure, or cancel.
RECIPIENT="snmplistener.anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_MONTH=25 |
PRIORITY_STRING=HIGH |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addOneTimeScheduleWithSNMPNotificationAndPriority $JOB_KEY "$DATE_STRING" $RECIPIENT $NOTIFICATION_STATUS $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ false | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 3 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setOnceDateTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 1 | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a one-time schedule to a job. The job waits until the approval is received and then runs. Depending on the resulting status of the job run, the command issues an SNMP notification. If the approval does not come on time, the schedule is marked as expired and the change ticket is closed by the approval system.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a one-time schedule to be added. It must be in the format YYYY-MM-DD HH:MM:SS.
The recipient argument identifies the SNMP listener. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | One-time schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
recipient | String | SNMP listener. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
approvalId | Integer | Approval ID to be attached to the job. |
The following example shows how to add a schedule to a job for a single run on the 1st of January 2005 at 11:35 PM. An SNMP trap will be generated on success, failure, or cancel.
RECIPIENT="snmplistener.anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
DAY_OF_MONTH=25 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_APPROVAL_ID=`blcli Job createApproval 2 2 "My change" 2 3 "" ""` |
JOB_KEY=`blcli Job addOneTimeScheduleWithSNMPNotificationAndWithApproval $JOB_KEY "$DATE_STRING" $RECIPIENT $NOTIFICATION_STATUS $JOB_APPROVL_ID` |
Command | Input | Return value stored name |
---|---|---|
Utility.stringToDate | $dateString$ | scheduleDate |
ApprovalRequest.findById | $approvalId$ | approvalRequest |
Schedule.isApprovalRequestAlreadyUsed | $approvalId$ | - |
Job.checkApprovalAccess | NAMED_OBJECT=approvalRequest | - |
Job.findByDBKey | $jobKey$ | job |
Job.isApprovalEnabled | NAMED_OBJECT=job NAMED_OBJECT=approvalRequest | - |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 3 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setOnceDateTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 1 | - |
JobSchedule.setApprovalRequestAPI | NAMED_OBJECT=approvalRequest | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a one time schedule in a time zone to a job. This command is not supported when the approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a one-time schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS.
For a list of valid Time Zone ids, use the Schedule listValidTimeZones command.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | One-time schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
timeZoneId | String | Time zone to be used for the one-time schedule to be added. |
The following example shows how to add a schedule to an execution task for a single run on the 1st of January 2005 at 11:35 PM in the UTC time zone.
DATE_STRING="2005-01-01 23:35:00" |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /Workspace snapshotTest` |
JOB_KEY=`blcli Job addOneTimeScheduleWithTimeZone $JOB_KEY "$DATE_STRING" UTC` |
Command | Input | Return value stored name |
---|---|---|
Schedule.findTimeZoneById | $timeZoneId$ | timeZone |
Job.checkApprovalEnabled | $jobKey$ false | - |
Utility.stringToDateWithTimeZone | $dateString$ $timeZoneId$ | scheduleDate |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setOnceDateTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 1 | - |
JobSchedule.setRecurringTimeZone | NAMED_OBJECT=timeZone | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a permission to a job.
Returns the ACL.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | DBKey of the job. |
roleName | String | Name of the role. |
authName | String | Name of the authorization. |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | job |
BlAcl.addPermission | NAMED_OBJECT=job $roleName$ $authName$ | - |
Utility.setTargetObject | job | - |
Job.update | NAMED_OBJECT=job | - |
Job.getDBKey | no input | - |
Variable Name | Variable Type | Description |
---|---|---|
assetClassKey | DBKey | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobAssetClassList | java.util.List | no description |
Adds a component to the job by DBKey.
<b>boolean</b> - returns true if this operation modified the job component list.Variable Name | Variable Type | Description |
---|---|---|
componentKey | DBKey | - the DBKey of the component to add. |
Adds a component group to this job by DBKey.
<b>boolean</b> - returns true if this operation modified the job component group list.Variable Name | Variable Type | Description |
---|---|---|
groupKey | com.bladelogic.om.infra.model.base.keys.SBLGroupKey | - the component group DBKey. |
Adds a list of component groups to this job.
<b>boolean</b> - returns true if this operation modified the job component group list.Variable Name | Variable Type | Description |
---|---|---|
groupList | java.util.List | - the list of component groups. |
Adds a list of components to the job.
<b>boolean</b> - returns true if this operation modified the job component list.Variable Name | Variable Type | Description |
---|---|---|
jobComponentList | java.util.List | - the list of components to add. |
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
assocType | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobDepotObjectGroupList | java.util.List | no description |
Variable Name | Variable Type | Description |
---|---|---|
deviceKey | DBKey | no description |
Variable Name | Variable Type | Description |
---|---|---|
deviceId | Integer | no description |
Adds a server group to this job by SBLGroupKey.
<b>boolean</b> - returns true if this operation modified the job server group list.Variable Name | Variable Type | Description |
---|---|---|
groupKey | com.bladelogic.om.infra.model.base.keys.SBLGroupKey | - the SBLGroupKey. |
Adds a list of server groups to this job.
<b>boolean</b> - returns true if this operation modified the job server group list.Variable Name | Variable Type | Description |
---|---|---|
groupList | java.util.List | - the list of server groups. |
Variable Name | Variable Type | Description |
---|---|---|
l | java.util.List | no description |
Variable Name | Variable Type | Description |
---|---|---|
componentKey | DBKey | no description |
Variable Name | Variable Type | Description |
---|---|---|
l | java.util.List | no description |
Adds a master device to the job.
<b>boolean</b> - returns true if this operation modified the job master device list.Variable Name | Variable Type | Description |
---|---|---|
deviceKey | DBKey | - the DBKey of the master device to add. |
Adds a list of master devices to the job.
<b>boolean</b> - returns true if this operation modified the job master device list.Variable Name | Variable Type | Description |
---|---|---|
jobMasterDeviceList | java.util.List | - the List of SJobMasterDevice object to add. |
Adds a master snapshot to a job by DBKey.
<b>boolean</b> - returns true if this operation modified the job master snapshot list.Variable Name | Variable Type | Description |
---|---|---|
snapshotKey | DBKey | - the DBKey of the snapshot. |
Adds a list of master snapshots to the job.
<b>boolean</b> - returns true if this operation modified the job master snapshot list.Variable Name | Variable Type | Description |
---|---|---|
masterSnapshot | java.util.List | - the master snapshots to add. |
Variable Name | Variable Type | Description |
---|---|---|
snapshotKey | DBKey | no description |
Variable Name | Variable Type | Description |
---|---|---|
l | java.util.List | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobTargetJobGroupList | java.util.List | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobTargetJobList | java.util.List | no description |
Adds a template to the job by DBKey.
<b>boolean</b> - returns true if this operation modified the job template list.Variable Name | Variable Type | Description |
---|---|---|
templateKey | DBKey | - the DBKey of the component template. |
Adds a list of template groups to the job.
<b>boolean</b> - returns true if this operation modified the job template group list.Variable Name | Variable Type | Description |
---|---|---|
groupList | java.util.List | - the list of template groups. |
Adds a list of templates to the job.
<b>boolean</b> - returns true if this operation modified the job template list.Variable Name | Variable Type | Description |
---|---|---|
templateList | java.util.List | - the List of component templates. |
This command adds a target component gto a job.
The argument jobKey is the handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command. Use the componentKey argument to provide a handle to the component to be added.
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to be updated. |
componentKey | DBKey | Handle of the component to be added |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.addSJobComponent | $componentKey$ | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
This command is applicable for Snapshot, Audit, Compliance and Deploy jobs only.
This command adds a target component group to a job.
The argument jobKey is the handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command. Use the groupName argument to provide the fully qualified path to the target component group (for example, /WestCoast/Windows).
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to be updated. |
groupName | String | Name of the component server group. |
Command | Input | Return value stored name |
---|---|---|
ComponentGroup.groupNameToDBKey | $groupName$ | groupKey |
Job.findByDBKey | $jobKey$ | - |
Job.addSJobComponentGroup | NAMED_OBJECT=groupKey | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
This command adds a target server group to a job.
The argument jobKey is the handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command. Use the groupName argument to provide the fully qualified path to the target server group (for example, /WestCoast/Windows).
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to be updated. |
groupName | String | Name of the target server group. |
The following example shows how to add several target server groups to a job.
GROUPS=`cat groups.txt` |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
for GROUP in $GROUPS |
do |
JOB_KEY=`blcli addTargetGroup $JOB_KEY $GROUP` |
done |
Command | Input | Return value stored name |
---|---|---|
ServerGroup.groupNameToDBKey | $groupName$ | groupKey |
Job.findByDBKey | $jobKey$ | - |
Job.addSJobDeviceGroup | NAMED_OBJECT=groupKey | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
This command adds multiple target server groups to a job.
The argument jobKey is the handle to the job being modified.
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to be updated. |
groupNames | com.bladelogic.om.infra.cli.helper.StringList | Comma-separated list of the target server group names. |
The following example shows how to add server groups named serverGroup1 and serverGroup2 to a snapshot job tstSnap in job group /snapshots.
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots tstSnap` |
JOB_KEY=`blcli Job addTargetGroups $JOB_KEY serverGroup1,serverGroup2` |
Command | Input | Return value stored name |
---|---|---|
Job.addTargetGroupsByName_api | $jobKey$ $groupNames$ | job |
Job.getDBKey | no input | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
targetGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.addTargetGroupsByName-api | $jobkey$ $targetGroups$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
targetGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.addTargetGroupsByName_api-api | $jobkey$ $targetGroups$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
The following command adds a target server to a job.
The argument jobKey is the handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to be updated. |
serverName | String | Name of the target server. |
Command | Input | Return value stored name |
---|---|---|
Server.getServerDBKeyByName | $serverName$ | serverKey |
Job.findByDBKey | $jobKey$ | - |
Job.addSJobDevice | NAMED_OBJECT=serverKey | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
This command adds multiple target servers to a job.
The argument jobKey is a handle to the job you are modifying.
This command returns a handle to the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle to the job you want to update. |
serverNames | com.bladelogic.om.infra.cli.helper.StringList | List of the target server names. |
The following example shows how to add servers named engrhas21agt1 and engrhas21agt2 to a Snapshot Job called tstSnap in the job group /snapshots.
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots tstSnap` |
JOB_KEY=`blcli Job addTargetServers $JOB_KEY engrhas21agt1,engrhas21agt2` |
Command | Input | Return value stored name |
---|---|---|
Job.addTargetServersByName_api | $jobKey$ $serverNames$ | job |
Job.getDBKey | no input | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
targetServers | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.addTargetServersByName-api | $jobkey$ $targetServers$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
targetServers | com.bladelogic.om.infra.cli.helper.StringList | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServers | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.addTargetServersByName_api-api | $jobkey$ $targetServers$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServers | com.bladelogic.om.infra.cli.helper.StringList | no description |
This command adds a Template to a job. Jobs that can use this command are Discovery, Compliance, and Snapshot
The argument jobKey is the handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command. Use the templateKey argument to provide a handle to the template to be added.
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to be updated. |
templateKey | DBKey | Handle of the component to be added |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.addSJobTemplate | $templateKey$ | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
This command adds a weekly schedule to a job.This command is not supported if the approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a weekly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS. Use the daysOfWeek argument to specify a sum representing the days when the job should execute. Each day of the week has a value, as shown below:
Add values representing the days when you want the job to run. For example, if you want the job to run on Monday, Wednesday, and Friday, then daysOfWeek=42. Use the frequency argument to specify an interval in weeks for the job to run (for example, 2 means the job runs every other week).
This command does not send a job notification. To add a schedule that includes notifications, see the Job addWeeklyScheduleWithSNMPNotification or Job addWeeklyScheduleWithEMailNotification commands.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Weekly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
daysOfWeek | Integer | Days of the week when the job should execute. See above for a more detailed description. |
frequency | Integer | Interval in weeks when the job should run. |
The following example shows how to add weekly job run to a job. In the example, the job runs every three weeks at 11:35 PM on Monday, Wednesday, and Friday.
DATE_STRING="2005-01-01 23:35:00" |
DAYS_OF_WEEK=42 |
FREQUENCY=3 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addWeeklySchedule $JOB_KEY "$DATE_STRING" $DAYS_OF_WEEK $FREQUENCY` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 3 | - |
JobSchedule.setDaysOfWeek | $daysOfWeek$ | - |
JobSchedule.setFrequency | $frequency$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a weekly schedule to a job and, depending on the resulting status of the job run, issues an email notification. This command is not supported if the approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a weekly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS. Use the daysOfWeek argument to specify a sum representing the days when the job should execute. Each day of the week has a value, as shown below:
Add values representing the days when you want the job to run. For example, if you want the job to run on Monday, Wednesday, and Friday, then daysOfWeek=42. Use the frequency argument to specify an interval in weeks for the job to run (for example, 2 means the job runs every other week).
The recipient argument identifies the receiver of the email that this command generates. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Weekly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
daysOfWeek | Integer | Days of the week when the job should execute. See above for a more detailed description. |
frequency | Integer | Interval in weeks when the job should run. |
recipient | String | Receiver of the email notification. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
The following example shows how to add weekly job runs to a job. In the example, the job runs every three weeks at 11:35 PM on Sunday, Wednesday, and Friday. An email is sent on success, failure, or cancel.
RECIPIENT="datacenteradmin@anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
DAYS_OF_WEEK=41 |
FREQUENCY=3 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addWeeklyScheduleWithEMailNotification $JOB_KEY "$DATE_STRING" $DAYS_OF_WEEK $FREQUENCY $RECIPIENT $NOTIFICATION_STATUS` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 1 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 3 | - |
JobSchedule.setDaysOfWeek | $daysOfWeek$ | - |
JobSchedule.setFrequency | $frequency$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a weekly schedule with specified priority to a job and, depending on the resulting status of the job run, issues an email notification. This command is not supported if the approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a weekly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS. Use the daysOfWeek argument to specify a sum representing the days when the job should execute. Each day of the week has a value, as shown below:
Add values representing the days when you want the job to run. For example, if you want the job to run on Monday, Wednesday, and Friday, then daysOfWeek=42. Use the frequency argument to specify an interval in weeks for the job to run (for example, 2 means the job runs every other week).
The recipient argument identifies the receiver of the email that this command generates. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Set priorityString to one of the following priorities:
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Weekly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
daysOfWeek | Integer | Days of the week when the job should execute. See above for a more detailed description. |
frequency | Integer | Interval in weeks when the job should run. |
recipient | String | Receiver of the email notification. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
priorityString | String | Priority of weekly schedule to be added. |
The following example shows how to add weekly job runs with high priority to a job. In the example, the job runs every three weeks at 11:35 PM on Sunday, Wednesday, and Friday. An email is sent on success, failure, or cancel.
RECIPIENT="datacenteradmin@anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
PRIORITY_STRING=HIGH |
DAYS_OF_WEEK=41 |
FREQUENCY=3 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addWeeklyScheduleWithEMailNotificationAndPriority $JOB_KEY "$DATE_STRING" $DAYS_OF_WEEK $FREQUENCY $RECIPIENT $NOTIFICATION_STATUS $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 1 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 3 | - |
JobSchedule.setDaysOfWeek | $daysOfWeek$ | - |
JobSchedule.setFrequency | $frequency$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a weekly schedule to a job with a specified priority .This command is not supported if approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a weekly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS. Use the daysOfWeek argument to specify a sum representing the days when the job should execute. Each day of the week has a value, as shown below:
Add values representing the days when you want the job to run. For example, if you want the job to run on Monday, Wednesday, and Friday, then daysOfWeek=42. Use the frequency argument to specify an interval in weeks for the job to run (for example, 2 means the job runs every other week).
Set priorityString to one of the following priorities:
This command does not send a job notification. To add a schedule that includes notifications, see the Job addWeeklyScheduleWithSNMPNotificationAndPriority or Job addWeeklyScheduleWithEMailNotificationAndPriority commands.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Weekly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
daysOfWeek | Integer | Days of the week when the job should execute. See above for a more detailed description. |
frequency | Integer | Interval in weeks when the job should run. |
priorityString | String | Priority of weekly schedule to be added. |
The following example shows how to add weekly job run with high priority to a job. In the example, the job runs every three weeks at 11:35 PM on Monday, Wednesday, and Friday.
DATE_STRING="2005-01-01 23:35:00" |
PRIORITY_STRING=HIGH |
DAYS_OF_WEEK=42 |
FREQUENCY=3 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addWeeklyScheduleWithPriority $JOB_KEY "$DATE_STRING" $DAYS_OF_WEEK $FREQUENCY $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 3 | - |
JobSchedule.setDaysOfWeek | $daysOfWeek$ | - |
JobSchedule.setFrequency | $frequency$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a weekly schedule to a job and, depending on the resulting status of the job run, issues an SNMP notification. This command is not supported if the approval is enabled for the job type
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a weekly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS. Use the daysOfWeek argument to specify a sum representing the days when the job should execute. Each day of the week has a value, as shown below:
Add values representing the days when you want the job to run. For example, if you want the job to run on Monday, Wednesday, and Friday, then daysOfWeek=42. Use the frequency argument to specify an interval in weeks for the job to run (for example, 2 means the job runs every other week).
The recipient argument identifies the SNMP listener. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Weekly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
daysOfWeek | Integer | Days of the week when the job should execute. See above for a more detailed description. |
frequency | Integer | Interval in weeks when the job should run. |
recipient | String | SNMP listener. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
The following example shows how to add weekly job runs to a job. In the example, the job runs every three weeks at 11:35 PM on Sunday, Wednesday, and Friday. An SNMP trap is generated on success, failure, or cancel.
RECIPIENT="snmplistener.anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
DAYS_OF_WEEK=41 |
FREQUENCY=3 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addWeeklyScheduleWithSNMPNotification $JOB_KEY "$DATE_STRING" $DAYS_OF_WEEK $FREQUENCY $RECIPIENT $NOTIFICATION_STATUS` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 3 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 3 | - |
JobSchedule.setDaysOfWeek | $daysOfWeek$ | - |
JobSchedule.setFrequency | $frequency$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a weekly schedule with a specified priority to a job and, depending on the resulting status of the job run, issues an SNMP notification. This command is not supported if approval is enabled for the job type
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a weekly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS. Use the daysOfWeek argument to specify a sum representing the days when the job should execute. Each day of the week has a value, as shown below:
Add values representing the days when you want the job to run. For example, if you want the job to run on Monday, Wednesday, and Friday, then daysOfWeek=42. Use the frequency argument to specify an interval in weeks for the job to run (for example, 2 means the job runs every other week).
The recipient argument identifies the SNMP listener. The statusType argument determines the statuses for which you want to issue a notification. The possible statuses each have a value as follows:
For statusType, add the statuses for which you want to issue notifications. For example, if you want to issue notifications when the job status is Failure or Cancel, then statusType=12.
Set priorityString to one of the following priorities:
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Weekly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
daysOfWeek | Integer | Days of the week when the job should execute. See above for a more detailed description. |
frequency | Integer | Interval in weeks when the job should run. |
recipient | String | SNMP listener. |
statusType | Integer | Sum of all statuses for which you want to issue notifications. See above for a more complete description. |
priorityString | String | Priority of weekly schedule to be added. |
The following example shows how to add weekly job runs with high priority to a job. In the example, the job runs every three weeks at 11:35 PM on Sunday, Wednesday, and Friday. An SNMP trap is generated on success, failure, or cancel.
RECIPIENT="snmplistener.anundisclosedcompany.com" |
NOTIFICATION_STATUS=14 |
DATE_STRING="2005-01-01 23:35:00" |
PRIORITY_STRING=HIGH |
DAYS_OF_WEEK=41 |
FREQUENCY=3 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addWeeklyScheduleWithSNMPNotificationAndPriority $JOB_KEY "$DATE_STRING" $DAYS_OF_WEEK $FREQUENCY $RECIPIENT $NOTIFICATION_STATUS $PRIORITY_STRING` |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.stringToJobPriority | $priorityString$ | priorityEnum |
Utility.createModelObject | Notification | - |
Notification.setNotificationType | 3 | - |
Notification.setRecipient | $recipient$ | - |
Notification.setStatusTypes | $statusType$ | - |
Utility.storeTargetObject | notifier | - |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.add | NAMED_OBJECT=notifier | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setJobPriority | NAMED_OBJECT=priorityEnum | - |
JobSchedule.setSchedFreqTypeId | 3 | - |
JobSchedule.setDaysOfWeek | $daysOfWeek$ | - |
JobSchedule.setFrequency | $frequency$ | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command adds a weekly schedule to a job for a specific time zone.This command is not supported if the approval is enabled for the job type.
The argument jobKey is a handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command.
The dateString argument defines a weekly schedule to be added to the job definition. It must be in the format YYYY-MM-DD HH:MM:SS. Use the daysOfWeek argument to specify a sum representing the days when the job should execute. Each day of the week has a value, as shown below:
Add values representing the days when you want the job to run. For example, if you want the job to run on Monday, Wednesday, and Friday, then daysOfWeek=42. Use the frequency argument to specify an interval in weeks for the job to run (for example, 2 means the job runs every other week).
For a list of valid Time Zone ids, use the Schedule listValidTimeZones command.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
dateString | String | Weekly schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
daysOfWeek | Integer | Days of the week when the job should execute. See above for a more detailed description. |
frequency | Integer | Interval in weeks when the job should run. |
timeZoneId | String | Time zone to be used for the one-time schedule to be added. |
The following example shows how to add weekly job run to a job. In the example, the job runs every three weeks at 11:35 PM on Monday, Wednesday, and Friday in UTC.
DATE_STRING="2005-01-01 23:35:00" UTC |
DAYS_OF_WEEK=42 |
FREQUENCY=3 |
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots snapconfig` |
JOB_KEY=`blcli Job addWeeklySchedule $JOB_KEY "$DATE_STRING" $DAYS_OF_WEEK $FREQUENCY` |
Command | Input | Return value stored name |
---|---|---|
Schedule.findTimeZoneById | $timeZoneId$ | timeZone |
Job.checkApprovalEnabled | $jobKey$ true | - |
Utility.stringToDate | $dateString$ | scheduleDate |
Utility.createModelObject | JobSchedule | - |
JobSchedule.setJobId | $jobKey$ | - |
JobSchedule.setRecurringTime | NAMED_OBJECT=scheduleDate | - |
JobSchedule.setSchedFreqTypeId | 3 | - |
JobSchedule.setDaysOfWeek | $daysOfWeek$ | - |
JobSchedule.setFrequency | $frequency$ | - |
JobSchedule.setRecurringTimeZone | NAMED_OBJECT=timeZone | - |
Schedule.create | no input | - |
JobSchedule.getScheduleId | no input | scheduleId |
Utility.setInputAsTargetObject | $jobKey$ | - |
This command applies an ACL policy to a Job.
When an ACL policy is applied to an object, all access checks on that object will check both the permissions in its ACL along with the permissions of the associated ACL policy.
Returns the DBKey of the modified object.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Job Key. |
policyName | String | Name of the ACL policy to use. |
The following example shows how to apply the ACL policy called "Test Policy" to the Job with DB Key "Job DB Key".
Job applyAclPolicy "Job DB Key" "Test Policy" |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | objsrc |
BlAclPolicy.findByName | $policyName$ | policy |
BlAclPolicy.applyAclPolicy_api | NAMED_OBJECT=policy NAMED_OBJECT=objsrc | obj |
Utility.setTargetObject | obj | - |
Job.update | NAMED_OBJECT=obj | - |
Job.getDBKey | no input | - |
This command applies an ACL template to a job.
Returns the DBKey of the modified object.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | DBKey of the job. |
templateName | String | Name of the ACL template to use. |
replace | Boolean | Flag indicating whether or not you want to replace all ACL entries (true/false). |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | objsrc |
BlAclTemplate.findByName | $templateName$ | template |
BlAclTemplate.applyAclTemplate_api | NAMED_OBJECT=template NAMED_OBJECT=objsrc $replace$ | job |
Utility.setTargetObject | job | - |
Job.update | NAMED_OBJECT=job | - |
Job.getDBKey | no input | - |
This command is deprecated. Please consider using bulkRemoveJobPropertyValues .
This command removes property values for one or more jobs.
As input, the command requires the name of a local file. The file should be in CSV format with the following columns: Job Name, Job Group Name, Job Type Id, and Property Name. Each line in the CSV file correlates to one property value being removed from one job.
Variable Name | Variable Type | Description |
---|---|---|
fileName | String | Local file in CSV format containing property names being removed. See above for a more complete description. |
fileDir | String | Directory containing the CSV file. |
Command | Input | Return value stored name |
---|---|---|
FileTransfer.pushFileToAppServer | $fileDir$ $fileName$ | appServerFile |
Job.bulkRemoveJobPropertyVals | NAMED_OBJECT=appServerFile | - |
Variable Name | Variable Type | Description |
---|---|---|
propertyValuesFile | String | no description |
Command | Input | Return value stored name |
---|---|---|
Job.bulkRemoveJobPropertyVals-api | $propertyValuesFile$ | - |
Variable Name | Variable Type | Description |
---|---|---|
propertyValuesFile | String | no description |
charsetName | String | no description |
Command | Input | Return value stored name |
---|---|---|
Job.bulkRemoveJobPropertyVals-api | $propertyValuesFile$ $charsetName$ | - |
Variable Name | Variable Type | Description |
---|---|---|
propertyValuesFile | String | no description |
Variable Name | Variable Type | Description |
---|---|---|
propertyValuesFile | String | no description |
charsetName | String | no description |
This command removes property values for one or more jobs.
As input, the command requires the name of a local file. The file should be in CSV format with the following columns: Job Name, Job Group Name, Job Type Id, and Property Name. Each line in the CSV file correlates to one property value being removed from one job.
Variable Name | Variable Type | Description |
---|---|---|
fileName | String | Local file in CSV format containing property names being removed. See above for a more complete description. |
fileDir | String | Directory containing the CSV file. |
The following example will remove the job properties using c:\tmp\bulk.txt.
blcli Job bulkRemoveJobPropertyValues bulk.txt /c/tmp/ |
Command | Input | Return value stored name |
---|---|---|
FileTransfer.pushFileToAppServer | $fileDir$ $fileName$ | appServerFile |
Job.bulkRemoveJobPropertyVals | NAMED_OBJECT=appServerFile | - |
Variable Name | Variable Type | Description |
---|---|---|
propertyValuesFile | String | no description |
Command | Input | Return value stored name |
---|---|---|
Job.bulkSetJobPropertyVals-api | $propertyValuesFile$ | - |
Variable Name | Variable Type | Description |
---|---|---|
propertyValuesFile | String | no description |
charsetName | String | no description |
Command | Input | Return value stored name |
---|---|---|
Job.bulkSetJobPropertyVals-api | $propertyValuesFile$ $charsetName$ | - |
Variable Name | Variable Type | Description |
---|---|---|
propertyValuesFile | String | no description |
Variable Name | Variable Type | Description |
---|---|---|
propertyValuesFile | String | no description |
charsetName | String | no description |
This command sets property values for one or more jobs.
As input, the command requires the name of a local file.The file should be in a CSV format with the following columns: Job Name, Job Group Name, Job Type Id, Property Name, and Property Value. Each line in the CSV file correlates to one property value being set on one job.
Variable Name | Variable Type | Description |
---|---|---|
fileName | String | Local file in CSV format containing property values. See above for a more complete description. |
fileDir | String | Directory containing the CSV file. |
The following example will set the job properties using c:\tmp\bulk.txt.
blcli Job bulkSetJobPropertyValues bulk.txt /c/tmp/ |
Command | Input | Return value stored name |
---|---|---|
FileTransfer.pushFileToAppServer | $fileDir$ $fileName$ | appServerFile |
Job.bulkSetJobPropertyVals | NAMED_OBJECT=appServerFile | - |
Checks the approval type access for the current user
Variable Name | Variable Type | Description |
---|---|---|
approvalRequest | com.bladelogic.om.infra.model.approval.ApprovalRequestInfo | no description |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalAccess-api | $approvalRequest$ | - |
Variable Name | Variable Type | Description |
---|---|---|
requestTypeEnum | com.bladelogic.om.infra.model.approval.ApprovalRequestType | no description |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalAccess-api | $requestTypeEnum$ | - |
Checks the approval type access for the current user
Variable Name | Variable Type | Description |
---|---|---|
approvalRequest | com.bladelogic.om.infra.model.approval.ApprovalRequestInfo | no description |
Variable Name | Variable Type | Description |
---|---|---|
requestTypeEnum | com.bladelogic.om.infra.model.approval.ApprovalRequestType | no description |
Checks whether the approval is enabled . Throws exception if enabled
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
notSupported | Boolean | no description |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled-api | $jobKey$ $notSupported$ | - |
Checks whether the approval is enabled . Throws exception if enabled
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
notSupported | Boolean | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobKeys | java.util.List | no description |
Command | Input | Return value stored name |
---|---|---|
Job.checkCancelPermission-api | $jobKeys$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobKeys | java.util.List | no description |
Marks a specific ClassField as unavailable in this instantiation of the object
Variable Name | Variable Type | Description |
---|---|---|
classField | com.bladelogic.om.infra.model.typesystem.type.ClassField | no description |
Clears a specific ClassField to its default.
Variable Name | Variable Type | Description |
---|---|---|
classField | com.bladelogic.om.infra.model.typesystem.type.ClassField | no description |
Clears a specific ClassField to its default.
Variable Name | Variable Type | Description |
---|---|---|
classFieldName | String | no description |
Resets all ClassField's to their defaults.
Removes a component group by DBKey.
<b>boolean</b> - returns true if this operation modified the job component group list.Variable Name | Variable Type | Description |
---|---|---|
groupKey | com.bladelogic.om.infra.model.base.keys.SBLGroupKey | - the component group DBKey. |
Removes all component groups from the job.
<b>boolean</b> - returns true if this operation modified the job component group list.Clears the list of components for the job.
<b>boolean</b> - returns true if this operation modified the job component list.
Variable Name | Variable Type | Description |
---|---|---|
deviceKey | DBKey | no description |
Removes a server group from this job by SBLGroupKey.
<b>boolean</b> - returns true if this operation modified the job server group list.Variable Name | Variable Type | Description |
---|---|---|
groupKey | com.bladelogic.om.infra.model.base.keys.SBLGroupKey | - the SBLGroupKey. |
Removes all server groups from this job.
<b>boolean</b> - returns true if this operation modified the job server group list.
Clears the job master device list.
<b>boolean</b> - returns true if this operation modified the job master device list.Removes all master snapshots from the job.
<b>boolean</b> - returns true if this operation modified the job master snapshot list.
Removes all template groups from the job.
<b>boolean</b> - returns true if this operation modified the job template group list.Removes all templates from the job.
<b>boolean</b> - returns true if this operation modified the job template list.This command removes a target component group from a job. See clearTargetComponentGroups for a command that clears all target component groups from a job.
The argument jobKey is the handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command. Use the groupName argument to provide the fully qualified path to the target component group (for example, /WestCoast/Windows).
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to be updated. |
groupName | String | Fully qualified path to the target component group to be removed. |
Command | Input | Return value stored name |
---|---|---|
ComponentGroup.groupNameToDBKey | $groupName$ | groupKey |
Job.findByDBKey | $jobKey$ | - |
Job.clearSJobComponentGroup | NAMED_OBJECT=groupKey | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
This command clears all target component groups from a job. See clearTargetComponentGroup for a command that clears a specific target component group from a job.
The argument jobKey is the handle to the job being modified.
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to be updated. |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.clearSJobComponentGroupList | no input | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
This command clears all target components from a job.
The argument jobKey is the handle to the job being modified.
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to be updated. |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.clearSJobComponentList | no input | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
This command removes a target server group from a job. See clearTargetGroups for a command that clears all target groups from a job.
The argument jobKey is the handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command. Use the groupName argument to provide the fully qualified path to the target server group (for example, /WestCoast/Windows).
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to be updated. |
groupName | String | Fully qualified path to the target server group to be removed. |
Command | Input | Return value stored name |
---|---|---|
ServerGroup.groupNameToDBKey | $groupName$ | groupKey |
Job.findByDBKey | $jobKey$ | - |
Job.clearSJobDeviceGroup | NAMED_OBJECT=groupKey | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
This command clears all target server groups from a job. See clearTargetGroup for a command that clears a specific target group from a job.
The argument jobKey is the handle to the job being modified.
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to be updated. |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.clearSJobDeviceGroupList | no input | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
This command removes a target server from a job. See clearTargetServers for a command that clears all target servers from a job.
The argument jobKey is the handle to the job being modified.
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to be updated. |
serverName | String | Name of the target server to remove. |
Command | Input | Return value stored name |
---|---|---|
Server.getServerDBKeyByName | $serverName$ | serverKey |
Job.findByDBKey | $jobKey$ | - |
Job.clearSJobDevice | NAMED_OBJECT=serverKey | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
This command clears all target servers from a job. See clearTargetServer for a command that clears a specific target server from a job.
The argument jobKey is the handle to the job being modified.
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to be updated. |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.clearSJobDeviceList | no input | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
a deep copy of this value
This command copies a job. jobKey is a handle to the job you want to copy. copyName is the new name of the copied job. jobGroup is the fully qualified path to the destination job group. If you want the job to remain in the same group, you still need to include the jobGroup argument.
This command returns the handle of the copied job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job you want to copy. |
jobGroup | String | Fully qualified path to the destination job group. |
copyName | String | New name of the copied job. |
The following example shows how to copy a job.
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots tstSnap` |
NEW_JOB_KEY=`blcli Job copyJob $JOB_KEY /myNewJobs myCopiedJob` |
Command | Input | Return value stored name |
---|---|---|
JobGroup.groupNameToId | $jobGroup$ | groupId |
Job.findByDBKey | $jobKey$ | job |
Job.createCopy | NAMED_OBJECT=job | newJob |
Utility.setTargetObject | newJob | - |
Job.setName | $copyName$ | - |
Job.setGroupId | NAMED_OBJECT=groupId | - |
Job.create | no input | - |
Job.getDBKey | no input | - |
This command will copy a Job. jobType is the type of the job to be copied. srcGroup is the fully qualified path to the job group of the job to be copied. srcName is the name of the name of the job to be copied. dstGroup is the fully qualified path to the destination job group. If the job is to remain in the same group, this still needs to be included. dstName is the name of the new job
This command returns the handle of the copied job.Variable Name | Variable Type | Description |
---|---|---|
jobType | String | Type of the job to be copied. |
srcGroup | String | Full path of the group of the job to be copied. |
srcName | String | Name of the job to be copied. |
dstGroup | String | Full path of the group of the new job |
dstName | String | Name of the new job |
Command | Input | Return value stored name |
---|---|---|
Utility.convertModelType | $jobType$ | modelType |
JobGroup.groupNameToId | $srcGroup$ | groupId |
Job.findHeaderByTypeGroupAndName | NAMED_OBJECT=modelType NAMED_OBJECT=groupId $srcName$ | jobHeader |
SJobHeader.getDBKey | no input | jobKey |
Job.copyJob | NAMED_OBJECT=jobKey $dstGroup$ $dstName$ | - |
Variable Name | Variable Type | Description |
---|---|---|
j | com.bladelogic.om.infra.model.job.Job | no description |
Variable Name | Variable Type | Description |
---|---|---|
j | com.bladelogic.om.infra.model.job.Job | no description |
This command creates an approval request. You can add this request to a job that requires approval.
This command returns an approval ID.
Set approvalType to one of the following integers:
Set changeType to one of the following integers:
Set impactId to one of the following integers:
Set riskLevel to one of the following integers:
Variable Name | Variable Type | Description |
---|---|---|
approvalType | Integer | The approval type. See list above. |
changeType | Integer | The change type. See list above. |
comments | String | A string that appears in the change summary. If you set approvalType to 5 (Existing Approval), then the comments argument is optional - you can leave it blank "". |
impactId | Integer | The impact ID. See list above |
riskLevel | Integer | The risk level. See list above. |
changeId | String | The change ID that you got from the change management system. Required only if you set approvalType to 5 (Existing Approval). |
taskId | String | The task ID that you got from the change management system. Required only if you set approvalType to 5 (Existing Approval). |
The following example shows how to create an approval request.
JOB_APPROVAL_ID=`blcli Job createApproval 2 2 "My change" 2 3 "" ""` |
Command | Input | Return value stored name |
---|---|---|
Job.createApprovalRequest | $approvalType$ $changeType$ $comments$ $impactId$ $riskLevel$ $changeId$ $taskId$ | - |
Requests approval which can be used to link schedules and approval required jobs execution through BLCLI example: createApproval"-type <value of id> -changeType <value of id> -comments <actual string for comments> -impact <value of id> -riskLevel <value of id> -changeId <actual change id> -taskId <actual task id>" available values for type id description 1 Remedy Manual Approval 2 Remedy Automatic Approval 3 Remedy Emergency Approval 4 PreApproved changeType id description 1 Project 2 Change 3 Asset Configuration 4 Asset Management 5 Asset Lease 6 Purchase Requisition 7 Asset Maintenance comments String which will be used in the change summary impact id description 1 1-Extensive/Widespread 2 2-Significant/Large 3 3-Moderate/Limited 4 4-Minor/Localized riskLevel id description 1 Risk Level 1 2 Risk Level 2 3 Risk Level 3 4 Risk Level 4 5 Risk Level 5 changeId Change Id from the ChangeManagement System taskId Task Id from the ChangeManagement System
Variable Name | Variable Type | Description |
---|---|---|
approvalType | Integer | no description |
changeType | Integer | no description |
comments | String | no description |
impactId | Integer | no description |
riskLevel | Integer | no description |
changeId | String | no description |
taskId | String | no description |
Command | Input | Return value stored name |
---|---|---|
Job.createApprovalRequest-api | $approvalType$ $changeType$ $comments$ $impactId$ $riskLevel$ $changeId$ $taskId$ | - |
Requests approval which can be used to link schedules and approval required jobs execution through BLCLI example: createApproval"-type <value of id> -changeType <value of id> -comments <actual string for comments> -impact <value of id> -riskLevel <value of id> -changeId <actual change id> -taskId <actual task id>" available values for type id description 1 Remedy Manual Approval 2 Remedy Automatic Approval 3 Remedy Emergency Approval 4 PreApproved changeType id description 1 Project 2 Change 3 Asset Configuration 4 Asset Management 5 Asset Lease 6 Purchase Requisition 7 Asset Maintenance comments String which will be used in the change summary impact id description 1 1-Extensive/Widespread 2 2-Significant/Large 3 3-Moderate/Limited 4 4-Minor/Localized riskLevel id description 1 Risk Level 1 2 Risk Level 2 3 Risk Level 3 4 Risk Level 4 5 Risk Level 5 changeId Change Id from the ChangeManagement System taskId Task Id from the ChangeManagement System
Variable Name | Variable Type | Description |
---|---|---|
approvalType | Integer | no description |
changeType | Integer | no description |
comments | String | no description |
impactId | Integer | no description |
riskLevel | Integer | no description |
changeId | String | no description |
taskId | String | no description |
base command for copying a job.
Variable Name | Variable Type | Description |
---|---|---|
job | com.bladelogic.om.infra.model.job.Job | no description |
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
msg | com.bladelogic.om.infra.mfw.msg.BlMessage | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobType | String | No description available |
jobName | String | No description available |
groupId | Integer | No description available |
Command | Input | Return value stored name |
---|---|---|
Utility.createModelObject | $jobType$ | - |
Job.setName | $jobName$ | - |
Job.setGroupId | $groupId$ | - |
Job.create | no input | - |
Job.getDBKey | no input | - |
Creates a job Object without calling save. This will prevent errors later on from other called creates. In addition, This command should be used when creating jobs because of transactionality. If Job.createJob were used, potentially invalid job objects could be created.
jobType is the job type object eg. NSHScriptJob, SnapshotJob, AuditJob,...
jobName is the name of the job
groupId is the ID of the group into which this job will be placed.
Variable Name | Variable Type | Description |
---|---|---|
jobType | String | Type of Job |
jobName | String | No description available |
groupId | Integer | No description available |
Command | Input | Return value stored name |
---|---|---|
Utility.createModelObject | $jobType$ | - |
Job.setName | $jobName$ | - |
Job.setGroupId | $groupId$ | - |
This command executes a job and returns immediately without waiting for the job to end. If approval is enabled for the job type, use the executeWithApproval command instead.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to execute. |
Command | Input | Return value stored name |
---|---|---|
Job.execute_api | $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.execute-api | $jobId$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobId | Integer | no description |
deviceIds | java.util.List | no description |
Command | Input | Return value stored name |
---|---|---|
Job.execute-api | $jobId$ $deviceIds$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobId | Integer | no description |
deviceIds | java.util.List | no description |
This command executes a job against one or more component groups. This command returns a schedule ID, which indicates when the job is scheduled to run.
The argument jobKey is the handle to the job you want to execute. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command. Use the groupsName argument to provide one or more fully qualified paths to the target component group(s) (for example, /WestCoast/Windows). Separate groups with commas.
Note: To use this command on an Advanced Deploy Job, the Reset job on failure option must be selected for the job, so that failed job runs are automatically reset. In addition, the last job run must not be in incomplete state. If necessary, you can manually reset the job.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to execute. |
groupsName | com.bladelogic.om.infra.cli.helper.StringList | Full path(s) and name(s) of the component group(s). |
The following example executes a job against the component groups compGroup1 and compGroup2.
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots tstSnap` |
blcli Job executeAgainstComponentGroups $JOB_KEY /Components/compGroup1,/Components/compGroup2 |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstComponentGroups_api | $jobKey$ $groupsName$ | - |
This command executes a job against one or more component groups. This command blocks until a job run is created for the job, and then returns the job run key.
The argument jobKey is the handle to the job you want to execute. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command. Use the groupsName argument to provide one or more fully qualified paths to the target component group(s) (for example, /WestCoast/Windows). Separate groups with commas.
Note: To use this command on an Advanced Deploy Job, the Reset job on failure option must be selected for the job, so that failed job runs are automatically reset. In addition, the last job run must not be in incomplete state. If necessary, you can manually reset the job.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to execute. |
groupsName | com.bladelogic.om.infra.cli.helper.StringList | Full path(s) and name(s) of the component group(s). |
The following example executes a job against compGroup1 and compGroup2.
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots tstSnap` |
blcli Job executeAgainstComponentGroupsForRunID $JOB_KEY /Components/compGroup1,/Components/compGroup2 |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstComponentGroupsForRunID_api | $jobKey$ $groupsName$ | - |
JobRun.getJobRunKey | no input | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetComponentGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstComponentGroupsForRunID_api-api | $jobkey$ $targetComponentGroups$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetComponentGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetComponentGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstComponentGroups_api-api | $jobkey$ $targetComponentGroups$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetComponentGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
targetServers | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstComponents-api | $jobKey$ $targetServers$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
targetServers | com.bladelogic.om.infra.cli.helper.StringList | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServers | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstComponents_api-api | $jobkey$ $targetServers$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServers | com.bladelogic.om.infra.cli.helper.StringList | no description |
This command executes a job against its failed targets.
Use the filterType argument to specify which type of failure you want to execute against. Set filterType to one of the following integers:
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle to the job. |
filterType | Integer | The failure level of the targets you want to execute against. |
The following example shows how to execute a job against its failed targets.
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /tasks tstJob` |
blcli Job executeAgainstFailedTarget $JOB_KEY 1 |
Command | Input | Return value stored name |
---|---|---|
JobRun.findLastRunKeyByJobKey | $jobKey$ true | jobRunDBKey |
JobRun.jobRunKeyToJobRunId | NAMED_OBJECT=jobRunDBKey | jobRunId |
Job.executeAgainstFailedTarget_api | $jobKey$ $filterType$ NAMED_OBJECT=jobRunId | - |
this API is for CLI call Execute job against failed target from a specific jobRun
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
filterType | Integer | 1-All 2-error 3-warning |
jobRunId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstFailedTarget_api-api | $jobKey$ $filterType$ $jobRunId$ | - |
this API is for CLI call Execute job against failed target from a specific jobRun
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
filterType | Integer | 1-All 2-error 3-warning |
jobRunId | Integer | no description |
This command executes a job against one or more server groups. This command returns the schedule ID of the job.
Note: To use this command on an Advanced Deploy Job, the Reset job on failure option must be selected for the job, so that failed job runs are automatically reset. In addition, the last job run must not be in incomplete state. If necessary, you can manually reset the job.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job. |
serverGroups | com.bladelogic.om.infra.cli.helper.StringList | List of server groups. |
The following example executes a job against server groups named /myGroup and /myOtherGroup.
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots tstSnap` |
blcli Job executeAgainstServerGroups $JOB_KEY /myGroup,/myOtherGroup |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstServerGroups_api | $jobKey$ $serverGroups$ | - |
This command executes a job against one or more server groups. This command blocks until a job run is created for the job, and then returns the job run key.
Note: To use this command on an Advanced Deploy Job, the Reset job on failure option must be selected for the job, so that failed job runs are automatically reset. In addition, the last job run must not be in incomplete state. If necessary, you can manually reset the job.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job. |
serverGroups | com.bladelogic.om.infra.cli.helper.StringList | List of server groups. |
The following example executes a job against server groups named /myGroup and /myOtherGroup.
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots tstSnap` |
blcli Job executeAgainstServerGroupsForRunID $JOB_KEY /myGroup,/myOtherGroup |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstServerGroupsForRunID_api | $jobKey$ $serverGroups$ | - |
JobRun.getJobRunKey | no input | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServerGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstServerGroupsForRunID_api-api | $jobkey$ $targetServerGroups$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServerGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServerGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstServerGroups_api-api | $jobkey$ $targetServerGroups$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServerGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
This command executes a job against specified targets. The targets are not necessarily defined as the job targets and do not change the job targets definition.
This command returns the schedule ID of the job.
Note: To use this command on an Advanced Deploy Job, the Reset job on failure option must be selected for the job, so that failed job runs are automatically reset. In addition, the last job run must not be in incomplete state. If necessary, you can manually reset the job.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job. |
serversName | com.bladelogic.om.infra.cli.helper.StringList | List of server names. |
The following example executes a job against servers named engrhas21agt1 and engrhas21agt2.
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots tstSnap` |
blcli Job executeAgainstServers $JOB_KEY engrhas21agt1,engrhas21agt2 |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstServers_api | $jobKey$ $serversName$ | - |
This command executes a job against specified targets. The targets are not necessarily defined as the job targets and do not change the job targets definition.
This command blocks until a job run is created for the job, and then returns the job run key.
Note: To use this command on an Advanced Deploy Job, the Reset job on failure option must be selected for the job, so that failed job runs are automatically reset. In addition, the last job run must not be in incomplete state. If necessary, you can manually reset the job.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job. |
serversName | com.bladelogic.om.infra.cli.helper.StringList | List of server names. |
The following example executes a job against servers named engrhas21agt1 and engrhas21agt2.
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots tstSnap` |
blcli Job executeAgainstServersForRunID $JOB_KEY engrhas21agt1,engrhas21agt2 |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstServersForRunID_api | $jobKey$ $serversName$ | - |
JobRun.getJobRunKey | no input | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServers | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstServersForRunID_api-api | $jobkey$ $targetServers$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServers | com.bladelogic.om.infra.cli.helper.StringList | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServers | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAgainstServers_api-api | $jobkey$ $targetServers$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServers | com.bladelogic.om.infra.cli.helper.StringList | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAndReturnScheduleID-api | $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
Goes to the app server, executes a job, waits until execution is done and returns the JobRun that resulted from that.
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
jobKey | DBKey | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAndWait-api | $typeId$ $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
jobId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAndWait-api | $typeId$ $jobId$ | - |
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
jobId | Integer | no description |
pi | com.bladelogic.om.infra.message.ProgressInterface | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAndWait-api | $typeId$ $jobId$ $pi$ | - |
Goes to the app server, executes a job, waits until execution is done and returns the JobRun that resulted from that.
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
jobKey | DBKey | no description |
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
jobId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
jobId | Integer | no description |
pi | com.bladelogic.om.infra.message.ProgressInterface | no description |
The argument jobKey is the handle to the job being modified. To find the jobKey for a specific job type, use the SnapshotJob getDBKeyByGroupAndName command. Use the groupName argument to provide the fully qualified path to the target component group (for example, /WestCoast/Windows).
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to be updated. |
groupsName | com.bladelogic.om.infra.cli.helper.StringList | Name of the component group. |
The following example execute job against server named engrhas21agt1 and engrhas21agt2 with the job specified by JobDBKey.
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots tstSnap` |
blcli Job executeAndWaitAgainstComponentGroups $JOB_KEY compGroup1,compGroup2 |
Command | Input | Return value stored name |
---|---|---|
Job.executeAndWaitAgainstComponentGroups_api | $jobKey$ $groupsName$ | - |
JobRun.getJobRunKey | no input | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetComponentGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAndWaitAgainstComponentGroups_api-api | $jobkey$ $targetComponentGroups$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetComponentGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job |
serverGroups | com.bladelogic.om.infra.cli.helper.StringList | List of server groups. |
The following example execute job against server named engrhas21agt1 and engrhas21agt2 with the job specified by JobDBKey.
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots tstSnap` |
blcli Job executeAndWaitAgainstServerGroups $JOB_KEY /myGroup |
Command | Input | Return value stored name |
---|---|---|
Job.executeAndWaitAgainstServerGroups_api | $jobKey$ $serverGroups$ | - |
JobRun.getJobRunKey | no input | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServerGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAndWaitAgainstServerGroups_api-api | $jobkey$ $targetServerGroups$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServerGroups | com.bladelogic.om.infra.cli.helper.StringList | no description |
Executes a job against specified targets. The targets are not necessarily defined as the job targets and do not change the job targets definition. If approval is enabled for the job type use the other command which takes in approval id as an additional input.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job |
serversName | com.bladelogic.om.infra.cli.helper.StringList | List of servers name. |
The following example execute job against server named engrhas21agt1 and engrhas21agt2 with the job specified by JobDBKey.
JOB_KEY=`blcli SnapshotJob getDBKeyByGroupAndName /snapshots tstSnap` |
blcli Job executeAndWaitAgainstServers $JOB_KEY engrhas21agt1,engrhas21agt2 |
Command | Input | Return value stored name |
---|---|---|
Job.executeAndWaitAgainstServers_api | $jobKey$ $serversName$ | - |
JobRun.getJobRunKey | no input | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServers | com.bladelogic.om.infra.cli.helper.StringList | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAndWaitAgainstServers_api-api | $jobkey$ $targetServers$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobkey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
targetServers | com.bladelogic.om.infra.cli.helper.StringList | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAndWaitForRunID-api | $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
Executes a job and wait for the job run to complete with a particular approval id.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
approvalId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.executeAndWaitWithApproval-api | $jobKey$ $approvalId$ | - |
Executes a job and wait for the job run to complete with a particular approval id.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
approvalId | Integer | no description |
This command executes a job and returns the schedule id.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | A handle to the job you want to execute. |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ false | - |
Job.executeAndReturnScheduleID | $jobKey$ | - |
Executes a job and waits for the job to end before returning the job run key.If approval is enabled for the job type use the other command which takes in approval id as an additional input.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | The handle to the job to run |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ false | - |
Job.findByDBKey | $jobKey$ | - |
Job.getType | no input | jobTypeId |
Job.executeAndWait | NAMED_OBJECT=jobTypeId $jobKey$ | - |
JobRun.getJobRunKey | no input | - |
Executes a job and waits for the job to end before returning the job run key.
Variable Name | Variable Type | Description |
---|---|---|
jobType | Integer | No description available |
jobKey | DBKey | No description available |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ false | - |
Job.executeAndWait | $jobType$ $jobKey$ | - |
JobRun.getJobRunKey | no input | - |
This command executes a job and waits for the Job Run ID before returning the job run key.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | A handle to the job you want to execute. |
Command | Input | Return value stored name |
---|---|---|
Job.checkApprovalEnabled | $jobKey$ false | - |
Job.executeAndWaitForRunID | $jobKey$ | - |
JobRun.getJobRunKey | no input | - |
Executes a job and wait for the job run id with a particular approval id.
job run keyVariable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
approvalId | Integer | approval id |
Command | Input | Return value stored name |
---|---|---|
Job.executeJobAndWaitForRunIDWithApproval-api | $jobKey$ $approvalId$ | - |
Executes a job and wait for the job run id with a particular approval id.
job run keyVariable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
approvalId | Integer | approval id |
Executes a job and wait for the job run id with a particular approval id. Only approvals with approval type pre-approved, automatic and emergency would be executed.
JobRunKey dbKeyVariable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | A handle to the Job to be executed. |
approvalId | Integer | approval id |
Command | Input | Return value stored name |
---|---|---|
Job.executeAndWaitWithApproval | $jobKey$ $approvalId$ | - |
This command executes a job and waits for the job run ID before returning the job run key. The job execution starts only after receiving an approval.
This command returns the DBKey of the job run.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | A handle to the job you want to execute. |
approvalId | Integer | Approval ID. |
The following example shows how to execute a job with approval and wait for the job run ID.
JOB_KEY=`blcli FileDeployJob getDBKeyByGroupAndName /filedeploy filedeployjob` |
JOB_APPROVAL_ID=`blcli Job createApproval 2 2 "My change" 2 3 "" ""` |
JOB_RUN_ID=`blcli Job executeJobWithApprovalAndWaitForRunID $JOB_KEY $JOB_APPROVAL_ID` |
Command | Input | Return value stored name |
---|---|---|
Job.executeJobAndWaitForRunIDWithApproval | $jobKey$ $approvalId$ | - |
This command executes a job and returns immediately without waiting for the job to end. Job execution starts only after receiving an approval.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job to execute. |
approvalId | Integer | Approval ID. |
The following example shows how to execute a job with approval.
JOB_KEY=`blcli FileDeployJob getDBKeyByGroupAndName /filedeploy filedeployjob` |
JOB_APPROVAL_ID=`blcli Job createApproval 2 2 "My change" 2 3 "" ""` |
JOB_KEY=`blcli Job executeWithApproval $JOB_KEY $JOB_APPROVAL_ID` |
Command | Input | Return value stored name |
---|---|---|
Job.executeWithApprovalAPI | $jobKey$ $approvalId$ | - |
Creates a schedule with the given approval id, job id and execute now schedule frequency, if the approval has been approved, the job will be executed when the scheduler pick it up.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
approvalId | Integer | approval id |
Command | Input | Return value stored name |
---|---|---|
Job.executeWithApprovalAPI-api | $jobKey$ $approvalId$ | - |
Creates a schedule with the given approval id, job id and execute now schedule frequency, if the approval has been approved, the job will be executed when the scheduler pick it up.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
approvalId | Integer | approval id |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
Command | Input | Return value stored name |
---|---|---|
Job.execute_api-api | $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
Expands the server groups of a given job to servers and then adds the servers individually back to the job
Variable Name | Variable Type | Description |
---|---|---|
job | com.bladelogic.om.infra.model.job.Job | no description |
Command | Input | Return value stored name |
---|---|---|
Job.expandServerGroups-api | $job$ | - |
Expands the server groups of a given job to servers and then adds the servers individually back to the job
Variable Name | Variable Type | Description |
---|---|---|
job | com.bladelogic.om.infra.model.job.Job | no description |
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
recursive | Boolean | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findAllByGroupId-api | $groupId$ $recursive$ | - |
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
recursive | Boolean | no description |
Variable Name | Variable Type | Description |
---|---|---|
modelType | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findAllByJobType-api | $modelType$ | - |
Variable Name | Variable Type | Description |
---|---|---|
modelType | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
modelType | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findAllByType-api | $modelType$ | - |
Variable Name | Variable Type | Description |
---|---|---|
modelType | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
serverId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findAllByTypeAndServer-api | $typeId$ $serverId$ | - |
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
serverId | Integer | no description |
This method returns the list of all jobs which can be executed by a given role.
Variable Name | Variable Type | Description |
---|---|---|
roleId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findAllExecutableJobsForRole-api | $roleId$ | - |
This method returns the list of all jobs which can be executed by a given role.
Variable Name | Variable Type | Description |
---|---|---|
roleId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findAllHeadersByGroup-api | $groupId$ | - |
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findAllHeadersByGroupId-api | $groupId$ | - |
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
modelType | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findAllHeadersByType-api | $modelType$ | - |
Variable Name | Variable Type | Description |
---|---|---|
modelType | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
modelType | Integer | no description |
name | String | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findAllHeadersByTypeAndName-api | $modelType$ $name$ | - |
Variable Name | Variable Type | Description |
---|---|---|
modelType | Integer | no description |
name | String | no description |
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
serverId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findAllHeadersByTypeAndServer-api | $typeId$ $serverId$ | - |
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
serverId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findBatchJobJobKeysByMemberJob-api | $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
Variable Name | Variable Type | Description |
---|---|---|
instanceKey | com.bladelogic.om.infra.model.base.keys.SBlValueKey | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findByAssociatedInstance-api | $instanceKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
instanceKey | com.bladelogic.om.infra.model.base.keys.SBlValueKey | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey-api | $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
breakObj | Boolean | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey-api | $jobKey$ $breakObj$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
breakObj | Boolean | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
runId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKeyAndRunId-api | $jobKey$ $runId$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
runId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
runKey | com.bladelogic.om.infra.model.base.keys.SJobRunKey | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findByJobRun-api | $runKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
runKey | com.bladelogic.om.infra.model.base.keys.SJobRunKey | no description |
Variable Name | Variable Type | Description |
---|---|---|
objectId | com.bladelogic.om.infra.model.base.definition.ObjectId | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findByObjectId-api | $objectId$ | - |
Variable Name | Variable Type | Description |
---|---|---|
objectId | com.bladelogic.om.infra.model.base.definition.ObjectId | no description |
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
jobKey | DBKey | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findByTypeAndKey-api | $typeId$ $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
jobKey | DBKey | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobType | Integer | no description |
groupKey | DBKey | no description |
jobName | String | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findByTypeGroupAndName-api | $jobType$ $groupKey$ $jobName$ | - |
Variable Name | Variable Type | Description |
---|---|---|
modelType | Integer | no description |
groupId | Integer | no description |
jobName | String | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findByTypeGroupAndName-api | $modelType$ $groupId$ $jobName$ | - |
Find a job given the job name and the full path to the parent group
To find the job model type names, check: getFullyResolvedPropertyValue .
Variable Name | Variable Type | Description |
---|---|---|
groupName | String | No description available |
jobName | String | No description available |
jobType | Integer | No description available |
Command | Input | Return value stored name |
---|---|---|
JobGroup.groupNameToDBKey | $groupName$ | groupDBKey |
Job.findByTypeGroupAndName | $jobType$ NAMED_OBJECT=groupDBKey $jobName$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobType | Integer | no description |
groupKey | DBKey | no description |
jobName | String | no description |
Variable Name | Variable Type | Description |
---|---|---|
modelType | Integer | no description |
groupId | Integer | no description |
jobName | String | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findHeaderByDBKey-api | $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
Variable Name | Variable Type | Description |
---|---|---|
modelType | Integer | no description |
groupId | Integer | no description |
jobName | String | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findHeaderByTypeGroupAndName-api | $modelType$ $groupId$ $jobName$ | - |
Variable Name | Variable Type | Description |
---|---|---|
modelType | Integer | no description |
groupId | Integer | no description |
jobName | String | no description |
Variable Name | Variable Type | Description |
---|---|---|
depotKey | com.bladelogic.om.infra.model.base.keys.SDepotObjectKey | no description |
modelType | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findJobKeysByDepotObjectKey-api | $depotKey$ $modelType$ | - |
Variable Name | Variable Type | Description |
---|---|---|
depotKey | com.bladelogic.om.infra.model.base.keys.SDepotObjectKey | no description |
modelType | Integer | no description |
Retrieve keys for all Jobs assigned to a Server Group.
a List of {@link SJobKey} objects that represent the Jobs that are assigned to this server group.Variable Name | Variable Type | Description |
---|---|---|
groupKey | com.bladelogic.om.infra.model.base.keys.SBLGroupKey | -- an SBLGroupKey instance representing the target Server Group. |
Command | Input | Return value stored name |
---|---|---|
Job.findJobKeysByServerGroupKey-api | $groupKey$ | - |
Retrieve keys for all Jobs assigned to a Server Group.
a List of {@link SJobKey} objects that represent the Jobs that are assigned to this server group.Variable Name | Variable Type | Description |
---|---|---|
groupKey | com.bladelogic.om.infra.model.base.keys.SBLGroupKey | -- an SBLGroupKey instance representing the target Server Group. |
Retrieve keys for all Jobs containing a given component template.
a List of {@link SJobKey} objects that represent the Jobs containing this component template.Variable Name | Variable Type | Description |
---|---|---|
templateKey | com.bladelogic.om.infra.model.base.keys.STemplateKey | -- an instance of StemplateKey class representing the contained template. |
Command | Input | Return value stored name |
---|---|---|
Job.findJobKeysByTemplateKey-api | $templateKey$ | - |
Retrieve keys for all Jobs containing a given component template.
a List of {@link SJobKey} objects that represent the Jobs containing this component template.Variable Name | Variable Type | Description |
---|---|---|
templateKey | com.bladelogic.om.infra.model.base.keys.STemplateKey | -- an instance of StemplateKey class representing the contained template. |
Quick way to find the option value of a job, given the option id. No need to retrieve the entire job object and then call getOptionValue() on it.
the string value of the specified Job OptionVariable Name | Variable Type | Description |
---|---|---|
jobId | Integer | the id of a Deploy Job |
optionId | Integer | the id of a Job Option |
Command | Input | Return value stored name |
---|---|---|
Job.findJobOptionValue-api | $jobId$ $optionId$ | - |
Quick way to find the option value of a job, given the option id. No need to retrieve the entire job object and then call getOptionValue() on it.
the string value of the specified Job OptionVariable Name | Variable Type | Description |
---|---|---|
jobId | Integer | the id of a Deploy Job |
optionId | Integer | the id of a Job Option |
Return JobRun objects for a Job where the additionalConditions may include PageSpec and ClassSpec settings to allow paging over a very large number of JobRun Objects.
list of JobRun.Variable Name | Variable Type | Description |
---|---|---|
job | com.bladelogic.om.infra.model.typesystem.value.ClassInstance | is the parent job. |
additionalConditions | com.bladelogic.om.infra.model.condition.expression.Condition | is whatever you want to add to an nary condition. |
classSpec | com.bladelogic.om.infra.model.generic.ClassSpec | is from PropertySetClass.JOB_RESULT to get all subclasses. |
pagingSpec | com.bladelogic.om.infra.model.generic.PagingSpec | allows to deal with huge numbers of results per run. |
Command | Input | Return value stored name |
---|---|---|
Job.findJobRunsByCondition-api | $job$ $additionalConditions$ $classSpec$ $pagingSpec$ | - |
Return JobRun objects for a Job where the additionalConditions may include PageSpec and ClassSpec settings to allow paging over a very large number of JobRun Objects.
list of JobRun.Variable Name | Variable Type | Description |
---|---|---|
job | com.bladelogic.om.infra.model.typesystem.value.ClassInstance | is the parent job. |
additionalConditions | com.bladelogic.om.infra.model.condition.expression.Condition | is whatever you want to add to an nary condition. |
classSpec | com.bladelogic.om.infra.model.generic.ClassSpec | is from PropertySetClass.JOB_RESULT to get all subclasses. |
pagingSpec | com.bladelogic.om.infra.model.generic.PagingSpec | allows to deal with huge numbers of results per run. |
Variable Name | Variable Type | Description |
---|---|---|
id | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findLatestById-api | $id$ | - |
Variable Name | Variable Type | Description |
---|---|---|
id | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findLatestHeaderById-api | $jobId$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobIds | java.util.Set | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findLatestHeadersByIds-api | $jobIds$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobIds | java.util.Set | no description |
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findNoAccessJobs-api | $groupId$ | - |
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
This method returns a log level of the parent deploy job set from UI.
jobId of the parent Deploy jobVariable Name | Variable Type | Description |
---|---|---|
jobId | Integer | - jobId of a child job |
Command | Input | Return value stored name |
---|---|---|
Job.findParentDeployJobKeyByChildJobKey-api | $jobId$ | - |
This method returns a log level of the parent deploy job set from UI.
jobId of the parent Deploy jobVariable Name | Variable Type | Description |
---|---|---|
jobId | Integer | - jobId of a child job |
This method returns a SBlValueKey of the parent job based upon the job key and type of its child
The SBlValueKey of the parent jobVariable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SBlValueKey | - SBlValueKey of a job |
type | Integer | - Type of job |
Command | Input | Return value stored name |
---|---|---|
Job.findParentPSIKeyByChildJobBlValueKey-api | $jobKey$ $type$ | - |
This method returns a SBlValueKey of the parent job based upon the job key and type of its child
The SBlValueKey of the parent jobVariable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SBlValueKey | - SBlValueKey of a job |
type | Integer | - Type of job |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
jobRunId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.findTargetServersByJobRun-api | $jobKey$ $jobRunId$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
jobRunId | Integer | no description |
This method returns a list of server names that are target of a job specified by jobKey and in one of the given states specified by serverStates. The server state names should be separated by comma.
a list of server names that are target of the given job and in the given state.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | - DBKey of a job |
serverStates | String | - Comma separated server state names |
Command | Input | Return value stored name |
---|---|---|
Job.findTargetServersByServerStates-api | $jobKey$ $serverStates$ | - |
This method returns a list of server names that are target of a job specified by jobKey and in one of the given states specified by serverStates. The server state names should be separated by comma.
a list of server names that are target of the given job and in the given state.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | - DBKey of a job |
serverStates | String | - Comma separated server state names |
This method returns a list of smart group names that are target of a job specified by jobKey.
a list of smart group names that are target of the given job and in the given state.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | - DBKey of a job |
Command | Input | Return value stored name |
---|---|---|
Job.findTargetSmartGroupsByJobKey-api | $jobKey$ | - |
This method returns a list of smart group names that are target of a job specified by jobKey.
a list of smart group names that are target of the given job and in the given state.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | - DBKey of a job |
This method returns a list of static server group names that are target of a job specified by jobKey.
a list of static group names that are target of the given job and in the given state.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | - DBKey of a job |
Command | Input | Return value stored name |
---|---|---|
Job.findTargetStaticGroupsByJobKey-api | $jobKey$ | - |
This method returns a list of static server group names that are target of a job specified by jobKey.
a list of static group names that are target of the given job and in the given state.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | - DBKey of a job |
Variable Name | Variable Type | Description |
---|---|---|
msg | com.bladelogic.om.infra.mfw.msg.BlMessage | no description |
Returns a Map of all the component templates for the job, mapping from the component dbkey to the component.
<b>Map</b> - the Map of DBKey to TemplateSvr objects.Returns a Map of all the component templates for the job, mapping from the component dbkey to the component.
<b>Map</b> - the Map of DBKey to TemplateSvr objects.Variable Name | Variable Type | Description |
---|---|---|
bForceLoadFromDB | Boolean | no description |
Returns a Map of all the component templates for the job, mapping from the component dbkey to the component and can Skip RBAC check based on falg passed.
<b>Map</b> - the Map of DBKey to TemplateSvr objects.Variable Name | Variable Type | Description |
---|---|---|
bForceLoadFromDB | Boolean | no description |
skipRBACCheck | Boolean | no description |
Jobs are both PropertySetInstances and PropertySetClasses. they are instances of the JOB class This object is the instance of the JOB class
PropertySetInstanceBean
Variable Name | Variable Type | Description |
---|---|---|
key | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
Command | Input | Return value stored name |
---|---|---|
Job.getAuditTrail-api | $key$ | - |
Variable Name | Variable Type | Description |
---|---|---|
key | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
Returns the list of ClassField's that are available in this instantiation of the object
the available ClassField's
Returns the ClassType of this object, either PropertySetClass or BlAssetClass
the ClassType
Find a DBKey to a job given the job name and the full path to the parent group
Variable Name | Variable Type | Description |
---|---|---|
groupName | String | No description available |
jobName | String | No description available |
jobType | Integer | No description available |
Command | Input | Return value stored name |
---|---|---|
Job.findByTypeGroupAndName | $groupName$ $jobName$ $jobType$ | jobReference |
Utility.setTargetObject | jobReference | - |
Job.getDBKey | no input | - |
Returns the class that holds the defaultValue for the specified ClassField
the defaultValue classVariable Name | Variable Type | Description |
---|---|---|
classField | com.bladelogic.om.infra.model.typesystem.type.ClassField | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
Command | Input | Return value stored name |
---|---|---|
Job.getDeployJobMaxRunId-api | $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | no description |
Variable Name | Variable Type | Description |
---|---|---|
assocType | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
depotObjectKey | DBKey | no description |
returns a value (potentially translated) for display
String
This command returns a list of smart group names (separated by commas) that are targets of a specific Job.
A list of smart group names separated by commas.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle to the job. |
The following example shows how to get the fully qualified smart group targets of a job.
JOB_KEY=`blcli AuditJob getDBKeyByGroupAndName /group1 auditJob1` |
blcli Job getFQTargetSmartGroups $JOB_KEY |
Command | Input | Return value stored name |
---|---|---|
Job.findTargetSmartGroupsByJobKey | $jobKey$ | - |
This command returns a list of static group names (separated by commas) that are targets of a specific Job.
A list of static server group names separated by commas.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle to the job. |
The following example shows how to get the fully qualified static group targets of a job.
JOB_KEY=`blcli AuditJob getDBKeyByGroupAndName /group1 auditJob1` |
blcli Job getFQTargetStaticGroups $JOB_KEY |
Command | Input | Return value stored name |
---|---|---|
Job.findTargetStaticGroupsByJobKey | $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
key | DBKey | no description |
Command | Input | Return value stored name |
---|---|---|
Job.getFolderHierarchyByDBKey-api | $key$ | - |
Variable Name | Variable Type | Description |
---|---|---|
key | DBKey | no description |
This command returns the fully resolved value of a given property in a given job. Using dot notation, you can get a nested property value in a job, as shown in the example below.
As input, you must provide a string describing the type of job. The valid job type strings are:
Variable Name | Variable Type | Description |
---|---|---|
jobTypeString | String | String representation of the job type. Valid job type strings are listed above. |
jobGroupName | String | Name of the job group. |
jobName | String | Name of the job. |
propertyName | String | Name of the property whose value you want to get. |
The following example gets the fully resolved property value of the nested property SUB_PROP, which resides in the property JOB_PROP. JOB_PROP is a property of a deploy job named testJob in the job group tstJobGroup:
blcli Job getFullyResolvedPropertyValue "DEPLOY_JOB" /tstJobGroup testJob JOB_PROP.SUB_PROP |
The following example gets the fully resolved property value of the PRIORITY* property. Note that the property name has an asterisk * at the end of it.
blcli Job getFullyResolvedPropertyValue UPDATE_SERVER_PROPERTY_JOB /All_Jobs USP_Job_1 PRIORITY* |
Command | Input | Return value stored name |
---|---|---|
Utility.convertModelType | $jobTypeString$ | modelType |
Job.findByTypeGroupAndName | $jobGroupName$ $jobName$ NAMED_OBJECT=modelType | job |
Job.getFullyResolvedValueAsString | $propertyName$ | - |
Returns the BlValue for the specified ClassField with property references expanded. This will never return null. If the value is a PropertyReferenceValue, this method will return the value referenced by the ReferenceValue in the context of this instance.
the BlValueVariable Name | Variable Type | Description |
---|---|---|
classField | com.bladelogic.om.infra.model.typesystem.type.ClassField | no description |
Returns the actual value for the specified ClassField with property references expanded. The return type must match the value type for the ClassField.
the valueVariable Name | Variable Type | Description |
---|---|---|
classField | com.bladelogic.om.infra.model.typesystem.type.ClassField | no description |
Returns the string value for the specified ClassField with property references expanded. This will never return null. If the value is a PropertyReferenceValue, this method will return the value referenced by the ReferenceValue in the context of this instance.
the string valueVariable Name | Variable Type | Description |
---|---|---|
classFieldName | String | no description |
Retrieves the current global default Job Parallelism value.
-- global default Job parallelism option.Command | Input | Return value stored name |
---|---|---|
Job.getGlobalDefaultJobParallelism-api | no input | - |
Retrieves the current global default Job Parallelism value.
-- global default Job parallelism option.
This command returns the group ID associated with a job.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle of the job |
The following example gets the group ID assiciated with the job specified by jobKey.
JOB_KEY=`blcli FileDeployJob getDBKeyByGroupAndName /filedeploy filedeployjob` |
blcli Job getGroupId $JOB_KEY |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.getGroupId | no input | - |
Returns the job header object.
<b>SJobHeader</b> - the header object.
Returns the job key.
<b>JobKey</b> - the job key.This command returns the name of a job using the DBKey as input.
Variable Name | Variable Type | Description |
---|---|---|
jobDBKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job. |
The following example will return the name of a job given the job's DBKey.
blcli Job getJobNameByDBKey DBKey:SJobKey:1-1 |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobDBKey$ | - |
Job.getName | no input | - |
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
type | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.getJobNames-api | $groupId$ $type$ | - |
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
type | Integer | no description |
Return the current Priority at the Job PSI level.
Return count of JobRuns for this JOb
number of JobRuns.Variable Name | Variable Type | Description |
---|---|---|
parentJob | com.bladelogic.om.infra.model.typesystem.value.ClassInstance | no description |
additionalCondition | com.bladelogic.om.infra.model.condition.expression.Condition | no description |
pagingSpec | com.bladelogic.om.infra.model.generic.PagingSpec | allows to deal with huge numbers of results per run. |
Command | Input | Return value stored name |
---|---|---|
Job.getJobRunsCountByCondition-api | $parentJob$ $additionalCondition$ $pagingSpec$ | - |
Return count of JobRuns for this JOb
number of JobRuns.Variable Name | Variable Type | Description |
---|---|---|
parentJob | com.bladelogic.om.infra.model.typesystem.value.ClassInstance | no description |
additionalCondition | com.bladelogic.om.infra.model.condition.expression.Condition | no description |
pagingSpec | com.bladelogic.om.infra.model.generic.PagingSpec | allows to deal with huge numbers of results per run. |
This command returns the last version of a job's DBKey using the Job Id
Variable Name | Variable Type | Description |
---|---|---|
JobId | Integer | The Job ID. |
The following example will return the DBKey of a job given the job's Id.
blcli Job getLastJobDBKeyByJobId $JobId |
Command | Input | Return value stored name |
---|---|---|
Job.findLatestById | $JobId$ | - |
Job.getDBKey | no input | - |
Returns the maximum no of targets that can be part of a single job
Command | Input | Return value stored name |
---|---|---|
Job.getMaximumNoOfTargetsInJob-api | no input | - |
Returns the maximum no of targets that can be part of a single job
Returns the globally-unique identifier for this object
the ObjectId
Variable Name | Variable Type | Description |
---|---|---|
optionId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
optionId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
optionId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
optionId | Integer | no description |
Returns the list of ClassField's that are overridden (not default) in this instantiation of the object
the overridden ClassField's
Returns the overridden (not default) BlValue for the specified ClassField. Returns null if !this.overridesValue(property). If the value is a PropertyReferenceValue this method will return the ReferenceValue, not the value that is referenced by the ReferenceValue.
the overridden BlValueVariable Name | Variable Type | Description |
---|---|---|
classField | com.bladelogic.om.infra.model.typesystem.type.ClassField | no description |
Returns the actual overridden (not default) value for the specified ClassField. The return type must match the value type for the ClassField.
the valueVariable Name | Variable Type | Description |
---|---|---|
classField | com.bladelogic.om.infra.model.typesystem.type.ClassField | no description |
Returns the parent job's version id for this job
Variable Name | Variable Type | Description |
---|---|---|
propName | String | no description |
Variable Name | Variable Type | Description |
---|---|---|
propName | String | no description |
failOnError | Boolean | no description |
This is here temporarily to allow a transition for code that was previously casting Job to SJob. This stopped working when SJob was moved to composition, rather than extension.
Returns the list of component groups for this job.
<b>List<b> - List of SJobComponentGroup objects.Returns the list of components for this job.
<b>List</b> - a List of SJobComponent objects.
Variable Name | Variable Type | Description |
---|---|---|
assocType | Integer | no description |
Returns the list of server groups for this job.
<b>List<b> - List of SJobDeviceGroup objects.
Returns the list of master devices for the job.
<b>List</b> - List of SJobMasterDevice objects.Returns the list of master snapshots for this job.
<b>List</b> - the list of SJobMasterSnapshot objects.
Returns the list of template groups for this job.
<b>List</b> - the list of SJobTemplateGroup objects.Returns the list of templates for this job.
<b>List</b> - the list of SJobTemplate objects.Used by CLI to get a list of target Servers that are in the specified states
Variable Name | Variable Type | Description |
---|---|---|
serverStates | String | a String of one or more server state separated by commas |
Returns a list of target Servers that are in the specified states.
Variable Name | Variable Type | Description |
---|---|---|
serverStateIds | java.util.List | a list of Server State ID (see ServerStateEnum) of one or more server state |
This command returns a list of server names (separated by commas) that are targets of a specific Job. Only servers in the state(s) specified by the serverState argument are returned. This command is deprecated. Use the listTargetServers command instead.
The serverState argument can be combination of the following. Separate multiple states by commas:
Note: This command is not relevant for Provisioning Jobs.
A list of server names separated by commas.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle to the job. |
serverState | String | The desired server states. |
The following example shows how to get the DECOMMISSIONED or NOT_ENROLLED server targets of a job.
JOB_KEY=`blcli AuditJob getDBKeyByGroupAndName /group1 auditJob1` |
blcli Job getTargetServers $JOB_KEY DECOMMISSIONED,NOT-ENROLLED |
Command | Input | Return value stored name |
---|---|---|
Job.findTargetServersByServerStates | $jobKey$ $serverState$ | - |
This command returns a list of target names (separated by commas) that are targets of a specific Job. blcli Job getTargets $JOB_KEY targetTypes This command is deprecated. Use the listTargets instead.
The argument targetTypes can have following values. Separate multiple targetTypes by comma:
The argument JOB_KEY is a handle to the job being queried. To find the jobKey for a specific job type, use the getDBKeyByGroupAndName for that particular job type. Below example is for AuditJob. AuditJob getDBKeyByGroupAndName command.
A list of target names separated by commas.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle to the job. |
targetTypes | String | The desired target type(s). |
The following example shows how to use this blcli to get the targets of a job.
Note: This blcli does not distinguish between Enrolled, Non-Enrolled, decomissioned servers when you query by using option "Servers". Use getTargetServers blcli for the same.
JOB_KEY=`blcli AuditJob getDBKeyByGroupAndName /group1 auditJob1` |
blcli Job getTargets $JOB_KEY Components |
blcli Job getTargets $JOB_KEY Servers,Components |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.getTargetsByTargetTypes | $targetTypes$ | - |
Used by CLI to get a list of targets that are in the specified types
Variable Name | Variable Type | Description |
---|---|---|
targetTypes | String | a String of one or more target type separated by commas (viz: Servers,Components) |
This method returns total count of targets in Batch Job
Variable Name | Variable Type | Description |
---|---|---|
batchJobId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.getTotalTargetCountForBatchJob-api | $batchJobId$ | - |
This method returns total count of targets in Batch Job
Variable Name | Variable Type | Description |
---|---|---|
batchJobId | Integer | no description |
Returns the BlValue for a ClassField. This will never return null. If the value is a PropertyReferenceValue, this method will return the ReferenceValue, not the value that is referenced by the ReferenceValue.
the BlValueVariable Name | Variable Type | Description |
---|---|---|
classField | com.bladelogic.om.infra.model.typesystem.type.ClassField | no description |
Returns the actual value for a ClassField. The return type must match the value type for the ClassField.
the valueVariable Name | Variable Type | Description |
---|---|---|
classField | com.bladelogic.om.infra.model.typesystem.type.ClassField | no description |
should only apply to primitives
a string rep of the value
Variable Name | Variable Type | Description |
---|---|---|
propName | String | no description |
the type of this value This will never return null.
Variable Name | Variable Type | Description |
---|---|---|
cid | Integer | no description |
r | com.bladelogic.om.infra.mfw.net.Reply | no description |
pD | java.lang.Object | no description |
Command | Input | Return value stored name |
---|---|---|
Job.handler-api | $cid$ $r$ $pD$ | - |
Variable Name | Variable Type | Description |
---|---|---|
cid | Integer | no description |
r | com.bladelogic.om.infra.mfw.net.Reply | no description |
pD | java.lang.Object | no description |
Returns whether a specific ClassField is available in this instantiation of the object
true if availableVariable Name | Variable Type | Description |
---|---|---|
classField | com.bladelogic.om.infra.model.typesystem.type.ClassField | no description |
Variable Name | Variable Type | Description |
---|---|---|
optionId | Integer | no description |
Invoke BLIP function to check the job is in white-list.
0 means job is running against allowable number of targets and it is in while-list. Otherwise, either of them not satisfied. BLIP: BladeLogic Intelligent Pre-check.Variable Name | Variable Type | Description |
---|---|---|
jobId | Integer | no description |
deviceIds | java.util.Set | no description |
Command | Input | Return value stored name |
---|---|---|
Job.invokeBLIP-api | $jobId$ $deviceIds$ | - |
Invoke BLIP function to check the job is in white-list.
0 means job is running against allowable number of targets and it is in while-list. Otherwise, either of them not satisfied. BLIP: BladeLogic Intelligent Pre-check.Variable Name | Variable Type | Description |
---|---|---|
jobId | Integer | no description |
deviceIds | java.util.Set | no description |
Variable Name | Variable Type | Description |
---|---|---|
batchJobId | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.invokeBLIPForBatchJob-api | $batchJobId$ | - |
Variable Name | Variable Type | Description |
---|---|---|
batchJobId | Integer | no description |
deviceIds | java.util.Set | no description |
Command | Input | Return value stored name |
---|---|---|
Job.invokeBLIPForBatchJob-api | $batchJobId$ $deviceIds$ | - |
Variable Name | Variable Type | Description |
---|---|---|
batchJobId | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
batchJobId | Integer | no description |
deviceIds | java.util.Set | no description |
Check whether approval is enabled for the job type or if the approval type is Pre-Approved approval type with one of the approval supported job types. Throws Exception if both are false.
Variable Name | Variable Type | Description |
---|---|---|
job | com.bladelogic.om.infra.model.job.Job | no description |
approvalRequest | com.bladelogic.om.infra.model.approval.ApprovalRequestInfo | no description |
Command | Input | Return value stored name |
---|---|---|
Job.isApprovalEnabled-api | $job$ $approvalRequest$ | - |
Check whether approval is enabled for the job type or if the approval type is Pre-Approved approval type with one of the approval supported job types. Throws Exception if both are false.
Variable Name | Variable Type | Description |
---|---|---|
job | com.bladelogic.om.infra.model.job.Job | no description |
approvalRequest | com.bladelogic.om.infra.model.approval.ApprovalRequestInfo | no description |
Returns true if this job is in a broken state (caused by the deletion of a referenced object). Note: In 7.5, only Deploy Jobs can be broken.
<b>boolean</b> - returns true if this job has been broken.
Command | Input | Return value stored name |
---|---|---|
Job.isCLAVersion2-api | no input | - |
Returns true if this job is in a deleted state.
<b>boolean</b> - returns true if this job has been deleted.
This method returns if BLIP feature is enabled
Command | Input | Return value stored name |
---|---|---|
Job.isEnableBlip-api | no input | - |
This method returns if BLIP feature is enabled
True if this object can be cast to it's main type, e.g. ServerImpl, false for GenericPSIImpl, etc
Returns whether the job should be access checked for .Modify
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
name | String | no description |
type | Integer | no description |
Command | Input | Return value stored name |
---|---|---|
Job.isJobNameExists-api | $groupId$ $name$ $type$ | - |
Variable Name | Variable Type | Description |
---|---|---|
groupId | Integer | no description |
name | String | no description |
type | Integer | no description |
This service determine whether Job Output functionality (both Job Result and NSH Job Output/Error) is enabled and visible by the UI. Can be modified using blasadmin.
true if Job Output functionality is enabledCommand | Input | Return value stored name |
---|---|---|
Job.isJobOutputEnabled-api | no input | - |
This service determine whether Job Output functionality (both Job Result and NSH Job Output/Error) is enabled and visible by the UI. Can be modified using blasadmin.
true if Job Output functionality is enabled
This method returns if the admin has enabled to check the maximum no of targets that can be part of a single job
Command | Input | Return value stored name |
---|---|---|
Job.isLimitMaxTargetsInJobEnabled-api | no input | - |
This method returns if the admin has enabled to check the maximum no of targets that can be part of a single job
true if this value represents the no-access null value.
true if this value represents a null value.
Variable Name | Variable Type | Description |
---|---|---|
property | com.bladelogic.om.infra.model.property.Property | no description |
Check if the configuration property "ShowConfirmationOnTargetSelection" is enabled.
Command | Input | Return value stored name |
---|---|---|
Job.isShowConfirmationOnTargetSelectionEnabled-api | no input | - |
Check if the configuration property "ShowConfirmationOnTargetSelection" is enabled.
Variable Name | Variable Type | Description |
---|---|---|
val | com.bladelogic.om.infra.model.typesystem.value.BlValue | no description |
Returns true if the targets of this job have been modified since the last time it was saved.
<b>boolean</b> - true if the targets have been modified.true if the contents are never saved (core data modified or non-core data modified).
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
Command | Input | Return value stored name |
---|---|---|
Job.jobExistsByDBKey-api | $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | no description |
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
groupKey | DBKey | no description |
jobName | String | no description |
Command | Input | Return value stored name |
---|---|---|
Job.jobExistsByTypeGroupAndName-api | $typeId$ $groupKey$ $jobName$ | - |
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
groupKey | DBKey | no description |
jobName | String | no description |
This command checks if a job exists given a type string, fully qualified static group name, and job name.
Variable Name | Variable Type | Description |
---|---|---|
typeString | String | The type string of the job. |
groupPath | String | The fully qualified static group name of the job. |
jobName | String | The name of the job. |
The following example shows how to check if a job exists in a static group. As input, you must provide a string describing the type of job. The valid job type strings are:
JOB_EXISTS=`blcli Job jobExistsByTypeStringGroupAndName NSH_SCRIPT_JOB "/Workspace" "MyScriptJob"` |
Command | Input | Return value stored name |
---|---|---|
Utility.convertModelType | $typeString$ | modelType |
Group.groupNameToDBKey | $groupPath$ 5005 | groupKey |
Job.jobExistsByTypeGroupAndName | NAMED_OBJECT=modelType NAMED_OBJECT=groupKey $jobName$ | - |
Returns a jobs ID given the DBKey
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | a handle to the job |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.getJobId | no input | - |
Returns a jobs Version given the DBKey
Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | a handle to the job |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.getJobVersionId | no input | - |
This command lists all jobs in a group.
This command returns a list of jobs.Variable Name | Variable Type | Description |
---|---|---|
qualifiedGroupName | String | Name of the job group whose jobs you want to list. |
The following example shows how to list all the jobs in group Group1.
blcli Job listAllByGroup Group1 |
Command | Input | Return value stored name |
---|---|---|
JobGroup.groupNameToId | $qualifiedGroupName$ | groupId |
Job.findAllHeadersByGroup | NAMED_OBJECT=groupId | - |
SJobHeader.getName | no input | - |
Utility.setTargetObject | no input | - |
Utility.listPrint | no input | - |
This command returns a list of server names that are targets of a specific Job. Only servers in the state(s) specified by the serverState argument are returned.
The serverState argument can be combination of the following. Separate multiple states by commas:
Note: This command is not relevant for Provisioning Jobs.
A list of server names.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle to the job. |
serverState | String | The desired server states. |
The following example shows how to get the DECOMMISSIONED or NOT_ENROLLED server targets of a job.
JOB_KEY=`blcli AuditJob getDBKeyByGroupAndName "/group1" "auditJob1"` |
blcli Job listTargetServers $JOB_KEY DECOMMISSIONED,NOT-ENROLLED |
Command | Input | Return value stored name |
---|---|---|
Job.findTargetServersByServerStates | $jobKey$ $serverState$ | - |
Utility.listPrint | no input | - |
This command returns a list of target names that are targets of a specific Job. blcli Job listTargets $JOB_KEY targetTypes
The argument targetTypes can have following values. Separate multiple targetTypes by comma:
The argument JOB_KEY is a handle to the job being queried. To find the jobKey for a specific job type, use the getDBKeyByGroupAndName for that particular job type. Below example is for AuditJob. AuditJob getDBKeyByGroupAndName command.
A list of target names separated by commas.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle to the job. |
targetTypes | String | The desired target type(s). |
The following example shows how to use this blcli to get the targets of a job.
Note: This blcli does not distinguish between Enrolled, Non-Enrolled, decomissioned servers when you query by using option "Servers". Use listTargetServers blcli for the same.
JOB_KEY=`blcli AuditJob getDBKeyByGroupAndName /group1 auditJob1` |
blcli Job listTargets $JOB_KEY Components |
blcli Job listTargets $JOB_KEY Servers,Components |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.getTargetsByTargetTypes | $targetTypes$ | - |
Utility.setTargetObject | no input | - |
Utility.listPrint | no input | - |
Variable Name | Variable Type | Description |
---|---|---|
typeId | Integer | no description |
msg | com.bladelogic.om.infra.mfw.msg.BlMessage | no description |
Command | Input | Return value stored name |
---|---|---|
Job.createInstance | $typeId$ $msg$ | - |
This command modifies the name and Description of specified Job.
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle to the job. |
newJobName | String | new job name to set to specified Job |
description | String | new Job Description |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.setName | $newJobName$ | - |
Job.setDescription | $description$ | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
Move a job to another group, given its full path. First step is to find a job object given the job key, then we move it to the specified group.
This command returns the handle to the moved Job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job being modified. |
toGroupName | String | Full path to where it is to be moved |
The following example demonstrates how to obtain a job key and then use the command to move the job to a different group.
JOB_FOLDER="/NSH_Jobs_1" |
JOB_NAME="Run on all Servers" |
JOB_KEY=`blcli NSHScriptJob getDBKeyByGroupAndName "$JOB_FOLDER" "$JOB_NAME"` |
MOVED_JOB_KEY=`blcli Job moveByJobKeyAndGroup "$JOB_KEY" "/NSH_Jobs_2"` |
Command | Input | Return value stored name |
---|---|---|
Job.moveJobToGroup | $jobKey$ $toGroupName$ | - |
Job.getDBKey | no input | - |
Move a job to another group, given its full path. First step is to find a job object given the job object name, model type and the full path to the parent group. Then we move it to the specified group.
As input, you must provide a string describing the type of job. The valid job type strings are:
Variable Name | Variable Type | Description |
---|---|---|
fromGroupName | String | Group where object is located |
jobName | String | Name of object |
toGroupName | String | Full path to where it is to be moved |
modelType | String | ModelType name from ModelType.java |
The following example demonstrates how to use the command.
blcli Job moveByTypeGroupAndName /NSH_Jobs_1 myNSHScriptJob /NSH_Jobs_2 NSH_SCRIPT_JOB |
Command | Input | Return value stored name |
---|---|---|
Utility.convertModelType | $modelType$ | modelTypeEnum |
JobGroup.groupNameToId | $toGroupName$ | toGroupId |
Job.findByTypeGroupAndName | $fromGroupName$ $jobName$ NAMED_OBJECT=modelTypeEnum | - |
Job.setGroupId | NAMED_OBJECT=toGroupId | - |
Job.update | no input | - |
Job.getDBKey | no input | jobKey |
This method moves a job from where it currently resides to the specified folder. This command is different from other methods of moving since it will not make an access check on .Modify on the job. It will make sure there is access to read the folder that it currently resides in and there will be access checks for reading and writing to the new group.
The moved jobVariable Name | Variable Type | Description |
---|---|---|
jobToMove | DBKey | no description |
toGroupId | Integer | - the id of the group to move to. |
Command | Input | Return value stored name |
---|---|---|
Job.moveJobToGroup-api | $jobToMove$ $toGroupId$ | - |
This method moves a job from where it currently resides to the specified folder. This command is different from other methods of moving since it will not make an access check on .Modify on the job. It will make sure there is access to read the folder that it currently resides in and there will be access checks for reading and writing to the new group.
The moved jobVariable Name | Variable Type | Description |
---|---|---|
jobToMove | DBKey | no description |
toGroupName | String | - the fully qualified name of the group to move to. |
Command | Input | Return value stored name |
---|---|---|
Job.moveJobToGroup-api | $jobToMove$ $toGroupName$ | - |
This method moves a job from where it currently resides to the specified folder. This command is different from other methods of moving since it will not make an access check on .Modify on the job. It will make sure there is access to read the folder that it currently resides in and there will be access checks for reading and writing to the new group.
The moved jobVariable Name | Variable Type | Description |
---|---|---|
jobToMove | DBKey | no description |
toGroupId | Integer | - the id of the group to move to. |
This method moves a job from where it currently resides to the specified folder. This command is different from other methods of moving since it will not make an access check on .Modify on the job. It will make sure there is access to read the folder that it currently resides in and there will be access checks for reading and writing to the new group.
The moved jobVariable Name | Variable Type | Description |
---|---|---|
jobToMove | DBKey | no description |
toGroupName | String | - the fully qualified name of the group to move to. |
Returns whether a specific ClassField is overriden (not default) in this instantiation of the object
true if overriddenVariable Name | Variable Type | Description |
---|---|---|
classField | com.bladelogic.om.infra.model.typesystem.type.ClassField | no description |
Variable Name | Variable Type | Description |
---|---|---|
s | String | no description |
Indicates if the reader of this object has rbac permissions to read it. It will only be false for generic objects (GenericPSIImpl), retrieved through the GenericObjectService or NamespaceService using a PagingSpec with includeNoAccessObjects true. If readAllowed is false, only the BL_INSTANCE properties will be available through this interface.
true if read access permittedThis command recursively sets a property on all jobs starting at the specified folder path.
Variable Name | Variable Type | Description |
---|---|---|
groupPath | String | The path to the folder. |
propertyName | String | The name of the property to set. |
value | String | The value to set. |
The following example recursively sets the isApproved property to true, starting at the folder /location123/jobs.
blcli Job recursivelySetProperty /location123/jobs isApproved true |
Command | Input | Return value stored name |
---|---|---|
PropertySetInstance.recursivelySetPropertyOnModelObject | 5005 $groupPath$ $propertyName$ $value$ | - |
This command removes an ACL policy from a Job.
When an ACL policy is removed from an object, all access checks through that object's ACL will no longer check against the internal ACL of the ACL policy that was removed. No checks are made to make sure one does not lock themselves out of an object by removing a policy.
Returns the DBKey of the modified object.Variable Name | Variable Type | Description |
---|---|---|
JobKey | DBKey | Job Key. |
policyName | String | Name of the ACL policy to remove. |
The following example shows how to remove an ACL policy called "Test Policy" from the Job with DB Key "Job DB Key".
Job removeAclPolicy "Job DB Key" "Test Policy" |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $JobKey$ | objsrc |
BlAclPolicy.findByName | $policyName$ | policy |
BlAclPolicy.removeAclPolicy_api | NAMED_OBJECT=policy NAMED_OBJECT=objsrc | obj |
Utility.setTargetObject | obj | - |
Job.update | NAMED_OBJECT=obj | - |
Job.getDBKey | no input | - |
This command removes all schedules from a job. The argument jobKey is the handle to the job being modified.
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | com.bladelogic.om.infra.model.base.keys.SJobKey | Handle to the job being modified. |
Command | Input | Return value stored name |
---|---|---|
Schedule.deleteAllByJob | $jobKey$ | - |
Utility.setInputAsTargetObject | $jobKey$ | - |
Variable Name | Variable Type | Description |
---|---|---|
optionId | Integer | no description |
This command removes a permission from a job.
Returns the ACL.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | DBKey of the job. |
roleName | String | Name of the role. |
authName | String | Name of the authorization. |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | job |
BlAcl.removePermission | NAMED_OBJECT=job $roleName$ $authName$ | - |
Utility.setTargetObject | job | - |
Job.update | NAMED_OBJECT=job | - |
Job.getDBKey | no input | - |
This command removes a property value from a job. The property name must be defined in the Job property class, or in the appropriate subclass of Job. The property must be defined as editable.
Variable Name | Variable Type | Description |
---|---|---|
objectKey | DBKey | DBKey of the job. |
propertyName | String | Name of the property. |
This example assumes that a job key is present in the CLI variable job_key. This example also assumes that a property called is_approved has been defined in the Job property class.
Job removePropertyValue $job_key is_approved |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $objectKey$ | modelObject |
Job.clearOverriddenValue | $propertyName$ | - |
Utility.setTargetObject | modelObject | - |
Job.update | NAMED_OBJECT=modelObject | - |
Variable Name | Variable Type | Description |
---|---|---|
auditTrail | com.bladelogic.om.infra.model.rbac.AuditTrail | no description |
Variable Name | Variable Type | Description |
---|---|---|
x | com.bladelogic.om.infra.model.notification.Notification | no description |
Variable Name | Variable Type | Description |
---|---|---|
anonymous | Boolean | no description |
Variable Name | Variable Type | Description |
---|---|---|
associated | Boolean | no description |
Sets the instance of the job (used to allow override of properties during the execution).
Variable Name | Variable Type | Description |
---|---|---|
propertySetInstance | com.bladelogic.om.infra.model.property.PropertySetInstance | no description |
Variable Name | Variable Type | Description |
---|---|---|
autoGenerated | Boolean | no description |
Variable Name | Variable Type | Description |
---|---|---|
optionId | Integer | No description available |
optionValue | Boolean | No description available |
Command | Input | Return value stored name |
---|---|---|
Job.setOptionValue | $optionId$ $optionValue$ | - |
Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | No description available |
optionId | Integer | No description available |
optionValue | Boolean | No description available |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.setOptionValue | $optionId$ $optionValue$ | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
Sets this job as having been broken.
Variable Name | Variable Type | Description |
---|---|---|
isBroken | Boolean | - true if the job has been broken. |
Variable Name | Variable Type | Description |
---|---|---|
arg0 | Boolean | no description |
Variable Name | Variable Type | Description |
---|---|---|
arg0 | Boolean | no description |
Variable Name | Variable Type | Description |
---|---|---|
l | java.util.List | no description |
Variable Name | Variable Type | Description |
---|---|---|
depotObjectKey | DBKey | no description |
partIdList | java.util.Set | no description |
Variable Name | Variable Type | Description |
---|---|---|
deprecated | Boolean | no description |
Variable Name | Variable Type | Description |
---|---|---|
description | String | no description |
This command sets the description on a job
This command returns a handle to the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle to the job. |
desc | String | Description for the job. |
The following example will set a job's description given a job's DBKey and description.
blcli Job setDescription DBKey:SJobKey:2000001-1 "First stage deployment" |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.setDescription | $desc$ | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
Variable Name | Variable Type | Description |
---|---|---|
b | Boolean | no description |
This command will enable/disable root level logs for a job
This command returns a handle to the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | Handle to the job. |
disableRootLogs | Boolean | Enable(false)/Disable(true) the root level logs |
The following example will disable root level logs.
blcli Job setDisableRootLogsOption DBKey:SJobKey:2000001-1 true |
The following example will enable root level logs.
blcli Job setDisableRootLogsOption DBKey:SJobKey:2000001-1 false |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.setDisableRootLogsOption | $disableRootLogs$ | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
Set the global default Job Parallelism value.
Variable Name | Variable Type | Description |
---|---|---|
defaultParallelism | Integer | -- negative values are ignored. |
Command | Input | Return value stored name |
---|---|---|
Job.setGlobalDefaultJobParallelism-api | $defaultParallelism$ | - |
Set the global default Job Parallelism value.
Variable Name | Variable Type | Description |
---|---|---|
defaultParallelism | Integer | -- negative values are ignored. |
Variable Name | Variable Type | Description |
---|---|---|
arg0 | Integer | no description |
Used in order to assign a property name for keeping the job run output result
Variable Name | Variable Type | Description |
---|---|---|
propertyName | String | a String value of the property name |
This command sets the max parallelism of a job identified by its DBKey. You can pass 0 as the second argument to set the max parallelism to unlimited.
This command returns the handle of the updated job.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | The DB Key of the job |
maxParallelism | Integer | The max parallelism of the job |
The following example set the max parallelism of a deploy job to 10, and then set it back to unlimited.
JOBKEY='blcli DeployJob getDBKeyByGroupAndName /default job1' |
NEWJOBKEY='blcli Job setMaxParallelism $JOBKEY 10' |
NEWJOBKEY1='blcli Job setMaxParallelism $NEWJOBKEY 0' |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.setParallelProcs | $maxParallelism$ | - |
Job.update | no input | - |
Job.getDBKey | no input | - |
Variable Name | Variable Type | Description |
---|---|---|
name | String | no description |
Variable Name | Variable Type | Description |
---|---|---|
l | java.util.List | no description |
Variable Name | Variable Type | Description |
---|---|---|
isNull | Boolean | no description |
Variable Name | Variable Type | Description |
---|---|---|
optionId | Integer | no description |
value | Boolean | no description |
Variable Name | Variable Type | Description |
---|---|---|
optionId | Integer | no description |
value | com.bladelogic.om.infra.model.option.OptionValue | no description |
Variable Name | Variable Type | Description |
---|---|---|
optionId | Integer | no description |
value | Integer | no description |
Variable Name | Variable Type | Description |
---|---|---|
optionId | Integer | no description |
value | String | no description |
Sets the overridden BlValue for the specified ClassField
Variable Name | Variable Type | Description |
---|---|---|
classField | com.bladelogic.om.infra.model.typesystem.type.ClassField | no description |
blValue | com.bladelogic.om.infra.model.typesystem.value.BlValue | no description |
Sets the actual overridden value for the specified ClassField. The value type must match the value type for the ClassField.
Variable Name | Variable Type | Description |
---|---|---|
classField | com.bladelogic.om.infra.model.typesystem.type.ClassField | no description |
value | java.lang.Object | no description |
Variable Name | Variable Type | Description |
---|---|---|
propertySetInstance | com.bladelogic.om.infra.model.property.PropertySetInstance | no description |
Variable Name | Variable Type | Description |
---|---|---|
number | Integer | no description |
Used to set the key for the parent job for this job
Variable Name | Variable Type | Description |
---|---|---|
parentJobKey | com.bladelogic.om.infra.app.service.job.JobKey | no description |
This command sets a property value on a job. The property name must be defined in the Job property class, or in the appropriate subclass of Job. The property must be defined as editable.
You can use the BMC BladeLogic blenc encryption utility to encrypt values you set with this command. For syntax and sample usage, see Server : setPropertyValue .
Variable Name | Variable Type | Description |
---|---|---|
objectKey | DBKey | DBKey of the job. |
propertyName | String | Name of the property. |
valueAsString | String | The value to set. |
This example assumes that a job key is present in the CLI variable job_key. This example also assumes that a property called is_approved has been defined in the Job property class.
Job setPropertyValue $job_key is_approved true |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $objectKey$ | modelObject |
PropertySetInstance.setPropertyValueByPSI | NAMED_OBJECT=modelObject $propertyName$ $valueAsString$ | - |
Utility.setTargetObject | modelObject | - |
Job.update | NAMED_OBJECT=modelObject | - |
Job.getDBKey | no input | - |
Variable Name | Variable Type | Description |
---|---|---|
jobAssetClassList | java.util.List | no description |
Sets the list of component groups for this job.
<b>boolean</b> - returns true if this operation modified the job component group list.Variable Name | Variable Type | Description |
---|---|---|
groupList | java.util.List | - the list of component groups. |
Sets the list of components for the job.
<b>boolean</b> - returns true if this operation modified the job component list.Variable Name | Variable Type | Description |
---|---|---|
jobComponentList | java.util.List | - the list of components. |
Variable Name | Variable Type | Description |
---|---|---|
jobDepotObjectGroupList | java.util.List | no description |
Sets the list of server groups for this job.
<b>boolean</b> - returns true if this operation modified the job server group list.Variable Name | Variable Type | Description |
---|---|---|
groupList | java.util.List | - the list of server groups. |
Variable Name | Variable Type | Description |
---|---|---|
l | java.util.List | no description |
Variable Name | Variable Type | Description |
---|---|---|
l | java.util.List | no description |
Sets the list of master devices for the job.
<b>boolean</b> - returns true if this operation modified the job master device list.Variable Name | Variable Type | Description |
---|---|---|
jobMasterDeviceList | java.util.List | - the List of SJobMasterDevice objects to add. |
Sets the list of master snapshots for the job.
<b>boolean</b> - returns true if this operation modified the job master snapshot list.Variable Name | Variable Type | Description |
---|---|---|
masterSnapshot | java.util.List | - the list of master snapshots. |
Variable Name | Variable Type | Description |
---|---|---|
l | java.util.List | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobTargetJobGroupList | java.util.List | no description |
Variable Name | Variable Type | Description |
---|---|---|
jobTargetJobList | java.util.List | no description |
Sets the list of template groups for the job.
<b>boolean</b> - returns true if this operation modified the job template group list.Variable Name | Variable Type | Description |
---|---|---|
groupList | java.util.List | - the list of template groups. |
Sets the list of templates for the job.
<b>boolean</b> - returns true if this operation modified the job template list.Variable Name | Variable Type | Description |
---|---|---|
templateList | java.util.List | - the List of component templates. |
Sets the saved explicitly value for the job. Passing false to this method will result in the job not appearing in the GUI.
Variable Name | Variable Type | Description |
---|---|---|
isSavedExplicitly | Boolean | - true if the job was directly created by the user. |
Variable Name | Variable Type | Description |
---|---|---|
skipValidation | Boolean | no description |
Variable Name | Variable Type | Description |
---|---|---|
skipValidation | Boolean | no description |
Variable Name | Variable Type | Description |
---|---|---|
synchronize | Boolean | no description |
Variable Name | Variable Type | Description |
---|---|---|
value | java.lang.Object | no description |
Variable Name | Variable Type | Description |
---|---|---|
ignoreValue | Boolean | no description |
Variable Name | Variable Type | Description |
---|---|---|
valueType | com.bladelogic.om.infra.model.typesystem.type.DataType | no description |
This command shows the current permissions on a job.
Returns the ACL.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | DBKey of the job. |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.getBlAcl | no input | blacl |
BlAcl.aclToString | NAMED_OBJECT=blacl | - |
This command shows the current permissions on a job. 'extractPolicyPermissions' controls inclusion of permissions contained in policies
Returns the ACL.Variable Name | Variable Type | Description |
---|---|---|
jobKey | DBKey | DBKey of the job. |
extractPolicyPermissions | Boolean | If true, alongwith policy name, permissions contained in policy will be returned else only policy name will be returned |
Command | Input | Return value stored name |
---|---|---|
Job.findByDBKey | $jobKey$ | - |
Job.getBlAcl | no input | blacl |
BlAcl.aclToString | NAMED_OBJECT=blacl $extractPolicyPermissions$ | - |
Variable Name | Variable Type | Description |
---|---|---|
msg | com.bladelogic.om.infra.mfw.msg.BlMessage | no description |
Variable Name | Variable Type | Description |
---|---|---|
j | com.bladelogic.om.infra.model.job.Job | no description |
Variable Name | Variable Type | Description |
---|---|---|
j | com.bladelogic.om.infra.model.job.Job | no description |
Variable Name | Variable Type | Description |
---|---|---|
propertyName | String | no description |