Installation and Configuration guide
To be able to deploy RunAsService, you need to have the MS.Net
framework version 1.1 installed.
Installation is very easy, its just a matter of extracting the zip file into the desired location and running the Install.cmd file.
The Install.cmd batch file requires only 1 parameter, the account type the service uses to run. This can be one of the following:
For instance to install RunAsService using a specific
user account, type at the command prompt:
After entering a correct username and associated password the installation finishes.
RunAsService is configured using the MS.Net application configuration file.
The application configuration file is structured using XML format, and consists of 3 section:
<service.settings> <!-- Run application 1 as service --> <service> <name>Application 1</name> <executable>C:\Path-To\application-1.exe</executable> <parameters>Parameters for application 1</parameters> </service> ... <!-- Run application n as service --> <service> <name>Application n</name> <executable>C:\Path-To\application-n.exe</executable> <parameters>Parameters for application n</parameters> </service> </service.settings>
For every application that you want to run as a service, add a
Following is a sample configuration that contains 2 applications. The SubVersion server component, the application that started all this, and a java application.
<!-- Run Subversion server as service --> <service> <name>SubVersion Server</name> <executable>C:\Program Files\Subversion\bin\svnserve.exe</executable> <parameters>-d -r c:\bin\svn\repository</parameters> </service>
<!-- Run a java program as service --> <service> <name>Java Test Service</name> <executable>C:\j2sdk1.4.2_04\bin\java.exe</executable> <parameters>-cp c:\Java\test Test</parameters> </service>
Now that the configuration has completed, all that is left is starting the service.
Check the log4net logfile to see if any failure occured.