Pre-Con Ed: Upgrading CA Workload Automation DE to R12

transcript

World®’16

UpgradingCAWorkloadAutomationDEtoR12LeeRoberson,SeniorPrincipalConsultant,CATechnologies

MFX28E

MAINFRAME

@CAWORLD#CAWORLD

Thecontentprovidedinthis CAWorld2016presentationisintendedforinformationalpurposesonlyanddoesnotformanytypeofwarranty. The informationprovidedbyaCApartnerand/orCAcustomerhasnotbeenreviewedforaccuracybyCA.

ForInformationalPurposesOnlyTermsofthisPresentation

@CAWORLD#CAWORLD

Abstract

Learnhowtoperformanupgradefrom11.3toCAWorkloadAutomation(CAWA)DER12usingthenewIn-placeUpgradeMethod.Thein-placeupgrademethodupgradestheservertothesamedirectoryonyourcomputerwheretheserverwasoriginallyinstalled.

Thismethoddoesnotrequireyoutoinstallanewinstanceoftheserverordatabaseandmigrateartifacts,globalvariables,andhistorydata.

Thesessionwillalsodiscussthetraditionalmigrationmethodaswell.

LeeRobersonSeniorPrincipalConsultant,CATechnologies

@CAWORLD#CAWORLD

Agenda

INTRODUCTIONTOUPGRADEOPTIONS(IN-PLACEORMIGRATION)

IN-PLACEUPGRADEBENEFITS

IN-PLACEUPGRADEPROCESS

MIGRATIONUPGRADEOVERVIEW

ADDITIONALCONSIDERATIONS(NEWWEBUI,DESKTOPCLIENT,WEBSERVICES)

@CAWORLD#CAWORLD

In-placeUpgrade

§ In-place§ Minimaldown-

time§ Efficiency

TraditionalMigration

§ Newinstall§ Migrateartifacts§ EasyFail-back

CAWorkloadAutomationDEUpgradeMethods

Twooptionsprovideupgradeflexibilitytosupportclient

requirements

EachupgrademethodhasAdvantages

@CAWORLD#CAWORLD

CAWADEUpgradeOptions

§ In-placeUpgradeMethod

– NewsimplifiedupgradeprocessintroducedinR12.0

– UpgradesCAWADEServerinthesamedirectoryonyourcomputerwheretheserverwasoriginallyinstalled

– Usethein-placeupgrademethodtoupgradetheserverfromr11.3SP3build1406orhigher

– Time takenforthe upgradefrom11.3.03or12.0to12.0.01isnowreduceddramatically(oftenlessthananhour)

§ MigrationMethod

– Installnewinstanceoftheserveranddatabase

– Migrateartifacts,globalvariables,andhistorydatafromtheexistingservertothenewserver

– Usethemigrationmethodtoupgradetheserverfromr11.1orhigher

@CAWORLD#CAWORLD

In-placeUpgrade:SimplifiedUpgradeProcess

ReduceTimetoperformupgradefromCAWADE11.3.03tor12.0.xSPEED

Advantages§ UpgradeCAWADEin-place§ Minimaldown-time§ RollBacktopriorversionsupport§ Activeworkloadandhistorypreserved§ Nonewhardwarerequired

@CAWORLD#CAWORLD

§ In-placeupgradecanbeusedtoupgradethecurrentCAWADEserverwithminimaldowntime

§ NonewhardwareneededtoinstallthenewCAWADEserverandmigratethedataaswithmigrationmethod

§ Activeworkloadwillnotbelostduringin-placeupgrades

§ Activeworkloadisresumedafterin-placeupgradeisperformed

In-placeUpgradeBenefits

@CAWORLD#CAWORLD

In-PlaceUpgradeHighLevelOverview

§ Upgradeinstallationupgrades:– Configuration– JRErelease(exceptonz/Linux)– Binaryandlibraryfilesontheserver– Updatesthedatabaseschema,convertsartifactsversions(12.0SP1)

