| Running Protege Server as a Windows Service |
|
|
|
|
It is important that the Essential repository server is always running and able to serve requests from its clients, so it should be configured to run as a Service on Windows server platforms. Currently, the Protege software does not include the capability to run as a native Windows service, so the Microsoft SrvAny tool from the Windows Resource Kit should be used. Warning: The following steps include editing the Windows Registry and should be only be attempted by qualified personnel. If in any doubt, please consult your systems administrator. The Essential Project can accept no responsibility for any errors or failures resulting from editing the registry.
To use the Microsoft SrvAny tool, the Windows Resource Kit must be installed, as follows:
You should receive the following message: "The service was successfully added!" If you receive the "Unable to find the file at the given path" message, then modify the drive and directory to point to the location of the srvany.exe file Next edit the registry entry for the new service as follows:
Next, open the Services panel from Start->Settings->Control Panel->Administrative Tools->Services. In the list of services, you will see "Essential AM Server". Start this service to start the Protege Server. Then, double click on this service and set it to have Startup Type set to "Automatic". NOTE: It is normal for this to show in the list of services as not started, even when the Protege Server is actually running because the service invokes a batch file, which in turn invokes a batch file.
This solution, Windows Server 2003 Resource kit, enables a batch file to be started via a Service. Full Service-style behaviour may not operate as expected (e.g. start / stop) as the Essential server startup program is a Windows batch file that invokes 2 separate executables. To this end, a shutdown command is provided to gracefully stop the Protege server. Stopping the service from the control panel will NOT stop Protege server.
Defining Essential AM Server Service DependenciesWhere a database-based repository is used, the Essential Server will not start up correctly if it cannot establish a connection to the database that is now hosting the repository. To help with the automatic startup of the Essential Server, define a dependency between the Essential AM Server service and another service, such as your database server instance (if it is co-located with Essential) or with Tomcat (used for the Essential Viewer):
|