Disabling embedded applications in notificationsAdded by IBM on February 11, 2013 | Version 1 (Original)
|Standard notifications sent from IBM® Connections can include an OpenSocial embedded application that is displayed in supported email clients. You can remove embedded applications from all supporting notifications by disabling a configuration property in the notification-config.xml file.
Before you begin
To run administrative commands, you must use the wsadmin client. See Starting the wsadmin client
About this task
The notification types listed in the following table include the application/embed+json MIME part that is required for embedded application support. All other notifications support HTML and plain text versions only.
Table 1. Notification types that support embedded applications
|Files (specific to a file)||
- Create a file
- Update a file
- Comment on a file
- Like a file
- Share a file
- Create a blog entry
- Update a blog entry
- Comment on a blog entry
- Like a blog entry
|Ideation Blog entries||
- Create an ideation blog idea
- Update an ideation blog idea
- Comment on an ideation blog idea
- Create a forum topic
- Update a forum topic
- Reply to a forum topic
- Post a status update
- Comment on a status update
- Like a status update
- Repost a status update
- Send a network invitation
Embedded applications are only included in standard notifications; users must select the individual email option available from the Email Preferences page to receive them.
Parent topic: Configuring notifications
- 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.
- Enter the following command to 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, you must pick the node where the file is stored. This information is not used by the wsadmin client when you are making configuration changes.
- Enter the following command to check out the notification-config.xml file:
- 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.
- 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 installed IBM
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 application. 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.
- AIX or Linux:
- Microsoft Windows:
- From the temporary directory to which you checked out the notification-config.xml file, open it in a text editor.
- Locate the following section of the file:
<property name="globalSenderName">IBM Connections Administrator</property>
- Change the value of the <disableEmbeddedAppsInNotifications> element to true as follows:
The default value is false.
- Save and close the notification-config.xml file.
- Check in the configuration files using the following command: