Starting a managed server as standalone

Question

          greetings
          environment: weblogic 7.0 clustered on 2 sun boxes (1 box has admin server and
          a managed server, the other just managed server).
          we recently had hardware failure on on the box with the admin server and the managed
          server. I need to document how to get the lone managed server up and running w/o
          the adminserver/box available. I would like know if, in theory, I could start
          the managed server as standalone? That is, normally the managed server is started
          by using startManagedWebLogic.sh, could I use startWebLogic.sh and would it work?
          I dont have a real test environment to test it out or I would have done that (this
          config exists in production only). Any thoughts on this greatly appreciated. thanks
          in advance
          paul
          

Answer 1

"paul wetzel" <[email protected]> wrote in message
          news:[email protected]...
          >
          > greetings
          > environment: weblogic 7.0 clustered on 2 sun boxes (1 box has admin server
          and
          > a managed server, the other just managed server).
          > we recently had hardware failure on on the box with the admin server and
          the managed
          > server. I need to document how to get the lone managed server up and
          running w/o
          > the adminserver/box available. I would like know if, in theory, I could
          start
          > the managed server as standalone? That is, normally the managed server is
          started
          > by using startManagedWebLogic.sh, could I use startWebLogic.sh and would
          it work?
          Paul, look in the document titled "Creating and Configuring WebLogic Server
          Domains" (rev. September 2002), chapter 4, section "Starting a Managed
          Server when the Administration Server is not accessible".
          I think you are supposed to continue to use the startManagedWebLogic.sh
          script, even when the Administration Server (AS) is down. When the Managed
          Server (MS) fails to connect to the AS, it will fall-back on local copies of
          the configuration files. Now, the problem is how to keep the local
          configuration files on the MS in sync with the AS files. If you have MS1
          running from the same directory as the AS, then you should be fine. But with
          MS2 running on a different piece of hardware, you must either manually copy
          the relevant files, or you must (before disaster strikes) enable replication
          of the files.