It is too difficult if you/administrator need to start the WAS server manually everytime the machine is restarted or someone accidently logged out the user who started the process. You can copy the start server script to the Startup folder and it would start the server as expected, and other ways too to achieve the same effect.
Personally, I like to use Windows Service to control my processes because of 2 reasons, it integrates with the "Log On As" OS privilege and second, I get to see and click buttons, ;-)
To add Websphere Application Server processes, or Node Agent or Deployment Manager as Windows Services, you can utilize on the WASService.exe utility provided by Websphere resides in
For example, if you want to add the default profile (WAS 6 above) created by DWE installer as Windows Service, use the following command:
WASService.exe -add "WAS for DWE" -serverName server1 -profilePath
Yup, that's all, dude. Easy right?