<<

. 31
( 87 .)



>>

3. Click the New Folder icon to create a new folder.
4. Name the new folder Rule.
5. In the new folder, click the New Rule button to create a new rule.

At this point, you reach the rule de¬nition screen, as shown in Figure 9-1.


Editing Rules
The screen shown in Figure 9-1 allows you to specify the rule name and
description, as well as choose the rule type and edit the rule itself. Rule
editing is performed in the bottom part of the window. The rule editor
provides HTML links to help you identify a variable, and items are color
coded to help you recognize your options. For each such link, once you
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-09 WY009-BenNatan-v1.cls May 18, 2004 21:54




WebSphere Portal Personalization 167




Figure 9-1 Rule de¬nition screen for Pro¬ler rule.


click it a new window opens. In this window you may choose a value out
of a list of options. Once a selection is made, it is re¬‚ected in the rule text.
The color of links is as follows:

Blue indicates an item that is completed. It may still be clicked for
editing.
Red indicates an item that must be edited to ¬nish the rule.
Magenta indicates an item that is optional. It is not required to
complete the rule.

WebSphere personalization provides several types of rules, which are as
follows:

Pro¬lers”allow you to de¬ne types of visitors based on current user
properties and other object properties.
Select Content”allows you to choose content to be displayed, and
also allows to sort the order of returned results.
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-09 WY009-BenNatan-v1.cls May 18, 2004 21:54




168 Chapter 9


Update”allows you to perform updates to data (for example, user
pro¬les).
E-mail”allows you to send an e-mail.
Bindings”combine pro¬lers with an action (select, update, or
e-mail), so that speci¬c actions can take place under de¬ned
conditions.
Recommend Content”allows you to de¬ne rules for content
recommendation. This type of rule will be discussed in the next
section.
In order to complete editing a rule, you need to click all the blue links.
In the example of a pro¬ler rule, you need click the links for Pro¬le, Re-
source.Attribute, and value.
To enter a new pro¬ling rule, perform the following sequence of actions:
1. Click the Pro¬le link.
2. In the window that opens, enter the desired pro¬le name (see
Figure 9-2).
3. Click the Resource.Attribute link.
4. In the window that opens, choose the resource and attribute. For
example, Figure 9-3 shows the selection of the current date.
5. Click the value link.
6. In the value window, select the date, as shown in Figure 9-4.
7. Click Save.
Note that prior to saving you could add additional conditions or
additional classi¬cations of users (for example, using the else clause).




Figure 9-2 Specifying the pro¬le name.
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-09 WY009-BenNatan-v1.cls May 18, 2004 21:54




WebSphere Portal Personalization 169




Figure 9-3 Specifying the resource attribute.


Furthermore, the Resource.Attribute link allows you to use other pro¬lers
(via the Available Pro¬lers radio button) or an arithmetic expression com-
bining several attributes (via the respective radio button). The is equal
to link can be clicked to choose another type of comparison, out of the
following options:

includes
includes any of
is between
is between but not equal to
is equal to
is greater than




Figure 9-4 Specifying a date.
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-09 WY009-BenNatan-v1.cls May 18, 2004 21:54




170 Chapter 9


is greater than or equal to
is included in
is less than or equal to
is less than
is not equal to
Other types of rules are edited in a similar fashion, only that the building
blocks for these rules are different. Select content rules have the following
structure:
Select content
Whose Resource.Attribute is equal to value
add Condition
order as is
show all items

The whose clause is similar to the one used in pro¬ler rules. The two bottom
links in this rule allow ordering of the results, and limiting their number.
The ordering options are either “as is” (the default), in random ordering,
or sorted by some attributes. Show all items may be replaced by putting
a limit on the number of content elements to show. The limit may either be
a ¬xed numeric value or extracted from a resource attribute.
Update rules follow a similar structure:
Update
Resource.Attribute set to value

