The Windows Services Layer contains the PhoenixServices, which are a collection of services running as seperate processes from the Phoenix web application. Their main function is to handle long running operations that are not suited for a web application.
This topic contains the following sections.
Phoenix Services
The PhoenixServices run as a Windows service and are compiled into a single executable called phoenixservices.exe. The Phoenix Installer handles the installation of the services.
phoenixservices.exe currently contains 3 services:
Phoenix File Service - Removes old and unused files from the Phoenix temporary folder.
Phoenix Email Service - Transmits email batches.
Phoenix Search Service - Sends search requests to remote Phoenix nodes.
 Note: |
|---|
|
In a development environment, the Phoenix Services are not required -- the web application will run just fine without them. However, keep in mind that remote searching will be disabled, emails will not be sent, and temporary files will not be purged from the temp folder. |
Starting and Stopping services using the Services Management Console
Once installed, the PhoenixServices can be started and stopped independantly just like regular Windows services using the Services Management Console as shown below. You may also provide additional arguments for some services for debugging and troubleshooting. See the topic on each service for more information.
Configuration
The PhoenixServices are configured using settings from the phoenixservices.exe.config file. Normally, you will never need to modify this file since the Phoenix Node Configuration Tool (pxsetup.exe) makes changes to this file each time a new node is created.
 Important Note: |
|---|
|
If you manually edit phoenixservices.exe.config, you will need to start (or restart) all three services to apply the new settings. |
