Configuring an email provider for event notifications

To use Subscription Manager to send email notifications to users, you must specify and configure the email server that is used.

Before you begin

This topic applies to InfoSphere® Information Server version 11.3.1.2 and later. To configure email for versions 11.3.1.0 or 11.3.1.1, see this technote: http://www.ibm.com/support/docview.wss?uid=swg27044422.

You must have the Suite Administrator role to perform this task.

Procedure

  1. Open the common_event_mail.properties file, which is installed on the services tier at the default location of C:\IBM\Information Server\ASBServer\conf on Windows or /opt/IBM/Information Server/ASBServer/conf on UNIX or Linux.
  2. In the common_event_mail.properties file, specify the parameter values that are necessary to configure the simple main transfer protocol (SMTP) server for your email provider.

    The following table shows common parameters that are used for SMTP. The common_event_mail.properties file includes sample values for setting up a Gmail account by using these parameters. You can remove the comment hashmark (#) before some or all of the parameters in the file and provide the value appropriate for your email system. If you need to specify additional information, see the available parameters and their descriptions in the JavaMail API documentation: https://javamail.java.net/nonav/docs/api/com/sun/mail/smtp/package-summary.html.

    Table 1. Common parameters for configuring SMTP server.
    Parameter Description Sample value for Gmail account
    mail.smtp.sender The default user name for SMTP. my_user_name@gmail.com
    mail.smtp.password The password.

    {iisenc}izRA+9ADk58qnVRQaFh4iw==

    Note: This is an example of an encrypted password. To encrypt your password, run the encrypt command.
    mail.smtp.host The SMTP server to connect to. smtp.gmail.com
    mail.smtp.port The SMTP server port to connect to, if the connect() method does not explicitly specify a port. The default is 25. 465
    mail.smtp.socketFactory.port Specifies the port to connect to when you use the specified socket factory. If no value is specified, the default port is used. 465
    mail.smtp.auth If you specify true, the user is authenticated by using the AUTH command, if possible. The default is false. true
    mail.smtp.ssl.trust Specifying a host without specifying a socket factory enables use of a MailSSLSocketFactory. If you specify an asterisk (*), all hosts are trusted. You can specify a list of hosts to trust, each separated by white space. Otherwise, trust depends on the certificate that the server presents. smtp.gmail.com
    mail.smtp.socketFactory.class Specifies the name of a class that implements the javax.net.SocketFactory interface. This class is used to create SMTP sockets. javax.net.ssl.SSLSocketFactory
    mail.smtp.socketFactory.fallback If you specify true, failure to create a socket by using the specified socket factory class causes the socket to be created by using the java.net.Socket class. The default is true. false
  3. Save the file.
  4. If your email provider uses SSL, update your SSL configuration on the services tier computer:
    Table 2.
    For this WebSphere Application Server version Do these configuration steps
    Liberty Profile
    1. Run the UpdateSignerCerts command by using the server URL and port number.
      For example, for the Gmail example, run this command:
      UpdateSignerCerts -ss -url https://smtp.gmail.com:465
    2. Permanently accept the certificate.
    Network Deployment
    1. Log in to WebSphere Integrated Solutions Console.
    2. Browse to Global Security > SSL certificate and key management > Key stores and certificates > NodeDefaultTrustStore > Signer certificates.
    3. Click Retrieve from port.
    4. Specify the host name, SSL port, and alias.
    5. Click Retrieve signer information.
    6. Click OK, and save the configuration.
  5. If your WebSphere Application Server is configured for Internet Protocol v6 (IPv6) but your mail server is configured for IPv4, specify the following JVM argument in WebSphere Application Server to avoid connection errors: -Djava.net.preferIPv4Stack=true. See the following technote for more information: http://www.ibm.com/support/docview.wss?uid=swg21417365.
  6. Restart WebSphere Application Server.