Restrict forum topic editing to creatorsAdded by IBM | Edited by IBM on March 15, 2012 | Version 2 (Show original)
|You can restrict the editing of forum topics or replies to their creators. Only someone who created the topic or reply can edit it.
You can restrict the editing of forum topics or replies to their creators. Only someone who created the topic or reply can edit it.
About this task
To restrict forum topic editing to creators you must check out the LotusConnections-config.xml
file, open it in an editor and add some elements, and then check it back in. Then you must use a similar process to check out the forum-policy.xml
file, open it in an editor and delete rows containing edit_all_post
, and then check it back in.
- Start the wsadmin client by completing the following steps:
- Open a command prompt, and then change to the following directory of the system on which you installed the deployment manager:
is the WebSphere Application Server installation directory and <dm_profile_root>
is the Deployment Manager profile directory, typically dmgr01. For example, on Windows:
You must run the following command to start the wsadmin client from this specific directory because the Jython files for the product are stored here. If you try to start the client from a different directory, then the execfile() command that you subsequently call to initialize the administration environment for an IBM
® Connections component does not work correctly.
- Enter the following command to start the wsadmin client:
- AIX or Linux:
./wsadmin.sh -lang jython -user <admin_user_id> -password <admin_password> -port <SOAP_CONNECTOR_ADDRESS Port>
- Microsoft Windows:
wsadmin -lang jython -user <admin_user_id> -password <admin_password> -port <SOAP_CONNECTOR_ADDRESS Port>
Use the wsadmin client to access and check out the IBM Connections configuration files:
- <admin_user_id> is the user name of a person in the Administrator role on the IBM WebSphere® Application Server.
- <admin_password> is the password of the WebSphere Application Server administrator.
- <SOAP_CONNECTOR_ADDRESS Port> is the SOAP port for the WebSphere Application Server. The default value of the SOAP port is 8879. If you are using the default port value, you do not need to specify this parameter. If you are not using the default and you do not know the port number, you can look up its value in the WebSphere Application Server Integrated Solution Console. To look up the SOAP port number, perform the following steps:
- Open the WebSphere Application Server Integrated Solution Console for the deployment manager, and then select System Administration -> Deployment Manager.
- In the Additional properties section expand Ports, and then look for the SOAP_CONNECTOR_ADDRESS port entry to find the port number.
- AIX or Linux:
./wsadmin.sh -lang jython -username primaryAdmin -password p@assword -port 8879
- Microsoft Windows:
wsadmin -lang jython -username primaryAdmin -password p@assword -port 8879
Open the LotusConnections-config.xml file in an editor, and then add the following content:
- 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 web browser to make sure you did not introduce any errors. XML files that are well formed display in a web browser; if there are errors, the web browser reports that an error was encountered. Fix an errors before proceeding.
Check the configuration files back in during the same wsadmin session in which you checked them out.
In the wsadmin client, check out the forum-policy.xml file following steps in the topic Editing configuration files.
Open the forum-policy.xml file in an editor and delete any row containing edit_all_post.
Check in the forum-policy.xml file following steps in the topic Editing configuration files.
Stop and restart all of the IBM Connections application servers.
- Update the value of the version stamp configuration property to force users' browsers to pick up this change. 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","").
See Required post-customization step for more details.
- To check in the changed configuration property files, use the following command:
- After making updates, type the following command to deploy the changes:
- Do not exit the wsadmin client.
Parent topic: Administering Forums
Editing configuration files
Required post-customization step