About profile files
A profile file contains information that describes the designated entity rather than what the entity does. Examples of the type of information contained in a profile file are age, home address, and telephone number.
Profile data is not a requirement for an entity. However, if profile data is not defined, qualifier components cannot be created for the entity. When a profile is not described, the descriptive information needs to be included in each transaction record if it is needed as a criteria of a trigger system.
Profile data can be read from database tables, from an ASCII flat file format, or from a combination of database tables and a flat file feed.
The flat file format provides the highest engine throughput.
An entity associated with profile database tables must have a connection string to the table; it must also have one field designated as the key. This field is the common identifier on all data sources associated to the given entity.
An entity defined as having a flat file profile must have that file included with each engine run. A flat file profile must have the same characteristics as the flat file described above for transaction files.
There must be a single data line record for each unique ID in the transaction files. Transaction file records without an associated profile record are ignored. Profile records without an associated transaction file record are ignored. In both instances, extraneous records impact processing efficiency.
Here is an example of a simple profile file:
ID|AGE|ZIP
001234|25|11111
002941|55|22222
005555|31|33333
006789|60|44444
100382|18|55555
About naming profile files
Event Enabled Time Queue (EETQ) Profile Files
Copyright IBM Corporation 2012. All Rights Reserved.
