BMC Remedy IT Service Management Notification Engine Guide

More documents

Recommendations

Info

Invoking the notification subsystem Note So if you need to retain the entire message, we recommend retaining these messages on your email server. Invoking the notification subsystem Filters are triggered on certain application events. Filters populate data on the source forms and then push data from the source forms to the NTE:SYS-NT Process Control form for processing. One or more notification filters can trigger a notification event. The contents of the Notification Message Tag field are passed to the NTE:SYS-NT Process Control form, so it must be unique and must correspond to a notification message in the SYS:Notification Messages form. The notification filters perform the following actions: ■ Populate data on the source forms. ■ Push data from the source forms to the NTE:SYS-NT Process control form for processing. ■ Set the Notification Message Tag and temp fields, and then create a record in the NTE:SYS-NT Process Control form. The Notification Message Tag is the unique identifier for each notification event and message. After the Notification Process Control record is created, the notification fields on the source form are cleared. 14 BMC Remedy IT Service Management Notification Engine Guide
Notification transaction process A notification transaction uses the major components of the 7.6.00 Notification Engine, as shown in the figure below. Figure 3: Interaction of the major components in the 7.6.00 Notification Engine 1 The NTE:SYS-NT Process Control form is the center of the Notification Engine. All notifications are pushed to this form first. Depending on which parameters are included, it determines whether the notification is a group notification or an individual notification. Calling applications pass this information to the NTE:SYS- NT Process Control form. This information includes details such as the application, the recipient of the notification, and information about the parent record. 2 Escalations are run to process the pending notification events. Notification transaction process The application uses out-of-the-box escalation pools 1, 2, and 3 to enable multithreading processing for the records contained in the NTE:SYS-NT Process Control form. Chapter 1 BMC Remedy ITSM Notification Engine 15
Page 1 and 2: BMC Remedy IT Service Management No
Page 3 and 4: Support website Customer support Yo
Page 5 and 6: Contents Chapter 1 BMC Remedy ITSM
Page 7 and 8: BMC Remedy ITSM Notification Engine
Page 9 and 10: ■ System process control—Proces
Page 11 and 12: notification determine whether the
Page 13: Notification interface The NTE:Noti
Page 17 and 18: CTM:People form to see whether the
Page 19 and 20: To globally modify system default s
Page 21 and 22: Configuring Notification Engine esc
Page 23 and 24: Extending the Notification Engine e
Page 25 and 26: Setting up escalation workflow to p
Page 27 and 28: workflow to the EscalationPoolNumbe
Page 29 and 30: BMC Remedy ITSM notification events
Page 31 and 32: Event Message tag Filter Descriptio
Page 41 and 42: Table 11: Task Management System no
Page 46: 49532 *174240*

BMC Remedy IT Service Management Notification Engine Guide

Create successful ePaper yourself

Delete template?

Save as template?