CA Automic Release Automation

Blueprint for Achieving Continuous Delivery for Packaged Apps

Applying Agile methodologies to core backend or COTS applications is the crucial first step to building a Continuous Delivery pipeline for these systems. Stabilizing the environment(s) while ensuring there are no undocumented steps, and that both automated and manual tasks are fully documented, is critical. Automic will assess your current status, then define milestones and a project roadmap. CA Automic Release Automation is introduced here to establish a basic foundation upon which your digital transformation will be built.

Key Featured Resources

Siebel Autodiscovery 

Onboarding demo 

Webinar: End-to-End Deployment Pipeline 

Now is the time to take your COTS application one step further and achieve near zero downtime deployments. We do this by building on the first step, where we have laid a foundation for automation and created some basic workflows. Using CA Automic Release Automation’s modelling capabilities we will now include your environments and complete deployment workflows into a Continuous Delivery pipeline, which you can operate from within CA Automic Release Automation.

Key outcomes for this stage include: 

  • Versioning of releases.

  • Controlled automated promotions across environments.

  • Fully-automated production deployments.

Key Featured Resources

Siebel Non-repository Object Migration Demo 


ARA for Siebel Demo 


CA Automic Release Automation New Features: Managing the Deployment Pipeline 


With your Continuous Delivery pipeline fully automated, we now turn our attention to extending automation across your infrastructure and end-to-end processes using Automic’s advanced orchestration and self-service capabilities. This is also where “hot” or zero downtime deployments can be introduced safely into your environment.

Watch Key Feature Demos

Continuous Delivery for Siebel: Repository Migration  

Orchestrate the tool chain with AWS 

CA Automic Release Automation New Features: Main Infrastructure Delivery 

Now you have some of your main applications already Continuous Delivery enabled, we extend this capability across your entire portfolio. In this final stage you will implement end-to-end Continuous Deployment into production from multiple applications and teams. This is made possible with approval gates, compliance considerations and ITSM practices/tools that were included in the orchestration of deployments in previous steps. It allows all updates, changes and patches to all legacy/COTS/backend applications to follow Agile methodologies, join DevOps initiatives, and provide agility to the enterprise.

Within this phase, organizations will:

  • Bridge the gap between Continuous Delivery and Continuous Deployment.

  • Ensure production deployments are fully automated, on-demand and adhere to security, approval, compliance and change policies.

  • Enable you to on-board additional legacy systems, COTS software and backend applications.

  • Enable your organization to deliver legacy, COTS and backend applications following modern Agile methodologies.

  • Achieve closer alignment to DevOps and digital transformation initiatives.

Key Featured Resources

Quocirca: Business-Driven Application Release Automation

On-Demand Webinar: How to Achieve Continuous Delivery Without Downtime

How DevOps and Continuous Delivery are Redefining Application Delivery in the Enterprise

Find out more

Try Automic V12.1