Enable or disable the community owners ability to create
a unique web address for their community.
About this task
When this option is enabled, the ability to create a unique
community web address is provided in the Communities user interface
when users create or edit a community or subcommunity. Community members
can then use the web address to navigate directly to the community
or subcommunity. This feature is enabled by default.
Procedure
To enable or disable the community unique web address,
you need to update the communityHandle settings in the communities-config.xml file.
- Start the wsadmin client from the following
directory of the system on which you installed the Deployment Manager:
app_server_root\profiles\dm_profile_root\bin
where
app_server_root is
the WebSphere® Application
Server installation directory and
dm_profile_root is
the Deployment Manager profile directory, typically dmgr01.
You
must start the client from this directory or subsequent commands that
you enter do not execute correctly.
- Start the Communities Jython script interpreter.
- Use the following command
to access the Communities configuration files:
execfile("communitiesAdmin.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.
- Check out the Communities
configuration files using the following command:
CommunitiesConfigService.checkOutConfig("working_directory",
"cell_name")
where:
For example:
CommunitiesConfigService.checkOutConfig("/opt/my_temp_dir", "CommServerNode01Cell")
- Navigate to the working directory that you specified in
the previous step and open the communities-config.xml file
using a text editor.
- To configure the unique web address, set the value of the
enabled property for the communityHandle to true or false as needed.
For example, to disable the unique community web address:
<comm:communityHandle enabled="false" />
- 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
property changes in Communities for information about how to
save and apply your changes.