Guardium Enterprise Integrator: Advanced features of the TEXT database driver
JonasHirner 2700000YE4 Comment (1) Visits (4950)
In a recent Guardium implementation project I was asked to import external data into one of the Appliances and join it with monitored data. The information that should be integrated was provided as comma separated values in a text file.
When the enterprise integrator feature is licensed, this can easily be done by creating a custom table and using a Guardium TEXT datasource for the import. However in my particular case I was facing codepage conversion problems as well as format mismatches on some timestamp values.
While crawling through the Guardium log files and error messages, I noticed, that the TEXT driver that is installed on the Appliances actually seems to be a third party tool developed by HXTT (htt
I then tried to gather more details on that product and find some documentation on how to deal with format and codepage conversion. As a matter of fact the needed functions (along with a lot of other useful features) are directly provided by the TEXT driver. They simply aren´t mentioned in the Guardium help books.
Using the “connection property” you can tweak the import options when creating a TEXT datasource. Different parameters are separated by a semicolon.:
As an example, the property string could be set to:
This would limit the number of read rows to 10 and set a specific codepage. To handle the conversion, I used “timestampFormat” as well as “charSet”.
A detailed list and description of possible properties can be found in the HXTT installation documentation (htt