Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
E-mail administration
Before your run-time server can send personalized e-mail:
- Verify that the pznscheduler.ear has been installed as an Enterprise Application.
- Have a properly configured and operating SMTP e-mail server.
JavaMail provides the SMTP required to send e-mail. You can manage e-mail responses from customers and outgoing error conditions (such as unknown e-mail address) using a standard e-mail client.
- Configure a Mail Provider in the WebSphere Application Server Administrative Console.
- Create a mail provider or use the default mail provider. You can create a mail provider from WebSphere Application Server Administrative Console > Resources > Mail Providers.
- Create a mail session to use with Personalization. By default, Personalization looks for a mail session in jndi at mail/personalizationMailSession. The jndi name used is configurable in the PersonalizationService.properties if you want to use Personalization with an existing mail session you have configured. If you are creating a new mail session, specify a Mail Transport Host. This is the mail server Personalization uses to send e-mail. If your mail server is secured, specify a Mail Transport User ID and Mail Transport Password.
- Restart the server on which the e-mail rules execute for the changes to take effect.
- Additional configuration is available through the PersonalizationService.properties file. Using this file, you configure how often Personalization checks for rule events that run scheduled or repeating e-mails. You can also configure the mail session being used.