Versioning, Automated Build and Deploy for
Oracle Warehouse Builder
Life Cycle Management is a key element in the successful implementation of lean software development. Our solution extends your OWB development process with versioning, and automates the deploy processes for maximum efficiency.
Versioning
A dedicated versioning component (VCR4OWB) enables developers to work together. Including Checkout, Commit, Export, Remove and Status functionalities.
Automated Build
Once a single project or a complete Repository is versioned, it is built automatically. The build result is stored as an archive for later use.
Automated Deploy
A build archive is automatically deployed to test and productions environments according to the rules defined in the project life cycle.
This helps you develop faster yet cheaper and deploy more frequent
Higher quality
The versioning functionalities included in our solution, guarantee a more sound code base. On top of that, we support parallel development. This ensures transparent and reliable releases of your application.
More frequent deploys
Automating the build and deploy processes enhances the quality of the developed code. The process will be reliable, repeatable and auditable, and you will be able to deploy more frequently.
Earnings and Savings
More frequent and qualitative deploys result in a faster time-to-market. The automated process eliminates human mistakes, reduces the costs and frees up time that can be spent on other tasks.
It’s easy, see how it works
1. Versioning
The VCR connector (VCR4OWB) allows you to version individual objects (mapping, table, ...) or a whole list of objects (mappings, modules, project) into CVS. VCR4OWB makes use of the OWB Experts technology and avoids useless version changes, such as timestamp changes, through intelligent diff parsing.
2. Build
Once the objects are versioned, they are retrieved from the VCR and imported into the local OWB instance (build machine) by IKAN ALM. A Tcl-script (OMB*Plus scripting) is created dynamically, which describes all steps and dependencies for the later OWB-deploy.
3. Deploy
The deploy process consists of importing the metadata into the deploy OWB-repository and executing the Tcl-script to deploy everything into the target database. Deployment can happen over a customizable life cycle to one or more physical environments.
Pricing plans
Our affordable subscription plans include everything you need: versioning, automated deployment and life cycle management for your entire OWB environment, from development to production. Interested in one of our plans? This email address is being protected from spambots. You need JavaScript enabled to view it. for more details.
1 year
Unlimited users
Maintenance & support
included
per month
0%
3 years
Unlimited users
Maintenance & support
included
per month
10%
5 years
Unlimited users
Maintenance & support
included
per month
20%
For more information
Would you like a live demo?
If you would like to watch a live demo of this solution, use the button below to request an appointement. We will contact you as soon as possible.
Yes, give me a live demoDo you need more information?
Do you still have many question unanswered? Click the button below to have us contact you.
Yes, give me more information
Do you want to migrate from OWB to ODI?
Yes, I want to migrateOur intelligently automated conversion service allows an effortless and 100% accurate migration from OWB to the ODI equivalents.