When installing IBM Connections on Windows only the Deployment Manager is added as a windows service during the installation. Parts like the node agent or later on the Connections clusters are not added. To do so you need to run the following command from /WebSphere/AppServer/bin :
WASService.exe -add SERVICENAME -servername SERVERNAME -profilePath “C:\IBM\WebSphere\AppServer\profiles\AppSrv01” -stopArgs “-user wasadmin -password password” -userid windowsadmin -password password -startType automatic
This a freely chosen name for the service.
This the name of the specific server that needs to be stopped (such as nodeagent). To find out the names you can go to /WebSphere/AppServer/profiles/AppSrv01/bin and run serverstatus.bat -all . This will list all servers including the running status.
Edit it to fit your environment.
These are necessary to be able to not just start the service, but to also stop it. It will provide the WAS admin credentials during the stop process. Enter your own wasadmin user ID / password.
This user has to be a windows user that has the right to start and stop services. Once the service is created you can change it in the service setting in the Services list from Windows to local system account.
This defines whether this service is started automatically at booting or not.