Binder rules have a more complicated structure:
When Profiler is
Profile do Action
Otherwise do Action
Always do Action
Exclude do Action
order as is
show all items

The binder rule de¬nes an action to take place for a certain pro¬le. The
action to perform can be de¬ned to be any previously de¬ned select content
or update rule. The Otherwise clause allows you to de¬ne actions to run in
case the pro¬le is different, and the Always clause allows de¬ning actions
that are to run regardless of the pro¬le. None of these actions are compul-
sory. The Exclude clause allows you to de¬ne an action whose result shall
be removed from the result set of the rule. In other words, it allows you
to remove items from the output of this rule. The ordering and item limit
clauses are identical to those used in the select content rule.
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-09 WY009-BenNatan-v1.cls May 18, 2004 21:54




WebSphere Portal Personalization 171


The e-mail rule allows you to de¬ne an action by which e-mail is auto-
matically sent. The e-mail rule has the following ¬elds:

Recipient
Sender
ccRecipient
bccRecipient
Subject
bodyURI

These ¬elds are extracted from select content actions.


Campaigns
Campaign Management is a component of Personalization that allows you
to make rules to work. The portal personalization has a “default” set of rules,
referred to as the Normal View. The Normal View de¬nes the personalization
of your Web site when there are no active campaigns. Normal View displays
all of the content spots on your Web site, what content type they use, and
their assigned rules.
Campaigns provide a platform for setting business goals and specifying
a path for a Web site to achieve these goals. Campaigns are de¬ned by three
components: a set of rules, a speci¬c period of time when the campaign is
active, and content spots to be ¬lled. Through the rules, campaigns may
deliver personalized information via the Web or e-mail. They may also
display forms to users where they can provide information to the site.
Campaigns are accessible via the Personalization tab in the portal, above
the rules.
The Campaigns view shown in Figure 9-5 summarized all currently avail-
able campaigns. A campaign includes a collection of rules assigned to con-
tent spots on Web pages. These rules override the Normal View rules dur-
ing the speci¬ed period. It is possible to prioritize campaigns to determine
which one takes precedence in case there is an overlap in dates. It is possible
to have two campaigns with the same priority. In that case, both are used
based on the split percentage de¬ned.
For example, Figure 9-6 shows a 30-70 split between two campaigns,
which means the ¬rst will be shown for 30 percent of the time and the other
in the remaining instances.
Within a campaign or within the Normal View, you may assign rules to
each of the content spots, as shown in Figure 9-7.
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-09 WY009-BenNatan-v1.cls May 18, 2004 21:54




172 Chapter 9




Figure 9-5 The Campaigns view.




Figure 9-6 De¬ning Campaign priorities.
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-09 WY009-BenNatan-v1.cls May 18, 2004 21:54




WebSphere Portal Personalization 173




Figure 9-7 Assigning rules to content spots.


The Personalization APIs
The WebSphere Portal Personalization provides open APIs that allow the
portal and WebSphere Studio Advanced Edition to access your own user
and content data in customer data stores.
The WebSphere application server provides user-pro¬le functionality via
the packages:
com.ibm.websphere.userprofile.UserProfile
com.ibm.websphere.userprofile.UserProfileManager
com.ibm.websphere.userprofile.UserProfileExtender

WebSphere Personalization provides a more powerful mechanism with
better support and larger ¬‚exibility in implementing resources (both user
and content) for personalization. Flexibility is achieved via the support for
data modeling. You can de¬ne user models and content models suitable for
your own requirements. The APIs supplied by IBM to access resources in
your own data store are as follows:
com.ibm.websphere.personalization.resources.Resource
com.ibm.websphere.personalization.resources.ResourceDomain3
com.ibm.websphere.personalization.resources.ResourceManager3

To provide your own implementations of the Personalization APIs for
accessing resources in the customer data store, you can use wizards included
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-09 WY009-BenNatan-v1.cls May 18, 2004 21:54


<<

. 31
( 87 .)



>>