2 Replies Latest reply on Apr 8, 2001 2:06 PM by 3004

    Managed Servers on another machine

    3004

                I'm having problems getting a managed server running on
                another machine with NT. For simplicity, I'm using the
                'mydomain' that comes in the install. From the
                'mydomain' directory, I just:
                
                startWebLogic.cmd
                
                which starts up the weblogic server after adding my
                system password. Then, from the console, I add a new
                machine and a server on this machine. Then from the
                other machine in the equivalent 'mydomain' directory, I
                run:
                
                startManagedWebLogic.cmd server-2 machine1:7001
                
                And, it gives me this error:
                
                D:\bea\wlserver6.0>"D:\bea\jdk130\bin\java" -hotspot
                -ms64m -mx64m -classpath .;
                .\lib\weblogic_sp.jar;.\lib\weblogic.jar
                -Dweblogic.Domain=mydomain -Dweblogic.N
                ame="server-2" "-Dbea.home=D:\bea"
                -Dweblogic.management.server="machine1:7001"
                "-Djava.security.policy==D:\bea\wlserver6.0/lib/weblogic.policy"
                -Dweblogic.mana
                gement.password= weblogic.Server
                Enter password to boot weblogic server:system123
                Starting WebLogic Server ....
                Connecting to http://machine1:7001...
                ***************************************************************************
                
                The WebLogic Server did not start up properly.
                Exception raised:
                weblogic.management.configuration.ConfigurationException:
                serv
                er-2 not found
                weblogic.management.configuration.ConfigurationException:
                server-2 not found
                at
                weblogic.management.Admin.getBootstrapLocalServer(Admin.java:831)
                
                at
                weblogic.management.Admin.initialize(Admin.java:274)
                at
                weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
                at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
                
                at weblogic.Server.main(Server.java:35)
                Reason: Fatal initialization exception
                ***************************************************************************
                
                D:\bea\wlserver6.0>goto finish
                
                D:\bea\wlserver6.0>cd config\mydomain
                
                D:\bea\wlserver6.0\config\mydomain>ENDLOCAL
                
                
                I had a similar error when starting a managed server on
                the same machine, but I got it to work by changing the
                admin URL from "http://machine1:7001/" to just
                "machine1:7001".
                
                Any ideas?
                
                --Kurt
                
                
                
                
                
        • 1. Re: Managed Servers on another machine
          3004
          Kurt,
                    Your command line arguments are incorrect.
                    
                    its actually -Dweblogic.admin.host=machine1:7701
                    
                    Make sure you have server named server-2 in your config file and admin server
                    is not part of cluster.
                    
                    Cheers,
                    
                    -- Prasad
                    
                    Kurt Guenther wrote:
                    
                    > I'm having problems getting a managed server running on
                    > another machine with NT. For simplicity, I'm using the
                    > 'mydomain' that comes in the install. From the
                    > 'mydomain' directory, I just:
                    >
                    > startWebLogic.cmd
                    >
                    > which starts up the weblogic server after adding my
                    > system password. Then, from the console, I add a new
                    > machine and a server on this machine. Then from the
                    > other machine in the equivalent 'mydomain' directory, I
                    > run:
                    >
                    > startManagedWebLogic.cmd server-2 machine1:7001
                    >
                    > And, it gives me this error:
                    >
                    > D:\bea\wlserver6.0>"D:\bea\jdk130\bin\java" -hotspot
                    > -ms64m -mx64m -classpath .;
                    > .\lib\weblogic_sp.jar;.\lib\weblogic.jar
                    > -Dweblogic.Domain=mydomain -Dweblogic.N
                    > ame="server-2" "-Dbea.home=D:\bea"
                    > -Dweblogic.management.server="machine1:7001"
                    > "-Djava.security.policy==D:\bea\wlserver6.0/lib/weblogic.policy"
                    > -Dweblogic.mana
                    > gement.password= weblogic.Server
                    > Enter password to boot weblogic server:system123
                    > Starting WebLogic Server ....
                    > Connecting to http://machine1:7001...
                    > ***************************************************************************
                    >
                    > The WebLogic Server did not start up properly.
                    > Exception raised:
                    > weblogic.management.configuration.ConfigurationException:
                    > serv
                    > er-2 not found
                    > weblogic.management.configuration.ConfigurationException:
                    > server-2 not found
                    > at
                    > weblogic.management.Admin.getBootstrapLocalServer(Admin.java:831)
                    >
                    > at
                    > weblogic.management.Admin.initialize(Admin.java:274)
                    > at
                    > weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
                    > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
                    >
                    > at weblogic.Server.main(Server.java:35)
                    > Reason: Fatal initialization exception
                    > ***************************************************************************
                    >
                    > D:\bea\wlserver6.0>goto finish
                    >
                    > D:\bea\wlserver6.0>cd config\mydomain
                    >
                    > D:\bea\wlserver6.0\config\mydomain>ENDLOCAL
                    >
                    > I had a similar error when starting a managed server on
                    > the same machine, but I got it to work by changing the
                    > admin URL from "http://machine1:7001/" to just
                    > "machine1:7001".
                    >
                    > Any ideas?
                    >
                    > --Kurt
                    
                    
          • 2. Re: Managed Servers on another machine
            3004

                      I finally got this going, so I want to share it with others getting started in
                      managed servers/clusters.
                      
                      Apparently, "weblogic.admin.host" and "weblogic.management.server" are equivalent
                      properties. After I got things working, it didn't seem to matter which one I
                      used.
                      
                      Beware of adding a trailing slash on the end of the URL such as
                      "http://localhost:7001". I've been trained that this is not a well formed URL,
                      so I add it by habit; however, Weblogic will complain about not finding your
                      server. Just giving the "localhost:7001" will work as well.
                      
                      Whenever changing machines, servers, etc with the console, it's best to reboot
                      all the servers. I realize that it should be dynamic, but it doesn't seem to
                      work out that way. I'm learning to edit the 'config.xml' which seems to be a
                      safer bet at the moment.
                      
                      --Kurt
                      
                      
                      Prasad Peddada wrote:
                      
                      > Kurt,
                      > Your command line arguments are incorrect.
                      >
                      > its actually -Dweblogic.admin.host=machine1:7701
                      >
                      > Make sure you have server named server-2 in your config file and admin server
                      > is not part of cluster.
                      >
                      > Cheers,
                      >
                      > -- Prasad
                      >
                      > Kurt Guenther wrote:
                      >
                      > > I'm having problems getting a managed server running on
                      > > another machine with NT. For simplicity, I'm using the
                      > > 'mydomain' that comes in the install. From the
                      > > 'mydomain' directory, I just:
                      > >
                      > > startWebLogic.cmd
                      > >
                      > > which starts up the weblogic server after adding my
                      > > system password. Then, from the console, I add a new
                      > > machine and a server on this machine. Then from the
                      > > other machine in the equivalent 'mydomain' directory, I
                      > > run:
                      > >
                      > > startManagedWebLogic.cmd server-2 machine1:7001
                      > >
                      > > And, it gives me this error:
                      > >
                      > > D:\bea\wlserver6.0>"D:\bea\jdk130\bin\java" -hotspot
                      > > -ms64m -mx64m -classpath .;
                      > > .\lib\weblogic_sp.jar;.\lib\weblogic.jar
                      > > -Dweblogic.Domain=mydomain -Dweblogic.N
                      > > ame="server-2" "-Dbea.home=D:\bea"
                      > > -Dweblogic.management.server="machine1:7001"
                      > > "-Djava.security.policy==D:\bea\wlserver6.0/lib/weblogic.policy"
                      > > -Dweblogic.mana
                      > > gement.password= weblogic.Server
                      > > Enter password to boot weblogic server:system123
                      > > Starting WebLogic Server ....
                      > > Connecting to http://machine1:7001...
                      > > ***************************************************************************
                      > >
                      > > The WebLogic Server did not start up properly.
                      > > Exception raised:
                      > > weblogic.management.configuration.ConfigurationException:
                      > > serv
                      > > er-2 not found
                      > > weblogic.management.configuration.ConfigurationException:
                      > > server-2 not found
                      > > at
                      > > weblogic.management.Admin.getBootstrapLocalServer(Admin.java:831)
                      > >
                      > > at
                      > > weblogic.management.Admin.initialize(Admin.java:274)
                      > > at
                      > > weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
                      > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
                      > >
                      > > at weblogic.Server.main(Server.java:35)
                      > > Reason: Fatal initialization exception
                      > > ***************************************************************************
                      > >
                      > > D:\bea\wlserver6.0>goto finish
                      > >
                      > > D:\bea\wlserver6.0>cd config\mydomain
                      > >
                      > > D:\bea\wlserver6.0\config\mydomain>ENDLOCAL
                      > >
                      > > I had a similar error when starting a managed server on
                      > > the same machine, but I got it to work by changing the
                      > > admin URL from "http://machine1:7001/" to just
                      > > "machine1:7001".
                      > >
                      > > Any ideas?
                      > >
                      > > --Kurt