Populating operational categories on an event

For Incident Management to route Event incidents to the appropriate support group, operational categories must be populated on the event that is generated in BPPM. Use dynamic data tables in cells where you can define operational categories based on certain event slot values. The defined operational categories can then be used in a refine rule and the event can be populated with the operational categories.

You need to identify the pattern or slots based on which operational categories can be populated. For example, if you identify that you have large number of events for a slot value such as for mc_host_class as Windows and for mc_object_class as FileSystem, you can define a key that has a combination of these two slot values in an event (Windows+FileSystem).

To populate operational categories

1. Connect to the BMC ProactiveNet Performance Management (BPPM) server.
2. Create a file in the $BMC_PROACTIVENET_HOME/etc/cellName/kb/classes folder and name it as bem_op_categorization.baroc.

3. Add the following code to this file:

   MC_DATA_CLASS :
   BEM_OPERATIONAL_CATEGORIZATION ISA IBRSD_DATA
   DEFINES {
               Key : STRING, key = yes;
               Operational_Tier_1 : STRING;
               Operational_Tier_2 : STRING;
               Operational_Tier_3 : STRING;
   };
   END
4. Add an entry of the bem_op_categorization.baroc file in the .load file, which is located in the $BMC_PROACTIVENET_HOME/etc/cellName/kb/classes folder.

5. Open the $BMC_PROACTIVENET_HOME/etc/cellName/kb/records/ibrsd_record.baroc file and add the following code to the file:

   RECORD IBRSD_RecordIndexOpCat
   DEFINES
   {
     Index: STRING;
   }
   END

    

6. On the BPPM server, create a new .mrl file in the $BMC_PROACTIVENET_HOME/etc/cellName/kb/rules folder and name it as ibrsd_bem_op_categorization.mrl.

7. Add the following code to the file:

   refine
   create_index_for_dda_match : EVENT($NEW)
   {
   $IBRSD_RecordIndexOpCat.Index = $NEW.mc_host_class || ":" || $NEW.mc_object_class; 
   }
   END
   refine get_opcat_from_dda :
   EVENT($NEW)
   using
   {
    BEM_OPERATIONAL_CATEGORIZATION ($BPC) where
                   [
              $IBRSD_RecordIndexOpCat.Index == $BPC.Key
                   ]
   }
   {
     $NEW. itsm_operational_category1 = $BPC.Operational_Tier_1;
     $NEW. itsm_operational_category2 = $BPC.Operational_Tier_2;
     $NEW. itsm_operational_category3 = $BPC.Operational_Tier_3;
   }
   END

    

   Note

   In the above code, change the line $IBRSD_RecordIndexOpCat.Index = $NEW.mc_host_class || ":" || $NEW.mc_object_class as per the slots that you have considered as keys.

    

8. Add entry of this file into .load file located in the $BMC_PROACTIVENET_HOME/etc/cellName/kb/rules folder.
9. At a command prompt, perform the following:
   1. Compile the cell using the command:  mccomp –n {cell Name}
   2. Stop the cell using the command: mkill –n {cell name}
   3. Start the cell using the command mcell –n {cell name}
10. Form a key from the event slots for which you want to populate operational categories. The key can be a combination of certain event slot values. For example, you can form key as $EVENT.mc_object: $EVENT.mc_object_class.
11. In the BMC ProactiveNet Administration Console, click the Dynamic Data Editor tab.
12. Expand MyProduction > Data > IBRSD Data.
13. Select BEM Operational Categorization, right click in the table and click New to create a new entry.
     
14. Create a new entry in the table by adding the following values:

• 
  
  • ID - Enter a unique ID, which is usually an integer. 
  • Key - Enter the combination of slot values that you have identified. For example, FileSystem:Windows
  • Operational_Tier_1 - Enter a value to populate operational categories in Tier 1. For example, enter Windows
  • Operational_Tier_2 - Enter a value to populate operational categories in Tier 2. For example, enter FileSystem1
    
    

After the operational categories are populated on an event, the Event incident is routed to the appropriate support group for resolution. For more information, see Incident-routing-using-operational-categories.