Hi Steven,
What I have done to automate the start of the Admin Server and its managed instance in Windows are as follows:
1. Since my WLS is running in Production mode, I have set my user ID and password in the WLS_USER and WLS_PW variables in the setDomainEnv.cmd file in <my domain>\bin directory, so that it no longer prompts for user id and password on WLS startup.
2. I set the startWebLogic.cmd as a startup script in Windows Task Scheduler, which automates start of Admin Server.
3. For the managed instances, I have used Weblogic Scripting to automate the starting of instances using the Weblogic console. I have piggy backed this weblogic script to run behind the Admin Server Script, so that the managed instances start only after the Admin Server. I have attached the sample script for starting one instance as a reference. You need to invoke this script by using the following executable in <wlserver_10.3 install dir>\common\bin:
wlst <WLST script name>
for e.g. wlst startserver.py.
This will start your script automatically, as if you logged into the Admin console and manually started the managed server instance.
Hope this and the attached file helps you in your objective. I have also mailed these to you on your email ID. Please get back to me if you have queries.
Regards,
Renga
E1 9.0 8.98.3.2
Windows Server 2008 64 bit, SQL Server 2008 64 bit, Oracle WLS 10.3.2.0 64 bit