Blog posts

vendredi 20 mai 2016

When presenting our standard Life Cycle Management solution we often get the question about selectively deploying ODI objects that haven been committed to the version control repository.

Our standard implementation starts from an ODI Development repository and allows you to select from the added and modified objects these added and modified objects you want to commit or put in the version control repository. Once the code is committed, there is no way back. When you deploy (restore) to Test or Production Repositories all committed objects are taken into account. It is just a sequential process and a standard life cycle management process.

vendredi 6 mai 2016

Écrit par Rene De Vleeschauwer

Last week I told you I went to an event organized by the new HP, HP Enterprise. At the roundtable, one participant asked a question about rollback or revert.

The answer was a bit of a surprise to me. Mostly because we get this question often and you can hear in the question that in their opinion, you can’t do that. Why? Because it is not just a question of reverting the code, but what, amongst others, about database updates that happened?

Even when you tell the audience, yes we can, they are always skeptical. The answer you can do it, comforts them, but they still have doubts and don’t believe, when it happens, all will go well.

vendredi 29 avril 2016

Écrit par Rene De Vleeschauwer

Yesterday I went to an event organized by the new HP, HP Enterprise. At the end there was a roundtable and open discussion.

One of the (obvious) questions was on what the internal “lessons learned/benefits” were of applying DEVOPS internally at HP. The answer was short and clear: automation and repeatability.

By automation the process you streamline the operations, no room for human mistakes, everything is documented and repeatable. Questions were also about what with common components or database changes used by different applications? I personally didn’t agree with the answer where was stated that you can’t have one database shared by several applications. Would you?

vendredi 22 avril 2016

Écrit par Rene De Vleeschauwer

Per request we explain in more detail how our OWB to ODI conversion process works.

In this video we reveal our intelligently automated conversion service which allows an effortless and accurate migration from OWB to ODI. We'll talk about the different steps of the migration process: the assessment, conversion, testing and delivery of the ODI projects.

mercredi 20 avril 2016

Écrit par Rene De Vleeschauwer

Last week we spoke about our OWB to ODI conversion solution. Some people asked what the differences are with the Oracle Migration Utility.

To be clear: we can and have used the Oracle Migration Utility or our Utility. As a customer it is your choice, but you will certainly appreciate our features.

Here it comes, we support:

OWB 10.2 and above
ODI 11and above
all OS platforms

Page 2 sur 4

Blog

Commit: the point of no return? (lessons Learned)

Walk and don't look back (lessons learned)

Lessons Learned: DevOps

OWB to ODI Migration: How does this work?

Lessons Learned: our OWB converter versus the Oracle migration utility

Latest posts

Get free insight!