Working with Event Policies and Actions › Create an Event Policy with an Enrichment Action › Create a Java Method Enrichment Action › Java Method Enrichment Examples

Java Method Enrichment Examples

The following examples show how you can use the enrich event action to enrich events with information from a Java method when search patterns match. The examples uses CA CMDB and CA Spectrum enrichments provided with the Mid-tier connector. The enrichments could be useful in CA SOI for situations such as the following:

• You want to use CI properties in CA CMDB or CA Spectrum in alert queue criteria or for escalation policy
• You are using custom properties in CA CMDB or CA Spectrum that are not imported into CA SOI
• You want to use information from CA CMDB or CA Spectrum in alerts or CIs that are not managed in CA CMDB or CA Spectrum
• You want to parse partial information from a property for use in a different context

Important! The enrichments use .jar files that are only available with the Mid-tier connector. Deploy these provided enrichments on the Mid-tier connector only.

Example: Enrich events with location information from CA CMDB

This example enriches events with location information stored in CA CMDB. The information could help you create alert queues by location or add location-based criteria to escalation policy.

• Select Java Method on the Enrichment Configuration page, and select CMDB in the Templates drop-down list.
• Use the User and Password fields to enter valid credentials for the CA CMDB server, and leave the default values in all other fields.
• Do the following on the Enrichment Policy Configuration page:
  • Enter values for the provided method parameters in the Input Parameter column in the Assigned Values column:
    • endpointref: http://cmdbserver:8080/axis/services/USD_R11_WebService?wsdl
    • userid: ${user}
    • password: ${password}
    • propertylist: location.address,location.city

      Note: For CA CMDB r12 and above, use location.address1 instead of location.address.

    • selectquery: dns_name like "%s"
    • node: ${pattern1.AlertedMdrProdInstance}

    This parameter configuration queries the defined CA CMDB instance for CIs with a dns_name property that matches the event AlertedMdrProdInstance property value and returns the location.address and location.city properties of the matching CI. It uses substitution strings for the required CA CMDB credentials (referencing the credentials entered on the previous page) to avoid entering the information unencrypted.

  • Enter ${location.address} in the Assigned Value cell corresponding to the User Attribute 1 Event Property cell.

    Note: For CA CMDB r12 and above, use location.address1 instead of location.address.

  • Enter ${location.city} in the Assigned Value cell corresponding to the User Attribute 2 Event Property cell.

  This enrichment queries the defined CA CMDB instance for the location.address and location.city properties of the CI with a dns_name property value that matches the event AlertedMdrProdInstance property value. If there is no match, the enrichment does not occur. If there is a match, the location.address and location.city values are returned from the matching CI and assigned to the User Attribute 1 and User Attribute 2 properties in the enriched event.

  For example, consider an event with the AlertedMdrProdInstance value of server4. The server4 value matches a CA CMDB CI DNS name. The location.address and location.city values in the matching CI are 453 Elm St and Los Angeles, and these values appear in the enriched event for User Attribute 1 and User Attribute 2.

• Deploy the policy on the Mid-tier connector.
• (Optional) If you want enriched events to contain a link to the CI in CA CMDB, create a separate create event policy to add the following URL in the User Attribute 1 field to events that have been enriched:

  http://cmdbserver:8080/CAisd/pdmweb.exe?OP=SEARCH+FACTORY=nr+SKIPLIST=1+QBE.EQ.id=${pattern1.AlertedMdrProdInstance}
  

Example: Enrich events with CA Spectrum model attributes

This example enriches events with model attributes stored in CA Spectrum. The information could help you add CA Spectrum-specific information to CA SOI services.

Note: This example works with CA Spectrum r9.2.

• Select Java Method on the Enrichment Configuration page, and select Spectrum (By Name) in the Templates drop-down list.
• Use the User and Password fields to enter valid credentials for the CA Spectrum server, and leave the default values in all other fields.
• Do the following on the Enrichment Policy Configuration page:
  • Enter values for the provided method parameters in the Input Parameter column in the Assigned Values column:
    • i1: -searchmethod=by_name
    • i2: -broadcast=yes
    • i3: -landscapeout=spectrumserver
    • i4: landscapeuser=${user}
    • i5: -modeltype=Host_Device
    • i6: modelname=${AlertedMdrProdInstance }
    • i7: modelattributes=12bfd,12bfe

    This parameter configuration queries the defined CA Spectrum server for models with a name that matches the AlertedMdrProdInstance property value and returns the owner and organization properties of the matching model. You can enter the CA Spectrum hex codes for any model attribute.

  • Enter ${12bfd} in the Assigned Value cell corresponding to the User Attribute 1 Event Property cell.
  • Enter ${12bfe} in the Assigned Value cell corresponding to the User Attribute 2 Event Property cell.

  This enrichment queries the defined CA Spectrum server for the owner and organization attributes of the model with a name that matches the AlertedMdrProdInstance property value. If there is no match, the enrichment does not occur. If there is a match, the owner and organization values are returned from the matching CI and assigned to the User Attribute 1 and User Attribute 2 properties in the enriched event.

  For example, consider an event with the AlertedMdrProdInstance value of server4. The server4 value matches a CA Spectrum model name. The owner and organization values in the matching CI are Dave and Spectrum, and these values appear in the enriched event for User Attribute 1 and User Attribute 2.

• Deploy the policy on the Mid-tier connector.