In the old days, a Discovery Library Adapter was described as a Java component that exports the data from a certain product as an XML file that complies to the IDML XML schema format.
Well, since then a DLA has been described as a process to export data into this XML schema, without mentioning Java component, as the use of data integration tools, like Tivoli Directory Integrator, proved more effective to create an IDML file.
My goal is expand the mechanism to create DLA, and I always dreamed to create a DLA in perl. Well, here is the perfect opportunity:
The CA Spectrum DLA
This DLA is very simple and can be run in any machine
#!/usr/bin/perl
print "Go, talk to your CA representative and demand a change to CA's license agreement\n"
Done!!
Here is the deal: according the CA license agreement, CA owns the data it collects with its product, so other products can't retrieve it. So, it's illegal to write a DLA for CA. How stupid that it!!
Imagine if IBM Information Management group crafts the following statement: "The data stored in an IBM DB2 relational database belongs to IBM and can't be extract for the purpose of moving to another database."
Imagine if EMC puts a similar statement, saying: "The data stored in an EMC storage device belongs to EMC and can't be used to move data outside an EMC device."
The world would be unmanageable! As a customer, if I buy a certain product, I would expect that I can use the data collected in any way I want. Now with CA...
The solution: get rid of these CA. Your life will be better without them.
No comments:
Post a Comment