During a recent conversation with a prospect it happened again: Oracle ODI 12 has now a Life Cycle Management solution. End of story.

Luckily an Oracle employee took part in the discussion and admitted that ODI 12 had now versioning and that indeed versioning is just one part of Life Cycle Management.

I admit and know that you and many others are confused  when Life Cycle Management (LCM) or Application Life Cycle Management (ALM) or DEVOPS is brought to the table. Or when vendors like Atlassian with JIRA or HP with HPALM are being seen by customers to offer full ALM capabilities.

When we ask you the question “do you know what LCM or ALM is?” we sometimes get the answer yes and we have it as we have JIRA or HP ALM. Well LCM or ALM is more than issue tracking or testing.

Read more ...

I know this has nothing to do with Life Cycle Management for ODI, but a number of people asked if we could help with migrating their OWB legacy to ODI 11 or ODI 12.

That is why I would like to address our solution we call “intelligently automated” conversion. Together with Database & Technology Italy, an Oracle Gold Partner we have an unique offering. For more information, see our OWB to ODI page or download our OWB to ODI Migration White Paper

Read more ...

Last week we talked about partial build (and deployment).  Partial Build gives us the ability to just select these ODI objects (and dependencies) that have been changes since the last “Build”.

The next major step is deploying all or just the changed objects to a Test or Production Repository. Before you can do that you need to have your Architecture in place. What project streams do you have, what  is your Life Cycle and what are your target Repositories?

With project streams we refer to how your development is organized: one stream for ongoing development, a stream per release and one for emergency changes or hot fixes.

Read more ...

Last week we talked about Parallel Development. By applying some Best Practices we showed how you could several ODI projects in parallel and this without having to worry about merging.

Next step in the cycle is on how you deploy each individual project and more especially how you deploy often and fast with a minimum of overhead. Or how you put DEVOPS, being Continuous Integration and Continuous Deployment in practice.

Partial Build is the answer

The answer to this question is quite simple. Can you identify the  what has or is changed compared to what you have currently in production? The answer to this question is to identify the modifications and there are two ways how you can solve that. Partial Build is the answer. What do we mean by Partial Build?

Partial Build is the answer

Read more ...

Oracle Data Integrator offers many possibilities to re-use objects. One and the same model can be used by many different projects, scenarios generated by one project can be re-used by other projects, models can use knowledge modules from projects and so on... While this powerful feature has a positive impact on your workflow, it does come at a price.

ODI panels examples

Chances are since you're using ODI, you won't be working on just two simple projects, you will be working on many and large data integration projects which might change over time. Not to mention the creation of new projects which will in their turn be dependent on objects created for other projects.

Read more ...

Get free insight!

Let's analyze your current development and release process, and show you how to make it much faster and 100% reliable.

Yes, I want insight

Do you want to recieve the latest news and updates?