Automated ODI development process from Development, through Test and QA to Production

Automate your ODI development life cycle with DevOps and Toolchain Orchestration

Release your ODI software faster using Continuous Deployment, flexible version control and test automation

ODI development lifecycle automation and devops toolchain orchestration

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 Oracle ODI versioning
  • 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

    Examples:

    • 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?

    View all features...
 
ODI development lifecycle automation and devops toolchain orchestration

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.

Use the planning, issue tracking tool of your choice; With our generic ITS-plugin we link your requirements to the creation of your releases (deployment archives) and the deploys to your test, qa and production repositories

Here you use the ODI Studio to do your development job. Once development is done you version your code.

Versioning 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.

As part of the create step we assemble all ODI objects in a deployment archive, ready to deploy to your test or production repositories.

During verify you test. We can populate a test repository so you can do your test manually or we can apply automated testing. Use the testing tool of your choice, we will make sure it is Orchestrated as part of your life cycle.
We Package during the Create step. During the Deploy steps you can apply selection criteria to indicate what exactly of the archive you want to deploy or not. Examples are: deployment from dev to test of topoplogy? (probably not).
The last step in the process: deploy to the production process. Here you can indicate if you want to deploy all (development) objects or just the scenarios. If you want to run additional steps, you can. We will Orchestrate them and make sure they run as desired.

Leading you from idea to implementation in 3 simple steps

Discovery

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.

Form by ChronoForms - ChronoEngine.com OK, let's start

Pilot (POC)

The POC takes only one week. The first two days we will install IKAN ALM, and set up your desired life cycle. The remainder of the week you are free to test the solution and try out different scenarios.

Go!

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

ODI life cycle setup

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.

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
ODI archive using continuous integration

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.

rest

What our customers are saying

  • RMA client picture

    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."

  • Constellation Brands client picture

    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."

  • Vivium client picture

    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:

    Benefits of IKAN ALM Business Case What makes IKAN ALM unique
  • GMF client picture

    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"

Already using Jenkins or Cloudbees as your automation server?

All of our solutions (for z/OS, SAP and ODI) are also available as commercial Jenkins Plugins.
(More information coming soon)

IKAN ALM for zOS, SAP and ODI also available as Jenkins Plugins

  • Out-of-the-box experience and well documented
  • Includes support and maintenance plans

Get more info on Jenkins Plugins for ODI

CloudBees TAPP Premier partner logo
We are an official CloudBees Technical Alliance Partner (TAPP).

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 notification) 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.

These companies already use IKAN ALM

A list of our clients: Vivium, Reale Mutua, GMF and Constellation Brands