I have checked all these above scenarios.
When I try to publish the ear to the Server - it gives this in the startServer.log -
0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info:com.ibm.*=all.
0000000a WsServerContr 1 Executing executeUtilityOnWindows with args: c:\Program Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv08\config WW-DEVEAIH-0C7RNode04Cell WW-DEVEAIH-0C7RNode04 server1 -fromWinService \\.\pipe\w6SvcPipe_2BE58_15E34
0000000a WsServerContr 1 invokedByWindowsService has been set to true earlier
0000000a ManagerAdmin I TRAS0018I: The trace state has changed. The new trace state is *=info.
0000000a AdminTool A ADMU0128I: Starting tool with the AppSrv08 profile
0000000a AdminTool A ADMU3100I: Reading configuration for server: server1
0000000a AdminTool A ADMU3200I: Server launched. Waiting for initialization status.
0000000a AdminTool A ADMU3000I: Server server1 open for e-business; process id is 4324
00000016 WindowsServic 3 inputRec == Starting Service: WW-DEVEAIH-0C7RNode04
00000016 WindowsServic 3 inputRec ==
00000016 WindowsServic 3 inputRec == Successfully started service.
0000000a WindowsServic 1 retCode from childProcess.waitFor() is 0
0000000a WindowsServic 3 -- interrupt the
thread that is collecting stdout
00000014 WindowsServic 3 readAndDisplayServiceLogFile(), caught InterruptedException
0000000a WindowsServic 3 exitCode = 0