Skip to main content

skip to main content

developerWorks  >  Autonomic computing  >

Common Base Event best practices: Properties and elements at a glance

This online (and downloadable) datasheet can jumpstart your using Common Base Event properties

developerWorks
Document options

Document options requiring JavaScript are not displayed


Rate this page

Help us improve this content


Level: Introductory

Kane Scarlett (kane@us.ibm.com), developerWorks Editor, IBM

09 May 2006

More on the "Best Practices for the Common Base Event and Common Event Infrastructure" guide -- this time, an interactive, at-a-glance properties and elements datasheet that links you to the appropriate section in the guide for more information.

Following are two lists of properties/elements of the Common Base Event specification, provided so you can use them as a quick online reference when constructing Common Base Events. This sheet is designed so if you need more information about a using a property, you can click on the section number and are whisked directly to the appropriate section of the "Common Base Event Best Practices" guide for more information on that property and the best ways to use it, including all the best practices the authors of the guide concocted and the pitfalls they ran into.

Start converting those log files!

Required properties by alphabetical order

Element/propertyDescriptionSection
Component identification: applicationSpecifies the human-readable "common" name of the associated business solution2.3.5.4
Component identification: componentIdentifies the manageable resource associated with the event2.3.5.5
Component identification: componentIdTypeSpecifies the format and meaning of the component property2.3.5.6
Component identification: componentTypeIdentifies the type of component that is identified in component/componentIdType2.3.5.7
Component identification: executionEnvironmentSpecifies the hosting environment for the component specified in the component property2.3.5.9
Component identification: instanceIdSpecifies the operational instance of the component that reports the event2.3.5.10
Component identification: locationSpecifies the physical address that corresponds to the location of a component2.3.5.2
Component identification: locationTypeSpecifies the format and meaning of the value in the location property2.3.5.3
Component identification: processIdSpecifies the process identifier of the "running" process within the component that reports the event2.3.5.11
Component identification: subComponentIdentifies the specific part of a component that is associated with the event2.3.5.8
Component identification: threadIdSpecifies the thread identifier of the "running" thread within the component that reports the event2.3.5.12
creationTimeSpecifies the time the event was created2.3.2
reporterComponentIdIdentifies the component that reported the situation2.3.3|More info
situationImportant: describes the situation that was detected2.3.6
situation: categoryNameCategorizes the situation reported by the event2.3.6.1
SituationTypeProvides the additional data associated with each situation category2.3.7
SituationType: AvailableSituationDescribes a component's operational state and availability2.3.7.9
SituationType: AvailableSituation: availabilityDispositionSpecifies the availability disposition of the component associated with the event2.3.7.9.2
SituationType: AvailableSituation: operationDispositionSpecifies whether the component associated with the event has the ability to be started 2.3.7.9.1
SituationType: AvailableSituation: processingDispositionSpecifies the processing disposition of a component operation associated with the event2.3.7.9.3
SituationType: AvailableSituation: reasoningScopeSpecifies the scope of the situation2.3.7.9.4
SituationType: ConfigureSituationIdentifies information about a component's configuration data and indicates changes to that data2.3.7.5
SituationType: ConfigureSituation: reasoningScopeSpecifies the scope of the situation2.3.7.5.2
SituationType: ConfigureSituation: successDispositionSpecifies whether the configuration situation described by the event was successful2.3.7.5.1
SituationType: ConnectSituationDescribes aspects about a connection to another component2.3.7.4
SituationType: ConnectSituation: reasoningScopeSpecifies the scope of the situation2.3.7.4.3
SituationType: ConnectSituation: situationDispositionSpecifies additional information to describe the connection process2.3.7.4.2
SituationType: ConnectSituation: successDispositionSpecifies whether the connection process described by the event was successful2.3.7.4.1
SituationType: CreateSituationDescribes a component's attempt to create an entity2.3.7.10
SituationType: CreateSituation: reasoningScopeSpecifies the scope of the situation2.3.7.10.2
SituationType: CreateSituation: successDispositionSpecifies whether the create situation associated with the event was successful2.3.7.10.1
SituationType: DependencySituationDescribes a dependency relationship between two components2.3.7.8
SituationType: DependencySituation: dependencyDispositionSpecifies the availability status of the dependency item associated with the event2.3.7.8.1
SituationType: DependencySituation: reasoningScopeSpecifies the scope of the situation2.3.7.8.2
SituationType: DestroySituationDescribes a component's attempt to destroy or remove an entity2.3.7.11
SituationType: DestroySituation: reasoningScopeSpecifies the scope of the situation2.3.7.11.2
SituationType: DestroySituation: successDispositionSpecifies whether the destroy situation associated with the event was successful2.3.7.11.1
SituationType: FeatureSituationAnnounces whether a feature of a component is ready to service requests2.3.7.7
SituationType: FeatureSituation: featureDispositionSpecifies the availability disposition of a component feature associated with the event2.3.7.7.1
SituationType: FeatureSituation: reasoningScopeSpecifies the scope of the situation2.3.7.7.2
SituationType: OtherSituationDescribes situations that cannot be represented in any of the defined situation categories2.3.7.13
SituationType: reasoningScopeSpecifies the scope of the situation2.3.7.1
SituationType: ReportSituationConveys general information about a component2.3.7.12
SituationType: ReportSituation: reasoningScopeSpecifies the scope of the situation2.3.7.12.2
SituationType: ReportSituation: reportCategorySpecifies the type of data reported by the event2.3.7.12.1
SituationType: RequestSituationRepresents the processing of a request by a component2.3.7.6
SituationType: RequestSituation: reasoningScopeSpecifies the scope of the situation2.3.7.6.3
SituationType: RequestSituation: situationQualifierSpecifies additional information to describe the request situation2.3.7.6.2
SituationType: RequestSituation: successDispositionSpecifies whether the request situation described by the event was successful2.3.7.6.1
SituationType: StartSituationDescribes a start situation2.3.7.2
SituationType: StartSituation: reasoningScopeSpecifies the scope of the situation2.3.7.2.3
SituationType: StartSituation: situationQualifierSpecifies additional information to further describe the start situation2.3.7.2.2
SituationType: StartSituation: successDispositionSpecifies whether the startup process described by the event was successful2.3.7.2.1
SituationType: StopSituationDescribes a stop situation2.3.7.3
SituationType: StopSituation: reasoningScopeSpecifies the scope of the situation2.3.7.3.3
SituationType: StopSituation: situationQualifierSpecifies additional information to describe the stop situation2.3.7.3.2
SituationType: StopSituation: successDispositionSpecifies whether the stop process described by the event was successful2.3.7.3.1
sourceComponentIdIdentifies the component that was affected by the situation2.3.3|More info
versionA string used to identify the version of the Common Base Event specification event2.3.1

