Enabling email for Process Portal notifications
Process Portal users can set their preferences to receive an email notification when a newly created task is assigned to them or their group. The configuration works for all types of email. To use this capability, you must enable the email environment to send notifications.
Before you begin
Important: The following information applies to both
Heritage Process Portal
(deprecated) and Process Portal.
Verify
that the following components are stopped:
- Workflow Center server
- Workflow Server
If Process Portal users
are using email with an IBM® Lotus
Domino V9 server, they can complete Process Portal tasks
directly from their email notifications. To make sure that the integration
is set up correctly, complete the following prerequisite tasks:
- Configure single sign-on (SSO) with an LTPA token on IBM WebSphere Application Server and IBM Lotus Domino. See the IBM Lotus Domino documentation at Configuring single sign-on with an LTPA token on IBM WebSphere and IBM Lotus Domino platforms.
- Make sure that the IBM Lotus
Domino server is set up properly by following the steps in the IBM Lotus Domino documentation:
- Create an XML file that you import into IBM Lotus Domino as described in Using widgets in iNotes. Customize the following example:
<?xml version="1.0" encoding="UTF-8"?> <webcontextConfiguration version="1.1"> <palleteItem contributeTabOnStartup="false" contributeToSideshelfOnStartup="false" description="Embedded Experience OpenSocial gadget used to display Coach" hideThumbnail="false" id="1074909581" imageUrl="" providerId="com.ibm.rcp.toolbox.opensocial.provider.internal.OpenSocialPalleteProvider" singletonSidebar="false" title="BPM Coach EE" url="http://bpm80.swg.usma.ibm.com:9080/ProcessPortal/gadgets/OpenSocial/BPMOpenSocialGadget.xml" viewImageUrl=""> <preferences/> <data> <object-capabilities url="http://[hostname]:[WC_defaulthost port]/ProcessPortal/gadgets/OpenSocial/BPMOpenSocialGadget.xml"> <grant-feature id="opensocial-data"/> <grant-feature id="opensocial-templates"/> <grant-feature id="opensocial-1.0"/> <grant-feature id="dynamic-height"/> <grant-feature id="embedded-experiences"/> <grant-feature id="open-views"/> <grant-feature id="settitle"/> <grant-feature id="osapi"/> <grant-feature id="content-rewrite"/> <grant-feature id="embedded-experiences-render"/> <grant-feature id="core"/> </object-capabilities> </data> </palleteItem> </webcontextConfiguration>
- Set up Domino Web SSO authentication between the iNotes server and IM server as described in Setting up iNotes with Sametime.
- Configure the component as described in Configuring Domino Social Edition Open Social component for iNotes clients.
- Complete the configuration as described in Widgets created from an OpenSocial gadget.
- Set up SSO in IBM Lotus
Notes.
- Create an account as described in Creating and editing accounts from Notes preferences.
- Publish the account for all users as described in the Using administrative accounts to manage client plug-ins document in the IBM Domino 9.0 Social Edition Administrator Help.
- Create an XML file that you import into IBM Lotus Domino as described in Using widgets in iNotes.
- Perform
the actions described in Configuring SSL communication.Tip: Using the same security protocol for both the Business Automation Workflow server and the email server prevents an issue where Process Portal users see a blank task completion view in email.
- Adding the email server to the trusted servers list prevents problems with sizing in Process Portal. See Adding servers to the trusted server list.
- The email facility (used for task notification,
task assignment, and so on) must be configured to use a local SMTP
server that is listening on the default port (
25
) and does not require authentication. This local SMTP server can then be used to forward emails to any other external SMTP that requires authentication.
About this task
The entries in the email properties section in the 99Local.xml configuration
file define the properties for your email environment. Make all required
modifications to the 100Custom.xml file.
Important: Do not edit the 99Local.xml file.
Procedure
What to do next
So that process participants receive email notifications, ask them to update their user preferences.