Life Cycle Management (LCM) for ODI
Software needs to be released faster than ever to keep up with constantly changing business requirements caused by competition and digitalization. A well managed Continuous Deployment process will guarantee high quality releases and standardize you team and workflow. Use these tools in every step of the life cycle you think are best for the job!
- Versioning: use the Oracle ODI versioning or our VCR4ODI component
Life Cycle Management:
For each ODI project you can have one or more life cycles: one per VCR trunk or Branch You decide how a life cycle looks: the classic DTAP or longer or shorter? In each level of your life cycle you decide what happens using our predefined Phases
- Create a deploy archive: complete repository or just a delta?
- Run automated tests after you populate a test repository
- Apply database changes?
- Revert to a prior version?
- Approval management needed?
Orchestrate your ODI toolchain
Having the best tool for every step in your life cycle is one thing, but how to Orchestrate all of them? With our solution you can define and implement your own toolchain and we’ll make sure that they communicate with each other and your life cycle is executed in the right order.
Here you use the ODI Studio to do your development job. Once development is done you version your code with our VCR4ODI connector.
The VCR4ODI connector allows you to work at the individual object level so that you do not need to commit or restore a whole project, lock objects to prevent others from working on the same objects you are working on, restore objects from a previous version. On top of that, VCR4ODI will calculate all the dependencies between objects, and will automatically create a new version for Projects, Models, Scenarios and the global objects that are used.
As part of the create step we assemble all ODI objects in a deployment archive, ready to deploy to your test or production repositories.
Leading you from idea to implementation in 3 simple steps
Together we analyze your current setup and your development and release process. We will define the desired state and the 3 KPI's, and then prove them during the Proof of Concept.
The POC takes only one week. The first two days we will install IKAN and VCR4ODI, and set up your desired life cycle. The remainder of the week you are free to test the solution and try out different scenarios.
One of the outcomes of the Proof of Concept will be your business case: is it worth the investment and what are the benfits? Together we will define the final implementation and training plan.
ODI development at the pace of your business needs
Version and restore single projects or complete repositories outside of ODI using Subversion.
The ODI versioning component (VCR4ODI) will let you work work at the individual object level so that you do not need to commit or restore a whole project. It also calculates all the dependencies between objects.
Get free insight!
Let us give you personal insight on how DevOps can make your ODI development -and release process much faster and reliable.Yes, give me insight
Set up your desired life cycle, standard DTAP or whatever you need.
Define a Build level (the ODI objects and related dependencies to archive) and Test and Production levels that are used to deploy to ODI Test and Production repositories. Deploys can be made approval based.
Use Continuous Integration to create a full or incremental archive of single projects or a complete Repository.
Automatically deploy entire projects or choose to deploy just objects with or without dependencies, taking topology into account or not. Add more steps, for testing or database changes, if necessary.
What our customers are saying
Antonio Motta - ICT infrastructure manager, RMA (Italy)
"Our goal was to have one product, that managed the whole build and deploy process for all the platforms we used to deliver our IT services. We saved more than 2/3 on the software maintenance cost."
Jim McGrath - Data Warehouse Manager, Constellation Brands (USA)
"My internal team was excited about the possibilities your software offers and is anxious to hear next steps. Additionally, you should know that I have ensured my team knows the level of effort and support your team has provided.
It is hands down the best support I have seen from any vendor I’ve worked with."
Willy Mutsaerts - Technology Architect and Software asset management, P&V (Belgium)
"IKAN ALM allowed us to modernize our mainframe development as we wanted to use an eclipse based development environment and needed to have a compatible life cycle management solution to replace our current mainframe only version control software.
And IKAN ALM allowed us to interface with the mainframe and has extensive customization possibilities."
Watch Mr. Mutsaerts talk about IKAN ALM:
Jerome Rouil - IT Team Manager, GMF COVEA group (France)
"We did a POC to verify if IKAN ALM could support our different ways of deploying (on different types of platforms), our current way of doing development and the build and deploy scripts we were currently using.
IKAN ALM allows us to work from everywhere, and to reuse existing scripts. We could use our existing security system (LDAP), SMTP for messaging and notifications.
We use IKAN ALM for all our JAVA applications and SAS reporting that are deployed to 30 different locations"
Guido Klopper - IT Manager Business Intelligence, Tata Steel Group (Europe)
"After a detailed comparison and a successful POC, we concluded that IKAN ALM would be the best option for us.
Installation and customization took about a week. Now we have not only obtained significant savings, but also more frequent, faster and reliable deploys, and happy business users"
People are choosing DevOps because they want
High quality releases
As developers will version their code and as parallel development is supported you will have a more sound code base. Once the code is versioned, the build and deploy processes are fully automated. You can build and deploy as many times and as fast as you want.
More frequent deploys
A complete and automated process (build, deploy, approval and notiﬁcation) is triggered once a developer commits his code to the version control repository. This process is reliable, repeatable and auditable so you can you can deploy more frequently.
Lower development costs
More frequent and qualitative deploys means happy business people since they'll have their desired functionality available faster. The automated process eliminates human mistakes and allows people to do more interesting work. A true win/win.