Optional properties by alphabetical order

Element/propertyDescriptionSection
Aggregating events: elapsedTimeIndicates the time interval during which some number of identical events occurred2.4.6.2
Aggregating events: repeatCountSpecifies the number of occurrences of identical events within a specified time interval2.4.6.1
AssociatedEventsAllows for associated Common Base Events to be identified and grouped together so that they can be interpreted as a group by an appropriate association engine2.4.11
AssociatedEvents: associationEngineSpecifies the application that establishes the association among events by value or by reference2.4.11.1
AssociatedEvents: associationEngineInfoSpecifies the reference to the AssociationEngine element2.4.11.2
AssociatedEvents: resolvedEventsContains an array of globalInstanceIds that identifies those events that are associated with this event2.4.11.3
AssociationEngineIdentifies the application (association engine) that establishes the association among related events2.4.12
AssociationEngine: idSpecifies the primary identifier for the AssociationEngine element2.4.12.3
AssociationEngine: nameSpecifies the name of the application that creates the association2.4.12.1
AssociationEngine: typeDescribes the type of association created by this association engine2.4.12.2
ContextDataElementDefines the context or contexts that an event refers to2.4.9
ContextDataElement: contextIdThe actual content value for the context specified by reference2.4.9.4
ContextDataElement: contextValueThe actual content value for the context specified by value2.4.9.3
ContextDataElement: nameSpecifies the name of the application that created the contextDataElement 2.4.9.2
ContextDataElement: typeSpecifies the data type of the contextDataElement2.4.9.1
ExtendedDataElementOffers a standard way to extend a Common Base Event to provide supplemental information in a consistent format2.4.10
ExtendedDataElement: childrenRefers to other related ExtendedDataElement properties to specify the structured list of data elements2.4.10.5
ExtendedDataElement: hexValueThe actual content value for the extendedDataElement specified as a hexValue2.4.10.4
ExtendedDataElement: nameProvides a name used to identify and qualify the data contained in the ExtendedDataElement2.4.10.1
ExtendedDataElement: typeSpecifies the data type of the values for the ExtendedDataElement2.4.10.2
ExtendedDataElement: valuesThe actual content value for the ExtendedDataElement specified as a value2.4.10.3
extensionNameCommunicates the nature of the content found in the ExtendedDataElement property2.4.5
globalInstanceIdProperty provides a globally unique identifier that can be used to refer to or index the specific event2.4.2
localInstanceIdProvides a locally unique identifier that can be used to refer to or index the specific event2.4.1
Messages: msgContains the human-readable text that accompanies the event2.4.8.2
Messages: msgCatalogThe name of the message catalog that contains the locale-dependent message template2.4.8.8
Messages: msgCatalogIdRetrieves the locale-dependent message template from a message catalog2.4.8.7
Messages: msgCatalogTokensAn array of string values that contain substitution data used to render an internationalized message as fully formatted text2.4.8.10
Messages: msgCatalogTypeSpecifies the format of the msgCatalog2.4.8.9
Messages: msgDataElementProvides additional information about the message2.4.8.3
Messages: msgIdSpecifies the message identifier for the event2.4.8.4
Messages: msgIdTypeSpecifies the format of (how to interpret) the msgId property2.4.8.5
Messages: msgLocaleSpecifies the locale for which the message is rendered2.4.8.6
priorityDefines the importance of the event to establish a relative order in which the event records should be processed2.4.4
sequenceNumberSequences events in a logical order2.4.7
severityIndicates the severity level of the event from the point of view of the component that reports the event2.4.3



Back to top


Download

DescriptionNameSizeDownload method
At-a-glance Common Base Event properties guideac-cbeproperties.html30KBHTTP
Information about download methods


Resources

Learn

Get products and technologies
  • Autonomic Computing Toolkit: You can start your autonomic computing journey with the latest version of the Toolkit.

  • Common Base Event Specification v1.0.1: This specification defines a mechanism for managing events in business enterprise applications and how to communicate events in the autonomic computing model.

  • IBM trial software: Build your next development project with trial software, available for download directly from developerWorks.


Discuss
  • Dave Bartlett's blog: Listen in as Dave talks about integrating autonomic computing standards and capabilities throughout every layer in a system.


About the author

Kane Scarlett is the editor of the Autonomic computing technology zone for developerWorks. His past publishing work was with such magazines as Unix Review, Advanced Systems, and the -World publications (Java-, Sun-, NC-, Linux-), as well as some little oddball journals like National Geographic Magazine.




Rate this page


Please take a moment to complete this form to help us better serve you.



YesNoDon't know
 


 


12345
Not
useful
Extremely
useful
 


Back to top