EMS 7.x/8.0/8.1/8.2/8.2.1 versions do not provide a facility to install EMSCA as a Windows service. The following enhancement request has been created: EMS-4883
Running TIBCO EMS Central Administrator as Windows Service - This enhancement request will be implemented in the next EMS release: 8.3.
With EMS 7.x/8.0/8.1/8.2/8.2.1 versions, you can use the tool: procrun from the Apache commons daemon to create an EMSCA Windows service:
http://commons.apache.org/proper/commons-daemon/procrun.html
This solution is to stop the EMSCA service. This launches a second instance of EMSCA on top of the existing one, which fails to start because of locked files and then prunsrv manages to stop the whole thing. This is due to EMS 7.x/8.0/8.1/8.2/8.2.1 versiona of EMSCA that does not provide the StopMethod which is required for stopping the service. We do not recommend using Apache procrun to configure EMSCA as a service for EMS versions 7.x/8.0/8.1/8.2/8.2.1.
To configure prunsrv, you need to download prunsrv the Windows executable from the Apache website:
http://mirror.reverse.net/pub/apache//commons/daemon/binaries/windows/
Put the prunsrv executable under the EMS installation bin directory, then create a script to install the EMSCA Windows service. For example, the EMS bin directory is at D:\tibco\ems\8.2\bin. Prunsrv.exe is located in the same directory.
=================
set EMS_BIN=D:\tibco\ems\8.2\bin
set EMS_LIB=D:\tibco\ems\8.2\lib
set CLASSPATH=%EMS_BIN%\tibemsca.jar;%EMS_LIB%\jms-2.0.jar;%EMS_LIB%\tibjms.jar;%EMS_LIB%\tibjmsadmin.jar;%EMS_BIN%\jetty-all.jar;%EMS_BIN%\json_simple-1.1.jar;%EMS_LIB%\slf4j-api-1.4.2.jar;%EMS_LIB%\slf4j-simple-1.4.2.jar;%EMS_LIB%\tibcrypt.jar
d:\tibco\ems\8.2\bin\prunsrv //IS//emscaService --DisplayName="EMSCA Service" --Install=d:\tibco\ems\8.2\bin\prunsrv.exe --Jvm=auto --StartMode=jvm --StopMode=jvm --StartClass=com.tibco.messaging.emsca.internal.CentralAdminServer --Startup=auto --Classpath=%CLASSPATH% --StartPath=D:\tibco\ems\8.2\bin --StartParams="-c";"emsca.properties" --StopClass=com.tibco.messaging.emsca.internal.CentralAdminServer
=============
Then check the Window services, emscaService should be installed there. Start and Stop the service to test.