Migration

Migration issues discussed here include the following:

Migration from AlphaWorks Generic Log Adapter to TPTP Generic Log Adapter

The schema for the TPTP Generic Log Adapter is very different than that of the AlphaWorks version. That, along with the fact that the TPTP 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 TPTP version.

The recommended means of migration is to open the existing configuration and context files with an editor 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.

Replacement of #USE_PREVIOUS directive

The #USE_PREVIOUS directive that is available in the AlphaWorks version of the Generic Log Adapter is not included in the TPTP version. Instead, its functionality has been replaced with the Use Previous Match Substitution As Default property. See the parser component property list on the Configuration file structure page in Related References for more details.

Replacement of #ADAPTER directive

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 TPTP 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 values:
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"

Migration of rules from Common Base Event 1.0 to 1.0.1

The Generic Log Adapter for TPTP 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
Overview of the TPTP Generic Log Adapter
Common Base Event objects

Related tasks
Developing log parsers using TPTP Generic Log Adapter framework
Creating an adapter using regular expression rules
Creating an adapter using a static parser Java class

Related references
Configuration file structure
Common Base Event objects
Generic Log Adapter editor
Regular expression grammar