Pre-Con Ed: Best Practices: Enabling CA Workload Automation DE Artifacts to Move Applications Through the Development Lifecycle

World®’16

BestPractices:EnablingCAWorkloadAutomationDEArtifactstoMoveApplicationsThroughtheDevelopmentLifecycleJohnRooney,Sr.PrincipalConsultant,CATechnologies

MFX23E

MAINFRAMEANDWORKLOADAUTOMATION

2 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

©2016CA.Allrightsreserved.Alltrademarksreferencedhereinbelongtotheirrespectivecompanies.

Thecontentprovidedinthis CAWorld2016presentationisintendedforinformationalpurposesonlyanddoesnotformanytypeofwarranty. The informationprovidedbyaCApartnerand/orCAcustomerhasnotbeenreviewedforaccuracybyCA.

ForInformationalPurposesOnlyTermsofthisPresentation


Abstract

AsCAWorkloadAutomationDE(CAWLADE)userstakeadvantageofpre-

productionenvironmentstotestouttheirjobflows,ithasbecomemore

importanttobeabletoabletomigratetheCAWLADEartifactsfromDevto

productionwithaslittlemanualinterventionaspossible.Thistalkwilldiscussthe

strategiesandtoolstousetocreateanautomatedprocesstomigrateyourCA

WLADEartifactsthroughthelifecycleprocess.

JohnP.RooneyCATechnologiesSr.PrincipalConsultant


Agenda

MULTIPLEENVIRONMENTSANDSTANDARDS

USEOFSYMBOLICS

LEVERAGINGJAVASCRIPTS

IMEXUTIL – IMPORT/EXPORTUTILITY

1

2

3

4

Q&A

SUMMARY5

6


DecisiontouseyourEnterpriseWorkloadproductornot?

§ Istheapplicationbusinesscritical?

§ Doestheapplicationhaveabusinessimpacton:– Revenue– Service– Customer

Yes.ThenyouneedtousetheEnterpriseWorkloadsolution


OnceyouhaveaProductionWorkloadinstance,whatisthevalueofaPre-Productioninstance?§ Itisusedtoprotectproduction

– Minimizespotentialforproductionfailureoroutage– Testingofapplicationflowsbeforeproduction– TestingofApplicationIntegrationsinpre-prodenablesbetter

EnterpriseWorkloadusageandvisibility– PartofaDevOpsimplementationstrategy

§ TestingofCAWLADEserverupgradesandfixes


PotentialissueswithmultipleCAWLADEinstances

§ Manualefforttomigrateartifactsfromoneinstancetoanother– ManualefforttochangevalueslikeargumentsintheApplicationsand

Jobs– ChangeEventnamesandschedulingfrequencies

§ Hardtokeepartifactsinsyncwithoutnamingstandards


PotentialissueswithusingasingleCAWLADEinstances

§ Hardertokeeplogicalseparation

§ Applicationnameshavetobeuniquewithinaninstance– YoucannothavedifferentactiveversionsofthesameApplication

nameatthesametime– Needtochangeapplicationnames(likeaddingasuffix)toenable

multipleapplicationswithinthesameCAWLADEinstance

§ Hardertomaintainsecurityprofiles

§ Namingstandardsareamust!


ValueofcreatingNamingstandards

§ Easiertocategorizeartifactsforsearchingpurposes

§ Easiertodetermineownershiporresponsibility

§ Easiertocreateandonboardnewapplications


ValueofcreatingNamingstandards

§ Easiertocreateand/orclonesecurityrules

§ EasiertosubscribeinMonitoring– SubscriptiononlyallowsasingleApplicationFilter

§ EnablemovingapplicationsthroughadevelopmentlifecycleaspartofyourDevops strategy– Minimizeoreliminatemanualchangesbetweenstages


SuggestionsforCAWLADEArtifactNamingStandards

§ AshortBusinessApplicationnamecanbeveryusefulasaprefixforCAWLADEartifacts

§ Eventnamesshouldbeanindependentnameandnotassociatedwitharealuserid– ExampleDEV,TEST,PROD

§ AnothersuggestionforEventnamesistouseacustomernameordistributioncenternamewhenyouareusinganApplicationasaTemplateforamanytooneexecution– ExampleDC1,DC2,DC3


CAWLADEArtifactswherethebusinessapplicationnamecanbeusedasaprefix§ Event– EVENT_PREFIX. prefix_APPLICATION_NAME

§ Application– prefix_APPLICATION_NAME– RuntimenamecanoverridethesavedApplicationname

§ Resources- prefix_D/R/T_RESOURCE_NAME

§ SecurityGroup- prefix_GROUP

§ GlobalVariableContext


CAWLADEArtifactswherethebusinessapplicationnamemakessenseasaprefixfornon-commonartifacts§ Alerts- prefix_ALERT_NAME

§ JavaScripts - prefix_JAVASCRIPT_NAME

§ CalendarSpecialDays- prefix_SPECIAL_DAY

§ AgentGroup- prefix_Agent_group


SampleSecuritysettingforAppsdev inPre-prod

§ DenySUBSCRIBEALL– Helpswithperformance

§ AllowanyEventPrefix– Lessmaintenancebyallowing

userstousetheirownuseridastheprefixforevents


StaticVariables– ESPprefixedJavaScriptexecutedatEventLevel(maynotbenecessary)

§ Environmentname/prefix

§ Hostname/Port

§ Serverhomedirectory

§ CAWLADEServerID

