Email Notification Service Configuration

EmailNotification Service Configuration File

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configuration>

<!-- 
  ClearQuest login and password 
  cleartext password must be encrypted using "encrypt" command 
-->
<login>admin</login>
<password>unencrypted_password</password>

<!--
  DBSets configured for email notification
-->
<dbsets>
<!--each connection starts with <dbset> tag --> 
<dbset>
  <!--connection name (dbset)-->
  <name>ClearQuest Connection Name</name>
  <!-- dbset specific credentials can be specified here. It would override global settings
  password can be provided as clear text and encrypted using “encrypt” command.
 
  <login>connection-specific-login-name</login>
  <password>connection-specific-password</password>
  -->  

<!-- all user databases  -->
  <databases>
    <database>DB1</database>
    <database>DB2</database>
  </databases>
</dbset>

<dbset>
  <name>Another ClearQuest DBSet</name>
  <databases>
    <database>DB3</database>
  </databases>
</dbset>
</dbsets>

<!-- scheduled execution parameters  
     by  default the service queries the databases
     every 5 minutes (30 seconds) with 
     0 seconds offset from the beginning of the hour
<interval>300</interval>
<offset>0</offset>
-->
<!--additional configuration options 
Logfile – alternative log file name-->
<logfile>new_log_file_name</logfile>

<!-- Log level – desirable logging level -->
<loglevel>ALL</loglevel>

<!-- debug – turn on debug output -->
<debug>true</debug>

<!-- verbose – turn on console output -->
<verbose>true</verbose>


<!-- 
  Local configuration flag
  when set to "false" email settings are retrieved from the ClearQuest database
-->
<localconfig>false</localconfig>

<!-- example of the local email settings
<localconfig>true</localconfig>

 email host – SMTP server name. It might include port number. 

<email_host>hostname:port</email_host>
Alternatively, port number can be specified as <mail.smtp.port>port</mail.smtp.port>

  Authentication credentials. Password can be provided as clear text and encrypted using “encrypt” command.
<email_login>loginname</email_login>
<email_password>password</email_password>

turn on STARTTLS on smtp connection:
<mail.smtp.starttls>true</mail.smtp.starttls>
trust particular host self-signed or invalid certificate
<mail.smtp.ssl.trust>my.host.name</mail.smtp.ssl.trust>

use SSL:
<email_use_ssl>true</email_use_ssl>


-->

</configuration>