Configure the active content filter for Activities, Communities, and Forums 

IBM Connections provides a set of active content filter (ACF) configuration files that you can apply to the Activities, Communities, or Forums applications to limit or widen the types of content that users can add to their entries.


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 and Wikis, use the default acf-config.xml file, which filters active content in the following ways:

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:

acf-config-nf.xml

acf-config-nf-ns.xml

acf-config-nm.xml

acf-config-ns.xml

To edit configuration files, use the wsadmin client. See Starting the wsadmin client for details.


Procedure

  1. Edit the LotusConnections-config.xml file.

    1. 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, pick the node where the file is stored. This information is not used by the wsadmin client when you are making configuration changes.

    2. Check out the IBM Connections configuration files:

        LCConfigService.checkOutConfig("<working_directory>","<cell_name>")

        where:

        • <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 WAS cell hosting the IBM Connections application. This argument is case-sensitive, so type it with care. To obtain the cell name:print AdminControl.getCell()

        For example:

        • AIX or Linux:LCConfigService.checkOutConfig("/opt/temp","foo01Cell01")

        • Microsoft Windows:LCConfigService.checkOutConfig("c:/temp","foo01Cell01")

    3. Open the LotusConnections-config.xml file in a text editor.

    4. 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:

    5. Add the following attribute to the <sloc:serviceReference> element for the application you want to change:

        For example:

        acf_config_file="<file_name>"

        where <file_name> is one of the files described in the list above.

        For example, to configure the Activities application to prevent image margin changes, you could add the following acf_config_file element:

        <sloc:serviceReference 
         bootstrapHost="myServer.example.com" 
         bootstrapPort="2817" 
         clusterName="" 
         enabled="true" 
         serviceName="activities" 
         ssl_enabled="true" 
         acf_config_file="acf-config-nm.xml">
          <sloc:href>
            <sloc:hrefPathPrefix>/blogs</sloc:hrefPathPrefix>
            <sloc:static 
             href="http://enterprise.example.com:9082" 
             ssl_href="https://enterprise.example.com:9447"/>
            <sloc:interService href="https://enterprise.example.com:9447"/>
          </sloc:href>
        </sloc:serviceReference>

    6. Repeat Steps d and e to apply different filtering levels to different applications, and then save and close the configuration file.

    7. After making changes, check the configuration file back in and do so during the same wsadmin session in which you checked them out for the changes to take effect. See Apply common configuration property changes for information about how to save and apply your changes.

  2. Synchronize the nodes using the Integrated Solutions Console for the network deployment system.

  3. Restart the WAS.


Parent topic

Securing applications from malicious attack

Related concepts
Administer Communities
Administer Forums


   

 

});