_Job_wizard
THE FOLLOWING TEXT IS AN INCLUDE FOR THE DEFAULT JOB RUN NOTIFICATIONS DESCRIPTION
Default notifications can take the form of emails or SNMP traps. When a job completes, an SNMP trap is sent to a specified server, where it can be read using software that receives and interprets SNMP traps. Default notifications are sent when you run a job immediately (that is, you do not schedule the job) or a scheduled job completes but you have not set up email or SNMP notifications for that scheduled occurrence.
THE FOLLOWING TEXT IS AN INCLUDE FOR DEFAULT JOB RUN NOTIFICATIONS
Job Run Notifications
Field | Description |
|---|---|
Send email to | Lists email addresses of the accounts to notify when a job completes with the status that you specify. Separate multiple email addresses with semicolons, such as sysadmin@bmc.com;sysmgr@bmc.com. After entering email address information, check the statuses that cause an email to be generated. The statuses can be Success, Failed, or Aborted. |
Send SNMP trap to | Provides name or IP address of the server to notify when the job completes. After entering server information, select the statuses that should cause an SNMP trap to be generated. The statuses can be Success, Failed, or Aborted. TrueSight Server Automation provides a management information base (MIB) that describes its SNMP trap structure. You can use this MIB to create scripts that integrate traps into your trap collection system. The MIB is located on the Application Server host computer at installDirectory/Share/BladeLogic.mib. |
List failed servers in email notification | Indicates that email notifications should list all servers on which a job has failed. |
THE FOLLOWING TEXT IS AN INCLUDE FOR DEFAULT JOB RUN NOTIFICATIONS THAT DO NOT LIST FAILED SERVERS
Job Run Notifications
Field | Description |
|---|---|
Send email to | Lists email addresses of the accounts to notify when a job completes with the status that you specify. Separate multiple email addresses with semicolons, such as sysadmin@bmc.com;sysmgr@bmc.com. After entering email address information, select the statuses that cause an email to be generated. The statuses can be Success, Failed, or Aborted. |
Send SNMP trap to | Provides name or IP address of the server to notify when the job completes. After entering server information, select the statuses that should cause an SNMP trap to be generated. The statuses can be Success, Failed, or Aborted. TrueSight Server Automation provides a management information base (MIB) that describes its SNMP trap structure. You can use this MIB to create scripts that integrate traps into your trap collection system. The MIB is located on the Application Server host computer at installDirectory/Share/BladeLogic.mib. |
THE FOLLOWING TEXT IS AN INCLUDE FOR DEFAULT PATCHING JOB RESULT NOTIFICATIONS
Patching Job Run Notifications
Field | Description |
|---|---|
Send email to | Lists email addresses of the accounts to notify when a job completes with the status that you specify. Separate multiple email addresses with semicolons, such as sysadmin@bmc.com;sysmgr@bmc.com. After entering email address information, select the statuses that cause an email to be generated. |
Append patch analysis results to email | Indicates emailed notifications should include detailed patch analysis results. Note: This option is relevant only for Patching Jobs and not for Patching Remediation Jobs. You cannot send attachments for Patching Remediation Jobs, or for the child Deploy Jobs of Patching Analysis and Patching Remediation Jobs |
Limit email body size | Limits the size of email that is generated by appending patch analysis results. Enter the maximum size, in kilobytes, in the text box. The default value is 1000 KB. |
Send SNMP trap to | Provides name or IP address of the server to notify when the job completes. After entering server information, select the statuses that should cause an SNMP trap to be generated. TrueSight Server Automation provides a management information base (MIB) that describes its SNMP trap structure. You can use this MIB to create scripts that integrate traps into your trap collection system. The MIB is located at installDirectory/Share/BladeLogic.mib. |
List failed servers in email notification | Indicates email notifications should list all servers on which a job has failed. |
Create incident on job failure | Creates an incident in BMC Remedy ITSM if the job fails. This option is available if this job type was selected to support the creation of ITSM incidents and a connection to BMC Remedy ITSM was set up. For more information, see Enabling-Change-Automation-for-TrueSight-Server-Automation-jobs. |
THE FOLLOWING TEXT IS AN INCLUDE FOR DEFAULT AUDIT RESULT NOTIFICATIONS
Audit Results Notifications
Field | Description |
|---|---|
Send email to | Lists email addresses of the accounts to notify when a job completes with the status that you specify. Separate multiple email addresses with semicolons, such as sysadmin@bmc.com;sysmgr@bmc.com. After entering email address information, select the statuses that cause an email to be generated. |
Append audit results to email | Indicates emailed notifications should include audit results. |
Limit email body size | Limits the size of email that is generated by appending audit results. Enter the maximum size, in kilobytes, in the text box. The default value is 1000 KB. |
Send SNMP trap to | Provides name or IP address of the server to notify about audit results. After entering server information, select the statuses that should cause an SNMP trap to be generated. |
THE FOLLOWING TEXT IS AN INCLUDE FOR SNAPSHOT RESULT NOTIFICATIONS
Snapshot Change Notifications
Field | Description |
|---|---|
Send email to | Lists email addresses of the accounts to notify if snapshot results change. Separate multiple email addresses with semicolons, such as sysadmin@bmc.com;sysmgr@bmc.com. After entering email address information, check the statuses that cause an email to be generated. The statuses can be either Changed or Not Changed. |
Append snapshot change results to email | Indicates emailed notifications should include snapshot changes. |
Limit email body size to | Limits the size of email that is generated by appending snapshot changes. Enter the maximum size, in kilobytes, in the text box. The default value is 1000 KB. |
Send SNMP trap to | Provides name or IP address of the server to notify about snapshot changes. After entering server information, select the statuses that should cause an SNMP trap to be generated. The statuses can be either Changed or Not Changed. |
THE FOLLOWING TEXT IS AN INCLUDE FOR COMPLIANCE RESULT NOTIFICATIONS
Compliance Results Notifications
Field | Description |
|---|---|
Send email to | Lists email addresses of the accounts to notify if compliance results. Separate multiple email addresses with semicolons, such as sysadmin@bmc.com;sysmgr@bmc.com. Notification can occur when results are consistent, inconsistent, or both. |
Append compliance results to email | Indicates emailed notifications should include compliance results. |
Limit email body size | Limits the size of email that is generated by appending compliance results. Enter the maximum size, in kilobytes, in the text box. The default value is 1000 KB. |
Send SNMP trap to | Provides name or IP address of the server to notify about compliance results. After entering server information, select the results that should cause an SNMP trap to be generated. For example, if you select Inconsistent and a Compliance Job indicates that two components are inconsistent, an SNMP trap is sent. |
THE FOLLOWING TEXT IS AN INCLUDE FOR PARALLEL PROCESSING, A SETTING FROM THE GENERAL PANEL
Choose one of the following options:
- Unlimited — Simultaneously runs the job on as many servers as possible. Application Server settings control the number of targets the job can access.
- Limited — Specifies the maximum number of targets on which the job can run simultaneously. Limiting the number of targets is useful when a job might temporarily disrupt the functionality of a target server, and you want to limit that disruption to a small fraction of your managed servers.
If you want the job processed serially at the target servers, set this value to 1. Note, however, that although this is the best approach for achieving serial processing, it does not always guarantee full serial processing at all targets; the first two or three targets might still run in parallel.