Edit configuration settings to enable email notifications in the Lotus® 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 Configuring notifications
topic before you can start this procedure.
About this task
You might choose not to enable email notifications if you have configured Lotus 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 consists of the following notifications:
- Activities: notify
- Blogs: notify
- Bookmarks: notify
- Communities: memberAdded and requestToJoin
- Profiles: notify
To configure email notifications, complete the following steps:
- Start the wsadmin client from the following directory of the system on which you installed the deployment manager:
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.
- Use the following command to access the Lotus Connections configuration files:
- 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.
If you want to enable mail for all of the applications and if you installed Lotus Connections into multiple WebSphere Application Server 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, you must perform these steps to edit the notification-config.xml file associated with each WebSphere Application Server profile.
- Microsoft Windows:
- From the temporary directory to which you checked out the notification-config.xml file, open it in a text editor.
- Find the <config> element with the ID attribute equal to notification-config.
- Change the value of the enabled attribute to true. For example:
- 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.
- Change the value of the enabled attribute associated with the <source> element to true. For example:
<type name="notify" notificationType="DIRECTED">
- Save and close the notification-config.xml file.
- Check in the configuration files using the following command:
If you plan to specify administrator email addresses now, keep the notifcation-config.xml file checked out; you must edit values in it to complete the next procedure.
What to do next
See Defining valid administrator email addresses
for some additional steps that you must take to configure automatic notifications in Activities.
Parent topic: Configuring notifications
Changing common configuration property values
Starting the wsadmin client
Defining valid administrator email addresses
Sending mail from any available mail server
Sending mail from a dedicated mail server