WebSphere Portal, Express Beta Version 6.1
Operating systems: i5/OS, Linux,Windows

Using the member fixer tool with IBM Lotus Web Content Management

Use the member fixer tool to check whether any Member Manager users or groups referenced in IBM® Lotus Web Content Management™ items have been renamed or deleted from Member Manager.

The member fixer tool will not work if there are any locked items in a Web content library. Before running the member fixer tool, an administrator must unlock any locked items.

If you have a large number of items, you may need to increase the session timeout setting of your server. This is changed using the WebSphere Application Server administration console. Go to Application Servers > WebSphere_Portal > Container Settings > Web Container Settings > Session Management. See the WebSphere Application Server information center for more information.

  1. Log in to the portal as an administrator.
  2. To view a report of Member Manager users or groups referenced in Web Content Management items, open the member fixer tool.
    Open the following URL in the browser:
    http://hostname.yourco.com:port_number/wps/wcm/connect
?MOD=MemberFixer&realm=realmname&library=libraryname
  3. If there have been changes to Member Manager users and groups, update the items that reference them.
    Open the following URL in the browser:
    http://hostname.yourco.com:port_number/wps/wcm/connect
?MOD=MemberFixer&realm=realmname&library=libraryname&fix=true
  4. If the member fixer tool indicates that certain mismatched member conditions exist, enter the specified URL to correct the conditions.
    Condition description URL to correct condition
    Nonexistent users or groups have alternate distinguished names (DNs) available. To update the items that reference the nonexistent users or groups:
    http://hostname.yourco.com:
port_number/wps/wcm/connect
?MOD=MemberFixer&realm=realmname&library=libraryname
&fix=true&alt_dn=update
    To remove the members that reference the users or groups:
    http://hostname.yourco.com:
port_number/wps/wcm/connect
?MOD=MemberFixer&realm=realmname&library=libraryname
&fix=true&alt_dn=remove
    Users or groups have invalid distinguished names (DNs) To remove users and groups that have invalid distinguished names:
    http://hostname.yourco.com:
port_number/wps/wcm/connect
?MOD=MemberFixer&realm=realmname&library=libraryname
&fix=true&invalid_dn=remove
    Users or groups have been found with mismatched external IDs in Member Manager. To update the external IDs in Member Manager with correct external IDs:
    http://hostname.yourco.com:
port_number/wps/wcm/connect
?MOD=MemberFixer&realm=realmname&library=libraryname
&fix=true&mismatched_id=update
    To remove those users and groups with mismatched external IDs:
    http://hostname.yourco.com:
port_number/wps/wcm/connect
?MOD=MemberFixer&realm=realmname&library=libraryname
&fix=true&mismatched_id=remove
    Note: These URL options can be combined when the conditions occur at the same time. For example, if alternate DNs are available for nonexistent users and groups and there are mismatched external IDs in Member Manager, you might use the following URL:
    http://hostname.yourco.com:port_number/wps/wcm/connect
?MOD=MemberFixer&realm=realmname&library=libraryname
&fix=true&alt_dn=update&mismatched_id=update

Preserving dates

You can preserve the last modified date of items updated by the member fixer module by adding &preserve_dates=true to the URL used to run the member fixer.

Multiple LDAP branches

The member fixer module's "alt_dn" mode checks for mapped alternate DNs in the WCMConfigServices.properties file before using the configured values in the wpconfig.properties file.

If you use multiple LDAP branches, you should perform the following steps to map the user and group domain names before running the member fixer module:

  1. Update the following property in the was_profile_root/PortalServer/wcm/config/WCMConfigServices.properties file file:

    EXISTING_DN_KEY=NEW_DN_SYNTAX where EXISTING_DN_KEY is the key constructed from the existing domain name and NEW_DN_SYNTAX is the replacement domain name syntax where the user's or groups id/common name has been replaced with the string "[ID]".

  2. Replace all equals characters "=" and spaces " " with underscores "_" and use the string "[ID]" in place of the user or group id/common name.

    For example, if you have a user branch with the following DN syntax: cn=John Smith,ou=Portal Users,o=IBM

    Construct the EXISTING_DN_KEY by replacing all "=" and " " with "_" in the domain name, and the user id, in this case "John Smith" with "[ID]", In this example the EXISTING_DN_KEY will be: cn_[ID],ou_Portal_Users,o_IBM

    If you are changing the syntax of this branch to cn=John Smith,ou=Portal,o=IBM the NEW_DN_SYNTAX will be the new domain name with the user id In this example, "John Smith" is replaced with "[ID]", i.e: cn=[ID],ou=Portal,o=IBM

    This results in the following mapping entry in your WCMConfigServices.properties file: cn_[ID],ou_Portal_Users,o_IBM=cn=[ID],ou=Portal,o=IBM

    You can use more than one mapping entry for different user and group branches. For example:

    cn_[ID],ou_Portal_Users,o_IBM=cn=[ID],ou=Portal,o=IBM cn_[ID],ou_WCM_Users,o_IBM=cn=[ID],ou=WCM,o=IBM

  3. You then run the member fixer as normal using the alt_dn option.
Parent topic: Users and groups
Library | Support | Terms of use |

Last updated: Wednesday, February 20, 2008 10:51am EST

Copyright IBM Corporation 2000, 2008. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)