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/)

PacificRack(19.9美元/年)内存1Gbps带vps1GB洛杉矶QN机房,七月特价优惠

pacificrack怎么样?pacificrack商家发布了七月最新优惠VPS云服务器计划方案,推出新款优惠便宜VPS云服务器采用的是国产魔方管理系统,也就是PR-M系列,全系基于KVM虚拟架构,这次支持Windows server 2003、2008R2、2012R2、2016、2019、Windows 7、Windows 10以及Linux等操作系统,最低配置为1核心2G内存1Gbps带宽1...

华纳云-618大促3折起,18元/月买CN2 GIA 2M 香港云,物理机高防同享,10M带宽独享三网直连,无限流量!

官方网站:点击访问华纳云活动官网活动方案:一、香港云服务器此次推出八种配置的香港云服务器,满足不同行业不同业务规模的客户需求,同时每种配置的云服务都有不同的带宽选择,灵活性更高,可用性更强,性价比更优质。配置带宽月付6折季付5.5折半年付5折年付4.5折2年付4折3年付3折购买1H1G2M/99180324576648直达购买5M/17331556710081134直达购买2H2G2M892444...

特网云(1050元),IP数5 个可用 IP (/29) ,美国高防御服务器 无视攻击

特网云特网云为您提供高速、稳定、安全、弹性的云计算服务计算、存储、监控、安全,完善的云产品满足您的一切所需,深耕云计算领域10余年;我们拥有前沿的核心技术,始终致力于为政府机构、企业组织和个人开发者提供稳定、安全、可靠、高性价比的云计算产品与服务。官方网站:https://www.56dr.com/ 10年老品牌 值得信赖 有需要的请联系======================特网云美国高防御...

nslookup为你推荐
sns网站有哪些最近两年哪些SNS网站比较火易名网诚询,易名网注册的域名怎么转到喜欢的网页上啊?刚刚网新员工入职自我介绍怎么写?300051三五互联170号段和三五互联什么关系可信网站可信网站认证网络u盘你们谁知道网络硬盘怎么用申请400电话申请400电话需要什么条件谷歌新漏洞安卓上黑客给你发一个MP4代码短信手机就会被控制的那个漏洞现在谷歌有出第二段补丁吗?帝国cms帝国cms 登录或退出提示页面404错误???微博通微博通登陆手机号和绑定号码不一样
asp虚拟主机 香港服务器租用99idc 安徽双线服务器租用 isatap paypal认证 网页背景图片 网通ip 免费网站申请 中国智能物流骨干网 河南移动邮件系统 建立邮箱 工作站服务器 银盘服务是什么 重庆电信服务器托管 沈阳主机托管 中国域名 ssl加速 睿云 accountsuspended apache启动失败 更多