§ Database/FTPUserids

§ Symlib JavaScriptforDefaultSymbolics


DynamicVariables– APPLandWOBprefixedJavaScriptexecutedattheApplicationorJobLevel

§ Dates

§ Agents

§ Directories/paths

§ Databaseservers

§ Emailids

§ Times/SLAs/Criticaljobs

§ Notifications

§ Jobname/qualifier


SampleJavaScripttocreatedatesymbolics invariousformats


SampleDefaultGlobalVariableContext§ UsingaJavaScriptorGlobalVariableContextenablesbeing

abletochangeallinstancesatonetime– LeavetheApplicationsalone– Couldhaveseparationofdutiesforupdatingvalues


WaystominimizeoreliminatechangeswhilemovingthroughthelifecycleusingJavaScripts§ DefinedefaultcontextwithstaticvariablesdefinedintheEvent

– MaynotneedtomovetheEventthoughthelifecycle

§ DefinedynamicvariablesinaJavaScriptdefinedintheApplicationatEventTriggertime– Datesymbolics forpast,presentandfuturedates

§ EmbedJavascripts inthejobdefinition– Forvaluesthatneedtobesetjustbeforethejobisexecuted

§ InvokeRepositorybasedJavaScripts forgenericfunctions


Waystominimizeoreliminatechangeswhilemovingthroughthelifecycle§ TrytomakeitsothatonlytheApplicationneedstobe

migrated– UselinksforAPPLSTARTandAPPLENDasfunctionstoexecute

JavaScripts toset-upotherjobsandtokeeptheApplicationasself-sufficientaspossible

§ %IFfunctioninvariousjobdefinitionfields– Canenabledecisionmakingforaparticularjobfield


Waystominimizeoreliminatechangeswhilemovingthroughthelifecycle§ %IFfunctioninvariousjobdefinitionfields

§ Createapplicationstandardsfordeployingapplications– Standarddirectorynamesinpre-prodandprodwillminimizetheneed

forcreatingexceptionsymbolics

§ UnixandLinuxareinterchangeablejobtypes– CantestwithaUnixagentbutactuallyuseLinuxinproduction

§ Useagentgroupingoragentalias– Randomorroundrobin– Don’thavetospecifythe“real”agentname


LeveragingAgentAlias

§ DonotneedtodefinetherealagentnameintheCAWLADEtopologytouseaparticularagent

§ Anagentaliascanbeset-upforanyreasonandforanypurpose– CApre-salesroutinelyusesaliasestomimiccustomer’sagents– Multiplealiasescanbeset-uponanagent

§ Coulduseproductionagentnamesforpre-prodagents

§ Whenretiringanagent,canbeaneasywaytoswitchagentswithoutchangingjobdefinitionsimmediately


IMEXUTIl – Import/ExportUtility

§ Usefulasawayofexportingallartifactsasanotherwayofbackinguptheinstance– Restoreanindividualartifactwithouthavingtorestoreawholedatabase

§ Createasoftwarechangeprocessfromapre-prodinstancetoaproductioninstance

§ Caution:ifCAWLADEinstancesaredifferentreleases,maynotbeabletobeused– Releasedependent(doesnotapplytoSPreleases)


ExportinganApplicationTriggerandPassApplicationnameasUser1forexecutionfromexternalChangeManagementproduct


ImportinganApplicationTriggerandPassApplicationnameasUser1forexecutionfromexternalChangeManagementproduct


ApplicationParameterscanbeusedwithaTemplateApplication§ Canexecutedynamicallybywebservices§ Canexecuteanapplicationandpass

manymorethanfourparameterstoit


ExecutingaTemplateApplicationusingWebServices


Summary

§ SomeupfrontnamingconventionscanhelpoutlaterwhenplanningforApplicationlifecyclemanagement

§ LeverageJavaScripts andGlobalvariablesforCAWLADEinstancerelatedsymbolics

§ IMEXUTILcanbeveryusefulformanagingtheactualmovementofartifactsfrompre-prodtoprod


RecommendedSessionsSESSION# TITLE DATE/TIME

MFX37EYouVoiceCounts!CustomerDrivenRequirementsforCAWorkloadAutomation

11/15/2016at1:00pm

BanyanA/B

MFX141ELLab:IncreasedAgilityandFlexibilitywithWebServicesforCAWLADEandESP

11/15/2016at9:30am

SouthSeasD

MFX30S CustomerUseCase:RealWorldAutomationinRetail11/16/2016at3:45pm

BanyanA/B

MFX136SDeliveringCAWorkloadAutomationfromaSaaSplatform

11/17/2016at4:30pm

JasmineB


MustSeeDemos

ModernWorkloadAutomation

CAWLADEMFandWorkloadAutomation

SeamlessApplicationAutomationAgents&AdvancedIntegrationsMFandWorkloadAutomation

CAConversionasaService

CAWorkloadAutomationMFandWorkloadAutomation

Innovations:CrossEnterpriseWorkloadAutomationCAWLAAE&DEMFandWorkloadAutomation


Questions?

@CAWORLD#CAWORLD ©2016CA.AllRIGHTSRESERVED.32 @CAWORLD#CAWORLD

MainframeandWorkloadAutomation

FormoreinformationonMainframeandWorkloadAutomation,pleasevisit:http://cainc.to/9GQ2JI

Technology

Pre-Con Ed: Best Practices: Enabling CA Workload Automation DE Artifacts to Move Applications Through the Development Lifecycle