Environment
Novell exteNd Application Server 5.2.1
Microsoft Windows XP Professional Windows XP Professional Support Pack 1
Microsoft Windows XP Professional Windows XP Professional Support Pack 2
Situation
How can you capture log activity when you are running the exteNd
Application Server as a Windows service?
Resolution
You can use SilverServiceUtil to create an application server
service as follows:
SilverServiceUtil -create -service serviceName -display displayName -program pathToExecutable
[-outputDir outputDirectory -maxOutputFiles numFiles -startupOptions options]
By default, the log file will be written to your AppServer/temp directory and will be named "NameOfYourService.out" Note: By default this file will be overwritten each time you restart your service.
If you do not want the log file to be overwritten each time the service is restarted, you can use the numFiles SilverServiceUtil option to specify the number of log files to be created.
Here are some examples of how you can configure the numFiles option:
If you specify 0, or if the value is not specified, the log file will be overwritten each time the service is restarted. The log file will be named:
nameOfService.out
If you are running a Version 4 server as a service named SilverAppServerService4 and have specified 0 for numFiles, the one and only log file would be named:
SilverAppServerService4.out
If you specify a number larger than 0, a new file will be created each time the service is restarted, up to the number you specify, after which the numbering restarts. The log files will be named:
nameOfService.nnn.out
Using the preceding example, the first log file would be named:
SilverAppServerService4.000.out
The next time the service starts, the following log file will be created:
SilverAppServerService4.001.out
A warning message is sent to the server console when 80 percent of numFiles has been reached. If numFiles itself is reached, the service will behave as if numFiles were defined as 0, until the output files are removed.
SilverServiceUtil -create -service serviceName -display displayName -program pathToExecutable
[-outputDir outputDirectory -maxOutputFiles numFiles -startupOptions options]
By default, the log file will be written to your AppServer/temp directory and will be named "NameOfYourService.out" Note: By default this file will be overwritten each time you restart your service.
If you do not want the log file to be overwritten each time the service is restarted, you can use the numFiles SilverServiceUtil option to specify the number of log files to be created.
Here are some examples of how you can configure the numFiles option:
If you specify 0, or if the value is not specified, the log file will be overwritten each time the service is restarted. The log file will be named:
nameOfService.out
If you are running a Version 4 server as a service named SilverAppServerService4 and have specified 0 for numFiles, the one and only log file would be named:
SilverAppServerService4.out
If you specify a number larger than 0, a new file will be created each time the service is restarted, up to the number you specify, after which the numbering restarts. The log files will be named:
nameOfService.nnn.out
Using the preceding example, the first log file would be named:
SilverAppServerService4.000.out
The next time the service starts, the following log file will be created:
SilverAppServerService4.001.out
A warning message is sent to the server console when 80 percent of numFiles has been reached. If numFiles itself is reached, the service will behave as if numFiles were defined as 0, until the output files are removed.