Before you begin
This is not a required procedure. Only perform this if you want to change the level of filtering performed by the active content filter.
All of the applications, except Blogs, Wikis, and Forums, use the default acf-config.xml file, which filters active content in the following ways:
- You can change the formatting of content within rich text fields, but styles cannot be added to entries using HTML.
- Flash animations are not permitted.
The following configuration files are shipped with IBM Connections and stored in the LotusConnections-config\extern directory. To change the level of filtering that is performed by the active content filter, you can replace the default configuration file with one of these files:
Allows style changes, but strips forms and flash. The types of forms that are not allowed are form HTML elements. Form HTML elements are used to add things like buttons or fields to a web page. acf-config-nf-ns.xml
Prevents style changes and strips forms and flash.acf-config-nm.xml
Prevents users from changing the margins on images. By default, these applications permit image margin changes.acf-config-ns.xml
Allows forms, but strips style changes and flash. Preventing style changes affects rich text fields. If you configure the active content filter to prevent style changes, then users will not be able to perform the common tasks associated with changing the style of rich text content, such as changing the font color, margins, and so on.
To edit configuration files, you must use the wsadmin client. See Starting the wsadmin client
Parent topic: Securing applications from malicious attack
Applying common configuration property changes
Common configuration properties
- Edit the LotusConnections-config.xml file.
- Enter the following command to access the IBM Connections configuration file: execfile("connectionsConfig.py")
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 IBM Connections configuration files:
- working_directory is the temporary working 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.
AIX® and Linux® only: The directory must grant write permissions or the command does not run successfully.
- cell_name is the name of the WebSphere® Application Server cell hosting the IBM Connections application. This argument is case-sensitive, so type it with care. If you do not know the cell name, type the following command while in the wsadmin command processor:print AdminControl.getCell()
- AIX or Linux:LCConfigService.checkOutConfig("/opt/temp","foo01Cell01")
- Microsoft Windows:LCConfigService.checkOutConfig("c:/temp","foo01Cell01")
- Open the LotusConnections-config.xml file in a text editor.
- Find the <sloc:serviceReference> element for the application to which you want to change filtering levels. The application name is specified in the serviceName attribute.
Change the active content filter configuration for the applications with the following serviceName attributes:
- Add the following attribute to the <sloc:serviceReference> element for the application you want to change:
is one of the configuration files (acf-config-nf.xml
, or acf-config-ns.xml
For example, to configure the Activities application to prevent image margin changes, you could add the following acf_config_file
- Repeat Steps d and e to apply different filtering levels to different applications, and then save and close the configuration file.
- After making changes, you must check the configuration file back in and you must do so during the same wsadmin session in which you checked them out for the changes to take effect. See Applying common configuration property changes for information about how to save and apply your changes.
- Synchronize the nodes using the Integrated Solutions Console for the network deployment system.
- Restart the WebSphere Application Server.