case study: jack henry & associates automates application deployments through crises with...

World®’16

CaseStudy:JackHenryandAssociatesAutomatesApplicationDeploymentsThroughCrisesWithDRArchitectureandReleaseAutomationChristopherJamesFarrar- Adv.Sys./NetworkAdmin.- JackHenryandAssociates

DO5X43S

DEVOPS

2 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

©2016CA.Allrightsreserved.Alltrademarksreferencedhereinbelongtotheirrespectivecompanies.

Thecontentprovidedinthis CAWorld2016presentationisintendedforinformationalpurposesonlyanddoesnotformanytypeofwarranty. The informationprovidedbyaCApartnerand/orCAcustomerhasnotbeenreviewedforaccuracybyCA.

ForInformationalPurposesOnlyTermsofthisPresentation


Abstract

JackHenryandAssociates,Inc.(JHA)providesmorethan300productsandservicesthatenableitscustomerstoprocessfinancialtransactions,automatetheirbusinessesandsucceedinanincreasinglycompetitivemarketplace.

AsthecompanystreamlinesitseverydayapplicationdeploymentwithCAReleaseAutomation,disasterrecoveryhasbecomeamajorconcerntomakesurethatdeploymentofthedifferentapplicationscontinuesintheeventofnaturaldisasters,attacksorinfrastructurefailures.JHAdevelopedadisasterrecoverystrategy,wherethesupportingfilesandsystemsforreleaseautomationweresetupandmaintainedinadifferentdatacenter.

ThissessionwilldiscusstheprocessandthechallengesJHAencounteredwhileimplementingitsdisasterrecoveryarchitecture,andtheresultingsolutionthatensuresbusinesscontinuity,eveninthemostdisastrousofcircumstances.

ChristopherJamesFarrarJackHenryandAssociatesAdv.Sys./NetworkAdmin

© 2016 Jack Henry & Associates, Inc.®4

Dates contained in this presentation are provided as estimates only and can be changed at any time at the sole discretion of Jack Henry & Associates, Inc. This information may not be incorporated into any contract and should not be relied upon in making purchasing decisions.HANK YO FOR THEOPPORTUNITY TOSHARE JHA’S STORY

Legal Disclaimer


What’s My Story?

Chris FarrarAdvanced Systems/ Network Administrator for Jack Henry and Associates

Current Role - Release Automation SME§ Work with development/ Operations

teams to engineer RA deployments§ Release Process design and

DevOps advisor

Previous Experience§ Enterprise deployment automation

and scripting§ Windows XP upgrade for retail

1200+ client environment


Importance of Disaster Recovery to JHA

What are the business drivers?

Business continuity is our primary business driver

Since CA Release Automation deploys code quickly and efficiently, it is critical to a DR strategy

JHA needs to be prepared to stay in a DR scenario for an extended period of time, this includes updates

JHA is prepared for the worst case scenario in a major disaster event. If there are issues with the secondary site then we are prepared to re-build a production or DR site on the fly


How Does Jack Henry Use CA Release Automation


Release Automation Adoption

Card Processing Solutions Release team is responsible for coordinating release activities for dozens of applications

These applications span Windows, Linux and Mainframe platforms

Deployment process varies greatly

We look to CA Release Automation as a way to centralize and standardize deployments across the various applications and platforms.


Release Automation Adoption – Current State

A Work in Progress§ We currently deploy four applications via CA Release Automation§ SharePoint Dashboarding§ Limited Reporting capabilities at this time

CA Release Automation Activity§ Deploy binaries§ Notifications§ Transformation of configuration files from environment to environment§ Deploy Database scripts§ Rollback§ Approvals


Release Automation Adoption – Flagship App

Customers use this web application as a means to monitor ATM usage, state and profitability.

Web Portal for ATM Monitoring


Release Automation Adoption – Results So Far

Since using CA Release Automation for web portal application deployment

Deployment times reduced (less than five minutes start

to finish)

Eliminates Human Error

Scripted notifications

Archived data for reporting

purposes and audit


What Is the Problem and How Do We Solve It?


Problem/ Solution – HA Architecture

Image taken from CA Wiki at https://docops.ca.com/ca-release-automation/5-5-2/en/installation/install-to-provide-high-availability

HA architecture was supported by CA out of box


Problem/ Solution – Single Points of Failure

Image taken from CA Wiki at https://docops.ca.com/ca-release-automation/5-5-2/en/installation/install-to-provide-high-availability

Single points of failure at Database server and Repository server


Problem/ Solution – Jack Henry Goals for DR

Jack Henry standard requirement – all applications must have a DR counter part to fail over to

Need to be able to deploy production applications/ updates in the event of a total site failure§ RA functionality§ Artifacts§ Access to agents


We’ve Identified the Single Points of Failure…How Do We Get Around Them?


Architecture Overview –DR RAC, SQL, Repository


How Do We Synchronize SQL and Repository Servers?

Replicate


Replication/ Synchronization MethodsDFSR for Nexus Repository

%ReleaseAutomationServerRepository%\sonatype-work\nexus

Copy Don’t CopyConf IndexerLogs Timeline\indexPlugin-repositoryStorage


Replication/ Synchronization MethodsSQL Replication

Log shipping§ More of a manual method but other more automated methods available

(SQL AlwaysOn)§ Due to infrequency of need for SQL failover (twice annually)§ Adds several manual steps to DR failover procedure

§ Disable log shipping jobs§ Script executed to pull DR Database out of Read-only


What Happened When We Flipped the Switch?


Failover Testing Results – 1st Round

§ CA Release Automation worked but could not deploy…

§ MMOPPSRADEXEC01 cannot connect to DR RAC

§ “Utility” server type needs to be changed from RAC to DR RAC

§ Usual permission / access issues


Failover Testing Results – 1st RoundLessons Learned

Opened up connectivity to Dev execution server from DR RAC

Included Utility server change over in procedure


Failover Testing Results – 2nd Round

§ Able to deploy!

§ Dynamic Duration reporting parameter references CA Release Automation database, this will need to be updated

§ Process adjustments


Failover Testing Results – Future State

Scripted solution for changing utility server type

More automated SQL replication

Integrating management servers to HA


CA Release Automation can now deploy web portal application and others in the event of a total site failure at the primary data center.

Epilogue

If the DR environment for Portal is not fully updated, then updates could be deployed quickly and efficiently.

If the DR environment is destroyed and new servers were created, Portal could be deployed quickly.


Questions?


RecommendedSessions

SESSION# TITLE DATE/TIME

DO5X09SGMFinancialTransformsAppDeploymentswithCAReleaseAutomationand“GoldDeploymentStandards”

11/16/2016at03:00pm

DO5X07SJeweler’sMutualInsuranceStreamlinesComplexAppDeployw/CARA

11/17/2016at12:45pm

DO5T19SGMFinancialBuildsaSustainable,Holistic,ContinuousDeliveryPractice

11/17/2016at04:30pm


MustSeeDemos

ModernizeAppDeliveryIntegratedCDTheater5- DOV501P

DeliverTestDataFasterTestDataManagerTheater5- DOV511P

DeliverBetterAppsServiceVirtualizationTheater5- DOV507P

OrchestrateYourReleaseReleaseAutomationTheater5- DOV513P


Stayconnectedatcommunities.ca.com

Thankyou.


DevOps– ContinuousDelivery

FormoreinformationonDevOps– ContinuousDelivery,pleasevisit:http://cainc.to/PiTFpu

case study: jack henry & associates automates application deployments through crises with...

Technology