Trying to create Managed Server service in Win 2003 does not work

Question

Hello ... I've created an AdminServer service with no problems:
SETLOCAL
set DOMAIN_NAME=ClassicDomain
set USERDOMAIN_HOME=D:\Apps\Middleware\user_projects\domains\ClassicDomain
set SERVER_NAME=AdminServer
set PRODUCTION_MODE=true
set MEM_ARGS=-Xms256m -Xmx512m
call "D:\Apps\Middleware\user_projects\domains\ClassicDomain\bin\setDomainEnv.cmd"
call "D:\Apps\Middleware\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
I can get the AdminServer to start and get into the Admin Console.
I'm trying to create a service for the WLS_Forms Managed Server and can create the service, which does start ... but it does not start my WLS_Forms Managed Server:
SETLOCAL
set DOMAIN_NAME=ClassicDomain
set USERDOMAIN_HOME=D:\Apps\Middleware\user_projects\domains\ClassicDomain
set SERVER_NAME=WLS_Forms
set PRODUCTION_MODE=true
set
JAVA_OPTIONS=-Dweblogic.Stdout="D:\Apps\Middleware\user_projects\domains\ClassicDomain\stdout.txt" -Dweblogic.Stderr="D:\Apps\Middleware\user_projects\domains\ClassicDomain\stderr.txt"
set ADMIN_URL=http://localhost:7001
set MEM_ARGS=-Xms1024m -Xmx1024m
call "D:\Apps\Middleware\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
Both services/servers reside on the same box.
Can someone lend a hand and indicate what is failing?
Thanks

Answer 1

That is not typically the case since you could normally also use a start script like:
<DOMAIN_HOME>/bin/startManagedServer(.sh/.cmd) managedServerName
One thing to note is that Node Manager is the mechanism by which the Admin Console is able to start the managed servers. The Admin Server has not mechanism to do this directly, it is indirectly done via Node Manager.
You should ask in the Forms / Reports forum for how that product is typically started with WebLogic in 11g.
Forms