Moving Admin server

Question

Hey guys,
i have been assigned the task of moving our weblogic 10 (rhel AS 3) administration server from one location to another, and changing its ip address. i have replicated our environment into a virtual environment and tried changing the ip address of the administration server, but unfortunately the managed nodes were unable to connect to the new ip address of the admin server. the nodes still tried to connect back to the old ip address of the admin server. can someone please tell me the proper steps i need to take in order to make this work. Thanks
Edited by: user10950056 on Apr 6, 2009 10:21 AM

Answer 1

sorry for the delayed reply. been busy with other projects. i started back from square one and has now made a little more progress with the task at hand. here are the steps i have taken so far
1. replicate management server to new vm host
2. turn off original management server and bring up vm management server
3. ran the command grep -r "oldmanagementserverip" *|grep -v "log" on managed node
4. ran the command grep -r "oldipaddressofmanagementserver" *|grep -v "log" on managed node
5. edit all the files that came up in the search. edited them to point to the new management vm
the managed node can now be started remotely from the admin console. however i cannot start it up on the managed node locally by running startWeblogic.sh. Here is the output when attempting to start manually:
starting weblogic with Java version:
java version "1.5.0_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
BEA JRockit(R) (build R27.3.1-1_CR344434-89345-1.5.0_11-20070925-1628-linux-ia32, compiled mode)
Starting WLS with line:
/var/bea/10x/jrockit_150_11/bin/java -jrockit -Xms256m -Xmx512m -da -Dplatform.home=/var/bea/10x/wlserver_10.0 -Dwls.home=/var/bea/10x/wlserver_10.0/server -Dweblogic.home=/var/bea/10x/wlserver_10.0/server -Dwli.home=/var/bea/10x/wlserver_10.0/integration -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/var/bea/10x/patch_wlw1001/profiles/default/sysext_manifest_classpath:/var/bea/10x/patch_wls1001/profiles/default/sysext_manifest_classpath -Dweblogic.Name=10.129.1.148 -Djava.security.policy=/var/bea/10x/wlserver_10.0/server/lib/weblogic.policy weblogic.Server
<Apr 8, 2009 12:03:49 PM EDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
/var/bea/10x/wlserver_10.0/platform/lib/p13n/p13n-schemas.jar:/var/bea/10x/wlserver_10.0/platform/lib/p13n/p13n_common.jar:/var/bea/10x/wlserver_10.0/platform/lib/p13n/p13n_system.jar:/var/bea/10x/wlserver_10.0/platform/lib/wlp/netuix_common.jar:/var/bea/10x/wlserver_10.0/platform/lib/wlp/netuix_schemas.jar:/var/bea/10x/wlserver_10.0/platform/lib/wlp/netuix_system.jar:/var/bea/10x/wlserver_10.0/platform/lib/wlp/wsrp-client.jar:/var/bea/10x/wlserver_10.0/platform/lib/wlp/wsrp-common.jar:/var/bea/wl-prod-dr/lib/antlr-2.7.5H3.jar:/var/bea/wl-prod-dr/lib/sqljdbc.jar>
<Apr 8, 2009 12:03:50 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.3.1-1_CR344434-89345-1.5.0_11-20070925-1628-linux-ia32 from BEA Systems, Inc.>
<Apr 8, 2009 12:03:51 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.0 MP1 Thu Oct 18 20:17:44 EDT 2007 1005184 >
<Apr 8, 2009 12:03:53 PM EDT> <Info> <Management> <BEA-141223> <The server name 10.129.1.148 specified with -Dweblogic.Name does not exist. The configuration includes the following servers
<Apr 8, 2009 12:03:53 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name 10.129.1.148 specified with -Dweblogic.Name does not exist. The configuration includes the following servers
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:148)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:38)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:378)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:125)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:647)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:419)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:377)
at weblogic.Server.main(Server.java:67)
im guessing its complaining that theres no dns entry for the new management vm.
im also unable to stop the managed node through admin console. here is the logs when i attempt to do so on the new management vm:
####<Apr 8, 2009 12:13:12 PM EDT> <Info> <Server> <managementservername> <managementservername> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1239207192996> <BEA-002634> <The server "managednodename" disconnected from this server.>
####<Apr 8, 2009 12:13:12 PM EDT> <Info> <JMX> <managementservername> <managementservername> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1239207193000> <BEA-149507> <JMX Connectivity has been discontinued with the managed server managednodename.>