Enable email notifications 

Edit configuration settings to enable email notifications in the IBM® Connections applications if you did not do so during the installation.

Before you begin

Only complete this procedure if you did not enable email notifications during the product installation. You must complete the steps described in the Configure notifications topic before you can start this procedure.

About this task

You might choose not to enable email notifications if you have configured IBM Connections to hide email addresses, for example. Even when you do not enable email notifications, if you installed the Home page application, the product still supports a subset of notifications that can be displayed in the Home page application. The subset includes the notifications of type "Directed," which are listed in the topic named Configure notifications.

To configure email notifications...


  1. Start the wsadmin client from the following directory of the system on which you installed the deployment manager:


      Note: You must start the client from this directory or subsequent commands that you try to run will not execute properly. See Starting the wsadmin client for more details.

  2. Access the IBM Connections configuration files:


      If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, pick the node where the file is stored. This information is not used by the wsadmin client when you are making configuration changes.

  3. Check out the notification-config.xml file using the following command:



      • <temp_dir> is the temporary directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft Windows operating system.

          Note: AIX and Linux only: The temporary directory must grant write permissions or the command will not run successfully.

      • <cell_name> is the WebSphere® Application Server cell to which you installed the application for which you are enabling mail. This argument is case-sensitive, so type it with care.

      Note: If you want to enable mail for all of the applications and if you installed IBM Connections into multiple WAS profiles, for example: Activities is installed on AppSrv01, Blogs is installed on AppSrv02, and so on), then there is a notification-config.xml file for each component. If you used this type of deployment, perform these steps to edit the notification-config.xml file associated with each WAS profile.

      For example:

      • AIX/Linux:


      • Microsoft Windows:


  4. From the temporary directory to which you checked out the notification-config.xml file, open it in a text editor.

  5. Find the <config> element with the ID attribute equal to notification-config.

  6. Make sure that the value of the enabled attribute is set to true. For example:
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="notification-config" version="3.0" xsi:noNamespaceSchemaLocation="notification-config.xsd" enabled="true" buildlevel="LC3.0.1_20110317_1229">

  7. Search for the <source name="<applicationName>" string to find the section of XML markup that defines the notification settings for the application for which you want to enable email notifications.

  8. Change the value of the enabled attribute associated with the <source> element to true. For example:

      name="Activities" imagesURL="{notification.source.url}/images/" enabled="true" defaultFollowFrequency="DAILY"> <type name="notify" notificationType="DIRECTED"> ... </source>

  9. Save and close the notification-config.xml file.

  10. Check in the configuration files using the following command:


      Note: If you plan to specify administrator email addresses now, keep the notifcation-config.xml file checked out; edit values in it to complete the next procedure.

What to do next

See Define valid administrator email addresses for some additional steps that take to configure automatic notifications in Activities.

Parent topic

Configure notifications

Related tasks
Change common configuration property values
Starting the wsadmin client
Define valid administrator email addresses
Sending mail from any available mail server
Sending mail from a dedicated mail server

January 10, 2012 9:58:33 AM


Jan 10, 2012 9:58:33 AM 8 Jan 10, 2012 9:55:33 AM 7 Jan 10, 2012 9:55:02 AM 6 Jan 10, 2012 9:50:29 AM 5 Jan 10, 2012 9:47:58 AM 4 Jan 10, 2012 9:47:06 AM 3 Jan 10, 2012 9:37:35 AM 2 Nov 21, 2011 3:48:06 PM Changed Step 6 to be passive -- to say "make sure it's set to true" in... 1