serverindexnslookup
nslookup 时间:2021-04-18 阅读:(
)
CopyrightIBMCorporation2006TrademarksMakeaquickerandeasierrecoveryfromanunplanneddeploymentmanagerfailoverPage1of7MakeaquickerandeasierrecoveryfromanunplanneddeploymentmanagerfailoverRohithAshokNovember22,2006Fewthingsaremorestressfulandfrustratingthananunplannedoutage.
ThisisespeciallytruewhentheunplannedoutageisthedeploymentmanagerofalargeNetworkDeploymentcell.
ThisarticlewalksthroughexamplesofsomefeaturesavailableinIBMWebSphereApplicationServerNetworkDeploymenttohelpyouprepareforaneasyrecoveryfromsuchanoutage.
IntroductionByitsverynature,WebSphereApplicationServerNetworkDeploymentisadistributedsystemrangingacrossmanymachines.
Whilefewthingsaremorestressfulandfrustratingthananunplannedoutage,therearewaysyoucanlessentheimpact.
Thegoalofthisarticleistoshowhowyoucanharnessthissystemandmakerecoveryaquickandsimpletask.
ThisarticleassumesyouhaveagoodunderstandingofWebSphereApplicationServerNetworkDeploymentandsomeknowledgeofnetworkconfiguration.
SamplecellForthepurposesofthisarticle,let'sassumewehaveacellwithfivenodes(Figure1).
Thenodecountisn'tsignificant,butthemorenodesyouhave,thegreatertheimpactwhenthedeploymentmanagerislost.
Figure1.
SamplecelldeveloperWorksibm.
com/developerWorks/MakeaquickerandeasierrecoveryfromanunplanneddeploymentmanagerfailoverPage2of7Thiscellisspreadacrossfivedifferentsystems:System1:Node1(1NodeAgent/20applicationservers)Host:node1.
samplecompany.
com(10.
10.
0.
1)System2:Node2(1NodeAgent/20applicationservers)Host:node2.
samplecompany.
com(10.
10.
0.
2)System3:Node3(1NodeAgent/20applicationservers)Host:node3.
samplecompany.
com(10.
10.
0.
3)System4:Node4(1NodeAgent/20applicationservers)Host:node4.
samplecompany.
com(10.
10.
0.
4)System5:DeploymentManagernodeHost:dmgr.
samplecompany.
com(10.
10.
0.
5)Oneachcluster,asingleapplicationisinstalledforatotalof20applications.
Ifthiswasaproductioncell,andthedeploymentmanager'smachinesimplydiedandwascompletelyunrecoverable,itwouldbeverydifficulttoreconstitutethiscellquickly.
Yourbestbetwouldbetotryandrestorethedeploymentmanagerfromsomebackup,assumingonewastaken.
Thedeploymentmanagerholdstheconfiguration--themasterrepository--fortheentirecell.
Ifyoulookatthefilesystemonthedeploymentmanager,youwillseeallfournodesdefined,aswellasthedeploymentmanagernode.
Thisconfigurationmakesuptheentirecell.
Listing1.
System5/WebSphere/AppServer/profiles/Dmgr01/config/cells/productionCell/nodes/dmgrNode/.
.
.
/WebSphere/AppServer/profiles/Dmgr01/config/cells/productionCell/nodes/node1/.
.
.
/WebSphere/AppServer/profiles/Dmgr01/config/cells/productionCell/nodes/node2/.
.
.
/WebSphere/AppServer/profiles/Dmgr01/config/cells/productionCell/nodes/node3/.
.
.
/WebSphere/AppServer/profiles/Dmgr01/config/cells/productionCell/nodes/node4/.
.
.
Theapplicationservernodes,however,donotneedtheentirecellconfiguration;rather,theyneedonlythesubsetoftheconfigurationthattheythemselvesrequire.
Eachindividualnodehastheentireconfigurationpertainingtoitsownnodeandjusttheserverindex.
xmloftheothernodes.
Listing2.
System1/WebSphere/AppServer/profiles/Dmgr01/config/cells/productionCell/nodes/node1/.
.
.
/WebSphere/AppServer/profiles/Dmgr01/config/cells/productionCell/nodes/node2/serverindex.
xml/WebSphere/AppServer/profiles/Dmgr01/config/cells/productionCell/nodes/node3/serverindex.
xml/WebSphere/AppServer/profiles/Dmgr01/config/cells/productionCell/nodes/node4/serverindex.
xml/WebSphere/AppServer/profiles/Dmgr01/config/cells/productionCell/nodes/dmgrNode/serverindex.
xmlMethod1:SetupthebackupnodeTheplanhereistouseanapplicationservernodeasabackup.
Byreplicatingtheentireconfigurationtreefromtheactualdeploymentmanagernodetoanotherapplicationservernode,ibm.
com/developerWorks/developerWorksMakeaquickerandeasierrecoveryfromanunplanneddeploymentmanagerfailoverPage3of7thedeploymentmanagercanbequicklyrestartedonthebackupnode.
Tobegintheprocess,youfirstneedanapplicationservernode.
Inaproductionenvironment,itisbestnottouseanodethatservesapplications,butrathertochooseanewnodededicatedasabackup.
A.
Createbackupnode1.
WewillfirstinstallWebSphereApplicationServeronanewsystem:System6.
Wheninstallingtheproduct,installitintothesamelocationonthefilesystemasthedeploymentmanagersystem.
IfyouinstalledWebSphereApplicationServerinthe/WebSphere/AppServerdirectoryonthedeploymentmanagersystem,makesureitisinstalledonthebackupsysteminthesameplace.
2.
CreateanewCustomorStandaloneprofile.
ThenodenamewewillgiveisbackupNode.
Then,federatethenewnodeintotheexistingcell.
Listing3.
System6/WebSphere/AppServer/profiles/Dmgr01/config/cells/productionCell/nodes/backupNode/.
.
.
System6:BackupnodeHost:backup.
samplecompany.
com(10.
10.
0.
6)Thisnode'spurposeisstrictlyforbackup/failover,notforhostinganyapplicationservers.
Whenthebackupdeploymentmanagerisrunning,itwillcreateitslogsintheexactsameplaceasdoesthedeploymentmanagersystem.
Eventhough/WebSphere/AppServer/profiles/Dmgr01/logshasnotbeencreatedbytheprofilemanagementtools,itwillbecreatedbytherunningserver.
B.
ConfigurebackupnodeRightnow,thebackupNodeisjustlikeanyothernode;itonlymanagesitsownconfigurationandasmallsubset(serverindex.
xml)fortheothernodes.
Tosetupthisnodeasabackup,youneedtoautomaticallyreplicatethedeploymentmanager'scell-wideconfiguration.
Todothis,youneedtosetupacustompropertyonthebackupNode'snodeagent,eitherusingtheadministrativeconsoleorbyusingasimplejythonscript.
Tousetheadministrativeconsole:3.
Thecustompropertycanbesetontheadministrativeconsole(Figure2)bynavigatingtoSystemAdministration=>NodeAgents=>nodeagent=>FileSynchronizationService=>CustomProperties=>New.
developerWorksibm.
com/developerWorks/MakeaquickerandeasierrecoveryfromanunplanneddeploymentmanagerfailoverPage4of7Figure2.
AddcustompropertyusingadministrativeconsoleThenewpropertytocreateis:Name:recoveryNodeValue:trueDescription:(optional)4.
Oncethispropertyisset,thenodeagentmustberestarted.
Thenexttimethenodeagentissynchronized,itwillextracttheentirecellconfiguration,notjustitsown.
Anytimeaconfigurationchangeismadeonthedeploymentmanagerandsynchronized,thisbackupNodewillalsodownloadthenewchange,regardlessofthenodethechangewasactuallydirectedto.
5.
YoudonotneedtocreateanyapplicationserversonthebackupNode.
Youonlyneedthenodeagentupandrunningtokeeptheconfigurationcurrent.
Alternatively,youcanuseajythonscripttosetthecustomproperty.
BelowisasimplescriptthatillustrateshowtosetthecustompropertyonthebackupNode'snodeagent.
(Beforerunning,changealloccurrencesofinthescripttotheactualnodename.
)Listing4.
Jythonscripttosetacustomproperty#ScripttocreatetherecoveryNodecustomproperty#Step1:Getahandletothenodeagentnodeagent=AdminConfig.
getid('/Node:/Server:nodeagent/')printnodeagent#Step2:GetahandletotheConfigSynchronizationServicesyncservice=AdminConfig.
list('ConfigSynchronizationService',nodeagent)printsyncservice#Step3:CreatethecustompropertyAdminConfig.
create("Property",syncservice,[["name","recoveryNode"],["value","true"]])#Step4:SaveAdminConfig.
saveibm.
com/developerWorks/developerWorksMakeaquickerandeasierrecoveryfromanunplanneddeploymentmanagerfailoverPage5of7C.
CreateascripttostartthedeploymentmanagerNowthatyouhavethedeploymentmanagerconfigurationautomaticallyreplicatedonthebackupNode,youneedawaytostartit.
YoucannotusethestandardStartServer.
shscript,asthescriptmakessomeassumptionsaboutrunningonthelocalnode.
StartServer[.
sh|.
bat]/startManager[.
sh|.
bat]worksbyreadingtheconfigurationofthelocalnodeandstartingaserveronthatnode.
IfyoutrytorunstartManager[.
sh|.
bat]onthebackupNode,itwillnotletyoutostartthedeploymentmanager;thedeploymentmanagerdoesnothavebackupNodeasitsnodename,butratherdmgrNode.
SinceyoucannotusetheexistingstartManagerscript,youmustcreateanotherscripttostarttheserver:6.
Run.
/startNode.
[sh|.
bat]-script.
Thiscommandwillgenerate:start_nodeagent.
sh(or.
batifWindows).
Youmusttheneditthescripttopointtothedeploymentmanagerconfigurationratherthanthenodeagent.
7.
Renamethescripttostart_backup_dmgr.
sh.
8.
Changethecontentsofthefile;thekeychangeisattheendofthefileintheexeccall:Listing5.
Modifystart_backup_dmgr.
shexec"/build/websphere/WASX/u0622.
06.
wasx/AppServer/java/bin/java".
.
.
"/build/websphere/WASX/u0622.
06.
wasx/AppServer/profiles/AppSrv01/config""productionCell""backupNode""nodeagent"""9.
Changethe"backupNode"todmgrNodeand"nodeagent"todmgrtoread:Listing6.
Modifystart_backup_dmgr.
shexec"/build/websphere/WASX/u0622.
06.
wasx/AppServer/java/bin/java".
.
.
"/build/websphere/WASX/u0622.
06.
wasx/AppServer/profiles/AppSrv01/config""productionCell""dmgrNode""dmgr"""Theoutputofyournewstart_backup_dmgr.
shisverydifferentthantheexpectedstartManager[.
sh|.
bat]output.
Thebackupdeploymentmanagershouldonlybeusedforoperationalcontrol,sinceanychangesmadetothesystemarenotreflectedbacktotheoriginaldeploymentmanager.
Method2:SharedfilesystemAsecondoptionisuseafilesystemthatissharedbetweentheprimarydeploymentmanagersystemandabackupsystem.
Youcansetupasecondsystemtosharethedeploymentmanagerprofileitself,andstartthedeploymentmanageronthatsecondsystem.
IfyouexamineaV6.
0.
XorV6.
1installation,allthedatapertainingtoadeploymentmanager(oranyprofileforthatmatter)isstoredundertheWAS_HOME/profiles/directory.
ConsidertheearlierexamplewherethedeploymentmanagerisinstalledonSystem5undertheHFS:/WebSphere/AppServer/profiles/Dmgr01/config/cells/productionCell/nodes/dmgrNode/.
.
.
Again,youneedtoinstallWebSphereApplicationServeronSystem6.
However,thistimeyoudonotneedtocreateanyprofiles,youcaninsteadsharethedeploymentmanager'sprofiledirectory.
developerWorksibm.
com/developerWorks/MakeaquickerandeasierrecoveryfromanunplanneddeploymentmanagerfailoverPage6of7BymountingtheshareddirectoryinexactlythesameplaceonSystem6,youhaveessentiallyduplicatedthesystem.
Theduplicationoftheprofileenablesthesamedeploymentmanagertobestartedontheothersystem.
Oncethisdirectoryisshared,youcanrunstartManager[.
sh|.
bat]fromthebackupsystem.
Thedownsidetothismethodisthesharedfilesystemmustbemaintainedbyyou.
Therecanalsobesomeconsiderableperformancecoststousingasharedfilesystem,bothonthemastersystemandonthebackupsystem.
Onemajoradvantageofthissystemisthatanychangesmadetothedeploymentmanager'smasterrepositorywhileusingthebackupsystemarecommitted.
Oncetheprimarydeploymentmanagermachineisrebuilt,thechangeswillnotbelostwhenthefilesystemisremounted.
ConfiguringDNSformulti-homedhostsOnceyouhavefoundawaytostartadeploymentmanageronaremotesystem,youstillmayhavesomeissuestoresolve.
Whenyouoriginallyconfiguredthatdeploymentmanager,aspecifichostthatresolvedtoaspecificIPwasgiven.
Inourexample,thehostnamedmgr.
samplecompany.
comresolvedto10.
0.
0.
5.
Toenablethedeploymentmanagertobelocatedonthebackupsystem(10.
0.
0.
6)weneedtosetupwhat'scalledamulti-homeDNSentry.
Inourexample,weareusingmultipleinterfacesacrossmultiplemachines,eachwithasingleIPaddresspermachine.
HereisanexampleofourDNSentry:Listing7.
DNSentryADMIN:SYSTEM6:/u/ADMIN>nslookupdmgr.
samplecompany.
comDefaultingtonslookupversion4Startingnslookupversion4Server:dnsserver.
samplecompany.
comAddress:10.
0.
0.
100Name:dmgr.
samplecompany.
comAddresses:10.
0.
0.
5,10.
0.
0.
6ByconfiguringtheDNSentryfortwohosts,itenablesaneasytransitionbetweenthemsincenore-configurationisneeded.
Aslongasonlyonesystemoneitherhostisrunningatanygiventime,onlyonedeploymentmanagerwillbeused.
Thenodeagentsandclientswillautomaticallytrythefirst(primary)addressandthenfailovertotrythesecond(backup)address.
Onceacellhasbeensetupinthisway,thedeploymentmanagerandallnodeagentsmustberestartedtore-readtheconfiguration.
Bydefault,theJVMcachesDNSentriesandtherestartisneededtorefreshthem.
ConclusionThisarticlediscussedonewayofbuildingamorefaulttolerantdeploymentmanagerusingfeaturesthatexistinWebSphereApplicationServerNetworkDeploymentV6.
x,anddescribedhowtouseeitheraWebSphereApplicationServerconfigurationoptionorasharedfilesystemtoautomaticallyreplicatetheentirecell-wideconfigurationtoabackupsystem.
ThisbackupsystemthenusesapreconfiguredDNSentrytostartupandreplacethefaileddeploymentmanager.
Thelossofadeploymentmanagerisagreatblowtoaproductioncell,andsoitiscriticalthatthisserverremainrunningandfunctionaltoensureahighlyavailabletopology.
ibm.
com/developerWorks/developerWorksMakeaquickerandeasierrecoveryfromanunplanneddeploymentmanagerfailoverPage7of7RelatedtopicsWebSphereApplicationServerInformationCenterSettingtherecoveryNodepropertyCopyrightIBMCorporation2006(www.
ibm.
com/legal/copytrade.
shtml)Trademarks(www.
ibm.
com/developerworks/ibm/trademarks/)
提速啦的来历提速啦是 网站 本着“良心 便宜 稳定”的初衷 为小白用户避免被坑 由赣州王成璟网络科技有限公司旗下赣州提速啦网络科技有限公司运营 投资1000万人民币 在美国Cera 香港CTG 香港Cera 国内 杭州 宿迁 浙江 赣州 南昌 大连 辽宁 扬州 等地区建立数据中心 正规持有IDC ISP CDN 云牌照 公司。公司购买产品支持3天内退款 超过3天步退款政策。提速啦的市场定位提速啦主...
racknerd当前对美国犹他州数据中心的大硬盘服务器(存储服务器)进行低价促销,价格跌破眼镜啊。提供AMD和Intel两个选择,默认32G内存,120G SSD系统盘,12个16T HDD做数据盘,接入1Gbps带宽,每个月默认给100T流量,5个IPv4... 官方网站:https://www.racknerd.com 加密数字货币、信用卡、PayPal、支付宝、银联(卡),可以付款! ...
iON Cloud怎么样?iON Cloud是Krypt旗下的云服务器品牌,成立于2019年,是美国老牌机房(1998~)krypt旗下的VPS云服务器品牌,主打国外VPS云服务器业务,均采用KVM架构,整体性能配置较高,云服务器产品质量靠谱,在线率高,国内直连线路,适合建站等用途,支付宝、微信付款购买。支持Windows server 2012、2016、2019中英文版本以及主流Linux发行...
nslookup为你推荐
账号企业conn.aspconn.asp 在哪打开?应该怎样打开?360arp防火墙在哪谁知道360防火墙的arp防火墙文件在哪95188是什么电话95188是什么号码我刚收到短信是什么支付宝的验证码厦门三五互联科技股份有限公司厦门三五互联科技股份有限公司广州分公司 待遇怎么样啊,电话营销的温州都市报招聘在温州哪里好找工作?工具条手机的工具栏怎么在任务栏里?怎么把工具栏调到手机下面?如何发帖子如何发表帖子什么是seo学习SEO的好处是什么?社区动力我是一名新入职社区员工,怎样做好社区工作?
老域名全部失效请记好新域名 荣耀欧洲 台湾服务器 美国主机推荐 免费主机 ibox官网 网站卫士 购买国外空间 web服务器搭建 cxz 酸酸乳 数据湾 hosting web服务器有哪些 wannacry勒索病毒 硬防 域名商城 ddos攻击软件 新浪轻博客 web服务器的配置 更多