Community articleConfiguring the recent updates feature by profile type
Added by IBM contributorIBM on March 28, 2013
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

Edit settings in the profiles-policy.xml file to configure the recent updates feature according to profile type.



Edit settings in the profiles-policy.xml file to configure the recent updates feature according to profile type.

Before you begin

To edit configuration files, you must use the IBM® WebSphere® Application Server wsadmin client. See Starting the wsadmin client for information about how to start the wsadmin command-line tool.

About this task

The recent updates feature allows users to connect with people in their network by posting messages to their profile and commenting on their status messages. As administrator, you can enable or disable the feature for specific profile types, depending on your organization's needs. You can also configure access control settings according to profile type.

Procedure

The following steps provide information about the properties that you can set for the recent updates feature, and the access levels and scopes that you can configure.
  1. Start the wsadmin client from the following directory of the system on which you installed the Deployment Manager:
  2. 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.
  3. Start the Profiles Jython script interpreter.
    1. Enter the following command to access the Profiles configuration files:
    2. 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.
  4. Use the following command to check out the profiles-policy.xml file:
  5. 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")

  6. Open the profiles-policy.xml file using a text editor, from the temporary directory to which you checked it out.
  7. Edit the following properties for the recent updates feature as needed.
  8. profile.board
    Enables or disables the Profiles recent updates feature.

    Note: Configuring this property does not affect the ability to post status messages. For information about configuring the recent updates feature, see Configuration settings for the Recent Updates feature.

    This property takes a string value. Possible values include:
    • true. Enables the recent updates feature for users with the specified profile type. When set to true, message posts display in the user interface.
    • false. Disables the recent updates feature for users with the specified profile type. When set to false, message posts do not display in the user interface. The access control level settings are also ignored when the feature is disabled.

    profile.board.write.message
    Controls user access to post messages.

    Access levels for this property can be defined using one of the following scopes:
    • none. No user can post messages to users with the specified profile type.
    • self. Users with the specified profile type can view and post messages in their own recent updates area. Administrators can also view and post messages in the recent updates area of users with the specified profile type.
    • colleagues_not_self. Only people who belong to the network of the user with the specified profile type, and who have the person role, can view and post messages to the user's recent updates area. Users with the specified profile type cannot post messages to their own recent updates area.
    • Note: If resourceOwner is specified on the access check, the resource owner constraint must also be met, unless the user has the self role.
    • colleagues_and_self. People who belong to the network of the user with the specified profile type, and who have the person role, can view and post messages to the user's recent updates area. Users with the specified profile type can also post messages to their own recent updates area.
    • Note: If resourceOwner is specified on the access check, the resource owner constraint must also be met, unless the user has the self role.
    • person_not_self. Users with the person J2EE role can post messages to or view the recent updates area of users with the specified profile type. Users with the specified profile type cannot post messages to their own recent updates area.
    • Note: If resourceOwner is specified on the access check, the resource owner constraint must also be met, unless the user has the self role.
    • person_and_self. Users with the person J2EE role, including self, can post messages to or view the recent updates area of users with the specified profile type. Users with the specified profile type can also post messages to their own recent updates area.
    • Note: If resourceOwner is specified on the access check, the resource owner constraint must also be met, unless the user has the self role.
    profile.board.write.comment
    Controls user access to post comments to the recent updates area.

    Access levels for this property can be defined using one of the following scopes:
    • none. No one can post comments to the recent updates area of users with the specified profile type.
    • self. Users with the specified profile type can view and post comments to their own recent updates area. Administrators can also view and post comments to the recent updates area of users with the specified profile type.
    • colleagues_not_self. Only the people who belong to the network of the user with the specified profile type, and who have the person role, can view and post comments to the user's recent updates area. Users with the specified profile type cannot post comments to their own recent updates area.
    • Note: If resourceOwner is specified on the access check, the resource owner constraint must also be met, unless the user has the self role.
    • colleagues_and_self. People who belong to the network of the user with the specified profile type, and who have the person role, can view and post comments to the user's recent updates area. Users with the specified profile type can also post comments to their own recent updates area.
    • Note: If resourceOwner is specified on the access check, the resource owner constraint must also be met, unless the user has the self role.
    • person_not_self. Users with the person J2EE role can post comments to and view the recent updates area of users with the specified profile type. Users with the specified profile type cannot post comments to their own recent updates area.
    • Note: If resourceOwner is specified on the access check, the resource owner constraint must also be met, unless the user has the self role.
    • person_and_self. Users with the person J2EE role, including self, can post comments to and view the recent updates area of users with the specified profile type. Users with the specified profile type can also post comments to their own recent updates area.
    • Note: If resourceOwner is specified on the access check, the resource owner constraint must also be met, unless the user has the self role.
    For example:

    <feature name="profile.board">
      <profileType type="default" enabled="true">
       <acl name="profile.board.write.message" scope="colleagues_and_self" /> 
       <acl name="profile.board.write.comment" scope="colleagues_and_self" /> 
      </profileType>
      <profileType type="contractor" enabled="true">
       <acl name="profile.board.write.message" scope="person_and_self" /> 
       <acl name="profile.board.write.comment" scope="colleagues_and_self" /> 
      </profileType>
      <profileType type="visitor" enabled="false" /> 
    </feature>


    The code sample above enables the recent updates feature for the default profile type, but restricts access to post messages and comments to people in the profile owner's network who have the person and the profile owner. The recent updates feature is also enabled for the contractor profile type, but access to post messages is restricted to users with the person role, including the profile owner. Access to post comments is restricted to the profile owner, and people in the profile owner's network who have the person role. The recent updates feature is disabled for the visitor profile type.
  9. Save your changes and check the profiles-policy.xml file back in using the following command:
  10. ProfilesConfigService.checkInPolicyConfig()

  11. To exit the wsadmin client, type exit at the prompt.
  12. Stop and restart the Profiles server.
Related concepts
Working with update messages and comments