Accessing the notification configuration file
To make configuration changes to notifications in HCL Connections, you must access and work with the notification-config.xml file.
To access configuration files, you must use the wsadmin client. See Starting the wsadmin client for information about how to start the wsadmin command line tool.
After changing notification configuration settings, you must check in the configuration file and restart the server to apply the changes. You must perform the check-in during the same wsadmin session in which you checked out the files for the changes that you made to take effect.
- To change notification configuration settings, complete the following steps.
Start the wsadmin client from the following directory of the system where 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. For more information, see the Starting the wsadmin client topic.
Enter the following command to access the HCL Connections configuration files:
If you are prompted to specify a service to connect to, type 1 to select 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 by using a local file path, you must select 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 change 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. Note: If you installed HCL Connections into multiple WebSphere Application Server profiles, (for example: Activities is installed on AppSrv01, and Blogs is installed on AppSrv02), 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.
From the temporary directory to which you checked out the notification-config.xml file, open it in a text editor and make the necessary changes.
Save and close the notification-config.xml file.
Check in the configuration files by using the following command:
Update the version stamp property to force a refresh of users' web browsers, so that they see the email preference changes the next time they access the product. See Required post-customization step.
Parent topic:Configuring notifications