At G Quincy Demo

atg
Version 2007.1
Quincy Funds Demo
Documentation
ATG
One Main Street
Cambridge, MA 02142
www.atg.com
Quincy Funds Demo Documentation

Document Version
Doc2007.1 QFDEMODOCv1 7/13/07
Copyright
Copyright 1998-2007 Art Technology Group, Inc. All rights reserved.
This publication may not, in whole or in part, be copied, photocopied, translated, or reduced to any electronic medium or machine-readable
form for commercial use without prior consent, in writing, from Art Technology Group, Inc. (ATG) ATG does authorize you to copy
documents published by ATG on the World Wide Web for non-commercial uses within your organization only. In consideration of this
authorization, you agree that any copy of these documents which you make shall retain all copyright and other proprietary notices
contained herein.
Trademarks
ATG, Art Technology Group, and DYNAMO are registered trademarks of Art Technology Group, Inc.
ATG Wisdom, ATG Dynamo Application Server, ATG Adaptive Scenario Engine, ATG Scenario Personalization, ATG Portal, ATG Commerce,
ATG Content Administration, ATG Data Anywhere Architecture, ATG Search, ATG Response Management, ATG Merchandising, ATG
Knowledge, ATG Self Service, ATG Commerce Assist, ATG Advisor, ATG Forum and ATG Business Control Center are trademarks of Art
Technology Group, Inc.
Microsoft, Windows and Word are the trademarks or registered trademarks of Microsoft Corporation in the United States and other countries.
IBM, AIX, and MQ-Series are the trademarks or registered trademarks of IBM Corporation in the United States and other countries. Oracle is a
registered trademark, and other Oracle product names, service names; slogans or logos referenced in this document are trademarks or
registered trademarks of Oracle Corporation. Adobe Acrobat Reader is a registered trademark of Adobe. CORBA is a trademark of the OMG
(Object Management Group). Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems,
Inc. in the United States and other countries. Primus, and its respective logo, and Primus Knowledge Solutions, are trademarks, registered
trademarks, or service marks of Primus.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
EditLive Authoring Software Copyright 2004 Ephox Corporation. All rights reserved. Includes code licensed from RSA Security, Inc. Some
portions licensed from IBM are available at http://oss.software.ibm.com/icu4j/. Includes software developed by the Apache Software
Foundation (http://www.apache.org/). Contains spell checking software from Wintertree Software Inc. The Sentry Spell Checker Engine
2000 Wintertree Software Inc.
All other product names, service marks, and trademarks mentioned herein are trademarks of their respective owners. This publication may
not, in whole or in part, be copied, photocopied, translated, or reduced to any electronic medium or machine-readable form for commercial
use without prior consent, in writing, from Art Technology Group (ATG), Inc. ATG does authorize you to copy documents published by ATG
on the World Wide Web for non-commercial uses within your organization only. In consideration of this authorization, you agree that any
copy of these documents which you make shall retain all copyright and other proprietary notices contained herein.
No Warranty
This documentation is provided as is without warranty of any kind, either expressed or implied, including, but not limited to, the implied
warranties of merchantability, fitness for a particular purpose, or non-infringement.
The contents of this publication could include technical inaccuracies or typographical errors. Changes are periodically added to the
information herein; these changes will be incorporated in the new editions of the publication. ATG may make improvements and/or changes
in the publication and/or product(s) described in the publication at any time without notice.
Limitation of Liability
In no event will ATG be liable for direct, indirect, special, incidental, economic, cover, or consequential damages arising out of the use of or
inability to use this documentation even if advised of the possibility of such damages. Some states do not allow the exclusion or limitation of
implied warranties or limitation of liability for incidental or consequential damages, so the above limitation or exclusion may not apply to
you.
ATG One Main Street Cambridge MA 02142
617.386.1000 phone 617.386.1111 fax www.atg.com
ATG Quincy Funds Demo Documentation
Contents
Introduction
About this Document

Audience
Modifying the Demo
2
2
3
Getting Started
Exploring the Demo

Running Quincy Funds on Oracle
5
6
Touring Quincy Funds
Entering as a Guest
Registering as an Investor
Changing Your Profile and Preferences
Changing Your Language Preference
Browsing as a Broker
Targeted E-Mail
Logging Out
Further Exploration
Tracking Visitor Interests

Exploring Tracking Scenarios
How Tracking Affects a Profile
Tracking for Page Developers
Tracking and Repositories for Programmers
Targeting Content
Previewing a Page as Different Users
Examining Targeting Rules
Targeting for Page Developers
Targeting for Programmers
Managing Visitors through Scenarios

Demonstrating a Simple Scenario
Inspecting the PromoteSpecialSituations Scenario
Demonstrating a Complex Scenario
Inspecting the PromoteGrowthFund Scenario
10
11
13
13
16
18
18
19
21
22
23
24
24
27
29
30
31
33
35
35
36
37
37
iii
Contents
Scenarios Sharing Slots

Scenarios for Page Developers
Scenarios and Slots for Programmers
40
42
43
Analyzing Visitor Behavior
45
Examining the SignupPromoTrial Scenario

Generating a Chart
Analyzing Visitor Behavior for Page Developers
Analyzing Visitor Behavior for Programmers
Repository Structure in the Quincy Funds Demo

Content Repository Loaders in the Quincy Funds Demo
Serving SQL Repository Items as org.w3c.Documents
atg.xml.FileToDOMPropertyDescriptor
atg.xml.StringToDOMPropertyDescriptor
Appendix A: Additional Scenario Examples

Converting Members into Satisfied Patrons
Sending a Monthly Newsletter
Using Scenario Templates
Advertising a Seminar
The E-Mail Seminar Promotion Segment
The Show Seminar Promotion Segment
Index
46
47
49
50
51
52
53
54
54
57
57
58
59
60
60
61
63
iv
Contents
1 Introduction
The Quincy Funds demo is designed to display the powerful Web site capabilities of the ATG 2007.1
product suite, specifically the personalization and scenarios features of the ATG Adaptive Scenario Engine.
The demo is a Web site for a fictional financial services company called Quincy Funds, whose marketing
strategies include the presentation of highly personalized site content that encourages visitors to invest
in mutual funds.
The Quincy Funds site is designed to accommodate three types of visitors:
Investors registered customers of Quincy Funds
Brokers -- fund managers who serve the customers
Guests -- casual visitors who as yet have no formal connection with Quincy Funds
The primary goal of the Quincy Funds Web site is to convert guest visitors into registered investors.
Ideally, these investors will develop a long-term relationship with the company, visiting the site regularly
and investing in a variety of funds. Brokers support this effort by posting finance-related articles and
monitoring investor activities.
In order to be successful, the Quincy Funds Web site needs to take into account the actual and perceived
benefits it can offer investors. Also, the site needs to accommodate customers with varying investment
strategies -- aggressive, moderate, and conservative -- and it needs to tailor initiatives for each type of
investor. Furthermore, it needs to adapt to the changing requirements of its visitors.
When you browse the Quincy Funds demo, you can view pages as different visitors in order to test how a
profile affects the content you see. As you visit different parts of the site, ATG 2007.1 obtains data about
you and adjusts your home page on the fly to display promotions that may interest you. Some of your
navigation patterns will be recorded and compiled into a chart; some may be tracked in your profile.
ATG 2007.1 provides these key components for managing visitor interactions:
Real-time profiling features provide the ability to changes a visitors profile

information on the fly according to his or her site activities (see Tracking Visitor
Interests)
User segmentation allows business managers to group similar visitors together

according to profile information
Content targeting allows designers to display personalized content to visitors who

match specified criteria (see Targeting Content)
1
1 - Introduction
Scenarios give business managers a graphical tool for building sophisticated

marketing campaigns that initiate contact with customers (for example, e-mail
campaigns) and respond to their behavior (see Managing Visitors through Scenarios)
Data analysis features allow business managers to use site metrics to gauge
campaign success and calculate return on investment (see Analyzing Visitor Behavior)
About this Document

This document discusses the features of the Quincy Funds Web site and the ATG 2007.1 tools used to
implement them. Each chapter builds on the information in previous chapters, so it is recommended that
you read the chapters in order. The document includes the following chapters and appendix:
Getting Started
Explains how to start the Quincy Funds demo.
Touring Quincy Funds
Leads you through the Web site as a guest, an investor, and a broker.
Tracking Visitor Interests
Describes how to configure a scenario to change an investors profile based on the
pages he or she browses.
Targeting Content
Provides instructions for displaying an image to only those visitors who match
specified criteria.
Managing Visitors through Scenarios
Demonstrates how scenarios in conjunction with slots can implement a marketing
strategy.
Analyzing Visitor Behavior
Illustrates how to monitor the success of a campaign by using a scenario to record
visitor reactions to it.
Includes sample scenarios intended to improve member retention and satisfaction.
Audience
The primary audience of this document is business users, although it also discusses the roles of page
developers and programmers in building a personalized Web site.
Business users define the goals for the Web site, determining the content it provides,
and the visitor behavior that must be tracked, and creating scenarios that implement
marketing strategies. Business users also create and analyze reports generated from
site data.
Page developers create the content pages, integrating the scenario elements created
by business users and the code elements created by programmers. Page developers
are also responsible for overall Web site appearance.
2
1 - Introduction
Programmers create the code elements that allow the system to provide dynamic,
personalized site content. They also configure repositories and perform database
administration duties.
This demonstration is by no means a complete application, but it does illustrate on a smaller scale nearly
all the techniques that a fully functional personalized site employs. Before running this demonstration,
you may want to familiarize yourself with the core concepts of the Personalization module and the
Scenarios module. These concepts are described in the ATG Personalization Guide for Business Users.
Note: The Quincy Funds demo site is not affiliated with any actual store or corporation. All product names
and descriptions are fictitious and do not reflect real products.
Modifying the Demo

The purpose of this demo is to help you become familiar with ATG 2007.1 functionality by showing you
many of the same features that you would use in a real ATG 2007.1 site. As you begin to learn the system,
you might want to use the demo to test your knowledge by altering some of the pages it contains. If you
do this, make sure that the modifications still permit the demo to run. For information on general
configuration changes you may have to make to support your modifications, refer to the ATG Installation
and Configuration Guide.
3
1 - Introduction
4
1 - Introduction
2 Getting Started
The Quincy Funds demo application is included with any version of the ATG product suite that contains
the ATG Adaptive Scenario Engine. The demo uses the same license as the Scenarios module
(DSSlicense.properties).
To access the Quincy Funds demo, complete the following steps:
1.
Start your SOLID database server. SOLID is the default database server used for
demonstration purposes.
2.
Start ATG 2007.1 on your application server (IBM WebSphere, BEA WebLogic, or JBoss
Application Server). Use the standard shortcut or command. For more information,
refer to the ATG Installation and Configuration Guide.
If you chose to install the demo during the installation process for your ATG products,
the QuincyFunds.ear file should already have been deployed on your application
server. If this is the case, the demo starts automatically with ATG 2007.1.
3.
Point your browser to the appropriate URL for your application server.
On IBM WebSphere Application Server:
http://localhost:9080/QuincyFunds
On BEA WebLogic Server:

On JBoss Application Server:

If the ATG server and the ATG Control Center are running on difference machines,
supply the machine name where ATG 2007.1 is running in place of the default
localhost. The default user name/password in all cases is admin/admin.
For additional information about startup options, refer to the ATG Installation and
Configuration Guide.
Exploring the Demo

To explore the demo fully, you need to start the ATG Control Center, which is a graphical interface to
many of the development and maintenance tasks involved in building a Web site with the ATG product
5
2 - Getting Started
suite. For example, you can use the ATG Control Center to create and preview content pages, manage
visitor profiles, and set up the business rules that determine how you will personalize content for each
visitor.
The way in which you start the ATG Control Center depends on how youve installed your ATG
components. To start an ATG Control Center that is installed on the same machine as the rest of the
product suite:
1.
Point your browser to the ATG Dynamo Admin Server interface

(http://localhost:port/dyn/admin, where the default port numbers on JBoss,
BEA WebLogic, and IBM WebSphere are 8080, 7001, and 9080 , respectively. For more
information, see Connecting to the Dynamo Administration UI in the ATG Installation and
Configuration Guide).
2.
When prompted for a user name and password, enter admin for both (unless youve
changed the defaults).
3.
Click the appropriate start button.

Use Start ACC in Server VM if you want to run the ATG Control Center on the
same machine that runs the server and you want to conserve memory.
Use Start ACC in Separate VM if you want to run the ATG Control Center and
server stack on separate machines or you want quicker startup loading.
4.
When the ATG Control Center starts, you are prompted for a user name and password.
Enter admin for both (unless youve changed the defaults).
Note: These instructions apply only if youve installed the ATG server and the ATG Control Center client
on the same host. If youve followed a different installation model, refer to the Running ATG Applications
chapter in the ATG Installation and Configuration Guide.
The first time you view a page or perform an operation, start-up processes such as component compiling
may affect performance. Quincy Funds comes precompiled, but if you make changes to a page or
component, it must be recompiled before it can be served again.
Running Quincy Funds on Oracle

The default ATG installation uses a SOLID database for storing Quincy Funds data. You may want to test
Quincy funds on Oracle to see how an application performs on a production-ready database. To run
Quincy Funds on an Oracle database, complete the following tasks:
Preparing to Import Data to Oracle
Configuring ATG 2007.1 to use Oracle
Populating the Database and Testing the Result
Before you begin, you need to install an Oracle database and client, which you can use to manipulate the
data contained within the database. For instructions on installing and setting up Oracle products, see the
manuals that accompany the software.
6
2 - Getting Started
Note that running the Quincy Funds demo on any database other than SOLID or Oracle is not supported.
Preparing to Import Data to Oracle

Before you can populate your Oracle database, you need to copy the Quincy Funds data from SOLID to a
neutral file. The export process generates all.xml in <ATG2007.1dir>\home to hold the exported data.
You also need to generate the Oracle schema.
1.
Start SOLID, then ATG 2007.1.
2.
From a SQL Plus Client, run the following scripts to generate the schema:
@C:\<ATG2007.1dir>\DAS\sql\install\oracle\das_ddl.sql
@C:\<ATG2007.1dir>\DPS\sql\install\oracle\dps_ddl.sql
@C:\<ATG2007.1dir>\DSS\sql\install\oracle\dss_ddl.sql
@C:\<ATG2007.1dir>\DSSJ2EEDemo\sql\install\oracle\dssdemo_ddl.sql
3.
From a command prompt, run the export command to create all.xml and copy data
from SOLID to it:
<ATG2007.1dir>\home\bin> startSQLRepository -m DSSJ2EEDemo
-exportRepositories all
all.xml -repository /atg/userprofiling/ProfileAdapterRepository
Configuring ATG 2007.1 to Use Oracle

After youve installed ATG 2007.1, you need to set two components so that they correspond with your
Oracle database:
1.
Launch the ATG Control Center.
2.
In the Pages and Components > Components by Path task area, navigate to
/atg/dynamo/service/jdbc.
3.
Double-click the FakeXADataSource component so it opens in the Component

Browser. Change the Configured values for these properties if youre using an Oracle
thin client:
driver - oracle.jdbc.driver.OracleDriver
password - <your_Oracle_password>
URL jdbc:oracle:thin:@<database_name>:<port>:<database_alias>
User <your_Oracle_username>
4.
Be sure to save your changes to the live site.
If you want to revert to using SOLID, change these properties back to their original values:
driver solid.jdbc.SolidDriver
password admin
URL jdbc:solid.://localhost:1313
user - admin
7
2 - Getting Started
Populating the Database and Testing the Result

After youve imported the data from all.xml, test the database to ensure that it does in fact contain the
data you intended to import.
1.
From a command prompt, run the import command to populate Oracle with the data
from all.xml:
<ATG2007.1dir>\home\bin> startSQLRepository -m DSSJ2EEDemo -import
all.xml
-repository /atg/userprofiling/ProfileAdapterRepository
2.
Start the Oracle database and restart ATG 2007.1.
3.
From a SQL Plus client, run the following command to query the database for user
data:
select * from DPS_USER;
8
2 - Getting Started
3 Touring Quincy Funds
Each visitor is represented by a profile, which is a set of properties that describes and maintains
information about a visitor. One property determines the visitors type; once a visitor enters the Quincy
Funds site, he or she is recognized as an investor, a broker, or a guest, and the home page is tailored to his
or her interests. Guest profiles contain basic information such as the type of browser that is used to access
the site. Profiles for investors and brokers maintain detailed information such as preferences and contact
information.
In addition to having a specific profile type, visitors are segmented into profile groups according to
information in their profiles. At Quincy Funds, investors are segmented according to their investment
strategy; they can belong to one of three profile groups: aggressive, conservative, or moderate.
All profiles contain a locale property that identifies the appropriate language (English, French, German, or
Japanese) in which to display the navigation bar and feature articles.
For detailed information on profiles, see Setting Up Visitor Profiles in the ATG Personalization Guide for
Business Users.
On each users home page, he or she can view the feature and new articles tailored to his or her interests.
The following functions are available to investors only:
Browse the funds offered by Quincy Funds. Investors who view funds may receive
prospectuses by mail.
Manage investment goals. Each investor has an Aggressiveness index (a profile

property) that tracks the number of risky funds he or she shows interest in. The site
adjusts this index as the user looks at various funds. For example, displaying
information about an aggressive fund causes this index to increase.
View the portfolio. The demonstration does not include functionality for maintaining
the portfolio; it demonstrates only that investors have portfolios, while brokers and
guests do not.
Brokers can do the following:
View the list of clients for each broker and use sales tools.
Send targeted e-mail to investors.
The remaining sections of this chapter walk you through the various features of the site as a guest, an
investor, and a broker. Note that many of the links are non-functional (or else take you to the list of funds)
since this is only a demonstration application.
9
3 - Touring Quincy Funds
Entering as a Guest
All site visitors are guests until they register or log in (at which point they become investors or brokers).
When you start the demo for the first time, you are logged into the home page as a guest. The browser
window title should read Quincy Funds - guest home.
Guests can view only news items, features, and the funds that Quincy offers. Each news item, feature, and
fund is a content item in one of the applications content repositories. Guests can choose the language
10
they prefer by using the menu at the bottom of the home page. In this demo, the site translates only the
features and the navigation bar.
A primary goal of Quincy Funds is to turn guests into investors. Not only is there an obvious link from the
navigation bar that reads Sign Up Now! (or, for example, Inscrivez-vous ici for French guests), but there is
also a clever hook: if visitors request the prospectus for a fund, they see a login/registration page that
encourages them to sign up. An image at the bottom left of the home page also encourages guests to
sign up. This image is driven by a customer acquisition scenario that will be discussed later. All these
features focus on turning visitors into members.
Registering as an Investor
Since guests have limited access to Quincy Funds, they need to register as investors if they want to use
additional features. On the guest home page, click the Sign-up Now! link, which takes you to a
registration form. When asked, enter a user name and password.
After you log in, supply personal contact and profile information. Be sure to select Jack Smith as your
broker. When you save your entries, the site stores your profile properties in the database. Later, you will
see how you can change these profile properties and how these properties affect the content you see.
After submitting this form, youre returned to the home page as a registered investor. The title of the page
showing in your browser should be Quincy Funds - investor home.
Now that you are an investor, your home page shows a (non-functional) portfolio and your investment
goals. Your home page also displays feature articles and news links, as well as a modified navigation bar:
11
To change your profile properties:

1.
Click on the Change My Investment Goals link.

The investment goal page opens and identifies your goals as conservative and longterm.
2.
Change your investment goals from Conservative to Aggressive, and click Change My
Goals.
12
3.
Return to your home page.

Note the new content: a promotion for an aggressive fund, Quincy Venture fund, at
the bottom of the page.
Changing your investment goals can also affect the feature articles displayed on your home page so that
they fit your new investment style. This is an example of tracking. See Tracking Visitor Interests for more
examples.
Changing Your Profile and Preferences

To edit your personal profile, select the My Profile link in the navigation bar. This brings up a form that
lets you edit the values of your profile properties.
Notice that the profile has a property called the Aggressive Index. This property tracks your investment
style by taking note of the funds you view. For example, if you look at the Quincy Venture fund, your
Aggressiveness index will increase by two. Test this by clicking QUIVF in the My Holdings section on your
home page. This is an example of an implicit property, because the propertys value is inferred through
your actions rather than your explicit input. Inspect your profile to see your changed Aggressive Index.
When you look at a fund and request a prospectus, the site pulls your address from the profile information
you entered while registering. The demo application wont actually send e-mail to confirm the shipment
of a prospectus.
Another form that affects the home page is your preferences. Select the My Preferences link from the
navigation bar. This lets you change the feature and news topics that you want to see, and also adjust the
number of articles that you want displayed on your home page. In this demo application, the repositories
contain few news articles, so setting these numbers high will have no effect. There are only three feature
articles in the demo repository for each investment style.
The My Preferences page also lets you select a preferred language. If you change your language
preference, only certain items will appear in your chosen language. Once finished, log out.
Changing Your Language Preference

The Quincy Funds application can display content in English, French, German, and Japanese. When you
modify your language preference, the navigation bar and the feature links change to the selected
language. Any dates, times, percentages, and currencies on each page also adhere to that language
selection.
As a guest, you can adjust your language preference on your home page. As a registered member, you
can specify a language preference, which is carried across site visits. At any time, you can change your
language through the My Preferences page.
About Locales (for Programmers)

A locale is a code that represents a language/country combination. The locales supported in Quincy
Funds are as follows:
13
Language / Country
Locale
English / United States
en_US
French / France
fr_FR
German / Germany
de_DE
Japanese / Japan
ja_JP
ATG 2007.1 determines a visitors locale by scanning these parameters in this order and implementing the
first that contains a valid value:
The locale property in a visitors profile
The AcceptLanguage HTTP header, which can be set on the visitors browser
The default visitor locale
The server locale
For example, to display a guest visitors home page in the correct language, ATG 2007.1 first looks to the
guests profile for the locale property, which is always null. Then it refers to the visitors browser for the
AcceptLanguage HTTP setting. If none exists, ATG 2007.1 pulls the locale information from the default
visitor locale. Finally, if none of these settings are configured, it uses the server locale.
Locales at Work
In the Quincy Funds application, a directory is set up for each of the sites locales. The locale-specific files
are in the following directories:
<ATG2007.1dir>/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/en
<ATG2007.1dir>/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/fr
<ATG2007.1dir>/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/de
<ATG2007.1dir>/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/ja
A separate Features repository contains feature articles in each supported locale.

When a visitor opens the Quincy Funds home page, he or she views index page. This page contains a
Switch servlet bean that finds the visitors locale (through the process outlined above) and displays the
home page in the corresponding language directory. This is an example of content rendered dynamically
through components.
For more information on the Switch servlet bean, see the ATG Page Developers Guide.
Displaying Japanese Characters

If you are running a Western operating system, you need to configure your computer to accept doublebyte, non-Latin characters. This is a two-part process that involves downloading the Japanese fonts from
the Microsoft Web site and configuring your browser preferences. If you installed the Japanese character
set when installing your clients operating system, you dont need to install the Japanese fonts now.
14
Important: If youre running on Windows 2000 and you didnt load the Japanese character set during
installation, you need to install it from the installation CD. Downloading the Japanese character set
supplied by the Microsoft Web site could damage your operating system.
To download the Japanese fonts:
1.
Launch Internet Explorer. You must use Internet Explorer for this procedure.
2.
Select Tools > Windows Update.
3.
Once you open the Microsoft update Web site, you receive a security warning dialog
box if you havent disabled it previously. Click Yes.
4.
Scroll to the International Language Support section. Click the checkbox next to
Japanese Menus and Dialogs for Internet Explorer. Click Download.
5.
On the Download Checklist page, click Start Download.
6.
Accept the license agreement by clicking Yes.
7.
Restart your computer when prompted to do so.
Once youve installed the Japanese character set, prepare your preferred browser by modifying the font
and language settings.
To customize your Internet Explorer browser:
1.
After youve installed the Japanese fonts, launch Internet Explorer. Select Tools >
Internet Options.
2.
Click Languages. Click Add, and select Japanese. Click OK.
3.
Click Fonts, select Japanese, then click OK.
4.
Click OK to save your changes and close the dialog box.
5.
Close and relaunch the browser.
6.
Select View > Encoding > More > Japanese (Auto-Select). Each time you open the
browser, you need to enter this setting.
To change your browser back to your default language, return to the language settings and move your
preferred language to the top of the list.
To customize your Netscape Navigator browser:
1.
After youve installed the Japanese fonts, launch Netscape Navigator. Select Edit >
Preferences.
2.
In the navigation tree, expand Appearance, and select Fonts.
3.
Select Japanese, MS Gothic, and MS Gothic from the available lists. Click OK.
4.
In the navigation tree, expand Navigator, and select Languages.
5.
Click Add, select Japanese, and click OK.
6.
Click OK to save your changes and close the dialog box.
7.
Close and relaunch your browser.
15
8.
Select View > Character Set > Japanese (Auto-Detect). Each time you open the
browser, you need to enter this setting.
To change your browser back to your preferred language, return to the language settings and move your
native language to the top of the list.
You may also need to configure the ATG Control Center to allow you to view Japanese files. For more
information, see the ATG Programming Guide.
Browsing as a Broker
Log in as a broker called jack/jack (user name and password). After you log in, you see the broker view of
the Quincy Funds home page, with a Broker Connection banner and a browser page title that reads
Quincy Funds - broker home. The home page no longer displays a portfolio, but it still shows news
articles and features directed specifically at brokers. The home page also shows a list of your clients and
some demo sales tools:
16
Click the name of one of your clients. The Quincy Funds demo displays the clients profile, stock holdings,
and latest activities on the Quincy Funds site. The My Clients link in the navigation bar opens a page that
lets you sort your clients according to their properties:
Investment strategy is aggressive
Investment strategy is conservative
Actual portfolio doesnt match their ideal portfolio
17
Targeted E-Mail
Click the E-mail link in the navigation bar to view the Targeted E-mail feature. This feature lets brokers
create, edit, and review e-mail that is targeted to investors whose profiles match the message and who
have indicated that they want to be contacted by e-mail.
Before you can test Targeted E-mail, you need to set the emailHandlerHostName property as described
below:
1.
In the ATG Control Center, open the Pages and Components > Components By Path
screen.
2.
Expand atg/dynamo/service.
3.
Double-click SMPTEmail to open it in a Component Editor.
4.
In the Properties tab, locate the emailHandlerHostName property.
5.
Change both Configured Value and Live Value to the name of your e-mail host. (A
standard name is mailhost.<companyname>.com.)
To create a targeted e-mail:

1.
Click the Create new mailing link to open the new mailing page.
2.
Select investors as your mailing audience.
3.
Enter a fictitious Subject, Senders Address, and Mailing name.
4.
Select a mailing template.
5.
Click Send Mail.
Once youre returned to the Targeted E-mail page, you can view all mailings youve sent. Click the
Summary of sent mailings link. Your summary should have one entry. Return to the Targeted E-mail
page.
The Edit content heading lists the e-mail templates in the making. Click a template to see the three
variable fields that a broker can edit:
Text for conservative investors
Text for aggressive investors
Signature
When the site sends e-mail, investors identified as aggressive receive the text written for them, and
conservative investors receive the text relevant to their investment style. You can create targeted e-mail
templates with a variety of customizable fields. Return to the broker home page.
Logging Out
When you have finished using the application, click Log-Out from the navigation bar. After logging out,
your session disconnects from your profile and reverts back to guest status. Your session is anchored to
18
your profile, not your IP address, to protect it from another visitor who might log in from your
workstation.
Further Exploration
In addition to browsing the demo as different types of visitor, you can also explore it from the point of
view of someone who works on the Quincy Funds Web site development team. The remaining chapters in
this guide show how business users, page developers, and programmers use ATG 2007.1s personalization
and scenario features to implement Quincy Funds customer relationship strategies.
19
20
4 Tracking Visitor Interests
Tracking is the ability to update a user profile on the fly based on the Web pages he or she views.
Tracking, used in conjunction with targeting, lets you personalize Web site content that accommodates
the changing interests of site visitors.
This chapter shows how a visitors navigation habits influence his or her profile information. You log in as
an investor and experience tracking at work: Based on the number of high-risk funds you browse, your
Aggressiveness index will increase or decrease. In this way, Quincy Funds determines a visitors
investment strategy, which the site uses in combination with targeting to advertise only those funds of
interest to the visitor.
To investigate tracking for aggressive investors:
1.
Log in as mary (user name and password).

The Quincy Funds investor home page opens.
2.
Click the My Profile link in the navigation bar to view Marys profile information.
The Aggressiveness index is six. This index measures how many risky funds you view
and for which you request information. For every aggressive fund, your index
increases; for conservative funds, it decreases.
3.
Click the Funds link.
4.
Click the Quincy Venture Fund - QUIVF link.
5.
Click the Send me the application and prospectus link to request sign up
information and verify Marys mailing address. Click OK.
6.
Return to your profile page; the aggressive index has increased to 10. Go to the Funds
page.
7.
Click the Quincy Venture Fund - QUIVF link again and then return to your profile
page immediately.
8.
View your profile: your index has increased to 12 because you viewed only the fund
and didnt request additional information. Return to the Funds page.
9.
Click the Quincy Money Market Fund - QUISB link and then return to your profile.
The Aggressiveness index has decreased by one to 11.
10. Log out.

Every fund and visitor profile is assigned a property called aggressivenessIndex. A funds
aggressivenessIndex is a fixed number. A profiles aggressivenessIndex accumulates the values
supplied by the aggressivenessIndex of the funds viewed by a visitor. The profile gathers an index
21
4 - Tracking Visitor Interests
value through implicit or hidden means. You could also alter a profiles aggressivenessIndex explicitly
by opening the My Profile page and modifying the provided value.
Tracking is most powerful when combined with targeting. You can determine which investors prefer
aggressive strategies (tracking) and tailor the images, articles, and fund information they view to their
interests (targeting). See Targeting Content for an example.
A business user designs the tracking scenario; a page developer configures the Web pages to send a flag
when a visitor views a fund. The programmer sets up related repositories.
Exploring Tracking Scenarios

To track an investors Aggressiveness, a business user builds a scenario that can analyze a visitors
navigation habits and interpret that behavior into degrees of Aggressiveness. For this scenario to work,
the Aggressive index property must be configured with an appropriate numeric value for each fund.
To view this tracking scenario:
1.
In the ATG Control Center, open the Scenarios > Scenarios screen.
2.
Navigate to QuincyFunds/InvestorTracking/TrackFundsViewed:
According to this scenario, once a visitor views a fund (which is an item), that visitors Aggressiveness
index accrues the funds index value. The visitors profile stores the aggressiveness tally as well as a list of
all funds the visitor browses: the third element instructs the system to add the funds name to the visitors
profile.
Heres the element-level explanation:
This scenario activates when a visitor views an item from the Funds
repository.
The aggressivenessIndex value for the viewed fund is added to the

visitors profile aggressivenessIndex value.
22
The name for the viewed fund is added to the visitors profile Fund
Viewed value.
The scenario ends.
For a discussion of scenarios, see Managing Visitors through Scenarios. For details on scenario elements
and building scenarios, see the Creating Scenarios chapter in the ATG Personalization Guide for Business
Users.
How Tracking Affects a Profile

Take a look at Marys profile to see how the site updated her properties based on your actions:
1.
In the ATG Control Center, open the People and Organizations > Users screen.
2.
Click List to see all profiles.
3.
Select View > Refresh.
4.
Select Mary to examine how your recent activities in Quincy Funds affect the visitor
profile.
The profile in the ATG Control Center consists of user-entered explicit information such as name,
password, and gender, as well as implicit information date of last session and broker ID. The
aggressivenessIndex equals 11 in the ATG Control Center profile just as it did in the Quincy Funds
Profile Web page. The fundsViewed property lists Quincy Venture fund (QUIVF) and Quincy Money
Market fund (QUISB), which are the funds you viewed in the previous section. This information is funneled
back to an investors broker.
To examine how the site uses the fundsViewed property:

1.
Log in to the Quincy Funds demonstration as jack (user name and password).
The Quincy Funds - broker home opens.
2.
From the My Clients list, click the Mary Hammond link.

Beneath the Recently Viewed Funds label are the two funds, Quincy Venture fund and
Quincy Money Market fund, traced from the ATG Control Center profile fundsViewed
property.
3.
Browse the Holdings list.
23
4.
Log out.
Jack can use this information as an indicator that Marys investment style is changing. Shes invested in an
aggressive fund, but she seems to be interested in a very conservative fund. Jack can send her a mix of email targeted to aggressive and conservative investors, and once her interests become clear, he can add
her to that group.
Tracking for Page Developers

A page developer is responsible for setting the fireContentEvent and fireContentTypeEvent
parameters for a given targeter. When these parameters are set to true and a user views the content
rendered from the targeter, the site fires an event. Another component is designed to listen for the event
and update the profile property.
For example, when you click a fund on the fundslist page, the system does the following:
1.
Sets the ElementID to the funds XML file.
2.
Opens the fund page.
3.
Passes the ElementID to the fund page so that it displays the text in the XML file.
The fund page opens (displaying the fund-specific text) and it fires an event (fireContentEvent and
fireContentTypeEvent) that contains the ElementId aggressiveIndex value. A listener receives the
event and adds that index value to the users aggressiveIndex profile property.
To examine the fireContentEvent and fireContentTypeEvent parameters, open fund.jsp in
<ATG2007.1dir>/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/en. A search in this file for either
parameter renders no results. The default value of these parameters is true, so a page without a value for
them behaves as if they were set to true.
Tracking and Repositories for Programmers

For programmers, the task of tracking visitor activity and interests involves defining the repositories that
store the profile and content information for the Web site.
The Quincy Funds demo contains the following repositories, with each one representing a collection of
items or information that shares subject matter and requires the same set of properties:
Investment Tips - Contains brief messages. The Quincy Funds home page is
configured to display a random tip each Tuesday to investors.
Funds - Contains information on all funds offered by Quincy Funds, with properties
that categorize each fund according to securities type and aggressiveness rating.
Offers Contains all fund promotions or offers focused towards prospective fund
subscribers.
24
Features - Contains all feature articles available for display. The Quincy Funds home
page displays selections from the list according to the visitors investment goals and
language preference or locale.
Images - Contains all images used in the demonstration. Each content item does not
contain the actual image data, but instead contains the image URL and properties that
are available for targeters.
Profile Contains all profiles for registered visitors. A profile is made up of implicit
information derived from visitor activities or explicit information entered by the visitor.
News - Contains the list of news articles available for display. The Quincy Funds home
page displays selections from this list according to the visitors interests.
E-mail Contains templates available to the Targeted E-mail feature.
Each repository has one or more item types, which are specified in the repository template definition file
that describes the relationship between the repository and the database. For a detailed discussion about
repositories, see the ATG Repository Guide.
The tracking example outlined in the previous sections requires a programmer to define
aggressiveIndex and fundsViewed properties in the Profile repository, and an aggressiveIndex
property in the Funds repository.
For more information on the repository implementations used in Quincy Funds, please refer to Repository
Structure in the Quincy Funds Demo.
25
26
5 Targeting Content
Targeters display certain content on a page based on a set of rules. For example, when an investor looks
at the investor home page, the site invokes ten separate targeters to produce that page.
Four targeters select and display the images that represent the visitors investment
goals.
One targeter shows feature articles.
One targeter shows news articles.
One targeter shows a promotion to aggressive investors.
One targeter displays a randomly selected investment tip each Tuesday.
One targeter is tied to a slot that advertises funds that arent in the investors portfolio.
One displays a warning if the investor has selected Japanese preference but hasnt
loaded the Japanese character set.
27
5 - Targeting Content
*
*
*
*
The asterisks in the image above indicate page components that use targeters.
Note: The image above doesnt demonstrate the Japanese language support targeter or the fund
advertisement targeter.
28
To use a targeter, you need to define the rule set that determines who should view a piece of content and
insert the targeter servlet bean to anchor that rule set to a particular page. The term targeter refers to the
rule set.
This chapter shows how a targeter determines the features to display on an investor home page.
To demonstrate how this targeter affects what you see:
1.
Log in as an investor called sandy (name and password). Notice the Feature articles
that appear on the home page:
Is Your Money Safe?
Playing it Safe
Saving for a Car
2.
Click the My Preferences Link. Change the Display features number to two. Click Save
to return to the home page.
3.
Click the Change My Investment Goals link. Change your investment style to
aggressive. Click Save.
4.
Return to the home page. Your Features should now include:

High Risk Hedge Funds
Quincy Bullish on International Markets
To implement this, a business user configured rules that decide when to show each feature to a given
broker. A page developer embedded the targeter servlet bean in the Broker home page.
Previewing a Page as Different Users

Another way to view the Quincy Funds site personalized for Sandy is through the preview feature in the
ATG Control Center.
To preview Quincy Funds as Sandy:
1.
In the ATG Control Center, open the Targeting > Preview screen.
2.
Enter the following information:

Login name: sandy
Password: sandy
User type: investor
Strategy: Aggressive
Number of feature items: 2
3.
Click Step 3 Choose the page you want to view.
29
From the All Document Roots list, select DSSJ2EEDemo >

J2EEApps/QuincyFunds > Quincy Funds J2EE DAF Demo
(QuincyFunds). The list of pages below changes to show the pages for the
application you just specified (<ATG2007.1dir>\DSSJ2EEDemo\j2eeapps\QuincyFunds\web-app\).
Select \en\index.jsp.
4.
Click File > Preview to open Sandys home page.
Examining Targeting Rules

Targeting rules determine when content appears to a set of visitors. You build a targeting rule by
identifying a piece of content and defining who can see it, when it will be displayed, and what will
happen if the who and when parameters arent met. A rule is a member of a rule set, which begins with a
show or hide statement and ends with a separator.
To inspect the targeting rules for an item in the Features repository:
1.
In the ATG Control Center, open the Targeting > Content Targeters screen.
2.
From the list of folders, select Features.
3.
In the right pane, select Features.
This targeter consists of three rule sets. Each rule set contains one rule. You can confirm this by selecting
one line in the rule set and the Edit > Select Entire Rule command. The entire rule set is selected. For this
example you need only examine the first rule:
Show this content:

Items whose Target Audience includes Person's Strategy
And whose Language starts with Locale's localeString
To these people:
people whose Usertype is investor
Each rule is based on a piece of content and begins with a content-related phrase. This phrase describes
what item the page should display. An item, in this example, is a file in the Features repository called a
feature. In short, this rule states that all items in the Features repository that meet both criteria will display
on an investors home page. Each criterion is based on a property value held by a feature.
Items whose Target Audience includes Person's Strategy
All items in the Features repository maintain a property called Target Audience that has the same
possible values as the Person's Strategy on a user profile. When you selected the investment style
aggressive, you updated this profile property. In this way, investors only see the features theyre likely to
be interested in.
And whose Language starts with Locale's localeString
30
Because items in the Features repository are offered in English, French, German, and Japanese, each item
has a property called Language that contain its locale. Similarly, each user profile contains locale settings
in a Locale property. This portion of the rule ensures that the features appear on a home page in an
investors language of choice, by comparing the profile value against the feature value.
Features that meet both criteria are presented to investors. The Usertype property on a user profile
determines whether visitors are recognized as a guest, an investor, or a broker.
Targeting for Page Developers

The business user builds the targeter rules; the page developer inserts the targeter servlet bean into the
investor home page. There are several kinds of targeter beans: each one governs the order in which
targeted items display differently. The bean in this example, TargetingRange, is used when several items
are available for display, because there may be multiple features that meet these criteria.
Examine the TargetingRange bean in the investor home page. In short, this code executes the targeter
rules, returns the number of items desired by the logged in visitor, and sorts them alphabetically by title.
Then the system displays the article name and image and provides a link to the feature text in full. If no
items are returned, it displays No Features Today notice.
To see how these tags appear on a page:
1.
Open investorhome.jsp in <ATG2007.1dir>/DSSJ2EEDemo/j2eeapps/QuincyFunds/web-app/en.
2.
Find the first instance of the TargetingRange bean, which is used to locate items in
the Features repository.
<dsp:droplet name="/atg/targeting/TargetingRange">
<dsp:param bean="/atg/registry/RepositoryTargeters/Features/Features"
name="targeter"/>
<dsp:param bean="Profile.numberfeatureitems" name="howMany"/>
<dsp:param name="sortProperties" value="+title"/>
<dsp:param name="fireContentEvent" value="false"/>
<dsp:param name="fireContentTypeEvent" value="false"/>
<dsp:oparam name="outputStart">
</dsp:oparam>
<dsp:oparam name="output">
<tr valign=top>
<td><dsp:a href="feature.jsp">
<dsp:param name="ElementId" param="element.repositoryId"/>
<img height="73" vspace="2" border="0" hspace="8" width="73"
src="<dsp:valueof
param="element.SmallImageURL">images/features/noimage.gif</dsp:valueof>">
</dsp:a></td>
<td><dsp:a href="feature.jsp">
31
<b><dsp:valueof param="element.title"/></b></dsp:a><br>
<dsp:valueof param="element.headline"></font></dsp:valueof> </td>
</tr>
</dsp:oparam>
<dsp:oparam name="empty">
<tr>
<td colspan=2>No Features today.</td>
</tr>
</dsp:oparam>
</dsp:droplet>
<dsp:droplet
name="/atg/targeting/TargetingRange">
Invokes the TargetingRange servlet bean. For

more information on TargetingRange, see
the ATG Page Developers Guide.
<dsp:param
bean="/atg/registry/Repository
Targeters/Features/Features"
name="targeter"/>
Instructs the servlet bean to run the Features

targeter against the items in the Features
repository.
<dsp:param
Sets the servlet beans howMany input

parameter to the visitors
numberoffeatureitems property. A visitor
can change this property value through the
Preferences page.
bean="Profile.numberfeatureitems"
name="howMany"/>
<dsp:param name="sortProperties"
value="+title"/>
Alphabetizes the located features by title.

Additional sorting mechanisms are available,
see the ATG Page Developers Guide.
<dsp:oparam
name="output">.</dsp:oparam>
Renders the located items as output.
<dsp:a href="feature.jsp">
<dsp:param name="ElementId"
param="element.repositoryId"/>
<dsp:valueof
param="element.SmallImageURL">images/
features/noimage.gif</dsp:valueof>">
</dsp:a>
Sets the ElementID parameter to the features

ID. Displays the image stored in the features
smallImageURL property, which is also a link
to the features text. When the image is clicked,
feature.jsp uses the ElementId to display
the text stored in the offers relativePath
property
<dsp:a href="feature.jsp">
<dsp:valueof
param="element.title"/></dsp:a>
Sets the ElementID parameter to the features

ID. Displays the features title as a link to the
features text. When the title is clicked, the
page passes the ElementID to Feature.jsp,
which inserts the text fragment appropriate for
that feature article.
<dsp:valueof param="element.headline">
Displays the features headline.
</dsp:valueof>
32
<dsp:oparam name="empty">
<td colspan=2>No Features
today.</td></dsp:oparam>
Displays No Features today if no features are

returned by the TargetingRange bean.
Targeting for Programmers

Its the programmers job to create the Features repository and to configure properties for the items it
contains. Then, a business user adds feature articles and defines property values. Business users use
properties such as Language and Targeting Audience in targeting rules.
To see items that are part of the Features repository:
1.
Open the Content > Features screen.
2.
Click List.
33
34
6 Managing Visitors through Scenarios
This chapter shows how scenarios can tailor your promotional campaign to encourage investors to
subscribe to funds. Quincy Funds primary goal is to attract guests to become investors and persuade
investors to buy funds. Using scenarios, Quincy Funds promotes new funds by sending e-mail and
displaying images on the home page of prospective buyers. This chapter provides two sample scenarios:
You can think of scenarios as a flowchart for Web site interactions. A scenario is based on a particular
visitor-initiated action or event, such as visiting the Quincy Funds Web site, and it provides a
predetermined response to that action. Business users build scenarios to accomplish marketing
campaigns. For a comprehensive discussion of scenarios, see the Creating Scenarios chapter in the ATG
Personalization Guide for Business Users.

In this example, you log in as a user who has not subscribed to the Quincy Special Situations fund. The
content that is displayed encourages you to read about this fund:
1.
Log in as mary (user name and password).
2.
Notice the image above the My Portfolio section:
3.
Log out.
This image displays for all visitors who dont own the Quincy Special Situations fund. The next section
shows how the scenario that implements this behavior is designed.
35
6 - Managing Visitors through Scenarios
Inspecting the PromoteSpecialSituations Scenario

Look at the Promote Special Situations scenario and see how each event acts as a scenario building block:
1.
2.
Navigate to QuincyFunds/InvestorPromotions/PromoteSpecialSituations:
This scenario is made up of one segment or string of actions called Portfolio Based Promotion. According
to this scenario, once a visitor logs in, if that visitor does not have the Quincy Special Situation fund in his
or her portfolio, the Special Situations Offer image will display on his or her home page.
Heres an element-by-element explanation:
This scenario begins when a visitor logs in to the Quincy Funds Web site.
A fork separates two actions into branches. If the visitor owns the Quincy
Special Situations fund, then it (specialsituations.xml) will appear in
his or her Fund List property. For those visitors whove invested in this
fund, the scenario ends.
Those who havent invested in this fund will proceed to the next action.
An image advertising Quincy Special Situations fund is placed in the slot

for those investors whove met the mentioned requirements.
The scenario ends.
36

This example shows how Quincy Funds promotes the Quincy Growth fund, among others, to eligible
investors.
To see how Quincy Funds promotional campaign advertises funds to qualifying users:
1.
Sign up as a new member. Set your zip code to 02471. Log out.
2.
Log in as the user you just created.
3.
On the home page, view the image just above My Portfolio.
4.
Log out and log in again.

The image changes.
5.

The image changes again.
6.

The image changes again.
7.
Continue until you are returned to the Quincy Growth fund promotion. Click the
image:
The site displays an article promoting the fund. This article provides a link to fund
statistics. From there, you can request an application and prospectus, and then
register to invest in the fund.
These images advertise a product or service available to you that you havent bought. Youre qualified to
view these advertisements based on your profile.
Inspecting the PromoteGrowthFund Scenario

The site displays these advertisements to potential customers through a series of scenarios. These
scenarios ensure that only the investors who dont own the Quincy Growth fund, for example, see the
promotional Quincy Growth fund image. Review the scenario that caused the Quincy Growth fund image
to display.
37
To review the scenario that caused the Quincy Growth fund image to display:
1.
2.
Navigate to Quincy Funds/Investor Promotions/PromoteGrowthFund:
(Note that both segments contain more elements than an appear in this image. Fork elements for each
locale have been removed to allow the image to display.)
This scenario consists of two segments or strings of actions. By grouping related segments in the same
scenario, you can manage them as a unit: when you want to cancel the Quincy Growth fund promotional
campaign, you can stop both segments by disabling the scenario.
The E-mail Fund Promotion Segment

st
This segment dictates that on May 1 2000 at 12:00 am, all visitors who indicated theyd like to receive email communication and havent already invested in Quincy Growth fund will receive the Quincy Growth
fund promotion mailing. The segment syntax identifies those visitors who are investors and have their
receiveEmail property set to yes.
This scenario is triggered by a time/date element: 12 am on May 1, 2000.
Only investors are included in this scenario.
Only those investors who indicated theyd like to receive e-mail are
included in this scenario.
38
A fork separates this condition from the next two, which means that if this
condition isnt met, the following two will be.
This element identifies those user profiles that contain growth.xml in
their Fund List.
This element works in conjunction with the next element. Only those who
dont own Quincy Growth fund will be affected by the next element.
An e-mail advertising Quincy Growth fund is sent to those who meet the
people conditions. View the e-mail through the Pages and Components
> Pages screen, by following the supplied path. Use the View > Preview
option to see how it will appear to recipients.
The scenario ends.
All investor profiles contain a property called Fund List, which lists their holdings. Of the identified
investors, some have invested in the Quincy Growth fund, and, therefore their Fund List property
contains the value /repositories/Funds/en_US/growth.xml. The remaining investors will receive
the promotional e-mail.
The Show Promotion Segment

The second segment, Show Promotion, implements the image behavior you viewed previously: to
present a Quincy Growth fund image to potential investors. This segment begins with a time element,
ensuring that the image serves as a Quincy Growth fund reminder, because the image displays on the site
only after the e-mail has been sent. All visitors who register or log in and havent invested in the Quincy
Growth fund will see an image advertising it on their home page.
This scenario is triggered by a date element: the days between May 1st and
st
December 31 2000.
A fork allows for several different actions to be included in this scenario.

Any visitor who logs in is affected by this scenario.
Also, any visitor who registers is affected by this scenario.
39
Another fork divides the scenario into two courses of actions.

If the visitors profile contains the Quincy Growth fund in the fund list,
the scenario jumps to the final element.
This element works in conjunction with the proceeding element. Only
those who dont own Quincy Growth fund will be affected by the next
element.
The site places an image advertising Quincy Growth fund in the slot for
those investors whove met the mentioned requirements.
The scenario ends.
Scenarios Sharing Slots

The Show Promotion segment displays the Quincy Growth fund image for all eligible investors. The image
exists in a slot with other images like the Special Situations fund and Seminar advertisements:
According to the example demonstrated in the previous section, when an investor views the investor
home page, the scenarios associated with QFOfferSlot run. When certain events in the scenarios occur,
the scenario fills the slot with images. Those investors who own stock in both funds wont see either
image.
40
About Slots
A slot is a bucket that receives content from scenarios and displays that content on a Web page. Multiple
scenarios can make use of one slot. You can configure the order in which the items in a slot display.
The content rendered from a slot is determined on the fly. A combination of scenario conditions causes
an image to be placed in a slot. These conditions can incorporate a certain day of the week, delay in time,
specific user properties, or actions initiated by the system or a site visitor. For example, you could display
one item to all investors who register in the spring, received a welcome e-mail, but havent yet invested in
a Quincy fund, or display another item on Mondays to all men whove identified their investment strategy
as aggressive although their actions prove theyre conservative.
To use a slot, you need to complete the following steps:
1.
Create the slot. (See Scenarios and Slots for Programmers.)
2.
Use a targeter servlet bean to embed the slot in a page. (See Scenarios for Page
Developers.)
3.
Create a scenario that fills the slot with content. (See Inspecting the
PromoteGrowthFund Scenario.)
For information on the differences between targeters and slots, see the Creating Scenarios chapter of the
ATG Personalization Guide for Business Users.
Placing an Image in a Slot

Return to the ATG Control Center Scenarios screen and browse the PromoteSpecialSituations
scenario. It resembles the Show Promotion segment in the PromoteGrowthFund scenario. Both scenarios
use QFOfferSlot.
Open the PromoteOverseasFund scenario. It displays an image advertising the Quincy Overseas Fund to
all investors who view the feature articles Global Investment Focus or Quincy Bullish on International
Markets but dont own the Quincy Overseas Fund. The image is displayed in the QFOfferSlot.
To test this scenario:
1.
Log in to the Quincy Funds demonstration as scott (user name and password). Under
the Features section, click the Global Investment Focus link to view the article.
2.
Return to the investor home page.

You should see this new image:
41
Because this scenario is session-scoped, the contents in the slot are discarded at the end of each session.
You need to view the international-related articles again to see the Quincy Overseas fund advertisement
again.
Scenarios for Page Developers

The page developer is responsible for inserting the targeter servlet bean that implements the slot into a
site page. This example uses the TargetingFirst bean; any targeting bean will work.
In short, the investor home page pulls from the QFOfferSlot the first item that complies with the slots
properties. That item displays as an image URL and links to offer.jsp.
To view how a slot is rendered in the investor home page:
1.
Open investorhome.jsp in <ATG2007.1dir>/DSSJ2EEDemo/j2eeapps/QuincyFunds/web-app/en.
2.
Locate the first instance of the TargetingRange bean, which is used to locate items in
the Features repository.
<dsp:droplet name="/atg/targeting/TargetingFirst">
<dsp:param bean="/atg/registry/Slots/QFOfferSlot" name="targeter"/>
<dsp:param name="howMany" value="1"/>
<dsp:a href="offer.jsp">
<img border="0" src="<dsp:valueof param="element.imageURL"/>"></dsp:a>
</dsp:oparam>
</dsp:droplet>
Heres description of the essential tags:
42
<dsp:droplet
name="/atg/targeting/TargetingFirst">
Invokes the TargetingFirst servlet bean.

For more information on TargetingFirst,
see the TargetingFirst section in ATG Page
Developers Guide.
<dsp:param
bean="/atg/registry/Slots/QFOfferSlot"
name="targeter"/>
Instructs the servlet bean to execute the

QFOfferSlot rules against the items in the
repository.
In conjunction with the servlet bean

(TargetingFirst) determines the number
of items that the site displays in the slot and
the order in which they should display.
<dsp:oparam name="output"></dsp:oparm>
Renders the located offer items as output

available for display.
<dsp:a href="offer.jsp">
<dsp:valueof
param="element.imageURL"/>"></dsp:a>
Displays the image identified in the offers

imageURL property as a link to offer.jsp.
Sets the ElementId to the offers ID and
passes it to offer.jsp. When the image is
clicked, offer.jsp uses the ElementID to
display the text stored in the offers
relativePath property.
Scenarios and Slots for Programmers

A programmer creates the QFOfferSlot. When you create a slot, you select a content source, which is
the slots repository (Offers, in this example) and a content type (HTML). Also, you determine how the slot
will post the content items it contains.
To view the slot:
1.
Open the Pages and Components > Components by Path screen.
2.
Navigate to atg/registry/Slots/QFOfferSlot.
The bar across the bottom of the Components panel displays information about the
selected component (QFOfferSlot): the path, class, scope, and description. The
scope indicates the level of persistence (options include session, global, and request).
Session scope means the items in the slot will be discarded when the session ends.
Note: Because QFOfferSlot is session-wide, in the PromoteOverseasFund scenario,
a visitor activates a trigger when viewing the international-related articles. Anytime
throughout the session, a visit to the investor home page may render the related
image in the slot. Once that visitor initiates a new session, the image wont be
available until the site activates the trigger again.
3.
Double-click QFOfferSlot to open it in the Component Editor.
43
Inspect the items in the Properties tab. These values decide how the slot displays content.
The generation property indicates whether the slot displays content received from
scenarios (passive) or triggers a scenario to solicit content (active).
The ordering property selects from all items available in a slot, the order in which
they display, either sequentially (following the chronology in which they were added)
or randomly.
The retrieval property manages the retrieval process. Will all items display in a
specific order and then be removed from the slot (destructive)? Or will that order
repeat (static)? Can an item display multiple times in rotation (rotating)?
According to the QFOfferSlot settings, the slot displays items placed in it by scenarios (passive): it
rotates the items it posts beginning with the first placed in the slot. For a complete discussion of slots, see
Using Slots in the ATG Personalization Guide for Business Users.
44
7 Analyzing Visitor Behavior
This chapter shows how scenarios can log visitor activities and provide tools for measuring Web site
success. It describes two approaches for encouraging guest visitors to register as members and compare
each outcome.
The scenario in this example determines what a visitor sees - not all guest visitors are presented with the
same images on the home page and monitors whether the visitor registers. Consequently, you can view
visitor behavior as a graph and draw generalizations about the effectiveness of each home page image.
To see this scenarios behavior:
1.
Log out of Quincy Funds if youre currently logged in.

You return to the guest home page. The graphic at the bottom of the left column,
beneath the Index of Features link, appears as one of these:
2.
Log in as eric (user name and password), and log out.

You return to the guest home page. Notice the graphic again and take note of any
changes.
3.
Continue logging in as different visitors and immediately logging out. Each time,
inspect the graphic for changes.
When you re-open the home page as different guests, you see that the image changes. Although both
images try to entice visitors to become members, the first image, called promo-signup-agg, takes a
more aggressive approach. The scenario driving the random display of images also records the actions of
the visitors organized by the initial image they view. This makes it possible for business users to generate
45
7 - Analyzing Visitor Behavior
a chart that helps determine which approach, aggressive or non-aggressive, causes more visitors to
register. The next section shows how to compile the gathered data into a chart.
Examining the SignupPromoTrial Scenario

In this scenario, most user events are followed by a recorder that tracks the next user activity and saves it
to a dataset. You can use the information collected for a dataset to compile a chart.
Review the scenario in the ATG Control Center to examine the role recording plays in the example from
the previous section:
1.
Open the Scenarios > Scenarios screen.
2.
From the file tree, expand Quincy Funds and Investor Acquisitions.
3.
Select SignupPromoTrial.
The SignupPromoTrial scenario appears in the display area.
A scenario reads like a flow chart; each element represents a visitor action or a system response.
According to this scenario, when a guest visits the Quincy Funds Web site and views the promo-signup
image, which is the active image in the QFHomePageSlot, a trigger activates a recorder to trace the
guests next action.
If the guest registers as a new member, the Standard Signup label gains an entry.
If the guest leaves the Web site without registering or logging in, the Standard
Dropout label gains an entry.
Note: Theres no need to track the activities of those who log in, because theyre already members.
Alternatively, the actions of those who view the promo-signup-agg image will be saved to the
respective Aggressive labels, which are part of the same dataset (QF Signups).
Each label identifies a group of users who responded similarly to the same image. You can think of the
dataset, QF Signups, as the superset of that recorded data. This means that you can graph the number of
guests who view the promo-signup image and join Quincy Funds against those that view the promosignup-agg image with the same result. In this way, you can analyze the results and determine which
graphic gleaned more new members.
To view QF Signups dataset:
1.
In the ATG Control Center, open the Analysis > Datasets screen.
2.
Select QF Signups.
On the top of the dataset display panel, the Sampling method radio buttons provide alternatives to
gathering complete data for every guest visitor in order to save space in the database. For example, you
may decide to track the actions of only 50% of the Quincy Funds guests.
The event mapper determines the specific kinds of information maintained by the recorder. In this
example, the selected event mapper (DSS Audit Trail Mapper) connects the dataset, session date/time,
46
label, and guest. This particular event mapper is preconfigured; had the scenario required additional
information, the programmer could have defined a new dataset. For more information on the DSS Audit
Trail Mapper, see the Recording Scenario Activity section of the Creating Scenarios chapter in the ATG
Generating a Chart
To create a chart, you select a chart template, modify it to meet your needs, and generate the chart. You
can automate the generation process by creating a template tailored to the frequency with which youd
like to see information (Hourly, Weekly, Monthly, etc.). For more information on charts, see the How Charts
Work section in the Creating Charts chapter of the ATG Personalization Guide for Business Users.
To build a chart and then view it:
1.
In the ATG Control Center, open the Analysis > Chart Templates screen. A chart
template has been predefined for this scenario.
2.
From the file tree, navigate to QuincyFunds\Weekly\QFSignupPromotions.
3.
Accept the chart template defaults. Click Generate Now to compile the chart.
The chart opens in the Analysis > Charts screen.
47
According to this chart, about eight of the visitors who saw the standard image joined Quincy Funds and
five did not. The standard image had about a 62% success rate (8/13). Of those who viewed the
aggressive image, about four signed on and ten didnt, which makes the success rate 29%. The standard
image attracts more new members.
48
Analyzing Visitor Behavior for Page Developers

The page developers role involves crafting the Quincy Funds guest home page so that it incorporates the
designed scenario. There are no extra tasks required to implement the reporting feature. As with any
scenario that includes a slot, the page developer is responsible for inserting the targeter servlet bean into
the page (guesthome) and defining the targeter parameters. For an explanation of slots in the Quincy
Funds demo, see About Slots.
See Scenarios for Page Developers for a thorough discussion of the TargetingFirst syntax. Below is a
high level description of the TargetingFirst bean.
To see how the slot is rendered in guesthome.jsp:
1.
Open guesthome.jsp in <ATG2007.1dir>/DSSJ2EEDemo/j2eeapps/QuincyFunds/web-app/en.
2.
Search for QFHomePageSlot.
Heres what you should see:
<dsp:droplet name="/atg/targeting/TargetingFirst">
<dsp:param bean="/atg/registry/Slots/QFHomePageSlot" name="targeter"/>
<img src="images/d.gif" vspace=4><br>
<dsp:a href="signup.jsp"><img border="0" alt="sign up!"
src="<dsp:valueof param="element.imageURL"/>"></dsp:a>
</dsp:oparam>
</dsp:droplet>
This code configures the JavaServer Page to query the database through a TargetingFirst bean. This
section defines:
the targeting servlet bean (<dsp:droplet

name="/atg/targeting/TargetingFirst">)
the targeter, which is a slot (<dsp:param

bean="/atg/registry/Slots/QFHomePageSlot" name="targeter"/>),
the number of items to display (<dsp:param name="howMany" value="1"/>),
the content that should display (<dsp:a href="signup.jsp"><img border="0"

alt="sign up!" src="<dsp:valueof param="element.imageURL"/>").
49
Analyzing Visitor Behavior for Programmers

In this instance, the programmer creates the QFHomePageSlot slot, which holds the promo-signup and
promo-signup-agg HTML content items.
To view the QFHomePageSlot slot:
1.
In the ATG Control Center, open the Pages and Components > By Module screen.
2.
Select Quincy Funds Demo and then Slots.
3.
Double-click QFHomePageSlot to open it in the Component Editor.
Review the Properties tab to see the complete list of properties and values, including those supplied by
the programmer and those that were automatically generated. The remaining tabs consist of paths and
details that describe the slot. For a detailed discussion on a programmers role in creating scenarios, see
Scenarios and Slots for Programmers.
Charting-related tasks that a programmer handles include creating the QF Signups dataset and the event
mapper. In this example, a pre-existing event mapper (DSS Audit Trail) was used. A database
administrator configures the database for recorders, event mappers, and datasets. For more information,
see the Using Scenario Recorders chapter in the ATG Personalization Programming Guide.
50
8 Repository Structure in the Quincy

Funds Demo
Content repositories in the Quincy Funds demo are designed to show a variety of approaches for
structuring SQL repositories for the delivery of Web site content. Each repository is an implementation of
ATG 2007.1s Generic SQL Adapter (GSA). For detailed information on GSA content repositories, please
refer to the SQL Content Repositories chapter in the ATG Repository Guide.
The Quincy Funds demo uses the following models. Note that both of these models are supported by ATG
2007.1s SQL/File System Connector. This configuration is sometimes referred to as a SQL Repository with
a Content Repository Loader.
Model 1: Hybrid content repository. Content is stored on the file system and
metadata is stored in the SQL repository.
In this configuration, a Content Repository Loader service monitors the file system on
a specified path (or collection of paths) and loads data from content files on the file
system into a GSA SQL repository, with a one-to-one mapping from a file to a content
repository item. One of the properties of the repository item, tagged in the itemdescriptor as the content-property, acts as a pointer to the file on the file system.
Model 2: Non-hybrid content repository. Both content and metadata are stored in
the SQL repository.
In this configuration, both metadata and the content itself are stored in the SQL
repository, with the content being stored in a single column. The Content Repository
Loader is used to load files in the file system to the SQL repository. Again, there is a
one-to-one mapping from a file to a content repository item.
It is important to note that neither model provides a means of propagating changes made to repository
items back from the repository to the source files. This behavior means that a user could theoretically
make a change to a repository item through the ATG Control Center, which would then be overwritten
the next time the content is loaded from the file system into the repository. To avoid this problem, the
ability to create or edit repository items through the ATG Control Center or JSPs is disabled for the Quincy
Funds demo.
For Model 1, note also that the metadata and the file content are not synchronized between the time
when changes are made to the file content and the scheduled run time of the Content Repository Loader.
Therefore a state could exist where the file content used by the Content Repository Loader to construct
the repository item could have been modified, but the Content Repository Loader (because it is a
scheduled service) has not yet propagated the modifications to the repository item. In this state, it is
possible for targeting rules or scenarios to reference and serve the file content according to repository
item properties that are no longer synchronized with their content. For this reason, Model 1 is suitable for
51
8 - Repository Structure in the Quincy Funds Demo
content repositories where synchronization between the content and the metadata is not an important
consideration, or where changes to the underlying content are very infrequent.
Model 2 does, however, guarantee synchronization of served content and metadata properties. With this
configuration, the file content that the Content Repository Loader uses to construct the repository item is
itself a property of the repository item; the item does not simply contain a pointer to the file. Therefore
there is no possibility of a loss of data integrity between the metadata and the content.
The content repositories in Quincy Funds use these models as follows:
News repository: XML content served using Model 1. This configuration

demonstrates the management of XML content exclusively through the Repository
API.
Model 1 is used in this case because the file content itself is never served (only
metadata is served), so synchronization is not an issue. Content is accessed only
through properties of the repository items. There is no serving of raw XML.
Email, Images, InvestmentTips, and Offers repositories: HTML content served

using Model 1.
These repositories demonstrate how Model 1 can be employed to serve HTML
content.
Funds repository: XML content served using Model 2. This configuration

demonstrates the management of XML content using the XMLTransform servlet bean
and XSL stylesheets.
Model 2 is used in this case because the file content is referenced and served (through
XMLTransform). Synchronization is therefore important.
This repository also gives examples of managing nested XML (XML content that has
items embedded in other items). The Content Repository Loader does not handle
nested XML items. This repository demonstrates how nested XML can be displayed by
means of XSL stylesheets, while the Content Repository Loader can still be employed
for the load process.
In addition, the Funds repository demonstrates how to create org.w3c.Documents
from SQL repository items. See Serving SQL Repository Items as org.w3c.Documents
for more information.
Features repository: HTML content served using Model 2.

The Features repository demonstrates the deployment of Model 2 to serve HTML
content in cases where synchronization between content and metadata is considered
to be important.
Content Repository Loaders in the Quincy Funds Demo

Each SQL content repository in the Quincy Funds demo has an associated Content Repository Loader (an
implementation of class atg.adapter.gsa.ContentRepositoryLoader) that is responsible for loading
the content into the repository. For each repository in Quincy Funds, the content is located at:
52
/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/repositories/{RepositoryName}
For instance, the content for the Funds repository is located as follows:
/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/repositories/Funds
As an example mapping, the following file

/DSSJ2EEDemo/j2ee-apps/QuincyFunds/
web-app/repositories/Funds/en_US/growth.xml
is mapped to the following repository item (id):

repositories/Funds/en_US/growth.xml
in repository:
/atg/demo/QuincyFunds/repositories/Funds/Funds
by the Content Repository Loader located at

/atg/demo/QuincyFunds/repositories/Funds/FundsLoader
Serving SQL Repository Items as org.w3c.Documents

Another important feature demonstrated by the Quincy Funds repositories is the ability to serve SQL
repository item properties as org.w3c.Document objects. (org.w3c.Documents are implementations of
the Document Object Model standard for XML documents; for more information, refer to the Document
Object Model Level 2 Core specification at http://www.w3.org/DOM/DOMTR.) Content stored in the
repository as a String or File can be transformed into an org.w3c.Document by means of the property
descriptor classes atg.xml.FileToDOMPropertyDescriptor and
atg.xml.StringToDOMPropertyDescriptor (both are extensions of
atg.repository.RepositoryPropertyDescriptor). The properties can then be used as input to the
XMLTransform servlet bean, for instance. For more information on the XMLTransform servlet bean, refer
to the ATG Page Developers Guide. For more information on using property descriptors, refer to UserDefined Property Types in the ATG Repository Guide.
Caching capability is also provided for org.w3c.Documents created through property descriptors.
org.w3c.Documents served from XML repositories are cached using a cache key that is based on either a
file name or URL. The ability to create org.w3c.Documents through SQL property descriptors, as
described above, requires a different cache key, because the property descriptors, in particular
atg.xml.StringToDOMPropertyDescriptor, do not have file or URL information. The cache key used
by the property descriptors for document caching is based on a concatenation of the repository items
repository name, item descriptor name, repository id, and content property name.
53
atg.xml.FileToDOMPropertyDescriptor
The FileToDOMPropertyDescriptor included with Quincy Funds is an implementation of class
atg.xml.FileToDOMPropertyDescriptor, which extends
atg.repository.RepositoryPropertyDescriptor. It takes another of the item descriptors
properties (of type File) as an attribute. It then transforms and caches the content of the other property as
an org.w3c.Document.
The following example definition is from the repository definition file
DSSJ2EEDemo/config/atg/demo/QuincyFunds/repositories/News/news.xml:
<property name="document" property-type = "atg.xml.FileToDOMPropertyDescriptor"

queryable="false">
<attribute name="documentSourcePropertyName" value = "newsContent"/>
<attribute name="contextRootName" value="QuincyFunds"/>
</property>
(Note that this property is not actually used in the demo.)

For more information on this property descriptor class, please refer to the ATG API Reference.
atg.xml.StringToDOMPropertyDescriptor
The StringToDOMPropertyDescriptor used by Quincy Funds is an implementation of class
atg.xml.StringToDOMPropertyDescriptor, which extends
atg.repository.RepositoryPropertyDescriptor. This property descriptor takes another of the
item descriptors properties (of type String) as an attribute. It then transforms and caches the content of
the other property as an org.w3c.Document.
The following example definition is from the repository definition file
DSSJ2EEDemo/config/atg/demo/QuincyFunds/repositories/Funds/funds.xml:
<property name="document" property-type = "atg.xml.StringToDOMPropertyDescriptor">

<attribute name="documentSourcePropertyName" value="fundContent"/>
<attribute name="contentTimeStampPropertyName" value="lastModified"/>
</property>
where fundContent is defined as follows:

<table name="dss_qf_fund_cont" type="auxiliary" id-column-name="id">
<property name="fundContent" column-name="file_content"
data-type="string" queryable="false"/>
</table>
The Quincy Funds demo contains an example of a reference to this property in an XMLTransform servlet
bean. The example is located in the following JSP:
54
DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/repositories/en/fund.jsp
<dsp:droplet name="/atg/dynamo/droplet/xml/XMLTransform">
<dsp:param name="input" param="element.document"/>
<dsp:param name="template" value="funds-investor-template.xsl"/>
<dsp:oparam name="failure">
<p> Failure to transform XML document: <dsp:valueof param="input"/>
</dsp:oparam>
</dsp:droplet>
For more information on this property descriptor class, please refer to the ATG API Reference.
55
56
Appendix A: Additional Scenario

Examples
This appendix provides additional examples of how you can implement a marketing strategy through
scenarios. These scenarios replicate real-life strategies and often incorporate multiple touchpoints (such
as e-mail) and delays in time. It may be difficult to walk through these scenarios as a site visitor, but you
can read through them to get a sense of the power and management potential provided by scenarios.

Once a visitor signs up to be a member, Quincy Funds has achieved a minor success, but has not yet met
its business goals, which include ensuring that members visit often, benefit from each visit, and purchase
funds. The Welcome Mail scenario resolves issues of visitor retention by predicting visitor actions and
countering those actions with a positive communication and offer.
To view the WelcomeMail scenario:
1.
2.
Expand the QuincyFunds and InvestorRetention folders.
3.
Click WelcomeMail.
The New Members segment specifies that all investors new to Quincy Funds will receive a welcome e-mail
five minutes after joining. New investors who havent logged in after 30 days will receive a second e-mail
containing an offer.
Compare these elements to the flow diagram to see how each element builds on the one that precedes it:
This scenario is triggered when a visitor registers as a member.

The system waits five minutes before initiating the next element.
57
Of those investors, only the ones whove entered an e-mail address
with their contact information are included.
An e-mail that welcomes new members is sent to those who meet the
people conditions. View the e-mail through the Pages and
Components > Pages screen, by following the supplied path. Use the
View > Preview option to see how it will appear to recipients.
A fork separates this element from the next into branches. If the new
investor logs into Quincy Funds, the scenario ends for him or her.
If 30 days pass without a visit from the new visitor, then the next
element occurs.
When the time condition is met, a second e-mail is sent to the
investor. This e-mail encourages the investor to return to the site by
extending a service. View the e-mail through the Pages and
Components > Pages screen, by following the supplied path. Use the
View > Preview option to see how it will appear to recipients.
The scenario ends.

In this example, a business user creates a monthly newsletter. Each month, the business user needs to
modify the e-mail message only, the scenario will automatically send the newsletter.
To view the MonthlyNewsletter scenario:
1.
2.
Navigate to QuincyFunds/InvestorRetention/MonthlyNewsletter.
This scenario sends an e-mail to investors on the first of each month. Heres how you read each element:
This scenario triggers on the first of each month.

58
An e-mail about Quincy Funds current events is sent to those who

meet the people conditions. View the e-mail through the Pages
and Components > Pages screen, by following the supplied path.
Use the View > Preview option to see how it will appear to
recipients.
The scenario ends.
Using Scenario Templates

A scenario template is a useful format for creating one generalized scenario that (with minor configuring),
applies to multiple situations. The MonthlyNewsletter scenario was derived from a scenario template
called QFScheduleMailing that includes all of the elements necessary for sending a mailing. To view the
QFScheduleMailing scenario template, open the Scenarios > Scenario Templates screen, and select
QFScheduleMailing.
As you can see, the template is made up of conditions with placeholders, indicated by parentheses. You
could adapt this template to create a scenario that sends information about investing to brokers.
To create a scenario from this template:
1.
2.
Select File > New Scenario to open the Create New Scenario wizard.
3.
Select QFScheduleMailing, and click Next.
4.
Place your scenario in the Quincy Funds root-level folder. Name your scenario New
Brokers. Click Finish.
5.
By selecting words and choosing from related drop-down lists, define the following:
Mailing Date: the 1 Monday of the month at 2:00am (Select the Weekday in
Month option and then specify the first Monday.)
st
Mailing Group: brokers

E-mail: Select the Quincy Funds demo from the list of applications at the top of
the window. The list at the bottom changes to show documents in this
application. Select /en/email/newsfeatures.html.
6.
Click OK. The scenario opens and appears as follows:
59
The scenario youve just created sends an e-mail to brokers that discusses the new feature articles. For
more information on scenario templates, see various sections in the Creating Scenarios chapter of the ATG
Quincy Funds is hosting a seminar to educate its investor community about investment strategies. This
scenario uses e-mail and an image on a Web page to publicize the seminar to those investors who are
eligible to attend.
To view the Promote Seminar scenario:
1.
2.
Navigate to QuincyFunds/InvestorPromotions/PromoteSeminar.
This scenario sends a targeted e-mail to only those investors who live near the seminar location. Once the
investors receive the e-mail, an advertisement for the seminar will appear on their home page.
Youll notice that this scenario was derived from a scenario template called QFSeminarPromotion
located on the Scenarios > Scenario Templates screen. If Quincy Funds sponsors the seminar in other
cities, the scenario template can be easily applied to create a new scenario. To use this template, you
would open the new scenario wizard, which requests a template and prompts you to configure the
variable elements.
The E-Mail Seminar Promotion Segment

This segment sends the e-mail message on May 15, 2000 to all investors who want to receive e-mail and
have the zip code 02471 or 02472.
60
This scenario is initiated by a date and time: May 15, 2000 at

12:00am.
A fork separates this action from the next into branches in order to
provide two options. Those investors who have identified their
postal code as 02471 in their profile will proceed to the action
following the fork.
Also, those investors who have identified their postal code as 02472
in their profile will proceed to the action following the fork.
Note: This scenario implies that for all investors who dont match
either postal code, the scenario will end with this element.
An e-mail publicizing the seminar is sent to those who meet the
preceding conditions. View the e-mail through the Pages and
Components > Pages screen by following the supplied path. Use
the View > Preview option to see how it will appear to recipients.
The scenario ends.
The Show Seminar Promotion Segment

The second segment displays the related seminar image when an investor with either postal code logs in
between May 15 and September 25 2000. You can assume that the seminar registration deadline is
September 25.
This scenario specifies a time element as its start and end points. The
scenario will execute between May 15 and September 25 2000.
This scenario only affects users who are logged in.
A fork separates this action from the next into branches in order to
provide two options. Those investors who have identified their postal
code as 02471 in their profile will proceed to the action following the
fork.
Also, those investors who have identified their postal code as 02472 in
their profile will proceed to the action following the fork.
Note: This scenario implies that for all investors who dont match either
postal code, the scenario will end with this element.
61
The seminar Offer image is placed in the QFOfferSlot and will be

displayed on the investor home page. If other images exist in the slot,
the Seminar Offer image may not display immediately.
The scenario ends.
You may notice that the slot, QFOfferSlot, is the same slot that is used in the Quincy Growth fund, the
Quincy Special Situations fund, and Quincy Overseas fund promotions. This means that when an investor
meets the criteria to view the images associated with each promotion, those images display in an order
specified by the slot.
62
Index
Content Repository Loaders, 52

converting members into satisfied patrons, 57
advertising a seminar, 60
aggressiveness index, 13, 21
analyzing visitor behavior, 45
for page developers, 49
for programmers, 50
ATG 2007.1
starting, with Quincy Funds, 5
ATG Control Center
editing demo properties in, 51
starting, 6
audit trail mapper, 46
brokers, 1
browsing, 15
features, 9
home page, 16
my clients, 17
targeted e-mail, 18, 59
business users, 2
charts, 45
scenarios, 35
targeting, 31
tracking, 22
fireContentEvent, 24
fireContentTypeEvent, 24
C
changing your profile and preferences, 13
chart templates, 47
charts
business users, 45
creating, 47
for page developers, 49
for programmers, 50
viewing, 47
components
SMPTEmail, 18
TargetingFirst, 42, 49
TargetingRange, 31
DRP servers, adding, 3
E
e-mail. See targeted e-mail
e-mail fund promotion segment, 38
e-mail seminar promotion segment, 60
emailHandlerHostName property, 18
event mappers for charts, 46
G
generating a chart, 47
generation property, 44
guests, 1
entering as, 10
features, 10
home page, 10
H
home page
brokers, 16
guests, 10
investors, 11
targeting used on, 27
I
internationalization, 9, 13
driven by personalization, 13
file structure, 14
Japanese support. See Japanese support
locales. See locales
investors, 1
features, 9
home page, 11
63
Index

J
Japanese support, 14
downloading fonts, 15
Internet Explorer browser settings, 15
Netscape Navigator browser settings, 15
JavaServer Pages, editing in demo, 51
PromoteGrowthFund scenario, 37
PromoteOverseasFund scenario, 41
PromoteSeminar scenario, 60
PromoteSpecialSituations scenario, 36
properties
emailHandlerHostName, 18
generation, 44
ordering, 44
retrieval, 44
locales, 13
English / United States, 13
file structure, 14
French / France, 13
German / Germany, 13
Japanese / Japan, 13
setting, 14
localization. See internationalization
logging out, 18
recorders, 46
event mappers, 46
recording visitor behavior, 46
registering as an investor, 11
repositories, 24
programmers, 24, 51
targeting, 33
repository items, editing in demo, 51
retrieval property, 44
rules, targeting, 30
modifying the demo, 3
O
Oracle
configuring ATG 2007.1 to use, 7
populating the demo database, 8
running the demo on, 6
ordering property, 44
org.w3c.Document objects, serving repository items as,
53
P
page developers, 2
charts, 49
scenarios, 42
slots, 42
targeting, 31
tracking, 24
populating the demo database (Oracle), 8
preferences, visitor, 13
previewing
pages, 24, 29
targeting results, 29
profile groups, 9
profiles, 9
aggressiveness index, 13
changing, 12, 13
how tracking affects, 23
trackfundsviewed scenario, 23
programmers, 3
charts, 50
repositories, 24
scenarios, 43
slots, 43
targeting, 33
tracking, 24
QF ScheduleMailing scenario template, 59

QF SeminarPromotion scenario template, 60
QFhomepageslot, 50
QFofferslot, 43, 62
QFsomepageslot, 49
S
scenario templates, 59
creating, 59
QF ScheduleMailing, 59
QF SeminarPromotion, 60
scenarios, 35
advertising a seminar, 60
business users, 35
page developers, 42
programmers, 43
PromoteGrowthFund, 37
PromoteSeminar, 60
PromoteSpecialSituations, 36
recorders, 46
sending a monthly newsletter, 58
SignupPromoTrial, 46
slots. See slots
TrackFundsViewed, 21, 22
using for visitor retention, 57
using to analyze visitor behavior, 45
WelcomeMail, 57
Show Promotion segment, 39
Show Seminar Promotion segment, 61
SignupPromoTrial scenario, 46
slots, 41
generation property, 44
ordering property, 44
placing images in, 41
programmers, 43
64
Index
QFofferslot, 41
retrieval property, 44
used by several scenarios, 40
SMPTEmail component, 18
SQL content repositories, 51
starting the ATG Control Center, 6
starting the demo, 5
T
tags
fireContentEvent, 24
fireContentTypeEvent, 24
targeted e-mail, 18
creating a mailing, 18
editing a mailing, 18
enabling, 18
viewing a summary of mailings, 18
targeting
business users, 29, 31
content, 27
example, 29
page developers, 31
previewing results, 29
programmers, 33
repositories, 33
rules, 30
used on investor home page, 27
TargetingFirst component, 42, 49

TargetingRange component, 31
TrackFundsViewed scenario, 21, 22
tracking
aggressiveness index, 13, 21
business users, 22
example, 21
page developers, 24
programmers, 24
using scenarios for, 22
visitor interests, 21
U
user profiles. See profiles
V
visitor retention
MonthlyNewsletter, 58
WelcomeMail scenario, 57
W
WelcomeMail scenario, 57
65
Index

At G Quincy Demo

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

At G Quincy Demo

Загружено:

Авторское право:

Доступные форматы

atg

Quincy Funds Demo Documentation

ATG Quincy Funds Demo Documentation

About this Document

Exploring the Demo

Touring Quincy Funds

Tracking Visitor Interests

Managing Visitors through Scenarios

ATG Quincy Funds Demo Documentation

Scenarios Sharing Slots

Analyzing Visitor Behavior

Examining the SignupPromoTrial Scenario

Repository Structure in the Quincy Funds Demo

Appendix A: Additional Scenario Examples

ATG Quincy Funds Demo Documentation

Investors registered customers of Quincy Funds

Brokers -- fund managers who serve the customers

Real-time profiling features provide the ability to changes a visitors profile

User segmentation allows business managers to group similar visitors together

Content targeting allows designers to display personalized content to visitors who

ATG Quincy Funds Demo Documentation

Scenarios give business managers a graphical tool for building sophisticated

About this Document

ATG Quincy Funds Demo Documentation

Modifying the Demo

ATG Quincy Funds Demo Documentation

ATG Quincy Funds Demo Documentation

On BEA WebLogic Server:

On JBoss Application Server:

Exploring the Demo

ATG Quincy Funds Demo Documentation

Point your browser to the ATG Dynamo Admin Server interface

Click the appropriate start button.

Running Quincy Funds on Oracle

Preparing to Import Data to Oracle

Configuring ATG 2007.1 to use Oracle

Populating the Database and Testing the Result

ATG Quincy Funds Demo Documentation

Preparing to Import Data to Oracle

Start SOLID, then ATG 2007.1.

Configuring ATG 2007.1 to Use Oracle

Launch the ATG Control Center.

Double-click the FakeXADataSource component so it opens in the Component

Be sure to save your changes to the live site.

ATG Quincy Funds Demo Documentation

Populating the Database and Testing the Result

Start the Oracle database and restart ATG 2007.1.

ATG Quincy Funds Demo Documentation

3 Touring Quincy Funds

Manage investment goals. Each investor has an Aggressiveness index (a profile

Brokers can do the following:

Send targeted e-mail to investors.

ATG Quincy Funds Demo Documentation

ATG Quincy Funds Demo Documentation

ATG Quincy Funds Demo Documentation

To change your profile properties:

Click on the Change My Investment Goals link.

ATG Quincy Funds Demo Documentation

Return to your home page.

Changing Your Profile and Preferences

Changing Your Language Preference

About Locales (for Programmers)

ATG Quincy Funds Demo Documentation