A common requirement when dealing with any application server install on Windows is to set it up as a Windows service.  It’s a bad idea to rely on the command line for running the server as it makes it far harder to administer.

For WebLogic the steps to do this are available on Oracle’s website:
http://docs.oracle.com/cd/E11035_01/wls100/server_start/winservice.html

A useful diagnostic if the service doesn’t appear to be working is to try and invoke the service using the beasvc command.  See the section “Verifying the Setup” in the above link for more information.  More times than not if your service isn’t starting then there was an error in the script you used to create the service in the first place (e.g. JVM argument).