Monitoring Audience Manager and Outbound E-mail processes

The <System> section of the configuration file OutboundEmail.xml allows you to specify system properties, including application monitoring. Application monitoring allows you to monitor the status of the Outbound E-mail processes.

About this task

You can monitor the following processes:

  • Queue Triggered Mailings Service
  • Synchronization Service
  • Collect Tracking Data service
  • Bounce Processor Service
  • Mailer Service

Procedure

  1. Install a Monitoring Agent on the Content Manager Server machine on which Outbound E-mail or Audience Manager is running. For more information, Monitoring SDL Tridion processes.
  2. Open OutboundEmail.xml located by default in the config subdirectory of your Content Manager root location in a plain-text editor or XML editor.
  3. Locate the <System> section, for example:
    <System>
      <LicenseFile /> 
      <CoreServiceUrl>http://localhost/webservices/CoreService2011.svc/wsHttp</CoreServiceUrl>
      <MonitoringAgentPort>20131</MonitoringAgentPort>
    </System>

    If you are using the SDL Tridion 2011-compatible endpoints, replace CoreService2011.svc with CoreService.svc.

  4. Set <MonitoringAgentPort> to the Heartbeat Monitoring ListenerPort specified in the cd_monitor_conf.xml configuration file.
  5. Save and close OutboundEmail.xml.
  6. Optionally, to override the default timeouts (in case false alarms are generated), add here ServiceType elements to the cd_monitor_conf.xml configuration file:
    <Service ServiceType="<OEServiceName>" TimeoutValue="10m" />

    where the value of the ServiceType can be one of the following:

    • OETrigger for Queue Triggered Mailings Service
    • OESynchronizer for Synchronization Service
    • OECollectTrackingData for Collect Tracking Data service
    • OEBounceProcessor for Bounce Processor Service
    • OEMailer for Mailer Service