Edit settings in the profiles-policy.xml file
to configure the status update feature.
Before you begin
To edit configuration files, use the IBM® WebSphere® Application
Server wsadmin client. See Starting
the wsadmin client for information about how to start the wsadmin
tool.
About this task
Profiles users can keep people in their network and the wider
organization informed about their latest activities by posting status
messages. You can control whether users can update their status message
by enabling or disabling status updates for specific profile types.
You can also configure access control settings for status updates
according to profile type. This profile policy is similar to that
of the activity stream settings described in Configuring the
recent updates feature; the Recent updates and Status
updates features are tightly related.
Procedure
The following steps provide information about the properties
you can set for the status update feature, and the access levels you
can configure.
- 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 Profiles Jython script interpreter.
- Enter the following command
to access the Profiles configuration files:
execfile("profilesAdmin.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.
-
Use the following command to check out the profiles-policy.xml
file:
ProfilesConfigService.checkOutPolicyConfig("<working_directory>", "cell_name")
where:
- working_directory is the temporary working directory to which the
configuration XML and XSD files will be copied. The files are kept in this working
directory while you make changes to them.
- cell_name is the name of the IBM WebSphere Application Server cell
hosting the Profiles application. This argument is required.
For
example:
ProfilesConfigService.checkOutPolicyConfig("/wsadminoutput", "jdoe30Node02Cell")
- Open the profiles-policy.xml file
using a text editor, from the temporary directory to which you checked
it out.
- Edit the following properties for the status update feature
as needed.
- profile.status
Enables or disables the status update feature.
This property
takes a string value. Possible values include:
- true. Enables the status update feature for users with the specified
profile type. The user interface for status messages displays.
- false. Disables the status update feature for users with the specified
profile type. The user interface for status messages does not display.
The access control level settings are also ignored when this feature
is disabled.
- profile.status.update
Controls user access to update status messages.
Access
levels for this property can be defined using one of the following
scopes:
- none. No one can update the status message of users with the specified
profile type.
- self. Users with the specified profile type can update their own
status message. Administrators can also update the status message
of users with the specified profile type.
For example:
<feature name="profile.status">
<profileType type="default" enabled="true">
<acl name="profile.status.update" scope="self" />
</profileType>
</feature>
This code sample enables the status update
feature for the default profile, but restricts the ability to update
status messages to profile owners and administrators.
- Save your changes and check the profiles-policy.xml file
back in using the following command:
ProfilesConfigService.checkInPolicyConfig()
- To exit the wsadmin client, type exit at
the prompt.
- Stop and restart the Profiles server.