| Portal, V6.1 |
The Portal User resource collection
Portal Personalization comes with a Portal User resource collection. This collection uses public APIs provided by IBM WebSphere Portal to access user information.
The collection allows rules to be written based on all properties of the WebSphere Portal user.
You use the Portal User resource collection to profile based on the property extension database. Use the Manage Properties menu option in the rule editor to add or remove dynamic or Lookaside properties from the collection. You may add any properties to this collection, but for them to function at runtime some values must be stored in Virtual Member Manager for the properties being used and the user executing the rule. The Manage Properties screen can also be used if the server on which you author rules has a different Virtual Member Manager configuration than the one on which the rules are deployed.
The resource collection is not new to WebSphere Portal V6.1, but it now shows the list of Portal User attributes automatically. You no longer have to add each WebSphere Portal property you want to use as a dynamic property in the Personalization rule editor. You do not need to generate Java code to use this collection or configure a security ID translator as is often required for Personalization User collections. You cannot currently write rules to select or recommend a list of users from this collection. This collection works with update rules as long as your repository allows writes. The collection works as if it is an LDAP collection that is automatically configured for the LDAP server.
You may continue to use your existing LDAP or custom user resource collections, and even use them in the same rules as the Portal User Collection. This is useful if you have multiple user repositories, you a have repository that is generally not used for Portal and only used for Personalization rules, or you requirements for attribute value translation ('CHI' should be interpreted as 'Chicago' for instance).
Use the Groups Attribute
The Groups attribute on the Portal User object exposes the distinguished names (dn) of the groups. An example of a distinguished name of a group is cn=wpsadmins, o=default organization, though the exact form will vary by your installation. Using distinguished name allows for more exact matching of groups, since it is possible for two groups to share a common name, such as wpsadmins. The includes operator may be used for inexact string matching, but will perform slightly slower. When possible, use the is operator and match to the distinguished name of the group.
Configure which properties show up for the Portal User Collection
The Personalization rule editor discovers the list of properties to show in rules through a public API (com.ibm.portal.um.PumaProfile). The list exposed by this API is configurable in your Member Manager configuration.
You may have a long list of properties that are available on the portal user, but do not want all of them to show up in the Personalization rule editor. For this purpose, set the property...
wmm.property.hide