Академический Документы
Профессиональный Документы
Культура Документы
March 2007
Extending IBRSD
BMC Software
Table of contents
Disclaimers .............................................................................................................. 3 Additional references ............................................................................................... 3 Introduction .............................................................................................................. 4 BMC Event Manger.................................................................................................. 5 4.1 Extending base class ........................................................................................ 5 4.2 Adding your event policy ................................................................................... 5 4.3 Enrich the events .............................................................................................. 5 4.4 Extending INT:Staging ...................................................................................... 5 4.5 Adding the gateway (IBRSD) mappings............................................................ 6 4.6 Pushing the fields.............................................................................................. 7 5 BMC Service Impact Manager ................................................................................. 8 5.1 Categorize the CIs ............................................................................................ 8 5.2 Extending the IBRSD_SM_INCIDENT Class .................................................... 9 5.3 Update the Rules ............................................................................................ 10 5.4 Update the IBRSD mappings .......................................................................... 10 5.5 Workflow ......................................................................................................... 11 6 Conclusion ............................................................................................................. 12 1 2 3 4
Page 2 of 12
3/30/2007
Extending IBRSD
BMC Software
1 Disclaimers
This document does not grant or imply official support for these configurations from BMC. There is no implication that these configurations are, or will be, supported. For questions of support and contracts please contact you Contract Manager.
2 Additional references
Refer to the Integration for BMC Remedy Service Desk User Guide on the BMC Impact Solutions 7.0.01 Documentation CD for information on IBRSD. Many customers find help for questions or problems on the BMC Impact Manager forums on DevCon: http://devcon.bmc.com/phpBB2/index.php?c=30&sid=86d1d1f9d71d4729070b79234d9 6ae90
Page 3 of 12
3/30/2007
Extending IBRSD
BMC Software
3 Introduction
This document outlines how to extend the integration between BMC Impact Manager (BEM and SIM) and the Remedy Service Desk by adding categorization information in the incidents created throught IBRSD. In the BEM scenario detailed in section 4, events are enriched with categorization (operational and product tiers) information that needs to be conveyed to the Service Desk. Step by step guidelines are provided to implement this functionality In the SIM scenario detailed in section 5, incidents created by SIM for service impacts contain the categorization information stored for the CI for which the incident is created. The scenarios in this document can of course be used as a base for other extensions.
Page 4 of 12
3/30/2007
Extending IBRSD
BMC Software
Extending IBRSD
BMC Software
You will need to create new menu fields anywhere in this form. I created a new tab called categorization as noted in the screen capture.
You will need to map these fields to the appropriate menus which will eventually be pushed into HPD:InterfaceIncidentCreate. You will want to create these fields identical to the fields found in HPD:InterfaceIncidentCreate. You can just do a copy of the fields from the HPD:InterfaceIncidentCreate form. After you perform the copy rename the database field name with underscores. Note: Please name your fields with _ instead of spaces.
BMC Software
Page 7 of 12
3/30/2007
Extending IBRSD
BMC Software
These attributes are already SIM enabled and the values will be published by default as noticed in the next screen shot.
Page 8 of 12
3/30/2007
Extending IBRSD
BMC Software
: STRING; : STRING; : STRING; : STRING; : STRING; : STRING; : SIM_NOTIFICATION_STATUS; : MC_PRIORITY; : REAL; : LIST_OF STRING; 3/30/2007
Extending IBRSD
BMC Software
prop_destination : LIST_OF STRING; manually_created_incident : INTEGER , default=0; incident_for : STRING; status_incident : STRING; status_reason : STRING; priority_urgency_option : INTEGER; status_impact_option : INTEGER; cell_name : STRING; policy_name : STRING; bOrphanedRoot : INTEGER, default=0; }; END
Page 10 of 12
3/30/2007
Extending IBRSD
BMC Software
MapName=SIMUseCase CopySource=FALSE #Copy contents of all the slots from source to destination before any translation #SourceClass= #DestinationClass= Description=Mapping for SIM Use Case Enable=TRUE { Short_Description=slot.msg Component_ID=slot.comp_id Impact_Component_Name=slot.comp_name Category = slot.comp_category Type = slot.comp_type Item = slot.comp_item Event_Priority=slot.comp_priority Event_Severity=slot.severity Root_Impact_Component_Names=slot.root_causes Status_Event=slot.comp_status Event_Requester="Jim" Keyword="SIM" z1D_FirstName="SIM" z1D_LastName="User" incident_for=slot.incident_for z1D_StatusIncident=slot.status_incident z1D_StatusReason=slot.status_reason DefaultCustom_Urgency=slot.priority_urgency_option DefaultCustom_Impact=slot.status_impact_option z1D_PolicyName=slot.policy_name z1D_CellName=slot.cell_name z1D_bOrphanedRoot=slot.bOrphanedRoot manually_created_incident=slot.manually_created_incident prop_destination=slot.prop_destination Notes="BMC Impact Manager Initiated Incident" }#end map for SIMUseCase Restart IBRSD to load the new mappings.
5.5 Workflow
No workflow changes are necessary since all workflow to move Category, Type and Item are already part of the base workflow.
Page 11 of 12
3/30/2007
Extending IBRSD
BMC Software
6 Conclusion
Please send comments to joe_teasdale@bmc.com.
Page 12 of 12
3/30/2007