A better and faster migration from ODI 11 to ODI 12
ODI12 has introduced Mappings to replace the ODI 11 Interfaces, what makes the ODI 11 Interfaces obsolete in ODI12. With an ODI 11 Interface you could define just one target. To create more complex data flows in ODI11 you needed to define and use Temporary Interfaces. With ODI 12 Mappings you can have more than one target and in one and the same Mapping you can create complex workflows, where in ODI 11 you needed several Interfaces.
Allthough ODI 12 comes with an Upgrade Assistant (Oracle UA) that converts the ODI 11 Interfaces to ODI 12 Mappings, the migration is troublesome. In our white paper we'll discuss the issues faced with Oracle's migration tool and how our UA+ add-on solves them.
Read the entire story in the document below.
Migration from OWB to ODI
Since Oracle will stop supporting OWB, users are forced to migrate their OWB projects to ODI. Although they have different features, OWB and ODI are conceptually similar. Our intelligently automated conversion service allows an effortless migration from OWB to the ODI equivalents.
Read the entire story in the document below.
Develop software faster with less errors, using DevOps.
DevOps focusses on the interdependence of users, software development and IT operations. It stresses the importance of communication, collaboration and integration between all relevant stakeholders be it the business, software developers or people responsible for operations and production.
In this document, we'll explain how we can achieve this DevOps way of working by implementing an efficient Application Lifecycle Management (ALM) solution.
Read the entire story in the document below.
What is Lifecycle Management
The purpose of Lifecycle Management is to simplify and improve the development process. It addresses the development process and related downstream activities, the production environment (deployment) and the upstream activities like requirements management and issue tracking.
In general the LCM tool needs to serve the complete process and be independent of the development methodology used (e.g. waterfall, spiral, prototyping, agile,...). It should pay attention to the needs of all stakeholders and offer them freedom of tools choice.
The benefits of using LCM are:
- Fewer errors and faster results
- Reduced application development, testing and deployment costs
- Improved quality (CMMI) and traceability
Read the entire story in the document below.
Lifecycle Management for Oracle Data Integrator
To handle end-to-end Life Cycle Management for ODI, we combine the VCR4ODI adapter with IKAN ALM. In ODI we can use the VCR4ODI adapter to version our ODI projects in Subversion. The versioning of ODI projects will aid in parallel development and proper release management. Once versioned, IKAN ALM will build and deploy our projects automatically.
The entire ODI Life Cycle process is automated, well managed and no longer exposed to the risks of human mistakes.
Read the entire story in the document below.
Lifecycle Management for Oracle Warehouse Builder
By combining the VCR4OWB adapter with IKAN ALM we've created a complete, automated LCM solution for OWB. First of all VCR4OWB allows you to version the OWB objects into a Versioning Repository which enables concurrent versioning at object level.
Once all OWB and non-OWB objects are versioned, IKAN ALM can Build and Deploy your application. Deployment can happen over a customizable Lifecycle using different physical environments including pre- and post-approvals.The OWB processes can be integrated with other processes or tools in order to come to one global “release” embedding OWB and non-OWB elements.
Read the entire story in the document below.