The schema for the Hyades Generic Log Adapter is very different than that of the AlphaWorks version. That, along with the fact that the Hyades version supports Common Base Event version 1.0.1, requires that a manual migration be performed on all existing configurations and contexts created with the AlphaWorks Generic Log Adapter before they can be run on the Hyades version.
The recommended means of migration is to open the existing configuration and context files with an editor (Internet Explorer is a great choice) and copying the rules individually to the clipboard then paste them in the Adapter Configuration Editor. Be aware that the editor you are copying from must support XML or your entity references will be corrupted when they are saved to the new file. Also be aware that the classes that implement the context and the components have also changed.
The #USE_PREVIOUS directive that is available in the AlphaWorks version of the Generic Log Adapter is not included in the Hyades version. Instead, its functionality has been replaced with the ‘Use Previous Match Substitution As Default’ property. See the parser property list for details.
The #ADAPTER directive that is available in the AlphaWorks version of the Generic Log Adapter has been replaced with ‘Use Built In Function’ checkbox on the Substitution Rule in the Hyades version. The following Common Base Event properties support the use of the ‘Use Built In Function’ checkbox on the Substitution Rule and are shown with their generated value(s):
| Common Base Event Property | Generated Value |
|---|---|
| localInstanceId | <local hostIP address or "Unknown Host"> <current time in milliseconds> <log record's hash code> |
| globalInstanceId | 128 bit Globally Unique IDentifier |
| componentIndentification.location | <local host IP address or "Unknown Host"> |
| componentIdentification.locationType | "IPV4"/"IPV6" or "None" |
The Generic Log Adapter for Hyades supports Common Base Event 1.0.1. This means there will need to be minor changes made to older configuration rules to have them work correctly with the new schema. The primary difference is that the situationType property has been removed from the Common Base Event 1.0.1 specification and has been replaced by the Situation element. Rules now need to be written to identify which type of situation this message applies to. Additional rules need to be written to identify the specifics according to the type of situation.
Related concepts
Generic Log Adapter editor
Related tasks
Developing an end-to-end transform solution
Testing an adapter configuration file with the editor test views
Deleting an adapter configuration file
Related reference
Configuration file structure
Regular expression grammar
Generic Log Adapter editor icons
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.