Oracle® Enterprise Manager Installation and Configuration Guide for Remedy Help Desk 6 Connector 10g Release 4 (10.2.0.4) Part Number E14983-01 |
|
|
PDF · Mobi · ePub |
The Remedy Help Desk 6 Connector integrates Remedy Help Desk 6.x with Enterprise Manager. Using this connector, you can create a Remedy trouble ticket, update an existing ticket, or close a ticket based on alerts in Enterprise Manager. The Remedy Connector integrates Enterprise Manager with Remedy Help Desk through either an HTTP or HTTPS connection.
You can create, update, or close tickets based on only the following types of alerts in Enterprise Manager:
Metric alerts
Availability alerts (includes alerts for Up, Down, Blackout Started, Blackout Ended, Agent Unreachable
, Agent Unreachable Resolved, Metric Error Detected,
and Mertic Error Resolved).
The following sections explain various Remedy Connector concepts that you must understand before you start using the Remedy Connector.
Auto Ticketing
Manual Ticketing
Ticket Templates
Grace Period
Whenever an alert is triggered or its state changes in Enterprise Manager, the Remedy Connector can automatically open or update a ticket. You can specify the set of alerts for which tickets must be opened and the alert severity for which this should happen.
You can do this in Notification Rules, the user-defined rules that define the criteria by which notifications should be sent for alerts.
See Also:
"Configuring Notifications" in the Oracle Enterprise Manager Advanced Configuration GuideAfter the ticket is opened, any subsequent update of the alert, such as a change in alert severity, updates the ticket. After the alert is cleared (severity is set to Clear
), you can optionally close the ticket.
See Also:
Section 4.1, "Automatically Creating a Trouble Ticket"From the Enterprise Manager console, you can manually open a Remedy ticket based on an open alert in Enterprise Manager. The Remedy Connector populates the ticket with details based on the alert and the ticket template selected.
See Also:
Section 4.2, "Manually Creating a Trouble Ticket"Ticket templates are XML transformation style sheets that transform Enterprise Manager alerts to a ticket format before the requests are sent to Remedy Service Desk.
These templates specify how Enterprise Manager alert attributes can populate the fields of a Remedy ticket. A ticket template helps in the mapping of Enterprise Manager Alert fields into Remedy ticket fields.
In Auto Ticketing, a notification method is created for each registered ticket template. The selected notification method determines which ticket template is used when a notification is sent out to the connector. For manual ticketing, you have to select a ticket template before submitting a request to create the ticket.
The Remedy Service Desk Connector includes some out-of-box default ticket templates. You may want to customize the templates to suit your needs.
See Also:
Chapter 5, "Using Default Templates"The grace period provides you with a configuration to prevent the creation of a large number of tickets for frequently reoccurring alerts. For alerts that occur frequently within a relatively short time interval, it is often desirable to open and maintain a ticket that tracks each occurrence of the alert instead of separate tickets each time.
For recurring alerts, the grace period is a time period during which reoccurrences of the same alert update (or re-open) an existing ticket for the alert, rather than create a new ticket.
For example, an alert triggers and a ticket is opened for it. If the grace period is one hour and the alert is cleared at 10:00 a.m., and if the same alert retriggers before 11:00 a.m. (one-hour grace period), the original ticket will be updated/reopened.