In my previous blog, I showed how to do an ELT from Oracle DB to XML in ODI.  Every ELT uses a Loading Knowledge Module (LKM), which describes how the data is loaded from one system to another, and an Integration Knowledge Module (IKM), which describes how the data is integrated in the target system. These Knowledge Modules are fully extensible and can be edited from within ODI Studio.

Oracle Data Integrator (ODI) is Oracle's data integration platform engineered to provide fast and easy data transformation and data integration processes, through E-LT (Extract - Load Transform) mechanism, between different technologies.  For example, using ODI's transformation mechanism I can create daily snapshots of my data residing in an Oracle DB and store these snapshots in a XML format.  These XML snapshot files can serve as XML payloads for an external web-service to consume this data.

Your BPM project is ready to "Go-Live" and you are excited about finally reaching this point. You are thinking about your creation and all the countless hours spent discussing requirements, revisiting and changing them, creating robust processes, designing and executing flawless architecture, and following best practices while writing code.  But no creation can sustain for long without a plan for maintenance.  No matter how bulletproof the code is and how many testing iterations you have gone through, there will be changes requested or defects discovered in production.