The phoenixservices.exe.config file is used to configure all three PhoenixServices.

This topic contains the following sections.

Location

Phoenix installation folder.

The phoenixservices.exe.config file is used to configure the PhoenixServices.

Important Note:
If you manually edit phoenixservices.exe.config, you will need to start (or restart) all three services to apply the new settings.

connectionStrings

A database connection string for each Phoenix node that exists on the server must be identified in this section. Connection strings are added using the add element. The name attribute is used to uniquely identify the connection string. The connectionString attribute supplies the connection string information.

Important Note:
The connection string names will typically be identical to the connection strings found in the web.config of each individual Phoenix web folder on the server.

CopyAdding connection strings

<add name="PhoenixNode_1" connectionString="Server=.\MyServer;Database=PhoenixNode1;User ID=foo;Password=bar;Persist Security Info=True" />
<add name="PhoenixNode_2" connectionString="Server=.\MyServer;Database=PhoenixNode2;User ID=foo;Password=bar;Persist Security Info=True" />

PhoenixEmailService Settings

The PhoenixEmailService relies on the settings defined in this section.

SmtpServerName

The name of the SMTP server.

SmtpServerPort

The port number that the SMTP server uses.

SmtpUsername

For SMTP servers that requires authentication, this setting provides the username. Leave this value empty, if your SMTP server does not require authentication.

SmtpPassword

For SMTP servers that requires authentication, this setting provides the password. Leave this value empty, if your SMTP server does not require authentication.

SmtpFromEmail

For SMTP servers that do not allow relaying, this setting provides the email address of a sender that the SMTP server recognizes. Leave this value empty, if your SMTP server allows relaying.

PhoenixFileService Settings

The PhoenixFileService relies on the settings defined in this section.

FileTempFolder

A list of temporary folders for all Phoenix nodes running on the server. Each path is seperated with a semi-colon. When the PhoenixFileService runs, it traverses the contents of each path identified in this value. Files that are older than the interval set in FileAgeThreshold are removed.

Caution:
Extreme caution must be taken when modifying this value manually. Ensure that each path refers to the temporary folder that is used for each Phoenix node on the server. Indicating a path to a system folder, a program folder, or any other path that is not used by Phoenix to store temporary files could result in irreversible data loss, program instability or even an unrecoverable system failure. The PhoenixFileService has no knowledge of the files it is deleting and does not make any backups. Nor does it make use of the Windows recycle bin. Once they are gone, they are gone.

Caution:

Extreme caution must be taken when modifying this value manually.

Ensure that each path refers to the temporary folder that is used for each Phoenix node on the server. Indicating a path to a system folder, a program folder, or any other path that is not used by Phoenix to store temporary files could result in irreversible data loss, program instability or even an unrecoverable system failure.

The PhoenixFileService has no knowledge of the files it is deleting and does not make any backups. Nor does it make use of the Windows recycle bin. Once they are gone, they are gone.

FileScanInterval

The interval (in minutes) that the PhoenixFileService performs a scan of all known temporary folders. A value of 10 is typically used.

FileAgeThreshold

The age of the file (in minutes) before it should be removed by the PhoenixFileService. A value of 1440 (24 hours) is typically used.

PhoenixSearchService Settings

The PhoenixSearchService relies on the settings defined in this section.

SearchRequestTimeout

The number of seconds to wait for a remote node to return search results. If the remote node does not response to the request within this interval, the request is abandoned and processing moves on to the next node in the list. This value should typically be left at around 60 to 90 seconds.

Example

Below is an example of a phoenixservices.exe.config file that identifies two Phoenix nodes configured on the server.

CopyPhoenixServices Configuration File

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <connectionStrings>
    <add name="PhoenixNode1" connectionString="Server=MyServer;Database=Node1;User ID=phoenixUser;Password=foobar;Persist Security Info=True" />
    <add name="PhoenixNode2" connectionString="Server=MyServer;Database=Node2;User ID=phoenixUser;Password=foobar;Persist Security Info=True" />
  </connectionStrings>
  <appSettings>
    <add key="SmtpServerName" value="mysmtpserver" />
    <add key="SmtpServerPort" value="25" />
    <add key="SmtpUsername" value="" />
    <add key="SmtpPassword" value="" />
    <add key="SmtpFromEmail" value="" />
    <add key="FileTempFolder" value="D:\wwwroot\PhoenixNode1_Content\temp;D:\wwwroot\PhoenixNode2_Content\temp" />
    <add key="FileScanInterval" value="10" />
    <add key="FileAgeThreshold" value="1440" />
    <add key="SearchRequestTimeout" value="90" />
  </appSettings>
</configuration>