§ ItdoesNOT:– Updatethedefaultagentthatwasinstalledwiththeserver

@CAWORLD#CAWORLD

In-placeUpgradeProcedure

1. SuspendEventstostopanyworkloadtobetriggered

2. StoptheCAWADEserver

3. Takedatabasebackup

4. PerformIn-placeupgrade

5. Validation- checktheartifactspriortoresumingworkload

@CAWORLD#CAWORLD

In-placeUpgrade– R12.0.0Specificconsiderations

§ SpecifictoR12.0- Doesnotautomaticallyconvertartifactversionsinthedatabasefrom11.3toR12.0

§ ConverttheApplicationversiondefinitionsinthedatabasefromr11.3tor12(R12.0only;notrequiredforR12.0SP1upgrade)

§ RunartifactVersionConverterutility

@CAWORLD#CAWORLD

ConverttheApplicationversiondefinitions(R12.0.0only)

§ ConverttheApplicationversiondefinitionsinthedatabasefromr11.3tor12.0.0(not12.0SP1– Download/extractthe artifactVersionsConverter.zip filetoatemporarydirectory

§ Note:YoucanalsodownloadtheartifactVersionsConverter.zip filefromthepatchRO86729

– Copytheartifactversionsconverter.jarfileto:§ server_install_dir\libdirectory(Windows)orthe server_install_dir/libdirectory(UNIX)

– CopytheartifactVersionsConverter scriptto:§ artifactVersionsConverter.bat- server_install_dir\bindirectory(Windows)

§ artifactVersionsConverter.shtothe - server_install_dir\bindirectory(UNIX)

– (Optional)EditartifactVersionsConverter filetosetMAX_HEAP_SIZE=4096§ defaultis1GBmayneedtoincreaseifyouhavealargenumberofapplicationversions

– runtheartifactVersionsConverter.batfileonWindowsortheartifactVersionsConverter.shfileonUNIX

– VerifythatalltheApplicationversionsareconverted§ seethecawa_home/logs/artifactversions.log

@CAWORLD#CAWORLD

In-placeUpgrade- Prerequisites§ (CAWAHighAvailabilityconfigurationonly)removetheunusedserverconfigurationsfromthedatabaseifmoreserversinadditiontothe

preferredandStand-byserversarepointingtothedatabase,.– Important! Ensurethatserversnomorethantwoarepointingtothedatabase.Otherwise,thein-placeupgrademightfail.

§ Stoptheworkloadontheserver– SuspendallEvents orHoldallEvents

– ExecutethefollowingqueryinthedatabaseconsoletoretrievethestatusofalltheactiveApplicationsandjobsfromthespoolfile:

§ Selectname,type,thestate,status,starttime,endtime fromESP_RTWOB

– Storethequeryresultinafile.Youmighthavetorefertoitwhenyoustarttheworkloadprocessingafterthein-placeupgrade

– ForcecompleteonlytheapplicationsthathaveFTP,SFTP,andPeopleSoftjobs,whenyouupgradefromReleases11.3,11.3SP1, and11.3SP2

§ IfyouareupgradingfromRelease11.3SP3afterinstallingthepatchRO84946,youcancontinuewiththeupgradewithoutanyforcecompletionofapplications.

§ StopthePrimaryserver

§ StoptheStandbyserver(ifCAWAHighAvailabilityisconfigured)

§ BackuptheCAWADEserverdatabase

@CAWORLD#CAWORLD

SupportforIn-PlaceUpgrades

§ Upgrade11.3.xserverinstancesusingin-placeupgradebymodifyingtheexistingserverinstallfoldertor12installfolder.

§ Stoptheworkloadandserverbeforerunningin-placeupgrade

§ In-placeupgradewillaskforthefolderlocationwhichhastobeupdatedtor12level.

§ Beforerunningin-placeupgrade,takethebackupofdatabaseusedbythe11.3.xversion.Thisisaprerequisitestepbeforeproceedingwithupgrade.

§ In-placeupgrademodifiesallthefilesthatarerequiredforr12.0versionandalsomakesmodificationstothedatabasetobringittor12level

@CAWORLD#CAWORLD

In-placeUpgradeInstallOption

@CAWORLD#CAWORLD

In-placeUpgradeInstallOption§ Inplaceupgradewillaskforthefolderlocationwhichhastobeupdatedtor12level

@CAWORLD#CAWORLD

SupportforIn-placeUpgrades

§ Installerwillcreateabackupfolderwithatimestampintheinstalledfolder.Thebackupfolderhasalltheartifactsbeforein-placeupgradeisrun.

§ Restorescriptcanberuntorestorethecontentsbacktotheoriginalstate

§ Databasecanberestoredfromdatabasebackuptakenbeforerunningin-placeupgrade

§ In-placeupgradedoesnotupdatetheagents

§ Anyerrorsthatoccurduringin-placeupgradewillbeloggedintotheinstallationlogfiles.

@CAWORLD#CAWORLD

In-placeUpgrade– ImportantCaveats

§ In-placeupgradeneedstobeperformedtobringtheexistingCAWADEinstallationstoCAWADEr12SP1level

§ UpgradestoCAWADEserverr12SP1canbedonefromCAWADE11.3SP3build1414orhigher,CAWADEr12

§ Thedatabaseuserusedduringin-placeupgradesshouldbethesameuserusedduringCAWADEinstallation– Ifthesamedatabaseuserisnotused,upgradeswillfail.EspeciallyiftheCAWADE

serverdatabaseisusing“MSSQLWindowsauthentication”

§ Incaseofanyfailuresduringupgrades,installerwillreportanerrorandlogtheerrorsat$CAWA_HOME/upgrades/logs/inplaceupgrade.log

@CAWORLD#CAWORLD

AdditionalConsiderations

§ Ensurethedatabaseuserindb.properties andthedatabaseuserusedwhilecreatingthedatabaseandusedforinstallationarethesame.EspeciallyforWindowsauthenticationMSSQLdatabase

§ EnsureweusethesameWindowsusertoruntheupgradewiththeuserthatwasusedtoruntheinstallation

§ InstalllatestversionofCAWADesktopClient– BoththeCAWADEserverandCAWADesktopClientmustbeatthesameversionlevel

§ InstalllatestversionoftheCAWADEWebServices(optional)

§ InstalllatestreleaseofCAWADEStand-AloneCLI

§ InstallandleveragethenewCAWADEWebUI(netnewfunctionalityin12.0SP1)

§ Note:UsingtheCAWADEserverAPIinJavaScriptscriptsisnotsupported.Thejavascripts willfailafterin-placeupgradeormigration

@CAWORLD#CAWORLD

RollBackServerUpgradetoPreviousVersion§ Canrollbackserveraftersuccessfulin-placeupgradeandrestoretotheprevious

versionifnecessary

§ Thebinary,configuration,JRE,andlibraryfilesontheserverthataremodifiedbythein-placeupgradearerestored

§ StoptheServerandStandbyServer(HA)

§ Runrestore.bat/.shtorestorefilesanddirectories

§ Restoretheserverdatabasethatyoubackedup

§ DowngradeanyupgradedCAWADEDesktopClients,StandAloneCLIs,WebServices

§ UninstallnewCAWADEWebUI,ifdeployed,ItisNOTbackwardcompatible

@CAWORLD#CAWORLD

MigrationUpgrade:TraditionalApproachMigrateartifacts,globalvariables,historydatatonewserverFLEXIBILITY

Advantages§ Preservespreviousversionforfailback

§ Changedatabasetype§ Supportshardware/OSrefreshrequirements

§ Selectivemigrationofartifacts

@CAWORLD#CAWORLD

TraditionalMigrationMethod

§ RequiresinstallofnewCAWADEServerinstanceanddatabase

§ Migrationprocessthatmigratesartifacts,globalvariables,andhistorydatafromtheexistingservertothenewserver

§ Usethemigrationmethodtoupgradetheserverfromr11.1orhigher(11.1,r11.3,r12.0.x)

§ Migrationcanberunfromanydatabasetoanyotherdatabaseoftargetversion

@CAWORLD#CAWORLD

MigrationMethodBenefits

§ Migrationpreservesthepreviousserverwhilelettingyouusethenewservertorunyourpreviouslydefinedworkload

§ Migrationcanberunfromanydatabasetoanyotherdatabaseoftargetversion

§ Easilyfailbacktothepriorrelease

§ Goodforhardwarerefreshcycles,re-platformingprojects

§ Canbeusedtomigrateasubsetofworkloadartifacts

@CAWORLD#CAWORLD

MigrationMethodProcess(7steps)

@CAWORLD#CAWORLD

HowMigrationMethodWorks§ Migrationutilityreadsartifacts

fromthesourceserver

§ Convertsthemtothenewformat,andstorestheminfilesonthenewserver

§ Whenyoustartthenewserveraftermigration,thestoredartifactsareimportedintothenewserverdatabase

§ Globalvariablesandhistorydataaremigrateddirectlyintothenewserverdatabase

@CAWORLD#CAWORLD

MigratedArtifacts

§ Themigrationutilitymigratesthefollowingartifacts:– Agents

– Alerts

– ApplicationsandApplicationVersions

– Calendars

– Events

– Forecasts

– Users(security)

– Groups(security)

– JavaScripts (JavaScriptrepository)

– Resources

– ConnectionProfiles(Hadoop)

– SecurityProfiles(Hadoop)

@CAWORLD#CAWORLD

AssessingArtifactsforMigration

§ Assessartifactsinboththesourceandtarget(new)serverbeforeyoumigrate

§ Considerthefollowingimpacts:– Ifdefinitionsshare the samename,themigrationutilityoverwritesthenewartifactswithdefinitions

fromthesourceserver.

– Aftermigration,themigratedApplicationsandexistingApplicationscompeteforresources,usethesamesystemvariables,andsharecommondependenciesthatcanleadtounexpectedbehavior

– Toavoidtheseimpacts,werecommendthatyoudonotcreateartifactsorrunworkloadonthenewserverbeforemigration

– Alternatively,toavoidoverwritingartifacts,youcanselectivelydeletetheartifactsfromthetemporarydirectorythemigrationutilityusesbeforestartingthenewserver

– Whenyoustartthenewserver,itispopulatedwiththeartifactsstoredinthisdirectory

@CAWORLD#CAWORLD

UnsupportedCharactersinArtifactNames

§ Somecharactersthatwereallowedinartifactnamesinpreviousreleasesarenolongerallowed

§ Ifnameofanartifactcontainsunsupportedcharacters,themigrationutilitydisplaysanerrorandtheartifactisnotmigrated.Tomigrateartifactswithunsupportednames,reviewthemigrationerrors,changethenamesoftheartifacts,andrerunthemigrationutility.

§ Startinginr11.1,thefollowingspecialcharactersarenolongersupportedinjobnames:

§ forwardslash(/)

§ back slash(\)

§ colon(:)

§ semi-colon(;)

§ asterisk(*)

§ ampersand(&)

§ doublequote(")

§ less(<)

§ greater(>)

§ bar(|)

§ parentheses(())

§ backquote(`)

§ singlequote(')

§ equal(=)

§ period(.)

§ comma(,)

§ caret(^)

§ tilde(~)

§ questionmark(?)

@CAWORLD#CAWORLD

MigrateArtifacts,GlobalVariables,andHistoryData

§ Runmigrationutilityonnewservertomigrateartifacts,globalvariables,andhistorydata– migrate.bat[config_file](Windows)

– migrate.sh[config_file](UNIX/Linux)

§ Themigrationprogramconnectstothesourceserverandreads,converts,andstorestheartifactsonthenewserverfilesystem– migrationutilityusesthedefaultmigrationconfigurationfile

– Cancreateacustomizedconfigurationfiletoautomatesomeofthestepsinthefollowingprocedureortochangedefaultvalues

– Themigrationutilityusesdefaultloggingsettingsinthemigrationloggingconfigurationfileandlogsmigration-relatedinformationinthemigration.logfile

– Tochangethelogfilelocationorconfiguredefaultsettings,youcanmodifythemigrationloggingconfigurationfile

– Ifthemigrationprogramcannotread,convert,orstoreanartifact,itpromptsyoutostopthemigration,continuethemigrationuntilthenexterroroccurs,orcontinuethemigrationandignoresimilarerrors.

– YoucanskipthemigrationofApplicationversionsduringartifactsmigrationbyconfiguringthemigration.default.conffile

@CAWORLD#CAWORLD

MigrationCaveats- Artifacts

§ Migrationdoesnotperformanykindofmergingbetweenexistingandmigrateddata

§ Whenartifactsaremigrated,themigrationutilityreadsthemfromthesourceserver,

convertsthemtothenewformat,andstorestheminfilesonthenewserver.Whenyou

startthenewserveraftermigration,thestoredartifactsareimportedintothenewserver

database– Note: YoucandisablethisbehaviorbysettingtheRESET_POPULATED_FLAGpropertytofalseinthe

configurationfilethemigrationutilityuses

§ Becauseartifactsarestoredinfiles,youcanpreventindividualartifactsfrombeing

migratedbydeletingtheirfilesbeforestartingthenewserver.

@CAWORLD#CAWORLD

MigrationCaveats– GlobalVariablesandHistoryData

§ MigrationutilityreadsGlobalVariablesandhistorydatafromthesourceserverdatabase,

convertsthemtothenewformat,andimportsthemintothenewserverdatabase

§ Globalvariablesandhistorydataaremigrateddirectlyintothedatabase

§ Cannotpreventindividualglobalvariablesandhistorydatafrombeingmigrated.

§ Note: Ifworkloadwasexecutedonthenewserverbeforemigration,historydata

migrationcanfailifexistingdatabaserowsconflictwiththemigratedrows.Themigration

utilitydoesnotmergeexistingandmigrateddata.

@CAWORLD#CAWORLD

RecommendedSessions

SESSION# TITLE DATE/TIME

MFX23EBestPractices:EnablingCAWorkloadAutomationDEArtifactstoMoveApplicationsThroughtheDevelopmentLifecycle

11/14/2016at4:00pm

JasmineB

MFX141ELHandsonLab:IncreasedAgilityandFlexibilitywithWebServicesforCAWADEandCAWAESP

11/15/20116at9:30am

SouthSeasD

MFX30SCustomerUseCase:Real-WorldAutomationinRetailwithCAWorkloadAutomationDE

11/16/2016@3:34pm

BanyanA/B

MFX128SVisionandRoadmap:CAWorkloadAutomationDE(dSeries)

11/17/2016@1:45pm

BanyanA/B

@CAWORLD#CAWORLD

MustSeeDemos

ModernWorkloadAutomation

CAWLADEMFandWorkloadAutomation

SeamlessApplicationAutomationAgents&AdvancedIntegrationsMFandWorkloadAutomation

CAConversionService

CAWorkloadAutomationMFandWorkloadAutomation

Innovations:CrossEnterpriseWorkloadAutomationCAWLAAE&DEMFandWorkloadAutomation

@CAWORLD#CAWORLD

Questions?Informatica

Pre-Con Ed: Upgrading CA Workload Automation DE to R12

Technology