Required post-customization stepAdded by IBM | Edited by IBM on March 15, 2012 | Version 3 (Show original)
|Edit a configuration property to make sure that your users will see the changes you have made to the product the next time they log in without having to clear the cache of their web browser.
Edit a configuration property to make sure that your users will see the changes you have made to the product the next time they log in without having to clear the cache of their web browser.
Before you begin
Only perform this procedure if you made customization changes to the product user interface.
To edit configuration files, you must use the wsadmin client. See Starting the wsadmin client
About this task
Each product web page downloads static script and stylesheets that do not change often. To optimize performance, it is recommended that these pages are cached for extended periods of time so that end users only need to download them once per product upgrade. After you make customizations, you can instruct the server to ensure that all web browsers download new copies of these files. To force web browsers to refresh all cached content on the next visit, run the following command to update the product version stamp. The version stamp is automatically updated when you install any ifixes or major product version upgrades.
Parent topic: Customizing
Setting a maximum size on files
Setting maximum sizes on media, pages, and attachments
Restrict forum topic editing to creators
Enabling users to specify email notification preferences
Editing configuration files
Applying property changes in Activities
Applying property changes in Communities
Applying property changes in Forums
Applying property changes in the News repository
Applying property changes in Profiles
Applying Files property changes
Applying Wikis property changes
Customizing file type icons
Applying common configuration property changes
Customizing the Getting Started tab
Files configuration properties
Wikis configuration properties
- Use the wsadmin client to access and check out the IBM Connections configuration files.
- 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")
- Enter the following command to increment the value of the versionStamp property:
LCConfigService.updateConfig("versionStamp","<gmt_timestamp>") where <gmt_timestamp> is the GMT time. You can specify an empty string for the time stamp or provide a GMT value string. When you specify an empty string, the client calculates the current GMT time and updates the version stamp with that value. If you choose to provide the time, specify it using the following format: yyyyMMdd.HHmmss and specify the time in GMT. It is best to provide an empty string and let the client format the time stamp. For example: LCConfigService.updateConfig("versionStamp","").
- After making changes, you must check the configuration files 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.