It is Jeroen talking. Do I really need to give any other reason for attending? As I am missing the beginning of the partner conference, I need one. I am interested to hear their approach with xDB for this problem. They conceived of it just before the last EMC World, but it wasn’t fully flushed out. Want to see how real this is.
- Also known as XML Archiving
- Why does this topic matter?
- >50% of apps are legacy in typical enterprise portfolios
- 70% of IT budgets are for Existing systems
- 2 of 3 CIOs say their organizations do not have a single view of legacy system data for compliance reporting
- Data is important, can’t just get rid of it.
- Many legacy systems are written in Cobol, over 220 billion lines of Cobol code which is 80% of all code [to be fair, Cobol is very line intensive]
- The hardware it is running on is getting old and harder to repair/replace
- Solution Design Goals: Quick and easy search, Maintain Chain of Custody, Support Data and Unstructured Content, Standards-based, Keep costs low
- Can convert relational database to XML and then convert it back in order to validate no data loss
- Need to use a web-based UI to access the data, they have an XML Archive Client
- Do not pick one ETL tool for every scenario. Pick one for the application
- Using Dynamic Delivery Services for the storage and UI
- Template driven, trying for zero coding
- XForms, XSLT, XProc are all inputs to create the Archiving Application UI automatically
- Two versions, Standard and Extended, Extended has unstructured data and data compliance leveraging Kazeon
- Also a consulting offering around this solution. They have a financial analysis tool to prove ROI
- As always a demo
This was my last note-taking session. Off to the partner meeting, which I think is public, but it doesn’t really lend itself to this. I’ll tweet anything new and write an article if it becomes very interesting. See you next year.
All information in this post was gathered from the presenters and presentation. It does not reflect my opinion unless clearly indicated (Italics in parenthesis). Any errors are most likely from my misunderstanding a statement or imperfectly recording the information. Updates to correct information are reflected in red, but will not be otherwise indicated.