Email Service
The Email Service sends email notifications for business glossaries, scorecards, and workflows. Enable the Email Service to allow users to configure email notifications.
The Email Service sends emails for the following notifications:
- •Business glossary notifications.
- •Scorecard notifications.
- •Workflow notifications. Workflow notifications include emails sent from Human tasks and Notification tasks in workflows that the Data Integration Service runs.
The Email Service is associated with a Model Repository Service. The Model repository stores metadata for the email notifications that users configure. Both the Model Repository Service and the Email Service must be available for the Email Service to send email notifications.
The Email Service is highly available. High availability enables the Service Manager and the Email Service to react to network failures and failures of the Email Service. The Email Service has the restart and failover high availability feature. If a Email Service becomes unavailable, the Service Manager can restart the service on the same node or on a back-up node.
Before You Enable the Email Service
Before you enable the Email Service, complete the prerequisite tasks for the service.
Perform the following tasks before you enable the Email Service:
- •If the domain uses Kerberos authentication and you set the service principal level at the process level, create a keytab file for the service. For more information about creating the service principal names and keytab files, see the Informatica Security Guide.
- •Configure the Model repository options for the service.
- •Configure the email server properties.
Email Service Properties
You can configure general properties, Model Repository Service options, and email server properties for the Email Service. To configure the Email Service properties, select the service in the Domain Navigator and click Edit in the Properties view. You can change the properties while the service is running, but you must recycle the service for the changed properties to take effect.
General Properties
The following table describes the general properties for the service:
Property | Description |
---|
Name | Name of the service. You cannot change the name of the Email Service. |
Description | Description of the service. The description cannot exceed 765 characters. |
Node | Node on which the service runs. |
Backup Nodes | Nodes on which the service can run if the primary node is unavailable. |
Model Repository Service Options
Configure a Model repository to store metadata for the email notifications that users configure. The Model Repository Service must be available for the Email Service to send email notifications.
If the Model repository is integrated with a version control system, then you must synchronize the repository before you associate it with the Email Service.
The following table describes the Model Repository options for the service:
Property | Description |
---|
Model Repository Service | Model Repository Service associated with the Email Service. |
Username | User name of an administrator user in the Informatica domain. Not available for a domain with Kerberos authentication. |
Password | Password of the administrator user in the Informatica domain. Not available for a domain with Kerberos authentication. |
Email Server Properties
Configure the email server properties so Business Glossary and Data Quality users can configure email notifications.
The Email Service uses the email server configuration to send the following notifications:
- •Business glossary notifications.
- •Scorecard notifications.
- •Workflow notifications. Workflow notifications include emails sent from Human tasks and Notification tasks in workflows that the Data Integration Service runs.
The following table describes the email server properties for the service:
Property | Description |
---|
SMTP Server Host Name | The SMTP outbound mail server host name. For example, enter the Microsoft Exchange Server for Microsoft Outlook. Default is localhost. |
SMTP Server Port | Port number used by the outbound SMTP mail server. Valid values are from 1 to 65535. Default is 25. |
SMTP Server User Name | User name for authentication upon sending, if required by the outbound SMTP mail server. |
SMTP Server Password | Password for authentication upon sending, if required by the outbound SMTP mail server. |
SMTP Authentication Enabled | Indicates that the SMTP server is enabled for authentication. If true, the outbound mail server requires a user name and password. Default is false. |
Use TLS Security | Indicates that the SMTP server uses the TLS protocol. If true, enter the TLS port number for the SMTP server port property. Default is false. |
Use SSL Security | Indicates that the SMTP server uses the SLL protocol. If true, enter the SSL port number for the SMTP server port property. Default is false. |
Sender Email Address | Email address that the Email Service uses in the From field when sending notification emails from a workflow. Default is admin@example.com. |
Email Service Process Properties
When the Email Service is configured to run on primary and back-up nodes, a service process is enabled on each node. Only a single process runs at any given time, and the other processes maintain standby status. You can view the state of the service process on each node on the Processes view.
You can view the following information about the Email Service process:
- •Process Configuration. The state of the process configured to run on the node. The state can be Enabled or Disabled.
- •Process State. The state of the service process running on the node. The state can be Enabled or Disabled.
- •Node. The node that the service process runs on.
- •Node Role. Indicates whether the node has the service role, the compute role, or both roles.
- •Node Status. The state of the node that the process is running on. The state can be Enabled or Disabled.
Enabling, Disabling, and Recycling the Email Service
You can enable, disable, and recycle the Email Service from the Administrator tool.
By default, the Email Service is disabled. Enable the Email Service when you need to allow users to generate emails based on Human tasks in a workflow or changes to the Business Glossary. When you enable the Email Service, a service process starts on the node designated to run the service. The service is available to send emails based on the notification properties that users configure.
You might disable the Email Service if you need to perform maintenance. You might recycle the Email Service if you connect to a different Model Repository Service.
When you recycle or disable an Email Service, you must choose a mode to recycle or disable it in. You can choose one of the following options:
- •Complete. Wait for all subtasks to complete.
- •Stop. Wait up to 30 seconds for all subtasks to complete.
- •Abort. Stop all processes immediately.
Optionally, you can choose to specify whether the action was planned or unplanned, and enter comments about the action. If you complete these options, the information appears in the Events and History panels in the Domain view on the Manage tab.
To enable the service, select the service in the Domain Navigator and click Enable the Service.
To disable the service, select the service in the Domain Navigator and click Disable the Service.
To recycle the service, select the service in the Domain Navigator and click Recycle the Service. When you recycle the service, the Service Manager restarts the service. You must recycle the Email Service whenever you change a property for the service.