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

PIGYun中秋特惠:香港/韩国VPS月付14元起

PIGYun发布了九月份及中秋节特惠活动,提供8折优惠码,本月商家主推中国香港和韩国机房,优惠后最低韩国每月14元/中国香港每月19元起。这是一家成立于2019年的国人商家,提供中国香港、韩国和美国等地区机房VPS主机,基于KVM架构,采用SSD硬盘,CN2+BGP线路(美国为CUVIP-AS9929、GIA等)。下面列出两款主机配置信息。机房:中国香港CPU:1core内存:1GB硬盘:10GB...

Megalayer(159元 )年付CN2优化带宽VPS

Megalayer 商家我们还算是比较熟悉的,商家主要业务方向是CN2优化带宽、国际BGP和全向带宽的独立服务器和站群服务器,且后来也有增加云服务器(VPS主机)业务。这次中秋节促销活动期间,有发布促销活动,这次活动力度认为还是比较大的,有提供香港、美国、菲律宾的年付VPS主机,CN2优化方案线路的低至年付159元。这次活动截止到10月30日,如果我们有需要的话可以选择。第一、特价限量年付VPS主...

选择Vultr VPS主机不支持支付宝付款的解决方案

在刚才更新Vultr 新年福利文章的时候突然想到前几天有网友问到自己有在Vultr 注册账户的时候无法用支付宝付款的问题,当时有帮助他给予解决,这里正好顺带一并介绍整理出来。毕竟对于来说,虽然使用的服务器不多,但是至少是见过世面的,大大小小商家的一些特性特征还是比较清楚的。在这篇文章中,和大家分享如果我们有在Vultr新注册账户或者充值购买云服务器的时候,不支持支付宝付款的原因。毕竟我们是知道的,...

nslookup为你推荐
iprouteip route-static 192.168.1.0 255.255.255.0 3.3.3.2什么意思360和搜狗360搜索和搜狗搜索谁好谁流量大?为什么我在网上搜索到的数据有一定矛盾?做广告推广哪个好呢?360arp防火墙在哪arp防火墙在哪开额- -360里是哪个?flashfxp注册码谁知道 FlashFXP.rar的注册码?计算机cuteftp图文模块图文模块的标题栏填什么啊?广告后台朋友圈广告投放!在哪设置白名单显示隐藏文件隐藏的文件夹怎么显示出来邮件管理系统邮件管理软件哪种最好?邮件管理系统什么邮件管理软件最适合有分公司的企业?
深圳虚拟主机 南通服务器租用 联通vps 域名备案批量查询 华为云服务 singlehop debian6 个人域名 百兆独享 七夕快乐英文 me空间社区 中国电信测网速 美国独立日 阿里云官方网站 路由跟踪 德讯 lamp兄弟连 乐视会员免费领取 789电视剧网 博客域名 更多