BEA WebLogic Commerce Server. Registration and User Processing Package

Transcription

1 BEA WebLogic Commerce Server Registratio ad User Processig Package BEA WebLogic Commerce Server 3.2 Documet Editio 3.2 December 2000

2 Copyright Copyright 2000 BEA Systems, Ic. All Rights Reserved. Restricted Rights Leged This software ad documetatio is subject to ad made available oly pursuat to the terms of the BEA Systems Licese Agreemet ad may be used or copied oly i accordace with the terms of that agreemet. It is agaist the law to copy the software except as specifically allowed i the agreemet. This documet may ot, i whole or i part, be copied photocopied, reproduced, traslated, or reduced to ay electroic medium or machie readable form without prior coset, i writig, from BEA Systems, Ic. Use, duplicatio or disclosure by the U.S. Govermet is subject to restrictios set forth i the BEA Systems Licese Agreemet ad i subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights Clause at FAR ; subparagraph (c)(1)(ii) of the Rights i Techical Data ad Computer Software clause at DFARS , subparagraph (d) of the Commercial Computer Software--Licesig clause at NASA FAR supplemet ; or their equivalet. Iformatio i this documet is subject to chage without otice ad does ot represet a commitmet o the part of BEA Systems. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA Systems DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE OR WRITTEN MATERIAL IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. Trademarks or Service Marks BEA, WebLogic, Tuxedo, ad Jolt are registered trademarks of BEA Systems, Ic. How Busiess Becomes E-Busiess, BEA WebLogic E-Busiess Platform, BEA Builder, BEA Maager, BEA elik, BEA WebLogic Commerce Server, BEA WebLogic Persoalizatio Server, BEA WebLogic Process Itegrator, BEA WebLogic Collaborate, BEA WebLogic Eterprise, ad BEA WebLogic Server are trademarks of BEA Systems, Ic. All other product ames may be trademarks of the respective compaies with which they are associated. Registratio ad User Processig Package Documet Editio Date Software Versio 3.2 December 2000 BEA WebLogic Commerce Server 3.2

3 Cotets About This Documet What You Need to Kow... ix e-docs Web Site...x How to Prit the Documet...x Related Iformatio... xi Cotact Us!... xi Documetatio Covetios... xii 1. Overview of the Registratio ad User Processig Package What Is the Registratio ad User Processig Package? High-level Architecture About the Database Schema Developmet Roles Next Steps Customer Registratio ad Logi Services JavaServer Pages (JSPs) logi.jsp Template Sample Browser View Locatio i the WebLogic Commerce Server Directory Structure Tag Library Imports Java Package Imports Locatio i Default Webflow Icluded JSP Templates Evets Dyamic Data Display Form Field Specificatio Registratio ad User Processig Package iii

4 badlogi.jsp Template Sample Browser View Locatio i the WebLogic Commerce Server Directory Structure Tag Library Imports Java Package Imports Locatio i Default Webflow Icluded JSP Templates Evets Dyamic Data Display Form Field Specificatio successfullogi.jsp Template Sample Browser View Locatio i the WebLogic Commerce Server Directory Structure Tag Library Imports Java Package Imports Locatio i Default Webflow Icluded JSP Templates Evets Dyamic Data Display Form Field Specificatio ewuser.jsp Template Sample Browser View Locatio i the WebLogic Commerce Server Directory Structure Tag Library Imports Java Package Imports Locatio i Default Webflow Icluded JSP Templates Evets Dyamic Data Display Form Field Specificatio Iput Processors CustomerProfileIP Pipelie Compoets RegisterUserPC iv Registratio ad User Processig Package

5 3. Customer Profile Services JavaServer Pages (JSPs) viewprofile.jsp Template Sample Browser View Locatio i the WebLogic Commerce Server Directory Structure Tag Library Imports Java Package Imports Locatio i Default Webflow Icluded JSP Templates Evets Dyamic Data Display Form Field Specificatio editprofile.jsp Template Sample Browser View Locatio i the WebLogic Commerce Server Directory Structure Tag Library Imports Java Package Imports Locatio i Default Webflow Icluded JSP Templates Evets Dyamic Data Display Form Field Specificatio profileewaddress.jsp Template Sample Browser View Locatio i the WebLogic Commerce Server Directory Structure Tag Library Imports Java Package Imports Locatio i Default Webflow Icluded JSP Templates Evets Dyamic Data Display Form Field Specificatio profileeditaddress.jsp Template Sample Browser View Locatio i WebLogic Commerce Server Directory Structure Registratio ad User Processig Package v

6 Tag Library Imports Java Package Imports Locatio i Default Webflow Icluded JSP Templates Evets Dyamic Data Display Form Field Specificatio profileewcc.jsp Template Sample Browser View Locatio i the WebLogic Commerce Server Directory Structure Tag Library Imports Java Package Imports Locatio i Default Webflow Icluded JSP Templates Evets Dyamic Data Display Form Field Specificatio profileeditcc.jsp Template Sample Browser View Locatio i the WebLogic Commerce Server Directory Structure Tag Library Imports Java Package Imports Locatio i Default Webflow Icluded JSP Templates Evets Dyamic Data Display Form Field Specificatio chagepassword.jsp Template Sample Browser View Locatio i the WebLogic Commerce Server Directory Structure Tag Library Imports Java Package Imports Locatio i Default Webflow Icluded JSP Templates Evets vi Registratio ad User Processig Package

7 Dyamic Data Display Form Field Specificatio Iput Processors DeleteCreditCardIP DeleteShippigAddressIP UpdateAccoutIfoIP UpdateBasicIfoIP UpdatePaymetIfoIP UpdateShippigIfoIP Pipelie Compoets UpdateBasicIfoPC UpdatePaymetIfoPC UpdateShippigIfoPC UpdatePasswordPC Customer Self-Service JavaServer Pages (JSPs) mai.jsp Template orderhistory.jsp Template Sample Browser View Locatio i the WebLogic Commerce Server Directory Structure Tag Library Imports Java Package Imports Locatio i Default Webflow Icluded JSP Templates Evets Dyamic Data Display Form Field Specificatio orderstatus.jsp Template Sample Browser View Locatio i WebLogic Commerce Server Directory Structure Tag Library Imports Java Package Imports Locatio i Default Web Flow Icluded JSP Templates Registratio ad User Processig Package vii

8 Idex Evets Dyamic Data Display Form Field Specificatio paymethistory.jsp Template Sample Browser View Locatio i the WebLogic Commerce Server Directory Structure Tag Library Imports Java Package Imports Locatio i Default Webflow Icluded JSP Templates Evets Dyamic Data Display Form Field Specificatio Iput Processors SelectOrderForViewigIP Pipelie Compoets RefreshOrderHistoryPC RefreshPaymetHistoryPC viii Registratio ad User Processig Package

9 About This Documet This documet explais how to use the services available withi the BEA WebLogic Commerce Server Registratio ad User Processig package. This documet icludes the followig topics: Chapter 1, Overview of the Registratio ad User Processig Package, which describes the high-level architecture of the package ad provides itroductory iformatio about its services. Chapter 2, Customer Registratio ad Logi Services, which describes the JSP templates, iput processors, ad Pipelies associated with the customer registratio ad logi Web pages. Chapter 3, Customer Profile Services, which describes the JSP templates, iput processors, ad Pipelies associated with the customer profile Web pages. Chapter 4, Customer Self-Service, which describes the JSP templates, iput processors, ad Pipelies associated with the customer self-service Web pages. What You Need to Kow This documet is iteded for the followig audieces: The commerce egieer/jsp cotet developer, who uses JSP templates ad tag libraries to implemet iteractive Web pages to meet busiess requiremets. This user also maitais simple cofiguratio files. The busiess aalyst, who defies the compay s busiess protocols (processes ad rules) for a busiess-to-cosumer Web site. This user may set pricig policies ad discouts, ad may pla promotioal advertisig. Registratio ad User Processig Package ix

10 The site admiistrator, who uses Commerce ad Persoalizatio Server admiistratio screes to cofigure the site s rules, portals, property sets, user profiles, cotet delivery, ad product catalog. The Java/EJB programmer, who creates custom code to isert i the JSP files. This user may also hadle complex cofiguratio files. e-docs Web Site BEA product documetatio is available o the BEA corporate Web site. From the BEA Home page, click o Product Documetatio or go directly to the e-docs Product Documetatio page at How to Prit the Documet You ca prit a copy of this documet from a Web browser, oe file at a time, by usig the File >Prit optio o your Web browser. A PDF versio of this documet is available o the WebLogic Commerce Server documetatio Home page o the e-docs Web site (ad also o the documetatio CD). You ca ope the PDF i Adobe Acrobat Reader ad prit the etire documet (or a portio of it) i book format. To access the PDFs, ope the WebLogic Commerce Server documetatio Home page, click the PDF files butto ad select the documet you wat to prit. If you do ot have the Adobe Acrobat Reader, you ca get it for free from the Adobe Web site at x Registratio ad User Processig Package

11 Related Iformatio The followig BEA WebLogic Commerce Server documets cotai iformatio that is relevat to usig the Registratio ad User Processig package ad uderstadig how to customize or exted the provided services. BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet BEA WebLogic Commerce Server Order Processig Package BEA WebLogic Commerce Server Product Catalog Maagemet For more iformatio about J2EE as it relates to WebLogic Server security, see the iformatio posted o the Su Microsystems, Ic. Java(TM) 2 Platform, Eterprise Editio Web site at Cotact Us! Your feedback o the BEA WebLogic Commerce Server documetatio is importat to us. Sed us at docsupport@beasys.com if you have questios or commets. Your commets will be reviewed directly by the BEA professioals who create ad update the WebLogic Commerce Server documetatio. I your message, please idicate that you are usig the documetatio for the BEA WebLogic Commerce Server 3.1 release. If you have ay questios about this versio of BEA WebLogic Commerce Server, or if you have problems istallig ad ruig BEA WebLogic Commerce Server, cotact BEA Customer Support through BEA WebSupport at You ca also cotact Customer Support by usig the cotact iformatio provided o the Customer Support Card, which is icluded i the product package. Whe cotactig Customer Support, be prepared to provide the followig iformatio: Your ame, address, phoe umber, ad fax umber Your compay ame ad compay address Registratio ad User Processig Package xi

12 Your machie type ad authorizatio codes The ame ad versio of the product you are usig A descriptio of the problem ad the cotet of pertiet error messages Documetatio Covetios The followig documetatio covetios are used throughout this documet. Covetio boldface text Ctrl+Tab italics moospace text moospace boldface text moospace italic text Item Idicates terms defied i the glossary. Idicates that you must press two or more keys simultaeously. Idicates emphasis or book titles. Idicates code samples, commads ad their optios, data structures ad their members, data types, directories, ad fileames ad their extesios. Moospace text also idicates text that you must eter from the keyboard. Examples: #iclude <iostream.h> void mai ( ) the poiter psz chmod u+w * \tux\data\ap.doc tux.doc BITMAP float Idetifies sigificat words i code. Example: void commit ( ) Idetifies variables i code. Example: Strig expr xii Registratio ad User Processig Package

13 Covetio UPPERCASE TEXT Item Idicates device ames, eviromet variables, ad logical operators. Examples: LPT1 SIGNON OR { } Idicates a set of choices i a sytax lie. The braces themselves should ever be typed. [ ] Idicates optioal items i a sytax lie. The brackets themselves should ever be typed. Example: buildobjcliet [-v] [-o ame ] [-f file-list]... [-l file-list]... Separates mutually exclusive choices i a sytax lie. The symbol itself should ever be typed.... Idicates oe of the followig i a commad lie: That a argumet ca be repeated several times i a commad lie That the statemet omits additioal optioal argumets That you ca eter additioal parameters, values, or other iformatio The ellipsis itself should ever be typed. Example: buildobjcliet [-v] [-o ame ] [-f file-list]... [-l file-list] Idicates the omissio of items from a code example or from a sytax lie. The vertical ellipsis itself should ever be typed. Registratio ad User Processig Package xiii

14 xiv Registratio ad User Processig Package

15 CHAPTER 1 Overview of the Registratio ad User Processig Package The processes related to customer (user) profiles ad customer self-service are ecessary compoets of ay e-busiess expectig retur customers. To help you get to market faster tha your competitors, the BEA WebLogic Commerce Server product provides you with a Registratio ad User Processig package. This package cotais default implemetatios for the most commo pre- ad post-order processig services (registratio, logi, customer profile creatio/updates, ad customer self-service pages). Desiged to be used out-of-the-box, the Registratio ad User Processig package also allows your site desigers to customize these processes, without the eed for advaced programmig skills. This topic provides you with some backgroud iformatio about the Registratio ad User Processig package, ad itroduces you to the types of services that are available. This topic icludes the followig sectios: What Is the Registratio ad User Processig Package? High-level Architecture About the Database Schema Developmet Roles Next Steps Registratio ad User Processig Package 1-1

16 1 Overview of the Registratio ad User Processig Package What Is the Registratio ad User Processig Package? The Registratio ad User Processig package is a collectio of services used to facilitate the registratio of customers with your e-busiess site ad the activities customer ca perform after registerig. There are services for registratio, logi, customer profile creatio/updates, ad so o. Additioally, the customer self-service pages provide your customers with the ability to check the status of orders ad paymets. As show i Figure 1-1, each service i the package cosists of oe or more JavaServer Pages (JSPs) ad the busiess logic associated with them. Some of these templates may collect iformatio from your customers, while others will simply display dyamic data your customer previously supplied. Some JSPs may do both. This logic is implemeted as a combiatio of iput processors ad Pipelie compoets, each of which ca be modified to suit your eeds. You ca also create your ow iput processors ad Pipelie compoets to plug ito the Registratio ad User Processig package. 1-2 Registratio ad User Processig Package

17 What Is the Registratio ad User Processig Package? Figure 1-1 Structure of the Registratio ad User Processig Package Because all the busiess logic is maaged by a Pipelie ad accessed withi a Pipelie sessio, the state of your customer s experieces ca be maitaied. For detailed iformatio about Pipelies (icludig Pipelie compoets ad Pipelie sessios), see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. I additio to the services available i the Registratio ad User Processig package, the BEA WebLogic Commerce Server product also cotais services for browsig the product catalog ad for order processig. For iformatio o services related to the product catalog, see BEA WebLogic Commerce Server Product Catalog Maagemet. For iformatio o services related to order processig, see BEA WebLogic Commerce Server Order Processig Package. Registratio ad User Processig Package 1-3

18 1 Overview of the Registratio ad User Processig Package High-level Architecture The Registratio ad User Processig package is essetially a applicatio that utilizes the Webflow/Pipelie ifrastructure. Before you begi to customize or exted this applicatio, however, it is importat that you have a high-level uderstadig of how all the JSP templates i the Registratio ad User Processig package work together i the default Webflow. It is also importat that you uderstad how this package works i cojuctio with JSP templates i the Order Processig package. For more iformatio about the default Webflow, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. For more iformatio about the Order Processig package, see BEA WebLogic Commerce Server Order Processig Package. Figure 1-2 shows the ways i which your customer might move through the JSP templates i the logi ad registratio portio of the Registratio ad User Processig package. It also shows where the user processig portio of the package, the Product Catalog, ad the Order Processig package come ito play. Although this diagram shows the shoppig cart maagemet piece of the Webflow, it is ot discussed i this documet. For more iformatio about the shoppig cart ad the checkout process, see the Shoppig Cart Maagemet Services i the BEA WebLogic Commerce Server Order Processig Package documetatio. 1-4 Registratio ad User Processig Package

19 High-level Architecture Figure 1-2 Default Webflow for Logi/Registratio Registratio JSPs Aoymous Users Permitted From searchresults.jsp View Cart shoppigcart.jsp Check Out Logged I? To shippig.jsp No Yes logi.jsp successfullogi.jsp New Users Oly ewuser.jsp Figure 1-3 shows the ways i which your customer might move through the JSP templates i the user processig ad customer self-service portios of the Registratio ad User Processig package. It also shows where the Product Catalog, the Order Processig package, ad the logi/registratio portio of the package come ito play. Registratio ad User Processig Package 1-5

20 1 Overview of the Registratio ad User Processig Package Figure 1-3 Default Webflow for User Processig/Customer Self-Service From Catalog or Order or Register From mai.jsp User Profile JSPs Autheticated Users Oly viewprofile.jsp orderhistory.jsp paymethistory.jsp orderstatus.jsp editprofile.jsp chagepassword.jsp profileewcc.jsp profileewaddress.jsp profileeditcc.jsp profileeditaddress.jsp Note: All JSP templates iclude other templates, makig it easy for you to create ew pages with the same look ad feel. Whether you are customizig or extedig this architecture, everythig you eed to kow about the services i the Registratio ad User Processig package (icludig the JSP templates, iput processors, ad Pipelie compoets associated with them) is 1-6 Registratio ad User Processig Package

21 About the Database Schema provided i this documet. This icludes detailed iformatio about the database schema, for those advaced programmers who wat to take their e-busiess site to the ext level. About the Database Schema The database schema used for the Registratio ad User Processig package is the oe used for the BEA WebLogic Persoalizatio Server. For more iformatio about this database schema, see BEA WebLogic Persoalizatio Server Developer s Guide. Additioally, customer profiles i the BEA WebLogic Commerce Server are implemeted as Uified User Profiles (UUP). For more iformatio about UUP, see Creatig ad Maagig Users i the BEA WebLogic Persoalizatio Server documetatio. Developmet Roles This documet is iteded for the followig audieces: The commerce egieer/jsp cotet developer, who uses JSP templates ad tag libraries to implemet iteractive Web pages to meet busiess requiremets. This user also maitais simple cofiguratio files. The busiess aalyst, who defies the compay s busiess protocols (processes ad rules) for a busiess-to-cosumer Web site. This user may set pricig policies ad discouts, ad may pla promotioal advertisig. The site admiistrator, who uses Commerce ad Persoalizatio Server admiistratio screes to cofigure the site s rules, portals, property sets, user profiles, cotet delivery, ad product catalog. The Java/EJB programmer, who creates custom code to isert i the JSP files. This user may also hadle complex cofiguratio files. Registratio ad User Processig Package 1-7

22 1 Overview of the Registratio ad User Processig Package Next Steps Subsequet chapters of this documet describe the Registratio ad User Processig package i detail, ad provide you with iformatio about how to customize or exted the default implemetatios to meet your requiremets. These chapters are as follows: Customer Registratio ad Logi Services Customer Profile Services Customer Self-Service 1-8 Registratio ad User Processig Package

23 CHAPTER 2 Customer Registratio ad Logi Services For customers who pla o frequetig your e-busiess o a regular basis, it is beeficial to provide a way for them to store some persoal iformatio. I doig so, the orderig process will require less time because your customer will ot eed to reeter their ame, address, paymet iformatio, ad so o. For security, privacy, ad maagemet however, this feature requires customers to log ito your site with a userame/password combiatio. This topic describes the JavaServer Pages (JSPs) ad associated compoets that allow customers to register ad log ito your site by creatig a customer profile. This topic icludes the followig sectios: JavaServer Pages (JSPs) l logi.jsp Template l badlogi.jsp Template l successfullogi.jsp Template l ewuser.jsp Template Iput Processors l CustomerProfileIP Pipelie Compoets l RegisterUserPC Registratio ad User Processig Package 2-1

24 2 Customer Registratio ad Logi Services JavaServer Pages (JSPs) The Registratio ad User Processig package cotais a umber of JavaServer Pages (JSPs) that hadle customer registratio (iitial customer profile creatio) ad customer logi. Remember, you ca always use these templates for your Web site, or you ca adapt them to meet your specific eeds. This sectio describes each of these pages i detail. Note: For a descriptio of the complete set of JSPs used i the WebLogic Commerce Server Web applicatio ad a listig of their locatios i the directory structure, see the Summary of JSP Templates documetatio. logi.jsp Template Sample Browser View The logi.jsp template (show i Figure 2-1) allows a customer who has previously created a profile to log ito your e-commerce site by providig a valid userame/password combiatio. Sice this page is the etry poit to the checkout process, it also establishes mechaisms (such as sessios) that will allow customers to cotiue their shoppig experiece. For customers who have ot yet registered with your site, the logi.jsp template provides customers with a etry poit ito a page that allows them to register (create their iitial customer profile) for subsequet use o the site. Figure 2-1 shows a aotated versio of the logi.jsp template. The dashed lies ad umbers i the diagram are ot part of the template; they are refereced i the explaatio that follows the scree shot. 2-2 Registratio ad User Processig Package

25 JavaServer Pages (JSPs) Figure 2-1 Aotated logi.jsp Template The umbers i the followig list refer to the umbered regios i the figure: 1. The page header (top baer) is created from a import of the ierheader.jsp template. This is stadard across may of the JSP templates provided by WebLogic Commerce Server. The import call is: <%@ iclude file="/commerce/icludes/ierheader.jsp" %> 2. This regio provides two form fields for customers who already have a userame ad password combiatio. Whe the form is posted, autheticatio is hadled by the WebLogic Server (ot part of the default Webflow). 3. This regio provides a lik ito the page that allows ew customers to register with your e-commerce site. Registratio ivolves creatig a iitial customer profile, ad is where the customer will set their userame ad password for subsequet logis. 4. The logi.jsp template s cotet i regio 4 cotais the icluded ierfooter.jsp template. The iclude call i logi.jsp is: Registratio ad User Processig Package 2-3

26 2 Customer Registratio ad Logi Services iclude file="/commerce/icludes/ierfooter.jsp" %> ierfooter.jsp cosists of the horizotal footer at the bottom of the page, plus the right-side vertical colum that describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. I the ierfooter.jsp file, the right-side vertical colum is a iclude file: <%@ iclude file="/commerce/icludes/rightside.jsp" %> Locatio i the WebLogic Commerce Server Directory Structure You ca fid the logi.jsp template file at the followig locatio, where WL_COMMERCE_HOME is the directory i which you istalled WebLogic Commerce Server: %WL_COMMERCE_HOME%\server\webapps\wlcs\commerce\logi.jsp (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/commerce/logi.jsp (UNIX) Tag Library Imports Java Package Imports The logi.jsp template does ot use ay JSP tags. Therefore, the template does ot iclude imports of ay JSP tag libraries. The logi.jsp template uses Java classes i the followig packages ad therefore icludes these import statemets: <%@ page import= javax.servlet.http.* %> <%@ page import= com.beasys.commerce.webflow.* %> Locatio i Default Webflow The logi.jsp template itself is ot part of the default Webflow. Rather, it is automatically loaded ito the browser whe a protected page is refereced by the WebLogic Server. Note: All JSP templates i the /order ad /user subdirectories are protected ad are accessible oly by registered ad autheticated customers. 2-4 Registratio ad User Processig Package

27 JavaServer Pages (JSPs) Icluded JSP Templates If the customer already has a userame/password combiatio from prior registratio ad the customer s logi is successful, the ext page is the protected page the customer was attemptig to access. If the customer s logi is usuccessful, a versio of the logi.jsp template is reloaded with a error message (badlogi.jsp). If the customer is ot yet registered ad clicks o the Create butto, the ext page loaded will allow the customer to create a profile ad obtai a userame/password combiatio (ewuser.jsp). After the customer has registered, the customer will be retured to logi.jsp so they ca log i. If the customer s logi is the successful, the ext page is the successful logi page, (successfullogi.jsp), which allows customers to decide whether they wat to proceed to their shoppig cart (shoppigcart.jsp), proceed to checkout (shippig.jsp), or proceed to the mai page (mai.jsp). If the customer s logi is usuccessful, a versio of the logi.jsp template is reloaded with a error message (badlogi.jsp). Notes: The optio to proceed to checkout is oly provided o the successfullogi.jsp template if there are items i the customer s shoppig cart. For a detailed descriptio of the mai.jsp template, see Product Catalog JSP Templates ad Tag Library i the BEA WebLogic Commerce Server Product Catalog Maagemet documetatio. For a detailed descriptio of the shoppigcart.jsp ad shippig.jsp templates, see Shoppig Cart Maagemet Services or Shippig Services i the BEA WebLogic Commerce Server Order Processig Package documetatio. For more iformatio about the default Webflow, see Overview of the Registratio ad User Processig Package o page 1-1. The followig JSP templates are icluded i the logi.jsp template: ierheader.jsp, which creates the top baer. ierfooter.jsp, which creates a horizotal footer at the bottom of the page, ad also icludes the rightside.jsp template. rightside.jsp describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. Registratio ad User Processig Package 2-5

28 2 Customer Registratio ad Logi Services Evets The logi.jsp template presets a customer with two buttos, oly oe of which is cosidered a evet. The evet triggers a particular respose i the default Webflow that allows customers to cotiue. The other butto is a stadard HTML Submit butto that posts the page back to the WebLogic Server for autheticatio. Table 2-1 provides iformatio about the evet ad the busiess logic it ivokes. Table 2-1 logi.jsp Evets Evet butto(createuser) Webflow Respose(s) No busiess logic required. Loads ewuser.jsp. Note: The Logi butto actually is ot a evet that would trigger a Webflow respose. Rather, whe a customer clicks the butto, cotrol is tured over to the WebLogic Server (specifically, the RDBMS realm of the WebLogic Persoalizatio Server). The WebLogic Server remembers the HTTP request, determies whether the customer s userame ad password combiatio is correct, ad the reivokes the Webflow usig the request. Sice this autheticatio follows the WebLogic Server ad J2EE specificatios, more iformatio o this topic ca be foud i documets at the BEA WebLogic Server 5.1 Documetatio Ceter. Dyamic Data Display No dyamic data is preseted o the logi.jsp template. Form Field Specificatio The primary purpose of the logi.jsp template is to allow customers to eter their userame ad password usig two HTML form fields. It is also used to pass eeded iformatio to the Webflow. The form fields used i the logi.jsp template, ad a descriptio for each of these form fields are listed i Table Registratio ad User Processig Package

29 JavaServer Pages (JSPs) Table 2-2 logi.jsp Form Fields Parameter Name Type Descriptio evet Hidde Idicates which evet has bee triggered. It is used by the Webflow to determie what happes ext. origi Hidde The ame of the curret page (logi.jsp), used by the Webflow. j_userame Textbox The customer s logi ame, passed to WebLogic Server for autheticatio. j_password Password The customer s logi password, passed to WebLogic Server for autheticatio. Note: Parameters that are literals i the JSP code are show i quotes, while o-literals will require scriptlet sytax (such as <%= USER_NAME %>) for use i the JSP. Registratio ad User Processig Package 2-7

30 2 Customer Registratio ad Logi Services badlogi.jsp Template Sample Browser View The badlogi.jsp template (show i Figure 2-2) iforms a customer that they have etered a ivalid userame/password combiatio, ad allows the customer to try loggig ito your e-commerce site agai by providig a valid userame/password combiatio. Except for the error message, it behaves exactly as the logi.jsp template previously described. Figure 2-2 shows a aotated versio of the badlogi.jsp template. The dashed lies ad umbers i the diagram are ot part of the template; they are refereced i the explaatio that follows the scree shot. Figure 2-2 Aotated badlogi.jsp Template 2-8 Registratio ad User Processig Package

31 JavaServer Pages (JSPs) The umbers i the followig list refer to the umbered regios i the figure: 1. Regio 1 displays the logi error message to the customer, ad prompts the customer to try loggig i agai or to create a ew accout. 2. Because the badlogi.jsp template icludes the logi.jsp template, the followig regios are actually part of the logi.jsp template: a. The page header (top baer) is created from a import of the ierheader.jsp template. This is stadard across may of the JSP templates provided by the WebLogic Commerce Server. The import call is: <%@ iclude file="/commerce/icludes/ierheader.jsp" %> b. This regio provides two form fields for customers who already have a userame ad password combiatio. Whe the form is posted, autheticatio is hadled by WebLogic Server (ot part of the default Webflow). c. This regio provides a lik ito the page that allows ew customers to register with your e-commerce site. Registratio ivolves creatig a iitial customer profile, ad is where the customer will set their userame ad password for subsequet logis. d. The logi.jsp template s cotet i regio 2d cotais the icluded ierfooter.jsp template. The iclude call i logi.jsp is: <%@ iclude file="/commerce/icludes/ierfooter.jsp" %> ierfooter.jsp cosists of the horizotal footer at the bottom of the page, plus the right-side vertical colum that describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. I the ierfooter.jsp file, the right-side vertical colum is a iclude file: <%@ iclude file="/commerce/icludes/rightside.jsp" %> Locatio i the WebLogic Commerce Server Directory Structure You ca fid the badlogi.jsp template file at the followig locatio, where WL_COMMERCE_HOME is the directory i which you istalled WebLogic Commerce Server: %WL_COMMERCE_HOME%\server\webapps\wlcs\commerce\badlogi.jsp (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/commerce/badlogi.jsp (UNIX) Registratio ad User Processig Package 2-9

32 2 Customer Registratio ad Logi Services Tag Library Imports Java Package Imports The badlogi.jsp template does ot use ay JSP tags. Therefore, the template does ot iclude imports of ay JSP tag libraries. The badlogi.jsp template does ot use ay Java classes ad therefore does ot iclude ay package import statemets. Locatio i Default Webflow Customers arrive at the badlogi.jsp template whe they fail to provide a valid userame/password combiatio o the logi.jsp template. If the customer is registered ad the customer s secod attempt at loggig i is successful, the ext page is the protected page the customer was attemptig to access. If the customer s logi is usuccessful, the badlogi.jsp template is reloaded. If the customer is ot yet registered ad clicks o the Create butto, the ext page loaded will allow them to create a customer profile ad obtai a userame/password combiatio (ewuser.jsp). After the customer has registered, the customer will be retured to logi.jsp so they ca log i. Note: For more iformatio about the default Webflow, see Overview of the Registratio ad User Processig Package o page 1-1. Icluded JSP Templates The followig JSP template is icluded i the badlogi.jsp template: logi.jsp, which creates the etire page, with the exceptio of the error message at the top. Evets Because the badlogi.jsp template is essetially the same as the logi.jsp template, the badlogi.jsp template makes use of the same evets. For more iformatio about these evets, see logi.jsp Template o page Registratio ad User Processig Package

33 JavaServer Pages (JSPs) Dyamic Data Display Form Field Specificatio No dyamic data is preseted o the badlogi.jsp template. Because the badlogi.jsp template is essetially the same as the logi.jsp template, the badlogi.jsp template makes use of the same form fields. For more iformatio about these form fields, see logi.jsp Template o page 2-2. Registratio ad User Processig Package 2-11

34 2 Customer Registratio ad Logi Services successfullogi.jsp Template Sample Browser View The successfullogi.jsp template (show i Figure 2-3) iforms a customer who has just created a user profile ad logged i that the logi was successful, ad provides the customer with the opportuity to retur to their shoppig experiece through several avigatio optios. Figure 2-3 shows a aotated versio of the successfullogi.jsp template. The dashed lies ad umbers i the diagram are ot part of the template; they are refereced i the explaatio that follows the scree shot. Figure 2-3 Aotated successfullogi.jsp Template - With Checkout Optio 2-12 Registratio ad User Processig Package

35 JavaServer Pages (JSPs) The umbers i the followig list refer to the umbered regios i the figure: 1. The page header (top baer) is created from a import of the ierheader.jsp template. This is stadard across may of the JSP templates provided by WebLogic Commerce Server. The import call is: <%@ iclude file="/commerce/icludes/ierheader.jsp" %> 2. This regio idicates to the customer that their logi (ad thus registratio) was successful, ad provides them with liks to retur to their shoppig cart (shoppigcart.jsp), to cotiue to the checkout process (shippig.jsp) or to retur to the mai catalog page (mai.jsp). Notes: For a detailed descriptio of the mai.jsp template, see the Product Catalog JSP Templates ad Tag Library i the BEA WebLogic Commerce Server Product Catalog Maagemet documetatio. For a detailed descriptio of the shoppigcart.jsp ad shippig.jsp templates, see the Shoppig Cart Maagemet Services or the Shippig Services i the BEA WebLogic Commerce Server Order Processig Package documetatio. The optio to proceed to checkout is oly provided o the successfullogi.jsp template if there are items i the customer s shoppig cart. Otherwise, the successfullogi.jsp template will leave out this optio, as show i Figure 2-4. Registratio ad User Processig Package 2-13

36 2 Customer Registratio ad Logi Services Figure 2-4 successfullogi.jsp - Without Checkout Optio 3. The successfullogi.jsp template s cotet i regio 3 cotais the icluded ierfooter.jsp template. The iclude call i successfullogi.jsp is: <%@ iclude file="/commerce/icludes/ierfooter.jsp" %> ierfooter.jsp cosists of the horizotal footer at the bottom of the page, plus the right-side vertical colum that describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. I the ierfooter.jsp file, the right-side vertical colum is a iclude file: <%@ iclude file="/commerce/icludes/rightside.jsp" %> 2-14 Registratio ad User Processig Package

37 JavaServer Pages (JSPs) Locatio i the WebLogic Commerce Server Directory Structure You ca fid the successfullogi.jsp template file at the followig locatio, where WL_COMMERCE_HOME is the directory i which you istalled WebLogic Commerce Server: %WL_COMMERCE_HOME%\server\webapps\wlcs\commerce\user\ successfullogi.jsp (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/commerce/user/ successfullogi.jsp (UNIX) Tag Library Imports The successfullogi.jsp template uses Pipelie JSP tags. Therefore, the template icludes the followig JSP tag libraries: <%@ taglib uri= pipelie.tld prefix= pipelie %> Note: For more iformatio about the Pipelie JSP tags, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. These files reside i the followig directory for the WebLogic Commerce Server Web applicatio: %WL_COMMERCE_HOME%\server\webapps\wlcs\WEB-INF (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/WEB-INF (UNIX) Java Package Imports The successfullogi.jsp template uses Java classes i the followig packages ad therefore icludes these import statemets: <%@ page import= javax.servlet.* %> <%@ page import= javax.servlet.http.* %> <%@ page import= com.beasys.commerce.ebusiess.shoppigcart.* %> <%@ page import= com.beasys.commerce.webflow.* %> Locatio i Default Webflow Customers arrive at the successfullogi.jsp template whe they have successfully logged ito your e-commerce site (o the logi.jsp template) oly after just havig created a customer profile. Registratio ad User Processig Package 2-15

38 2 Customer Registratio ad Logi Services Note: If a customer had created a profile o a previous visit ad logged i usig the logi.jsp template, the customer would simply be take to the protected page the customer was tryig to access. Icluded JSP Templates From the successfullogi.jsp template, the customer ca retur to their shoppig cart (shoppigcart.jsp), cotiue to the checkout process (shippig.jsp), or retur to the mai catalog page (mai.jsp). Notes: The optio to proceed to checkout is oly provided o the successfullogi.jsp template if there are items i the customer s shoppig cart. For more iformatio about the default Webflow, see Overview of the Registratio ad User Processig Package o page 1-1. The followig JSP templates are icluded i the successfullogi.jsp template: ierheader.jsp, which creates the top baer. ierfooter.jsp, which creates a horizotal footer at the bottom of the page, ad also icludes the rightside.jsp template. rightside.jsp describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. Evets Every time a customer clicks a butto to view more detail about a order, it is cosidered a evet. Each evet triggers a particular respose i the default Webflow that allows them to cotiue. While this respose ca be to load aother JSP, it is usually the case that a iput processor ad/or Pipelie is ivoked first. Table 2-3 provides iformatio about these evets ad the busiess logic they ivoke. Table 2-3 successfullogi.jsp Evets Evet lik(shoppigcart) lik(checkout) Webflow Respose(s) IitShoppigCartIP IitShippigMethodListIP 2-16 Registratio ad User Processig Package

39 JavaServer Pages (JSPs) Table 2-3 successfullogi.jsp Evets Evet lik(home) Webflow Respose(s) GetTopCategoriesIP GetTopCategories Note: For more iformatio about the GetTopCategoriesIP ad GetTopCategories Pipelie, see BEA WebLogic Commerce Server Product Catalog Maagemet. Dyamic Data Display Oe purpose of the successfullogi.jsp template is to display avigatio optios that allow customers to cotiue their shoppig experiece after loggig i. However, if there are o items i the customer s shoppig cart, the checkout is ot a optio that should be displayed. The decisio of whether or ot to display this optio is accomplished o successfullogi.jsp usig a combiatio of Pipelie JSP tags ad accessor methods/attributes. First, the getpipelieproperty JSP tag retrieves the SHOPPING_CART attribute from the Pipelie sessio. Table 2-4 provides more detailed iformatio o this attribute. Table 2-4 successfullogi.jsp Pipelie Sessio Attributes Attribute Type Descriptio PipelieSessioCostats.SHOPPING_CART com.beasys.commerce.ebusiess.shoppigcart.shoppigcart The curretly active shoppig cart. Listig 2-1 illustrates how this attribute is retrieved from the Pipelie sessio usig the getpipelieproperty JSP tag. Listig 2-1 Retrievig the Shoppig Cart Attribute <pipelie:getpipelieproperty propertyname="<%=pipeliesessiocostats.shopping_cart%>" returname="shoppigcart" Registratio ad User Processig Package 2-17

40 2 Customer Registratio ad Logi Services returtype="com.beasys.commerce.ebusiess.shoppigcart. ShoppigCart"/> Note: For more iformatio o the getpipelieproperty JSP tag, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. The data stored withi the Pipelie sessio attribute is the accessed by usig accessor methods/attributes withi Java scriptlets. Table 2-5 provides more detailed iformatio about these methods/attributes for shoppigcart. Table 2-5 shoppigcart Accessor Methods/Attributes Method/Attribute isempty() Descriptio Returs true if the customer s shoppig cart is empty. The presece of items i the shoppig cart is evaluated usig this method i a Java scriptlet, as show i Listig 2-2. Listig 2-2 Usig Accessor Methods/Attributes Withi successfullogi.jsp Java Scriptlets <% if (shoppigcart!= ull && shoppigcart.isempty() == false) { %> <a href="<%=webflowjsphelper.createwebflowurl(pagecotext, "successfullogi.jsp","butto(checkout)", true)%>">checkout</a> <% } %> Form Field Specificatio No form fields are used i the successfullogi.jsp template Registratio ad User Processig Package

41 JavaServer Pages (JSPs) ewuser.jsp Template Sample Browser View The ewuser.jsp template (show i Figure 2-5 through Figure 2-7) allows a ew customer to register with your e-commerce site by creatig their customer profile, which icludes persoal iformatio, shippig address iformatio, paymet iformatio (optioal), ad accout iformatio. Figure 2-5 through Figure 2-7 show aotated versios of the ewuser.jsp template. Although there are three figures, together these scree shots form the sigle ewuser.jsp template. The dashed lies ad umbers i the diagram are ot part of the template; they are refereced i the explaatio that follows the scree shots. Figure 2-5 Aotated ewuser.jsp Template - Persoal Iformatio Registratio ad User Processig Package 2-19

42 2 Customer Registratio ad Logi Services The umbers i the followig list refer to the umbered regios i the figures: 1. The page header (top baer) is created from a import of the ierheader.jsp template. This is stadard across may of the JSP templates provided by WebLogic Commerce Server. The import call is: <%@ iclude file="/commerce/icludes/ierheader.jsp" %> 2. This regio provides form fields for customers to eter their persoal customer profile iformatio, icludig their ame, address, phoe umber(s), ad address. For the address, this regio utilizes the form fields defied i the icluded states.jsp ad coutries.jsp template files. Figure 2-6 Aotated ewuser.jsp Template - Shippig Address ad Paymet Iformatio (Optioal) 2-20 Registratio ad User Processig Package

43 JavaServer Pages (JSPs) 3. This regio provides form fields for customers to eter a shippig address. If the customer wishes to use the address they provided i the persoal iformatio sectio as their shippig address, the customer ca click the Same as Above checkbox istead of retypig the iformatio. Other tha the checkbox, this regio cosists almost etirely of the form fields defied i the icluded ewaddresstemplate.jsp template file. 4. If the customer would like to provide their paymet iformatio, regio 4 allows the customer to do so. This regio provides form fields for the type of credit card, the credit card holder s ame, the credit card umber, the credit card expiratio date, ad a address associated with the credit card. The iformatio requested i this regio is optioal, ad cosists etirely of the form fields defied i the icluded ewcctemplate.jsp template file. Figure 2-7 Aotated ewuser.jsp Template - Accout Iformatio 5. This regio provides the customer with the opportuity to specify their userame ad password for use o your e-busiess site. If the customer decides to submit this form data, the customer s profile will be saved ad the logi.jsp template will be reloaded to allow the customer to logi. Note: The maximum umber of characters allowed for userames ad passwords is set to 50, but there are o other restrictios. If you wat to impose other restrictios (such as required character types, disallowed character types, or legth requiremets), you must set up your ow field validator. 6. The ewuser.jsp template s cotet i regio 6 cotais the icluded ierfooter.jsp template. The iclude call i ewuser.jsp is: <%@ iclude file="/commerce/icludes/ierfooter.jsp" %> Registratio ad User Processig Package 2-21

44 2 Customer Registratio ad Logi Services ierfooter.jsp cosists of the horizotal footer at the bottom of the page, plus the right-side vertical colum that describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. I the ierfooter.jsp file, the right-side vertical colum is a iclude file: <%@ iclude file="/commerce/icludes/rightside.jsp" %> Locatio i the WebLogic Commerce Server Directory Structure You ca fid the ewuser.jsp template file at the followig locatio, where WL_COMMERCE_HOME is the directory i which you istalled WebLogic Commerce Server: %WL_COMMERCE_HOME%\server\webapps\wlcs\commerce\registratio\ ewuser.jsp (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/commerce/registratio/ ewuser.jsp (UNIX) Tag Library Imports The ewuser.jsp template makes use of the Webflow JSP tags. Therefore, the template icludes the followig JSP tag libraries: <%@ taglib uri= weblogic.tld prefix= webflow %> Note: For more iformatio about the Webflow JSP tags, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. These files reside i the followig directory for the WebLogic Commerce Server Web applicatio: %WL_COMMERCE_HOME%\server\webapps\wlcs\WEB-INF (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/WEB-INF (UNIX) Java Package Imports The ewuser.jsp template uses Java classes i the followig packages ad therefore icludes these import statemets: <%@ page import= javax.servlet.* %> <%@ page import= javax.servlet.http.* %> <%@ page import= com.beasys.commerce.webflow.tags.webflowtagcostats %> 2-22 Registratio ad User Processig Package

45 JavaServer Pages (JSPs) page import= com.beasys.commerce.webflow.httprequestcostats %> page import= com.beasys.commerce.foudatio.pipelie.* %> page import= com.beasys.commerce.webflow.* %> Locatio i Default Webflow The page prior to ewuser.jsp is the customer logi page (logi.jsp). If o errors are foud after a customer eters their iitial profile iformatio, customers are retured to the customer logi page (logi.jsp) where they ca use their accout iformatio to log i. If errors are foud, the ewuser.jsp is reloaded with a appropriate message ext to the erroeous form fields. Note: For more iformatio about the default Webflow, see Overview of the Registratio ad User Processig Package o page 1-1. Icluded JSP Templates The followig JSP templates are icluded i the ewuser.jsp template: ierheader.jsp, which creates the top baer. states.jsp, which cotais a list of states that are displayed whe the customer is prompted to eter a address. coutries.jsp, which cotais a list of coutries that are displayed whe the customer is prompted to eter a address. ierfooter.jsp, which creates a horizotal footer at the bottom of the page, ad also icludes the rightside.jsp template. rightside.jsp describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. About the Icluded ewaddresstemplate.jsp Template The ewaddresstemplate.jsp template (icluded i most JSP templates that prompt customers for a shippig address) provides a stadardized format for both the form field presetatio ad error hadlig. The form fields are orgaized i a table, ad upo form submissio, the iput processors associated with the ewaddresstemplate.jsp template will validate the form to esure that all required fields cotai values. If errors are detected, the ewaddresstemplate.jsp template Registratio ad User Processig Package 2-23

46 2 Customer Registratio ad Logi Services will be redisplayed, with a error message at the top ad the offedig field labels show i red (as opposed to the origial black) fot. Further, the iformatio your customer etered correctly will still be displayed i the form. The behavior described above is accomplished o the ewaddresstemplate.jsp template usig the getvalidatedvalue JSP tag, as show i Listig 2-3. Listig 2-3 Use of the getvalidatedvalue JSP Tag o ewaddresstemplate.jsp <table> <tr> <!-- use the webflow:getvalidatedvalue to retrieve a value from the HttpRequest. This value was placed there by the CustomerProfileIP iput processor --> <td> <webflow:getvalidatedvalue fieldname="<%=customer_shipping_address1%>" fieldvalue="customershippigaddress1" fieldstatus="status" validcolor="black" ivalidcolor="red" uspecifiedcolor="black" fieldcolor="fotcolor" /> <div class="tabletext"> <fot color=<%=fotcolor%>>address</fot> </div> </td> <td> <iput type="text" ame="<%=customer_shipping_address1%>" value="<%=customershippigaddress1%>" size="30" maxlegth="30"> </td> </tr> </table> Notes: For more iformatio about the getvalidatedvalue JSP tag, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. Because the ewaddresstemplate.jsp template collects address iformatio, this template also icludes states.jsp ad coutries.jsp where appropriate Registratio ad User Processig Package

47 JavaServer Pages (JSPs) About the Icluded ewcctemplate.jsp Template The ewcctemplate.jsp template (icluded i all JSP templates that prompt customers for credit card/paymet iformatio) provides a stadardized format for both the form presetatio ad error hadlig. The form fields are orgaized i a table, ad upo form submissio, the iput processors associated with the ewcctemplate.jsp template will validate the form to esure that all required fields cotai values. If errors are detected, the ewcctemplate.jsp template will be redisplayed, with a error message at the top ad the offedig field labels show i red (as opposed to the origial black) fot. Further, the iformatio your customer etered correctly will still be displayed i the form. The behavior described above is accomplished o the ewcctemplate.jsp template usig the getvalidatedvalue JSP tag, as show i Listig 2-4. Listig 2-4 Use of the getvalidatedvalue JSP Tag o ewcctemplate.jsp <table> <tr> <!-- use the webflow:getvalidatedvalue to retrieve a value from the HttpRequest. This value was placed there by the CustomerProfileIP iput processor --> <td> <webflow:getvalidatedvalue fieldname="<%=customer_creditcard_holder%>" fieldvalue="customercreditcardholder" fieldstatus="status" validcolor="black" ivalidcolor="red" uspecifiedcolor="black" fieldcolor="fotcolor" /> <div class="tabletext"> <fot color=<%=fotcolor%>>name o card</fot> </div> </td> <td> <iput type="text" ame="<%=customer_creditcard_holder%>" value="<%=customercreditcardholder%>" size="30"> </td> </tr> </table> Registratio ad User Processig Package 2-25

48 2 Customer Registratio ad Logi Services Notes: For more iformatio about the getvalidatedvalue JSP tag, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. Because the ewcctemplate.jsp template collects address iformatio, this template also icludes states.jsp ad coutries.jsp where appropriate. Evets The ewuser.jsp template presets a customer with two buttos, each of which is cosidered a evet. These evets trigger a particular respose i the default Webflow that allows customers to cotiue. While this respose ca be to load aother JSP, it is usually the case that a iput processor or Pipelie is ivoked first. Table 2-6 provides iformatio about these evets ad the busiess logic they ivoke. Table 2-6 ewuser.jsp Evets Evet butto(cacel) butto(save) Webflow Respose(s) GetCategoryIP CustomerProfileIP CustomerProfile Table 2-7 briefly describes each of the Pipelies from Table 2-6, as they are defied i the pipelie.properties file. For more iformatio about idividual Pipelie compoets, see Pipelie Compoets o page Table 2-7 New User Profile Pipelies Pipelie CustomerProfile Descriptio Cotais EcryptCreditCardPC ad RegisterUserPC, ad is trasactioal. Dyamic Data Display No dyamic data is preseted o the ewuser.jsp template Registratio ad User Processig Package

49 JavaServer Pages (JSPs) Form Field Specificatio The primary purpose of the ewuser.jsp template is to allow customers to eter their profile iformatio usig various HTML form fields. It is also used to pass eeded iformatio to the Webflow. The form fields used i the ewuser.jsp template, ad a descriptio for each of these form fields are listed i Table 2-8. Table 2-8 ewuser.jsp Form Fields Parameter Name Type Descriptio evet Hidde Idicates which evet has bee triggered. It is used by the Webflow to determie what happes ext. origi Hidde The ame of the curret page (ewuser.jsp), used by the Webflow. CUSTOMER_FIRST_NAME CUSTOMER_MIDDLE_NAME CUSTOMER_LAST_NAME CUSTOMER_ADDRESS1 CUSTOMER_ADDRESS2 CUSTOMER_CITY CUSTOMER_STATE CUSTOMER_ZIPCODE Textbox Textbox Textbox Textbox Textbox Textbox Listbox Textbox The customer s first ame. The customer s middle iitial. The customer s last ame. The first lie i the customer s street address. The secod lie i the customer s street address. The city i the customer s address. The state i the customer s address. The zip code i the customer s address. Registratio ad User Processig Package 2-27

50 2 Customer Registratio ad Logi Services Table 2-8 ewuser.jsp Form Fields Parameter Name Type Descriptio CUSTOMER_COUNTRY CUSTOMER_HOME_PHONE CUSTOMER_BUSINESS_PHONE CUSTOMER_ SAME_AS_ABOVE CUSTOMER_SHIPPING_ADDRESS1 CUSTOMER_SHIPPING_ADDRESS2 CUSTOMER_SHIPPING_CITY CUSTOMER_SHIPPING_STATE CUSTOMER_SHIPPING_ZIPCODE CUSTOMER_SHIPPING_COUNTRY CUSTOMER_CREDITCARD_TYPE CUSTOMER_CREDITCARD_HOLDER CUSTOMER_CREDITCARD_NUMBER Listbox Textbox Textbox Textbox Checkbox Textbox Textbox Textbox Listbox Textbox Listbox Listbox Textbox Textbox The coutry i the customer s address. The customer s home phoe umber. The customer s busiess phoe umber. The customer s address. Idicates that the customer s shippig address is the same as the cotact address. The first lie i the customer s shippig address. The secod lie i the customer s shippig address. The city i the customer s shippig address. The state i the customer s shippig address. The zip/postal code i the customer s shippig address. The coutry i the customer s shippig address. The type of the customer s credit card. The ame o the credit card. The umber of the customer s credit card Registratio ad User Processig Package

51 JavaServer Pages (JSPs) Table 2-8 ewuser.jsp Form Fields Parameter Name Type Descriptio CUSTOMER_CREDITCARD_MONTH CUSTOMER_CREDITCARD_YEAR CUSTOMER_CREDITCARD_ADDRESS1 CUSTOMER_CREDITCARD_ADDRESS2 CUSTOMER_CREDITCARD_CITY CUSTOMER_CREDITCARD_STATE CUSTOMER_CREDITCARD_ZIPCODE CUSTOMER_CREDITCARD_COUNTRY USER_NAME PASSWORD CONFIRM_PASSWORD Listbox Listbox Textbox Textbox Textbox Listbox Textbox Listbox Textbox Password Password The moth of the customer s credit card expiratio date. The year of the customer s credit card expiratio date. The first lie i the customer s billig address. The secod lie i the customer s billig address. The city i the customer s billig address. The state i the customer s billig address. The zip/postal code i the customer s billig address. The coutry i the customer s billig address. A idetity chose by the customer for logi. A password chose by the customer for logi. Cofirmatio of the password chose by the customer for logi. Note: Parameters that are literals i the JSP code are show i quotes, while o-literals will require scriptlet sytax (such as <%= USER_NAME %>) for use i the JSP. Registratio ad User Processig Package 2-29

52 2 Customer Registratio ad Logi Services Iput Processors This sectio provides a brief descriptio of each iput processor associated with the Customer Logi ad Registratio Services JSP template(s). Note: For more iformatio about the GetTopCategoriesIP iput processor, see BEA WebLogic Commerce Server Product Catalog Maagemet. CustomerProfileIP Class Name Descriptio Required HTTPServletRequest Parameters (Persoal Iformatio) com.beasys.commerce.ebusiess.customer.webflow. CustomerProfileIP Processes the iput of ewuser.jsp ad allows the customer to store their profile. Creates ad places a CustomerValue object ito the Pipelie sessio. CUSTOMER_FIRST_NAME CUSTOMER_MIDDLE_NAME CUSTOMER_LAST_NAME CUSTOMER_ADDRESS1 CUSTOMER_ADDRESS2 CUSTOMER_CITY CUSTOMER_STATE CUSTOMER_ZIPCODE CUSTOMER_COUNTRY CUSTOMER_HOME_PHONE CUSTOMER_BUSINESS_PHONE CUSTOMER_ 2-30 Registratio ad User Processig Package

53 Iput Processors Required HTTPServletRequest Parameters (Shippig Iformatio) HTTPServletRequest Parameters (Paymet Iformatio) Required HTTPServletRequest Parameters (Accout Iformatio) Required Pipelie Sessio Attributes Updated Pipelie Sesio Attributes Removed Pipelie Sessio Attributes Validatio SAME_AS_ABOVE CUSTOMER_SHIPPING_ADDRESS1 CUSTOMER_SHIPPING_ADDRESS2 CUSTOMER_SHIPPING_CITY CUSTOMER_SHIPPING_STATE CUSTOMER_SHIPPING_ZIPCODE CUSTOMER_SHIPPING_COUNTRY DEFAULT_SHIPPING_ADDRESS CUSTOMER_CREDITCARD_TYPE CUSTOMER_CREDITCARD_HOLDER CUSTOMER_CREDITCARD_NUMBER CUSTOMER_CREDITCARD_MONTH CUSTOMER_CREDITCARD_YEAR CUSTOMER_CREDITCARD_ADDRESS1 CUSTOMER_CREDITCARD_ADDRESS2 CUSTOMER_CREDITCARD_CITY CUSTOMER_CREDITCARD_STATE CUSTOMER_CREDITCARD_ZIPCODE CUSTOMER_CREDITCARD_COUNTRY USER_NAME PASSWORD CONFIRM_PASSWORD Noe PipelieSessioCostats.CUSTOMER PipelieSessioCostats.PASSWORD PipelieSessioCostats.CREDIT_CARD_KEY (oly if customer provides a credit card update). Noe Checks that the required fields cotai values ad checks that the credit card umber is ot less tha 16 digits (15 digits for AMEX type). Also checks that the password ad cofirm password fields cotai matchig values. Registratio ad User Processig Package 2-31

54 2 Customer Registratio ad Logi Services Exceptios IvalidIputExceptio, throw whe required fields are empty or credit card umber is less tha 16 digits (15 digits for AMEX type) Registratio ad User Processig Package

55 Pipelie Compoets Pipelie Compoets This sectio provides a brief descriptio of each Pipelie compoet associated with the Customer Logi ad Registratio Services JSP template(s). Note: Some Pipelie compoets exted other, base Pipelie compoets. For more iformatio o the base classes, see the Javadoc. RegisterUserPC Class Name Descriptio Required Pipelie Sessio Attributes Updated Pipelie Sessio Attributes Removed Pipelie Sessio Attributes Type JNDI Name Exceptios com.beasys.commerce.ebusiess.customer.pipelie. RegisterUserPC Retrieves the CustomerValue object ad password from the Pipelie sessio, ad creates a CUSTOMER attribute. PipelieSessioCostats.CUSTOMER PipelieSessioCostats.PASSWORD Noe PipelieSessioCostats.PASSWORD Java class Noe PipelieFatalExceptio, throw whe the Pipelie compoet caot create the user. Registratio ad User Processig Package 2-33

56 2 Customer Registratio ad Logi Services 2-34 Registratio ad User Processig Package

57 CHAPTER 3 Customer Profile Services Customers who have registered with your e-commerce site may, from time to time, chage the iformatio stored i their profile. For example, customers may wat to sed a shipmet to a differet address, or use a differet credit card. To help you meet your customers eeds, the Registratio ad User Processig Package provides you with a implemetatio of these Customer Profile Services. This topic describes the pages that allow registered customers to modify various aspects of their customer profile. This topic icludes the followig sectios: JavaServer Pages (JSPs) l viewprofile.jsp Template l editprofile.jsp Template l profileewaddress.jsp Template l profileeditaddress.jsp Template l profileewcc.jsp Template l profileeditcc.jsp Template l chagepassword.jsp Template Iput Processors l DeleteCreditCardIP l DeleteShippigAddressIP l UpdateAccoutIfoIP Registratio ad User Processig Package 3-1

58 3 Customer Profile Services l l l UpdateBasicIfoIP UpdatePaymetIfoIP UpdateShippigIfoIP Pipelie Compoets l UpdateBasicIfoPC l UpdatePaymetIfoPC l UpdateShippigIfoPC l UpdatePasswordPC JavaServer Pages (JSPs) The Registratio ad User Processig package cotais a umber of JavaServer Pages (JSPs) that allow customers to view or update their stored profile. Remember, you ca always use these templates for your Web site, or you ca adapt them to meet your specific eeds. This sectio describes each of these pages i detail. Note: For a descriptio of the complete set of JSPs used i the WebLogic Commerce Server Web applicatio ad a listig of their locatios i the directory structure, see the Summary of JSP Templates documetatio. viewprofile.jsp Template The viewprofile.jsp template (show i Figure 3-1) allows a registered customer to view their existig profile iformatio. It displays the existig iformatio i four categories: persoal iformatio, shippig addresses, credit cards, ad userame ad password. There are optios i each category for updatig, deletig, or addig iformatio. 3-2 Registratio ad User Processig Package

59 JavaServer Pages (JSPs) Sample Browser View Figure 3-1 shows a aotated versio of the viewprofile.jsp template. The dashed lies ad umbers i the diagram are ot part of the template; they are refereced i the explaatio that follows the scree shot. Figure 3-1 Aotated viewprofile.jsp Template The umbers i the followig list refer to the umbered regios i the figure: 1. The page header (top baer) is created from a import of the ierheader.jsp template. This is stadard across may of the JSP templates provided by WebLogic Commerce Server. The import call is: <%@ iclude file="/commerce/icludes/ierheader.jsp" %> Registratio ad User Processig Package 3-3

60 3 Customer Profile Services 2. Regio 2 displays the customer s existig persoal iformatio usig the WebLogic Server JSP tags ad the WebLogic Persoalizatio Server s User Maagemet JSP tags. It also provides customers with a butto that will allow customers to update their existig persoal iformatio (usig the editprofile.jsp template). 3. This regio displays ay shippig addresses the customer may have previously stored as part of their customer profile. This is accomplished usig the WebLogic Server JSP tags ad the WebLogic Persoalizatio Server s User Maagemet JSP tags. I this regio, your customer ca choose from buttos that allow them to delete a address, eter a ew shippig address (usig the profileewaddress.jsp tempate), or update a existig address (usig the profileeditaddress.jsp template). 4. If ay exists, regio 4 displays the customer s existig credit card (paymet) iformatio usig a combiatio of the WebLogic Server JSP tags ad the WebLogic Persoalizatio Server s User Maagemet JSP tags. For each credit card show, your customer ca decide to delete the card, eter a ew credit card (usig the profileewcc.jsp template), or chage the iformatio associated with the card (usig the profileeditcc.jsp template). 5. This regio displays the customer s curret userame, ad provides customers with a butto that will allow them to modify their password (usig the chagepassword.jsp template). 6. The viewprofile.jsp template s cotet i regio 6 cotais the icluded ierfooter.jsp template. The iclude call i viewprofile.jsp is: <%@ iclude file="/commerce/icludes/ierfooter.jsp" %> ierfooter.jsp cosists of the horizotal footer at the bottom of the page, plus the right-side vertical colum that describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. I the ierfooter.jsp file, the right-side vertical colum is a iclude file: <%@ iclude file="/commerce/icludes/rightside.jsp" %> Locatio i the WebLogic Commerce Server Directory Structure You ca fid the viewprofile.jsp template file at the followig locatio, where WL_COMMERCE_HOME is the directory i which you istalled WebLogic Commerce Server: 3-4 Registratio ad User Processig Package

61 JavaServer Pages (JSPs) %WL_COMMERCE_HOME%\server\webapps\wlcs\commerce\user\ viewprofile.jsp (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/commerce/user/ viewprofile.jsp (UNIX) Tag Library Imports The viewprofile.jsp template uses existig WebLogic Server JSP tags ad WebLogic Persoalizatio Server s User Maagemet JSP tags. Therefore, the template icludes the followig JSP tag libraries: <%@ taglib uri= weblogic.tld prefix= wl %> <%@ taglib uri= um.tld prefix= um %> Note: For more iformatio o the WebLogic Server JSP tags or the WebLogic Persoalizatio Server s User Maagemet JSP tags, see JSP Tag Referece i the BEA WebLogic Persoalizatio Server documetatio. These files reside i the followig directory for the WebLogic Commerce Server Web applicatio: %WL_COMMERCE_HOME%\server\webapps\wlcs\WEB-INF (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/WEB-INF (UNIX) Java Package Imports The viewprofile.jsp template uses Java classes i the followig packages ad therefore icludes these import statemets: <%@ page import="javax.servlet.*" %> <%@ page import="javax.servlet.http.*" %> <%@ page import="com.beasys.commerce.webflow.httprequestcostats" %> <%@ page import="com.beasys.commerce.webflow.pipeliesessiocostats" %> <%@ page import="com.beasys.commerce.webflow.tags.webflowtagcostats" %> <%@ page import="com.beasys.commerce.axiom.cotact.*" %> <%@ page import="com.beasys.commerce.ebusiess.customer.*" %> <%@ page import="com.beasys.commerce.webflow.*" %> Registratio ad User Processig Package 3-5

62 3 Customer Profile Services Locatio i Default Webflow If the customer is ot logged i, the page prior to the viewprofile.jsp template is the customer logi page (logi.jsp). If the customer is already logged i, the page prior to the viewprofile.jsp template is ay page from which the customer clicks the View Profile butto. Based o what the customer decides to do after viewig their profile, the ext page could be ay of the followig: editprofile.jsp, which allows customers to edit their persoal iformatio, icludig their ame, cotact address, ad phoe umbers, profileewaddress.jsp, which allows customers to add a ew shippig address, profileeditaddress.jsp, which allows customers to edit a shippig address, profileewcc.jsp, which allows customers to add a ew credit card to the profile, profileeditcc.jsp, which allows customers to edit iformatio about a existig credit card, or chagepassword.jsp, which allows customers to chage their accout password. Each of these pages are described i subsequet sectios of this documet. Note: For more iformatio about the default Webflow, see Overview of the Registratio ad User Processig Package o page 1-1. Icluded JSP Templates The followig JSP templates are icluded i the viewprofile.jsp template: ierheader.jsp, which creates the top baer. ierfooter.jsp, which creates a horizotal footer at the bottom of the page, ad also icludes the rightside.jsp template. rightside.jsp describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. 3-6 Registratio ad User Processig Package

63 JavaServer Pages (JSPs) Evets The viewprofile.jsp template presets a customer with several buttos, each of which is cosidered a evet. These evets trigger a particular respose i the default Webflow that allow customers to cotiue. While this respose ca be to load aother JSP, it is usually the case that a iput processor or Pipelie is ivoked first. Table 3-1 provides iformatio about these evets ad the busiess logic they ivoke. Table 3-1 viewprofile.jsp Evets Evet butto(updatebasicifo) butto(addnewshippigaddress) butto(updateshippigifo) butto(deleteshippigaddress) butto(addnewcreditcard) butto(updatepaymetifo) butto(deletepaymetifo) butto(chagepassword) Web Flow Respose(s) No busiess logic required. Loads editprofile.jsp. No busiess logic required. Loads profileewaddress.jsp. No busiess logic required. Loads profileeditaddress.jsp. DeleteShippigAddressIP DeleteShippigAddressFromProfile No busiess logic required. Loads profileewcc.jsp. No busiess logic required. Loads profileeditcc.jsp. DeleteCreditCardIP DeleteCreditCard No busiess logic required. Loads chagepassword.jsp. Table 3-2 briefly describes each of the Pipelies from Table 3-1, as they are defied i the pipelie.properties file. For more iformatio about idividual Pipelie compoets, see Pipelie Compoets o page Registratio ad User Processig Package 3-7

64 3 Customer Profile Services Table 3-2 View Profile Pipelies Pipelie DeleteShippigAddressFromProfile DeleteCreditCard Descriptio Cotais UpdateShippigIfoPC ad is trasactioal. Cotais UpdatePaymetIfoPC ad is trasactioal. Dyamic Data Display Oe purpose of the viewprofile.jsp template is to display the profile iformatio a customer had previously etered. This is accomplished o viewprofile.jsp usig a combiatio of WebLogic Server JSP tags, the WebLogic Persoalizatio Server s User Maagemet JSP tags, ad accessor methods/attributes. First, the getprofile JSP tag is used to set the customer profile (cotext) for which the customer iformatio should be retrieved, as show i Listig 3-1. Listig 3-1 Settig the Customer Cotext <um:getprofile profilekey="<%=request.getremoteuser()%>" profiletype="wlcs_customer" /> Note: For more iformatio o the WebLogic Persoalizatio Server s User Maagemet JSP tags, see JSP Tag Referece i the BEA WebLogic Persoalizatio Server documetatio. Next, the getproperty JSP tag is used to obtai the customer s cotact address, a collectio of the customer s shippig addresses, ad a collectio of the customer s credit cards, which are the iitialized with data from their correspodig objects. This is show i Listig 3-2. Listig 3-2 Obtaiig the Customer s Profile Iformatio <um:getproperty propertyname="cotactaddress" id="cotactaddressobject" /> 3-8 Registratio ad User Processig Package

65 JavaServer Pages (JSPs) <um:getproperty propertyname="shippigaddressmap" id="shippigaddressmapobject" /> <um:getproperty propertyname="creditcardsmap" id="creditcardsmapobject" /> Address cotactaddress = (Address) cotactaddressobject; Map shippigaddressmap = (Map) shippigaddressmapobject; Map creditcardsmap = (Map) creditcardsmapobject; The data stored withi these objects ca ow be accessed by callig accessor methods/attributes withi Java scriptlets. Table 3-3 provides more detailed iformatio about the methods/attributes for both the cotact ad shippig addresses. Table 3-4 provides iformatio about the methods/attributes for the customer s credit cards. Table 3-3 cotactaddress/shippigaddress Accessor Methods/Attributes Method/Attribute getstreet1() getstreet2() getcity() getcouty() getstate() getpostalcode() getcoutry() Descriptio The first lie i the customer s cotact or shippig street address. The secod lie i the customer s cotact or shippig street address. The city i the customer s cotact or shippig address. The couty i the customer s cotact or shippig address. The state i the customer s cotact or shippig address. The zip/postal code i the customer s cotact or shippig address. The coutry i the customer s cotact or shippig address. Registratio ad User Processig Package 3-9

66 3 Customer Profile Services Table 3-4 creditcard Accessor Methods/Attributes Method/Attribute Descriptio creditcard The credit card ame, cosistig of the credit card type ad 4 digits (for example, VISA-4111). Listig 3-3 illustrates how these accessor methods/attributes are used withi Java scriptlets Registratio ad User Processig Package

67 JavaServer Pages (JSPs) Listig 3-3 Usig Accessor Methods/Attributes Withi viewprofile.jsp Java Scriptlets <table>... <tr> <td><div class="tabletext"><b>address</b></div></td> <td><div class="tabletext"> <%=cotactaddress.getstreet1()%><br> <%=cotactaddress.getstreet2()%><br> <%=cotactaddress.getcity()%><br> <%=cotactaddress.getstate()%> &bsp; <%=cotactaddress.getpostalcode()%><br> <%=cotactaddress.getcoutry()%></div> </td> </tr>... <wl:repeat set="<%=((map)creditcardsmapobject).keyset().iterator()%>" id="creditcard" type="strig" cout="100000"> <tr> <td width="55%"> <div class="tabletext"><b><%=creditcard%></b></div> <td> </tr> </wl:repeat> </table> Notes: For more iformatio o the WebLogic Persoalizatio Server s User Maagemet JSP tags, see JSP Tag Referece i the BEA WebLogic Persoalizatio Server documetatio. The getpropertyasstrig JSP tag is used to directly obtai the customer s first ad last ame, the customer s home ad busiess phoe umbers, ad the customer s address. Listig 3-4 illustrates how to use the getpropertyasstrig JSP tag to display ths customer s ame i the welcome message at the top of the viewprofile.jsp template. Registratio ad User Processig Package 3-11

68 3 Customer Profile Services Listig 3-4 Obtaiig the Customer s Name <p class="head1"> <um:getpropertyasstrig propertyname="firstname" /> <um:getpropertyasstrig propertyname="lastname" /> s Profile </p> Form Field Specificatio No form fields are used i the viewprofile.jsp template Registratio ad User Processig Package

69 JavaServer Pages (JSPs) editprofile.jsp Template Sample Browser View The editprofile.jsp template (show i Figure 3-2) allows a registered customer to update the persoal iformatio i their stored profile, which icludes their ame, address, home ad busiess phoe umbers, ad address. Figure 3-2 shows a aotated versio of the editprofile.jsp template. The dashed lies ad umbers i the diagram are ot part of the template; they are refereced i the explaatio that follows the scree shot. Registratio ad User Processig Package 3-13

70 3 Customer Profile Services Figure 3-2 Aotated editprofile.jsp Template The umbers i the followig list refer to the umbered regios i the figure: 1. The page header (top baer) is created from a import of the ierheader.jsp template. This is stadard across may of the JSP templates provided by WebLogic Commerce Server. The import call is: <%@ iclude file="/commerce/icludes/ierheader.jsp" %> 3-14 Registratio ad User Processig Package

71 JavaServer Pages (JSPs) 2. Regio 2 provides customers with a series of form fields that allow customers to chage their persoal iformatio. Where available, existig data for the customer is dyamically displayed i the form fields usig WebLogic Server ad the WebLogic Persoalizatio Server s User Maagemet JSP tags. For the address, this regio utilizes the form fields defied i the icluded states.jsp ad coutries.jsp template files. The import calls are: <%@ iclude file="/commerce/icludes/states.jsp" %> <%@ iclude file="/commerce/icludes/coutries.jsp" %> 3. The editprofile.jsp template s cotet i regio 3 cotais the icluded ierfooter.jsp template. The iclude call i editprofile.jsp is: <%@ iclude file="/commerce/icludes/ierfooter.jsp" %> ierfooter.jsp cosists of the horizotal footer at the bottom of the page, plus the right-side vertical colum that describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. I the ierfooter.jsp file, the right-side vertical colum is a iclude file: <%@ iclude file="/commerce/icludes/rightside.jsp" %> Locatio i the WebLogic Commerce Server Directory Structure You ca fid the editprofile.jsp template file at the followig locatio, where WL_COMMERCE_HOME is the directory i which you istalled WebLogic Commerce Server: %WL_COMMERCE_HOME%\server\webapps\wlcs\commerce\user\ editprofile.jsp (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/commerce/user/ editprofile.jsp (UNIX) Tag Library Imports The editprofile.jsp template uses existig WebLogic Server JSP tags ad the WebLogic Persoalizatio Server s User Maagemet JSP tags. Therefore, the template icludes the followig JSP tag libraries: <%@ taglib uri= weblogic.tld prefix= wl %> <%@ taglib uri= um.tld prefix= um %> Registratio ad User Processig Package 3-15

72 3 Customer Profile Services Note: For more iformatio o the WebLogic Server JSP tags or the WebLogic Persoalizatio Server s User Maagemet JSP tags, see JSP Tag Referece i the BEA WebLogic Persoalizatio Server documetatio. These files reside i the followig directory for the WebLogic Commerce Server Web applicatio: %WL_COMMERCE_HOME%\server\webapps\wlcs\WEB-INF (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/WEB-INF (UNIX) Java Package Imports The editprofile.jsp template uses Java classes i the followig packages ad therefore icludes these import statemets: <%@ page import="javax.servlet.*" %> <%@ page import="javax.servlet.http.*" %> <%@ page import="com.beasys.commerce.webflow.*" %> <%@ page import="com.beasys.commerce.webflow.tags.webflowtagcostats" %> <%@ page import="com.beasys.commerce.foudatio.pipelie.*" %> <%@ page import="com.beasys.commerce.axiom.cotact.*" %> <%@ page import="com.beasys.commerce.ebusiess.customer.*" %> Locatio i Default Webflow The page before editprofile.jsp is the page o which a customer ca view their curret profile (viewprofile.jsp). If there are o errors i the form submissio, the ext page i the default Webflow is viewprofile.jsp. If correctios do eed to be made, editprofile.jsp is reloaded with a appropriate error message. Note: For more iformatio about the default Webflow, see Overview of the Registratio ad User Processig Package o page 1-1. Icluded JSP Templates The followig JSP templates are icluded ito the editprofile.jsp template: ierheader.jsp, which creates the top baer. states.jsp, which cotais a list of states that are displayed whe the customer is prompted to eter a address Registratio ad User Processig Package

73 JavaServer Pages (JSPs) coutries.jsp, which cotais a list of coutries that are displayed whe the customer is prompted to eter a address. ierfooter.jsp, which creates a horizotal footer at the bottom of the page, ad also icludes the rightside.jsp template. rightside.jsp describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. Evets The editprofile.jsp template presets customers with two butto evets that trigger a particular respose i the default Webflow, thereby allowig customers to cotiue. While this respose ca be to load aother JSP, it is usually the case that a iput processor or Pipelie is ivoked first. Table 3-5 provides iformatio about these evets ad the busiess logic they ivoke. Table 3-5 editprofile.jsp Evets Evet butto(back) butto(save) Webflow Respose(s) No busiess logic required. Loads viewprofile.jsp. UpdateBasicIfoIP EditBasicIfo Table 3-6 briefly describes each of the Pipelies from Table 3-5, as they are defied i the pipelie.properties file. For more iformatio about idividual Pipelie compoets, see Pipelie Compoets o page Table 3-6 Edit Profile Pipelies Pipelie EditBasicIfo Descriptio Cotais UpdateBasicIfoPC ad is trasactioal. Registratio ad User Processig Package 3-17

74 3 Customer Profile Services Dyamic Data Display Oe purpose of the editprofile.jsp template is to display the profile iformatio a customer had previously etered. This is accomplished o the editprofile.jsp template usig a combiatio of WebLogic Server JSP tags, the WebLogic Persoalizatio Server s User Maagemet JSP tags, ad accessor methods/attributes. First, the getprofile JSP tag is used to set the customer profile (cotext) for which the customer iformatio should be retrieved, as show i Listig 3-5. Listig 3-5 Settig the Customer Cotext <um:getprofile profilekey="<%=request.getremoteuser()%>" profiletype="wlcs_customer" /> Note: For more iformatio o the WebLogic Persoalizatio Server s User Maagemet JSP tags, see JSP Tag Referece i the BEA WebLogic Persoalizatio Server documetatio. Next, the getproperty JSP tag is used to obtai the customer s cotact address, which is the iitialized with data from the customer object, as show i Listig 3-6. Listig 3-6 Obtaiig the Customer s Cotact Address <um:getproperty propertyname="cotactaddress" id="cotactaddressobject" /> <% Address cotactaddress = (Address) cotactaddressobject; %> The data stored withi the cotactaddress object ca ow be accessed by callig accessor methods/attributes withi Java scriptlets. Table 3-7 provides more detailed iformatio about the methods/attributes for the cotact address Registratio ad User Processig Package

75 JavaServer Pages (JSPs) Table 3-7 cotactaddress Accessor Methods/Attributes Method/Attribute getstreet1() getstreet2() getcity() getcouty() getstate() getpostalcode() getcoutry() Descriptio The first lie i the customer s cotact street address. The secod lie i the customer s cotact street address. The city i the customer s cotact address. The couty i the customer s cotact address. The state i the customer s cotact address. The zip/postal code i the customer s cotact address. The coutry i the customer s cotact address. Note: The getpropertyasstrig JSP tag is used to directly obtai the customer s first ad last ame, the customer s home ad busiess phoe umbers, ad the customer s address. Listig 3-7 illustrates how to use the getpropertyasstrig JSP tag to obtai the customer s last ame. Listig 3-7 Obtaiig the Customer s Last Name <um:getpropertyasstrig propertyname="lastname" id="lastname" /> Listig 3-8 illustrates how these accessor methods/attributes are used withi Java scriptlets to display existig data withi the form fields. Registratio ad User Processig Package 3-19

76 3 Customer Profile Services Listig 3-8 Usig Accessor Methods/Attributes withi editprofile.jsp Java Scriptlets <table> <tr> <um:getpropertyasstrig propertyname="lastname" id="lastname" /> <td> <webflow:getvalidatedvalue fieldname="<%=customer_last_name%>" fielddefaultvalue="<%=(strig)lastname%>" fieldvalue="customerlastname" fieldstatus="status" validcolor="black" ivalidcolor="red" uspecifiedcolor="black" fieldcolor="fotcolor" /> <div class="tabletext"> <fot color=<%= fotcolor %>>Last ame </fot> </div> </td> <td> <iput type="text" ame="<%=customer_last_name%>" value="<%=customerlastname%>">* </td> </tr><tr> <td> <webflow:getvalidatedvalue fieldname="<%=customer_address1%>" fielddefaultvalue="<%=cotactaddress.getstreet1()%>" fieldvalue="customeraddress1" fieldstatus="status" validcolor="black" ivalidcolor="red" uspecifiedcolor="black" fieldcolor="fotcolor" /> <div class="tabletext"> <fot color=<%= fotcolor %>>Street address</fot> </div> </td> <td> <iput type="text" ame="<%=customer_address1%>" value="<%=customeraddress1%>">* </td> </tr> </table> 3-20 Registratio ad User Processig Package

77 JavaServer Pages (JSPs) Form Field Specificatio The primary purpose of the editprofile.jsp template is to allow customers to edit their profile iformatio usig various HTML form fields. It is also used to pass eeded iformatio to the Webflow. The form fields used i the editprofile.jsp template, ad a descriptio for each of these form fields are listed i Table 3-8. Table 3-8 editprofile.jsp Form Fields Parameter Name Type Descriptio evet Hidde Idicates which evet has bee triggered. It is used by the Webflow to determie what happes ext. origi Hidde The ame of the curret page (editprofile.jsp), used by the Webflow. CUSTOMER_FIRST_NAME CUSTOMER_MIDDLE_NAME CUSTOMER_LAST_NAME CUSTOMER_ADDRESS1 CUSTOMER_ADDRESS2 CUSTOMER_CITY CUSTOMER_STATE CUSTOMER_ZIPCODE Textbox Textbox Textbox Textbox Textbox Textbox Listbox Textbox The customer s first ame. The customer s middle iitial. The customer s last ame. The first lie i the customer s street address. The secod lie i the customer s street address. The city i the customer s address. The state i the customer s address. The zip code i the customer s address. Registratio ad User Processig Package 3-21

78 3 Customer Profile Services Table 3-8 editprofile.jsp Form Fields Parameter Name Type Descriptio CUSTOMER_COUNTRY CUSTOMER_HOME_PHONE CUSTOMER_BUSINESS_PHONE CUSTOMER_ Listbox Textbox Textbox Textbox The coutry i the customer s address. The customer s home phoe umber. The customer s busiess phoe umber. The customer s address. Note: Parameters that are literals i the JSP code are show i quotes, while o-literals will require scriptlet sytax (such as <%= CUSTOMER_ %>) for use i the JSP Registratio ad User Processig Package

79 JavaServer Pages (JSPs) profileewaddress.jsp Template Sample Browser View The profileewaddress.jsp template (show i Figure 3-3) allows a registered customer to add a ew shippig address to their stored profile. Figure 3-3 shows a aotated versio of the profileewaddress.jsp template. The dashed lies ad umbers i the diagram are ot part of the template; they are refereced i the explaatio that follows the scree shot. Figure 3-3 Aotated profileewaddress.jsp Template The umbers i the followig list refer to the umbered regios i the figure: 1. The page header (top baer) is created from a import of the ierheader.jsp template. This is stadard across may of the JSP templates provided by WebLogic Commerce Server. The import call is: Registratio ad User Processig Package 3-23

80 3 Customer Profile Services iclude file="/commerce/icludes/ierheader.jsp" %> 2. Regio 2 provides customers with a series of form fields that allow customers to add a shippig address. This regio utilizes the form fields defied i the icluded ewaddresstemplate.jsp template file, which itself icludes the states.jsp ad coutries.jsp template files. The import call i profileewaddress.jsp is: <%@ iclude file="/commerce/icludes/ewaddresstemplate.jsp %> 3. The profileewaddress.jsp template s cotet i regio 3 cotais the icluded ierfooter.jsp template. The iclude call i profileewaddress.jsp is: <%@ iclude file="/commerce/icludes/ierfooter.jsp" %> ierfooter.jsp cosists of the horizotal footer at the bottom of the page, plus the right-side vertical colum that describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. I the ierfooter.jsp file, the right-side vertical colum is a iclude file: <%@ iclude file="/commerce/icludes/rightside.jsp" %> Locatio i the WebLogic Commerce Server Directory Structure You ca fid the profileewaddress.jsp template file at the followig locatio, where WL_COMMERCE_HOME is the directory i which you istalled WebLogic Commerce Server: %WL_COMMERCE_HOME%\server\webapps\wlcs\commerce\user\ profileewaddress.jsp (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/commerce/user/ profileewaddress.jsp (UNIX) Tag Library Imports The profileewaddress.jsp template uses the Webflow ad Pipelie JSP tags. Therefore, the template icludes the followig JSP tag libraries: <%@ taglib uri= webflow.tld prefix= webflow %> <%@ taglib uri= pipelie.tld prefix= pipelie %> Note: For more iformatio about the Webflow ad Pipelie JSP tags, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet Registratio ad User Processig Package

81 JavaServer Pages (JSPs) These files reside i the followig directory for the WebLogic Commerce Server Web applicatio: %WL_COMMERCE_HOME%\server\webapps\wlcs\WEB-INF (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/WEB-INF (UNIX) Java Package Imports The profileewaddress.jsp template uses Java classes i the followig packages ad therefore icludes these import statemets: <%@ page import="javax.servlet.*" %> <%@ page import="javax.servlet.http.*" %> <%@ page import="com.beasys.commerce.webflow.*" %> <%@ page import="com.beasys.commerce.webflow.tags.webflowtagcostats" %> <%@ page import="com.beasys.commerce.foudatio.pipelie.*" %> <%@ page import="com.beasys.commerce.axiom.cotact.*" %> <%@ page import="com.beasys.commerce.ebusiess.customer.*" %> Locatio i Default Webflow The page before profileewaddress.jsp is the page o which a customer ca view their curret profile (viewprofile.jsp). If there are o errors i the form submissio, the ext page i the default Webflow is viewprofile.jsp. If correctios do eed to be made, profileewaddress.jsp is reloaded with a appropriate error message. Note: For more iformatio about the default Webflow, see Overview of the Registratio ad User Processig Package o page 1-1. Icluded JSP Templates The followig JSP templates are icluded i the profileewaddress.jsp template: ierheader.jsp, which creates the top baer. ierfooter.jsp, which creates a horizotal footer at the bottom of the page, ad also icludes the rightside.jsp template. rightside.jsp describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. Registratio ad User Processig Package 3-25

82 3 Customer Profile Services ewaddresstemplate.jsp, described i About the Icluded ewaddresstemplate.jsp Template o page Evets The profileewaddress.jsp template presets customers with two butto evets that trigger a particular respose i the default Webflow, thereby allowig customers to cotiue. While this respose ca be to load aother JSP, it is usually the case that a iput processor or Pipelie is ivoked first. Table 3-9 provides iformatio about these evets ad the busiess logic they ivoke. Table 3-9 profileewaddress.jsp Evets Evet butto(back) butto(save) Webflow Respose(s) No busiess logic required. Loads viewprofile.jsp. UpdateAddressIfoIP ProfileNewAddress Table 3-10 briefly describes each of the Pipelies from Table 3-9, as they are defied i the pipelie.properties file. For more iformatio about idividual Pipelie compoets, see Pipelie Compoets o page Table 3-10 New Profile Shippig Address Pipelies Pipelie ProfileNewAddress Descriptio Cotais UpdateShippigIfoPC ad is trasactioal. Dyamic Data Display No dyamic data is preseted o the profileewaddress.jsp template Registratio ad User Processig Package

83 JavaServer Pages (JSPs) Form Field Specificatio The primary purpose of the profileewaddress.jsp template is to allow customers to eter a ew shippig address usig various HTML form fields. It is also used to pass eeded iformatio to the Webflow. The form fields used i the profileewaddress.jsp template (most of which are actually imported from the ewaddresstemplate.jsp file), ad a descriptio for each of these form fields are show i Table Table 3-11 profileewaddress.jsp Form Fields Parameter Name Type Descriptio evet Hidde Idicates which evet has bee triggered. It is used by the Webflow to determie what happes ext. origi Hidde The ame of the curret page (profileewaddress.jsp), used by the Webflow. CUSTOMER_SHIPPING_ADDRESS1 CUSTOMER_SHIPPING_ADDRESS2 CUSTOMER_SHIPPING_CITY CUSTOMER_SHIPPING_STATE CUSTOMER_SHIPPING_ZIPCODE CUSTOMER_SHIPPING_COUNTRY Textbox Textbox Textbox Listbox Textbox Listbox The first lie i the customer s street address. The secod lie i the customer s street address. The city i the customer s address. The state i the customer s address. The zip code i the customer s address. The coutry i the customer s address. Registratio ad User Processig Package 3-27

84 3 Customer Profile Services Note: Parameters that are literals i the JSP code are show i quotes, while o-literals will require scriptlet sytax (such as <%= CUSTOMER_SHIPPING_COUNTRY %>) for use i the JSP Registratio ad User Processig Package

85 JavaServer Pages (JSPs) profileeditaddress.jsp Template Sample Browser View The profileeditaddress.jsp template (show i Figure 3-4) allows a registered customer to update the shippig address iformatio stored as part of their profile. Figure 3-4 shows a aotated versio of the profileeditaddress.jsp template. The dashed lies ad umbers i the diagram are ot part of the template; they are refereced i the explaatio that follows the scree shot. Figure 3-4 Aotated profileeditaddress.jsp Template The umbers i the followig list refer to the umbered regios i the figure: 1. The page header (top baer) is created from a import of the ierheader.jsp template. This is stadard across may of the JSP templates provided by WebLogic Commerce Server. The import call is: Registratio ad User Processig Package 3-29

86 3 Customer Profile Services iclude file="/commerce/icludes/ierheader.jsp" %> 2. Regio 2 provides customers with a series of form fields that allow customers to update a shippig address. This regio utilizes the form fields defied i the icluded editaddresstemplate.jsp template file, which itself icludes the states.jsp ad coutries.jsp template files. The import call i profileeditaddress.jsp is: <%@ iclude file="/commerce/icludes/editaddresstemplate.jsp %> 3. The profileeditaddress.jsp template s cotet i regio 3 cotais the icluded ierfooter.jsp template. The iclude call i profileeditaddress.jsp is: <%@ iclude file="/commerce/icludes/ierfooter.jsp" %> ierfooter.jsp cosists of the horizotal footer at the bottom of the page, plus the right-side vertical colum that describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. I the ierfooter.jsp file, the right-side vertical colum is a iclude file: <%@ iclude file="/commerce/icludes/rightside.jsp" %> Locatio i WebLogic Commerce Server Directory Structure You ca fid the profileeditaddress.jsp template file at the followig locatio, where WL_COMMERCE_HOME is the directory i which you istalled WebLogic Commerce Server: %WL_COMMERCE_HOME%\server\webapps\wlcs\commerce\user\ profileeditaddress.jsp (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/commerce/user/ profileeditaddress.jsp (UNIX) Tag Library Imports The profileeditaddress.jsp template uses the Webflow JSP tags ad WebLogic Persoalizatio Server s User Maagemet JSP tags. Therefore, the template icludes the followig JSP tag libraries: <%@ taglib uri= webflow.tld prefix= webflow %> <%@ taglib uri= um.tld prefix= um %> 3-30 Registratio ad User Processig Package

87 JavaServer Pages (JSPs) Note: For more iformatio o the WebLogic Persoalizatio Server s User Maagemet JSP tags, see JSP Tag Referece i the BEA WebLogic Persoalizatio Server documetatio. For more iformatio about the Webflow JSP tags, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. These files reside i the followig directory for the WebLogic Commerce Server Web applicatio: %WL_COMMERCE_HOME%\server\webapps\wlcs\WEB-INF (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/WEB-INF (UNIX) Java Package Imports The profileeditaddress.jsp template uses Java classes i the followig packages ad therefore icludes these import statemets: <%@ page import="javax.servlet.*" %> <%@ page import="javax.servlet.http.*" %> <%@ page import="com.beasys.commerce.webflow.*" %> <%@ page import="com.beasys.commerce.webflow.tags.webflowtagcostats" %> <%@ page import="com.beasys.commerce.foudatio.pipelie.*" %> <%@ page import="com.beasys.commerce.axiom.cotact.*" %> <%@ page import="com.beasys.commerce.ebusiess.customer.*" %> Locatio i Default Webflow The page before the profileeditaddress.jsp template is the page that allows a customer to view their curret profile (viewprofile.jsp). If there are o errors i the form submissio, the ext page i the default Webflow is viewprofile.jsp. If correctios do eed to be made, the profileeditaddress.jsp template is reloaded with a appropriate error message. Note: For more iformatio about the default Webflow, see Overview of the Registratio ad User Processig Package o page 1-1. Icluded JSP Templates The followig JSP templates are icluded i the profileeditaddress.jsp template: ierheader.jsp, which creates the top baer. Registratio ad User Processig Package 3-31

88 3 Customer Profile Services ierfooter.jsp, which creates a horizotal footer at the bottom of the page, ad also icludes the rightside.jsp template. rightside.jsp describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. editaddresstemplate.jsp, described below. About the Icluded editaddresstemplate.jsp Template The editaddresstemplate.jsp template (icluded i all JSP templates that allow customers to edit a shippig address) provides a stadardized format for both the form field presetatio ad error hadlig. The form fields are orgaized i a table, ad upo form submissio, the iput processors associated with the editaddresstemplate.jsp template will validate the form to esure that all required fields cotai values. If errors are detected, the editaddresstemplate.jsp template will be redisplayed, with a error message at the top ad the offedig field labels show i red (as opposed to the origial black) fot. Further, the iformatio your customer etered correctly will still be displayed i the form. Sice the editaddresstemplate.jsp template allows customers to edit a existig shippig address, the form fields o the page are also prefilled with iformatio previously etered by the customer. The behavior described above is accomplished o the editaddresstemplate.jsp template usig the getvalidatedvalue JSP tag ad the accessor methods/attributes for defaultshippigaddress, as show i Listig 3-9. Listig 3-9 Use of the getvalidatedvalue JSP Tag ad Accessor Methods/Attributes o editaddresstemplate.jsp <table> <tr> <!-- Use the webflow:getvalidatedvalue to retrieve the default value for the shippig address from the HttpRequest. This value was placed there by the CustomerProfileIP iput processor. Use the defaultshippigaddress to display the first lie usig its getstreet1() accessor method. --> <tr> <td> <webflow:getvalidatedvalue fieldname="<%=customer_shipping_address1%>" fielddefaultvalue="<%=defaultshippigaddress.getstreet1()%>" 3-32 Registratio ad User Processig Package

89 JavaServer Pages (JSPs) </td> fieldvalue="customershippigaddress1" fieldstatus="status" validcolor="black" ivalidcolor="red" uspecifiedcolor="black" fieldcolor="fotcolor" /> <div class="tabletext"> <fot color=<%= fotcolor %>>Street address</fot> </div> <td> <iput type="text" ame="<%=customer_shipping_address1%>" value="<%=customershippigaddress1%>" maxlegth="30">* </td> </tr> </table> Evets Notes: For more iformatio about the getvalidatedvalue JSP tag, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. For a list of the available accessor methods/attributes for defaultshippigaddress, see Table Because the editaddresstemplate.jsp template collects address iformatio, this template also icludes states.jsp ad coutries.jsp where appropriate. The profileeditaddress.jsp template presets customers with two butto evets that trigger a particular respose i the default Webflow, thereby allowig customers to cotiue. While this respose ca be to load aother JSP, it is usually the case that a iput processor or Pipelie is ivoked first. Table 3-12 provides iformatio about these evets ad the busiess logic they ivoke. Table 3-12 profileeditaddress.jsp Evets Evet butto(back) Webflow Respose(s) No busiess logic required. Loads viewprofile.jsp. Registratio ad User Processig Package 3-33

90 3 Customer Profile Services Table 3-12 profileeditaddress.jsp Evets Evet butto(save) Webflow Respose(s) UpdateShippigIfoIP ProfileEditAddress Table 3-13 briefly describes each of the Pipelies from Table 3-12, as they are defied i the pipelie.properties file. For more iformatio about idividual Pipelie compoets, see Pipelie Compoets o page Table 3-13 Edit Profile Shippig Address Pipelies Pipelie ProfileEditAddress Descriptio Cotais UpdateShippigIfoPC ad is trasactioal. Dyamic Data Display Oe purpose of the profileeditaddress.jsp template is to prepare the address iformatio a customer had previously etered, so the editaddresstemplate.jsp template ca display this iformatio i the address form fields. This is accomplished o the profileeditaddress.jsp template usig a combiatio of Webflow JSP tags, the WebLogic Persoalizatio Server s User Maagemet JSP tags, ad accessor methods/attributes. First, the getprofile JSP tag is used to set the customer profile (cotext) for which the customer iformatio should be retrieved, as show i Listig Listig 3-10 Settig the Customer Cotext <um:getprofile profilekey="<%=request.getremoteuser()%>" profiletype="wlcs_customer" /> Note: For more iformatio o the WebLogic Persoalizatio Server s User Maagemet JSP tags, see JSP Tag Referece i the BEA WebLogic Persoalizatio Server documetatio Registratio ad User Processig Package

91 JavaServer Pages (JSPs) Next, the getproperty JSP tag is used to obtai a list of the customer s shippig addresses, which are the iitialized with data from the customer object, as show i Listig Listig 3-11 Obtaiig the Customer s Shippig Address <um:getproperty propertyname="shippigaddressmap" id="shippigaddressmapobject" /> <% Map shippigaddressmap = (Map) shippigaddressmapobject; Strig addresskey = request.getparameter(address_key); Address defaultshippigaddress = (Address) shippigaddressmap.get(addresskey); %> The data stored withi the defaultshippigaddress object ca ow be accessed by callig accessor methods/attributes withi Java scriptlets. Table 3-14 provides more detailed iformatio about the methods/attributes for the default shippig address. Table 3-14 defaultshippigaddress Accessor Methods/Attributes Method/Attribute getstreet1() getstreet2() getcity() getcouty() getstate() getpostalcode() getcoutry() Descriptio The first lie i the customer s shippig street address. The secod lie i the customer s shippig street address. The city i the customer s shippig address. The couty i the customer s shippig address. The state i the customer s shippig address. The zip/postal code i the customer s shippig address. The coutry i the customer s shippig address. Form Field Specificatio The primary purpose of the profileeditaddress.jsp template is to allow customers to edit their profile iformatio usig various HTML form fields. It is also used to pass eeded iformatio to the Webflow. Registratio ad User Processig Package 3-35

92 3 Customer Profile Services The form fields used i the profileeditaddress.jsp template (most of which are actually imported from the editaddresstemplate.jsp file), ad a descriptio for each of these form fields are listed i Table Table 3-15 profileeditaddress.jsp Form Fields Parameter Name Type Descriptio evet Hidde Idicates which evet has bee triggered. It is used by the Webflow to determie what happes ext. origi Hidde The ame of the curret page (profileeditaddress. jsp), used by the Webflow. CUSTOMER_SHIPPING_ADDRESS1 CUSTOMER_SHIPPING_ADDRESS2 CUSTOMER_SHIPPING_CITY CUSTOMER_SHIPPING_STATE CUSTOMER_SHIPPING_ZIPCODE CUSTOMER_SHIPPING_COUNTRY Textbox Textbox Textbox Listbox Textbox Listbox The first lie i the customer s shippig address. The secod lie i the customer s shippig address. The city i the customer s shippig address. The state i the customer s shippig address. The zip/postal code i the customer s shippig address. The coutry i the customer s shippig address. Note: Parameters that are literals i the JSP code are show i quotes, while o-literals will require scriptlet sytax (such as <%= CUSTOMER_SHIPPING_COUNTRY %>) for use i the JSP Registratio ad User Processig Package

93 JavaServer Pages (JSPs) profileewcc.jsp Template Sample Browser View The profileewcc.jsp template (show i Figure 3-5) allows a existig customer to add ew credit card iformatio, which will be stored as part of their profile. Figure 3-5 shows a aotated versio of the profileewcc.jsp template. The dashed lies ad umbers i the diagram are ot part of the template; they are refereced i the explaatio that follows the scree shot. Figure 3-5 Aotated profileewcc.jsp Template Registratio ad User Processig Package 3-37

94 3 Customer Profile Services The umbers i the followig list refer to the umbered regios i the figure: 1. The page header (top baer) is created from a import of the ierheader.jsp template. This is stadard across may of the JSP templates provided by WebLogic Commerce Server. The import call is: <%@ iclude file="/commerce/icludes/ierheader.jsp" %> 2. Regio 2 provides customers with a series of form fields that allow customers to eter paymet iformatio related to a ew credit card. This regio utilizes the form fields defied i the icluded ewcctemplate.jsp template file, which itself icludes the states.jsp ad coutries.jsp template files. The iclude call i profileewcc.jsp is: <%@ iclude file="/commerce/icludes/ewcctemplate.jsp %> 3. The profileewcc.jsp template s cotet i regio 3 cotais the icluded ierfooter.jsp template. The iclude call i profileewcc.jsp is: <%@ iclude file="/commerce/icludes/ierfooter.jsp" %> ierfooter.jsp cosists of the horizotal footer at the bottom of the page, plus the right-side vertical colum that describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. I the ierfooter.jsp file, the right-side vertical colum is a iclude file: <%@ iclude file="/commerce/icludes/rightside.jsp" %> Locatio i the WebLogic Commerce Server Directory Structure You ca fid the profileewcc.jsp template file at the followig locatio, where WL_COMMERCE_HOME is the directory i which you istalled WebLogic Commerce Server: %WL_COMMERCE_HOME%\server\webapps\wlcs\commerce\user\ profileewcc.jsp (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/commerce/user/ profileewcc.jsp (UNIX) 3-38 Registratio ad User Processig Package

95 JavaServer Pages (JSPs) Tag Library Imports The profileewcc.jsp template uses the Webflow JSP tags. Therefore, the template icludes the followig JSP tag libraries: taglib uri= webflow.tld prefix= webflow %> Note: For more iformatio about the Webflow JSP tags, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. These files reside i the followig directory for the WebLogic Commerce Server Web applicatio: %WL_COMMERCE_HOME%\server\webapps\wlcs\WEB-INF (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/WEB-INF (UNIX) Java Package Imports The profileewcc.jsp template uses Java classes i the followig packages ad therefore icludes these import statemets: <%@ page import="javax.servlet.*" %> <%@ page import="javax.servlet.http.*" %> <%@ page import="com.beasys.commerce.webflow.*" %> <%@ page import="com.beasys.commerce.webflow.tags.webflowtagcostats" %> <%@ page import="com.beasys.commerce.foudatio.pipelie.*" %> <%@ page import="com.beasys.commerce.axiom.cotact.*" %> <%@ page import="com.beasys.commerce.ebusiess.customer.*" %> Locatio i Default Webflow The page before the profileewcc.jsp template is the page o which a customer ca view their curret profile (viewprofile.jsp). If there are o errors i the form submissio, the ext page i the default Webflow is viewprofile.jsp. If correctios do eed to be made, the profileewcc.jsp template is reloaded. Note: For more iformatio about the default Webflow, see Overview of the Registratio ad User Processig Package o page 1-1. Registratio ad User Processig Package 3-39

96 3 Customer Profile Services Icluded JSP Templates The followig JSP templates are icluded i the profileewcc.jsp template: ierheader.jsp, which creates the top baer. ierfooter.jsp, which creates a horizotal footer at the bottom of the page, ad also icludes the rightside.jsp template. rightside.jsp describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. ewcctemplate.jsp, described i About the Icluded ewcctemplate.jsp Template o page Evets The profileewcc.jsp template presets customers with two butto evets that trigger a particular respose i the default Webflow, thereby allowig customers to cotiue. While this respose ca be to load aother JSP, it is usually the case that a iput processor or Pipelie is ivoked first. Table 3-16 provides iformatio about these evets ad the busiess logic they ivoke. Table 3-16 profileewcc.jsp Evets Evet butto(back) butto(save) Webflow Respose(s) No busiess logic required. Loads viewprofile.jsp. UpdatePaymetIfoIP NewCreditCard Table 3-17 briefly describes each of the Pipelies from Table 3-16, as they are defied i the pipelie.properties file. For more iformatio about idividual Pipelie compoets, see Pipelie Compoets o page Table 3-17 New Credit Card Pipelies Pipelie NewCreditCard Descriptio Cotais EcryptCreditCardPC ad UpdatePaymetIfoPC, ad is trasactioal Registratio ad User Processig Package

97 JavaServer Pages (JSPs) Dyamic Data Display Form Field Specificatio No dyamic data is preseted o the profileewcc.jsp template. The primary purpose of the profileewcc.jsp template is to allow customers to eter ew credit card iformatio usig various HTML form fields. It is also used to pass eeded iformatio to the Webflow. The form fields used i the profileewcc.jsp template (most of which are actually imported from the ewcctemplate.jsp file), ad a descriptio for each of these form fields are listed i Table Table 3-18 profileewcc.jsp Form Fields Parameter Name Type Descriptio evet Hidde Idicates which evet has bee triggered. It is used by the Webflow to determie what happes ext. origi Hidde The ame of the curret page (profileewcc.jsp), used by the Webflow. CUSTOMER_CREDITCARD_TYPE CUSTOMER_CREDITCARD_HOLDER CUSTOMER_CREDITCARD_NUMBER CUSTOMER_CREDITCARD_MONTH CUSTOMER_CREDITCARD_YEAR CUSTOMER_CREDITCARD_ADDRESS1 Listbox Textbox Textbox Listbox Listbox Textbox The type of the customer s credit card. The ame o the credit card. The umber of the customer s credit card. The moth of the customer s credit card expiratio date. The year of the customer s credit card expiratio date. The first lie i the customer s billig address. Registratio ad User Processig Package 3-41

98 3 Customer Profile Services Table 3-18 profileewcc.jsp Form Fields Parameter Name Type Descriptio CUSTOMER_CREDITCARD_ADDRESS2 CUSTOMER_CREDITCARD_CITY CUSTOMER_CREDITCARD_STATE CUSTOMER_CREDITCARD_ZIPCODE CUSTOMER_CREDITCARD_COUNTRY Textbox Textbox Listbox Textbox Listbox The secod lie i the customer s billig address. The city i the customer s billig address. The state i the customer s billig address. The zip/postal code i the customer s billig address. The coutry i the customer s billig address. Note: Parameters that are literals i the JSP code are show i quotes, while o-literals will require scriptlet sytax (such as <%= CUSTOMER_CREDITCARD_COUNTRY %>) for use i the JSP Registratio ad User Processig Package

99 JavaServer Pages (JSPs) profileeditcc.jsp Template Sample Browser View The profileeditcc.jsp template (show i Figure 3-6) allows a customer to edit existig credit card iformatio, which will be stored as part of their profile. Figure 3-6 shows a aotated versio of the profileeditcc.jsp template. The dashed lies ad umbers i the diagram are ot part of the template; they are refereced i the explaatio that follows the scree shot. Figure 3-6 Aotated profileeditcc.jsp Template Registratio ad User Processig Package 3-43

100 3 Customer Profile Services The umbers i the followig list refer to the umbered regios i the figure: 1. The page header (top baer) is created from a import of the ierheader.jsp template. This is stadard across may of the JSP templates provided by WebLogic Commerce Server. The import call is: <%@ iclude file="/commerce/icludes/ierheader.jsp" %> 2. Regio 2 provides customers with a series of form fields that allow customers to update their paymet iformatio related to a credit card. This regio utilizes the form fields defied i the icluded editcctemplate.jsp template file, which itself icludes the states.jsp ad coutries.jsp template files. The import call i profileeditcc.jsp is: <%@ iclude file="/commerce/icludes/editcctemplate.jsp %> 3. The profileeditcc.jsp template s cotet i regio 3 cotais the icluded ierfooter.jsp template. The iclude call i profileeditcc.jsp is: <%@ iclude file="/commerce/icludes/ierfooter.jsp" %> ierfooter.jsp cosists of the horizotal footer at the bottom of the page, plus the right-side vertical colum that describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. I the ierfooter.jsp file, the right-side vertical colum is a iclude file: <%@ iclude file="/commerce/icludes/rightside.jsp" %> Locatio i the WebLogic Commerce Server Directory Structure You ca fid the profileeditcc.jsp template file at the followig locatio, where WL_COMMERCE_HOME is the directory i which you istalled WebLogic Commerce Server: %WL_COMMERCE_HOME%\server\webapps\wlcs\commerce\user\ profileeditcc.jsp (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/commerce/user/ profileeditcc.jsp (UNIX) Tag Library Imports The profileeditcc.jsp template uses the Webflow JSP tags ad WebLogic Persoalizatio Server s User Maagemet JSP tags. Therefore, the template icludes the followig JSP tag libraries: 3-44 Registratio ad User Processig Package

101 JavaServer Pages (JSPs) taglib uri= webflow.tld prefix= webflow %> taglib uri= um.tld prefix= um %> Note: For more iformatio about the Webflow JSP tags, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. For more iformatio o the WebLogic Persoalizatio Server s User Maagemet JSP tags, see JSP Tag Referece i the BEA WebLogic Persoalizatio Server documetatio. These files reside i the followig directory for the WebLogic Commerce Server Web applicatio: %WL_COMMERCE_HOME%\server\webapps\wlcs\WEB-INF (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/WEB-INF (UNIX) Java Package Imports The profileeditcc.jsp template uses Java classes i the followig packages ad therefore icludes these import statemets: <%@ page import="javax.servlet.*" %> <%@ page import="javax.servlet.http.*" %> <%@ page import="com.beasys.commerce.webflow.*" %> <%@ page import="com.beasys.commerce.webflow.tags.webflowtagcostats" %> <%@ page import="com.beasys.commerce.foudatio.pipelie.*" %> <%@ page import="com.beasys.commerce.axiom.cotact.*" %> <%@ page import="com.beasys.commerce.ebusiess.customer.*" %> Locatio i Default Webflow The page before the profileeditcc.jsp template is the page o which a customer ca view their curret profile (viewprofile.jsp). If there are o errors i the form submissio, the ext page i the default Webflow is viewprofile.jsp. If correctios do eed to be made, profileeditcc.jsp is reloaded. Note: For more iformatio about the default Webflow, see Overview of the Registratio ad User Processig Package o page 1-1. Icluded JSP Templates The followig JSP templates are icluded i the profileeditcc.jsp template: Registratio ad User Processig Package 3-45

102 3 Customer Profile Services ierheader.jsp, which creates the top baer. ierfooter.jsp, which creates a horizotal footer at the bottom of the page, ad also icludes the rightside.jsp template. rightside.jsp describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. editcctemplate.jsp, described below. About the Icluded editcctemplate.jsp Template The editcctemplate.jsp template (icluded i all JSP templates that allow customers to edit a credit card) provides a stadardized format for both the form field presetatio ad error hadlig. The form fields are orgaized i a table, ad upo form submissio, the iput processors associated with the editcctemplate.jsp template will validate the form to esure that all required fields cotai values. If errors are detected, the editcctemplate.jsp template will be redisplayed, with a error message at the top ad the offedig field labels show i red (as opposed to the origial black) fot. Further, the iformatio your customer etered correctly will still be displayed i the form. Sice the editcctemplate.jsp template allows customers to edit a existig shippig address, the form fields o the page are also prefilled with iformatio previously etered by the customer. The behavior described above is accomplished o the editcctemplate.jsp template usig the getvalidatedvalue JSP tag ad the accessor methods/attributes for defaultcreditcard, as show i Listig Registratio ad User Processig Package

103 JavaServer Pages (JSPs) Listig 3-12 Use of the getvalidatedvalue JSP Tag ad Accessor Methods/Attributes o editcctemplate.jsp <table> <tr> <!-- use the webflow:getvalidatedvalue to retrieve a value from the HttpRequest. This value was placed there by the CustomerProfileIP iput processor --> <td> <webflow:getvalidatedvalue fieldname="<%=customer_creditcard_holder%>" fielddefaultvalue="<%=defaultcreditcard.getname()%>" fieldvalue="customercreditcardholder" fieldstatus="status" validcolor="black" ivalidcolor="red" uspecifiedcolor="black" fieldcolor="fotcolor" /> <div class="tabletext"> <fot color=<%= fotcolor %>>Name o card</fot> </div> </td> <td> <iput type="text" ame="<%=customer_creditcard_holder%>" value="<%=customercreditcardholder%>">* </td> </tr> </table> Notes: For more iformatio about the getvalidatedvalue JSP tag, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. For a list of the available accessor methods/attributes for defaultcreditcard, see Table Because the editcctemplate.jsp template collects address iformatio, this template also icludes states.jsp ad coutries.jsp where appropriate. Registratio ad User Processig Package 3-47

104 3 Customer Profile Services Evets The profileeditcc.jsp template presets customers with two butto evets that trigger a particular respose i the default Webflow, thereby allowig customers to cotiue. While this respose ca be to load aother JSP, it is usually the case that a iput processor or Pipelie is ivoked first. Table 3-19 provides iformatio about these evets ad the busiess logic they ivoke. Table 3-19 profileeditcc.jsp Evets Evet butto(back) butto(save) Webflow Respose(s) No busiess logic required. Loads viewprofile.jsp. UpdatePaymetIfoIP UpdateCreditCard Table 3-20 briefly describes each of the Pipelies from Table 3-19, as they are defied i the pipelie.properties file. For more iformatio about idividual Pipelie compoets, see Pipelie Compoets o page Table 3-20 Edit Credit Card Pipelies Pipelie UpdateCreditCard Descriptio Cotais UpdatePaymetPC ad is trasactioal. Dyamic Data Display Oe purpose of the profileeditcc.jsp template is to prepare the credit card iformatio a customer had previously etered, so the editcctemplate.jsp template ca display this iformatio i the paymet iformatio form fields. This is accomplished o the profileeditcc.jsp template usig a combiatio the WebLogic Persoalizatio Server s User Maagemet JSP tags ad accessor methods/attributes. First, the getprofile JSP tag is used to set the customer profile (cotext) for which the customer iformatio should be retrieved, as show i Listig Registratio ad User Processig Package

105 JavaServer Pages (JSPs) Listig 3-13 Settig the Customer Cotext <um:getprofile profilekey="<%=request.getremoteuser()%>" profiletype="wlcs_customer" /> Note: For more iformatio o the WebLogic Persoalizatio Server s User Maagemet JSP tags, see JSP Tag Referece i the BEA WebLogic Persoalizatio Server documetatio. Next, the getproperty JSP tag is used to obtai the customer s list of credit cards (ad related billig iformatio), which is the iitialized with data from the customer object, as show i Listig Listig 3-14 Obtaiig the Customer s Credit Cards ad Billig Iformatio <um:getproperty propertyname="creditcardsmap" id="creditcardsmapobject" /> <% Map creditcardsmap = (Map) creditcardsmapobject; Strig creditcardkey = request.getparameter(creditcard_key); CreditCard defaultcreditcard = ull; defaultcreditcard = (CreditCard) creditcardsmap.get(creditcardkey); Address billigaddress = (Address) defaultcreditcard.getbilligaddress(); %> The data stored withi the defaultcreditcard ad billigaddress objects ca ow be accessed by callig accessor methods/attributes withi Java scriptlets. Table 3-21 provides more detailed iformatio about the methods/attributes for the default credit card, while Table 3-22 provides more iformatio about the accessor methods/attributes o billigaddress. Registratio ad User Processig Package 3-49

106 3 Customer Profile Services Table 3-21 defaultcreditcard Accessor Methods/Attributes Method/Attribute gettype() getname() getdisplaynumber() getnumber() getexpiratiodate() Descriptio The credit card type (VISA, MasterCard, AMEX, etc.). The credit card holder s ame. The credit card umber for display (12 Xs ad last 4 digits). The credit card umber. The credit card s expiratio date. Table 3-22 billigaddress Accessor Methods/Attributes Method/Attribute getstreet1() getstreet2() getcity() getcouty() getstate() getpostalcode() getcoutry() Descriptio The first lie i the customer s billig street address. The secod lie i the customer s billig street address. The city i the customer s billig address. The couty i the customer s billig address. The state i the customer s billig address. The zip/postal code i the customer s billig address. The coutry i the customer s billig address. Form Field Specificatio Aother purpose of the profileeditcc.jsp template is to allow customers to make chages to their credit card iformatio usig various HTML form fields. Ukow to your customers, it is also used to pass eeded iformatio to the Webflow. The form fields used i the profileeditcc.jsp template (most of which are actually imported from the editcctemplate.jsp file), ad a descriptio for each of these fields are listed i Table Registratio ad User Processig Package

107 JavaServer Pages (JSPs) Table 3-23 profileeditcc.jsp Form Fields Parameter Name Type Descriptio evet Hidde Idicates which evet has bee triggered. It is used by the Webflow to determie what happes ext. origi Hidde The ame of the curret page (profileeditcc.jsp), used by the Webflow. CUSTOMER_CREDITCARD_KEY_ORIGINAL CUSTOMER_CREDITCARD_TYPE CUSTOMER_CREDITCARD_HOLDER CUSTOMER_CREDITCARD_NUMBER CUSTOMER_CREDITCARD_DISPLAY_NUMBER CUSTOMER_CREDITCARD_MONTH CUSTOMER_CREDITCARD_YEAR CUSTOMER_CREDITCARD_ADDRESS1 CUSTOMER_CREDITCARD_ADDRESS2 CUSTOMER_CREDITCARD_CITY Hidde Listbox Textbox Textbox Hidde Listbox Listbox Textbox Textbox Textbox The map key of the customer s credit card. The type of the customer s credit card. The ame o the credit card. The umber of the customer s credit card. The display versio of the customer s credit card (12 Xs ad last 4 digits). The moth of the customer s credit card expiratio date. The year of the customer s credit card expiratio date. The first lie i the customer s billig address. The secod lie i the customer s billig address. The city i the customer s billig address. Registratio ad User Processig Package 3-51

108 3 Customer Profile Services Table 3-23 profileeditcc.jsp Form Fields Parameter Name Type Descriptio CUSTOMER_CREDITCARD_STATE CUSTOMER_CREDITCARD_ZIPCODE CUSTOMER_CREDITCARD_COUNTRY Listbox Textbox Listbox The state i the customer s billig address. The zip/postal code i the customer s billig address. The coutry i the customer s billig address. Note: Parameters that are literals i the JSP code are show i quotes, while o-literals will require scriptlet sytax (such as <%= CUSTOMER_CREDITCARD_COUNTRY %>) for use i the JSP Registratio ad User Processig Package

109 JavaServer Pages (JSPs) chagepassword.jsp Template Sample Browser View The chagepassword.jsp template (show i Figure 3-7) allows a customer to chage their password, which will be stored as part of their profile. Figure 3-7 shows a aotated versio of the chagepassword.jsp template. The dashed lies ad umbers i the diagram are ot part of the template; they are refereced i the explaatio that follows the scree shot. Figure 3-7 Aotated chagepassword.jsp Template The umbers i the followig list refer to the umbered regios i the figure: 1. The page header (top baer) is created from a import of the ierheader.jsp template. This is stadard across may of the JSP templates provided by WebLogic Commerce Server. The import call is: Registratio ad User Processig Package 3-53

110 3 Customer Profile Services iclude file="/commerce/icludes/ierheader.jsp" %> 2. Regio 2 provides customers with a series of form fields that allow customers to chage their password, by first eterig their old password, the eterig ad cofirmig their ew password. 3. The chagepassword.jsp template s cotet i regio 3 cotais the icluded ierfooter.jsp template. The iclude call i chagepassword.jsp is: <%@ iclude file="/commerce/icludes/ierfooter.jsp" %> ierfooter.jsp cosists of the horizotal footer at the bottom of the page, plus the right-side vertical colum that describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. I the ierfooter.jsp file, the right-side vertical colum is a iclude file: <%@ iclude file="/commerce/icludes/rightside.jsp" %> Locatio i the WebLogic Commerce Server Directory Structure You ca fid the chagepassword.jsp template file at the followig locatio, where WL_COMMERCE_HOME is the directory i which you istalled WebLogic Commerce Server: %WL_COMMERCE_HOME%\server\webapps\wlcs\commerce\user\ chagepassword.jsp (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/commerce/user/ chagepassword.jsp (UNIX) Tag Library Imports The chagepassword.jsp template uses Webflow JSP tags ad WebLogic Persoalizatio Server s User Maagemet JSP tags. Therefore, the template icludes the followig JSP tag libraries: <%@ taglib uri= webflow.tld prefix= webflow %> <%@ taglib uri= um.tld prefix= um %> Note: For more iformatio about the Webflow JSP tags, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. For more iformatio o the WebLogic Persoalizatio Server s User Maagemet JSP tags, see JSP Tag Referece i the BEA WebLogic Persoalizatio Server documetatio Registratio ad User Processig Package

111 JavaServer Pages (JSPs) These files reside i the followig directory for the WebLogic Commerce Server Web applicatio: %WL_COMMERCE_HOME%\server\webapps\wlcs\WEB-INF (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/WEB-INF (UNIX) Java Package Imports The chagepassword.jsp template uses Java classes i the followig packages ad therefore icludes these import statemets: <%@ page import="javax.servlet.*" %> <%@ page import="javax.servlet.http.*" %> <%@ page import="com.beasys.commerce.webflow.*" %> <%@ page import="com.beasys.commerce.webflow.tags.webflowtagcostats" %> <%@ page import="com.beasys.commerce.foudatio.pipelie.*" %> <%@ page import="com.beasys.commerce.axiom.cotact.*" %> <%@ page import="com.beasys.commerce.ebusiess.customer.*" %> Locatio i Default Webflow The page before the chagepassword.jsp template is the page o which a customer ca view their curret profile (viewprofile.jsp). If there are o errors i the form submissio, the ext page i the default Webflow is viewprofile.jsp. If correctios do eed to be made, chagepassword.jsp is reloaded. Note: For more iformatio about the default Webflow, see Overview of the Registratio ad User Processig Package o page 1-1. Icluded JSP Templates The followig JSP templates are icluded i the chagepassword.jsp template: ierheader.jsp, which creates the top baer. ierfooter.jsp, which creates a horizotal footer at the bottom of the page, ad also icludes the rightside.jsp template. rightside.jsp describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. Registratio ad User Processig Package 3-55

112 3 Customer Profile Services Evets The chagepassword.jsp template presets customers with two butto evets that trigger a particular respose i the default Webflow, thereby allowig customers to cotiue. While this respose ca be to load aother JSP, it is usually the case that a iput processor or Pipelie is ivoked first. Table 3-24 provides iformatio about these evets ad the busiess logic they ivoke. Table 3-24 chagepassword.jsp Evets Evet butto(back) butto(save) Webflow Respose(s) No busiess logic required. Loads viewprofile.jsp. UpdateAccoutIfoIP UpdateAccoutProfile Table 3-25 briefly describes each of the Pipelies from Table 3-24, as they are defied i the pipelie.properties file. For more iformatio about idividual Pipelie compoets, see Pipelie Compoets o page Table 3-25 Chage Password Pipelies Pipelie UpdateAccoutProfile Descriptio Cotais UpdatePasswordPC ad is trasactioal. Dyamic Data Display Oe purpose of the chagepassword.jsp template is to display the customer s userame. This is accomplished o the chagepassword.jsp template usig a simple Java scriptlet, as show i Listig Registratio ad User Processig Package

113 JavaServer Pages (JSPs) Listig 3-15 Displayig the Customer s Userame <td> <div class="tabletext"> <b><%=request.getremoteuser()%></b> </div> </td> Note: Customers caot chage their userame, oly their password. If the New Password ad Cofirm New Password form fields are ot filled i correctly, the page is displayed with all fields empty (that is, o fields are dyamically prefilled upo reload). Form Field Specificatio The primary purpose of the chagepassword.jsp template is to allow customers to make chages to their password usig HTML form fields. It is also used to pass eeded iformatio to the Webflow. The form fields used i the chagepassword.jsp template, ad a descriptio for each of these form fields are listed i Table Table 3-26 chagepassword.jsp Form Fields Parameter Name Type Descriptio evet Hidde Idicates which evet has bee triggered. It is used by the Webflow to determie what happes ext. origi Hidde The ame of the curret page (chagepassword.jsp), used by the Webflow. PASSWORD Password The customer s existig password used to logi. Registratio ad User Processig Package 3-57

114 3 Customer Profile Services Table 3-26 chagepassword.jsp Form Fields Parameter Name Type Descriptio NEW_PASSWORD CONFIRM_PASSWORD Password Password The ew password chose by the customer for logi. Cofirmatio of the ew password chose by the customer for logi. Note: Parameters that are literals i the JSP code are show i quotes, while o-literals will require scriptlet sytax (such as <%= CONFIRM_PASSWORD %>) for use i the JSP Registratio ad User Processig Package

115 Iput Processors Iput Processors This sectio provides a brief descriptio of each iput processor associated with the Customer Profile Services JSP template(s). DeleteCreditCardIP Class Name Descriptio Required HTTPServletRequest Parameters Required Pipelie Sessio Attributes Updated Pipelie Sessio Attributes Removed Pipelie Sessio Attributes Validatio Exceptios com.beasys.commerce.ebusiess.customer.webflow. DeleteCreditCardIP Deletes a CreditCard from the CreditCardMap ad creates a ew CustomerValue object; the sets the CreditCardMap o CustomerValue ad places it ito the Pipelie sessio. CREDITCARD_KEY PipelieSessioCostats.USER_NAME PipelieSessioCostats.CUSTOMER Noe Verifies that CREDITCARD_KEY is ot NULL. IvalidIputExceptio, throw if CREDITCARD_KEY is NULL. IvalidSessioStateExceptio, throw if the sessio is uavailable or has expired. Registratio ad User Processig Package 3-59

116 3 Customer Profile Services DeleteShippigAddressIP Class Name Descriptio Required HTTPServletRequest Parameters Required Pipelie Sessio Attributes Updated Pipelie Sessio Attributes Removed Pipelie Sessio Attributes Validatio Exceptios com.beasys.commerce.ebusiess.customer.webflow. DeleteShippigAddressIP Deletes a ShippigAddress from the ShippigAddressMap ad creates a ew CustomerValue object; the sets the ShippigAddressMap o CustomerValue ad places it ito the Pipelie sessio. ADDRESS_KEY PipelieSessioCostats.USER_NAME PipelieSessioCostats.CUSTOMER Noe Verifies that ADDRESS_KEY is ot NULL. IvalidIputExceptio, throw if ADDRESS_KEY is NULL. IvalidSessioStateExceptio, throw if the sessio is uavailable or has expired Registratio ad User Processig Package

117 Iput Processors UpdateAccoutIfoIP Class Name Descriptio Required HTTPServletRequest Parameters Required Pipelie Sessio Attributes Updated Pipelie Sessio Attributes Removed Pipelie Sessio Attributes Validatio Exceptios com.beasys.commerce.ebusiess.customer.webflow. UpdateAccoutIfoIP Processes the customer s iput from the chagepassword.jsp. Creates a CustomerValue object i the Pipelie sessio cotaiig the ew iformatio. PASSWORD NEW_PASSWORD CONFIRM_PASSWORD Noe PipelieSessioCostats.PASSWORD Noe Validates the curret password ad verifies that the required fields cotai values. IvalidIputExceptio, throw whe the curret password is icorrect, whe the required fields do ot cotai values, or if the ew password ad cofirm password values do ot match. ProcessigExceptio, throw i the case of a cofiguratio error. Registratio ad User Processig Package 3-61

118 3 Customer Profile Services UpdateBasicIfoIP Class Name Descriptio Required HTTPServletRequest Parameters Required Pipelie Sessio Attributes Updated Pipelie Sessio Attributes Removed Pipelie Sessio Attributes Validatio Exceptios com.beasys.commerce.ebusiess.customer.webflow. UpdateBasicIfoIP Processes the customer s iput from the editprofile.jsp. Creates a CustomerValue object i the Pipelie sessio cotaiig the ew iformatio. CUSTOMER_FIRST_NAME CUSTOMER_MIDDLE_NAME CUSTOMER_LAST_NAME CUSTOMER_ADDRESS1 CUSTOMER_ADDRESS2 CUSTOMER_CITY CUSTOMER_STATE CUSTOMER_ZIPCODE CUSTOMER_COUNTRY CUSTOMER_HOME_PHONE CUSTOMER_BUSINESS_PHONE CUSTOMER_ PipelieSessioCostats.USER_NAME PipelieSessioCostats.CUSTOMER Noe Verifies that the required fields cotai values. IvalidIputExceptio, throw if the required fields do ot cotai values. ProcessigExceptio, throw if the required Pipelie sessio attributes are ot available Registratio ad User Processig Package

119 Iput Processors UpdatePaymetIfoIP Class Name Descriptio Required HTTPServletRequest Parameters Required Pipelie Sessio Attributes Updated Pipelie Sessio Attributes Removed Pipelie Sessio Attributes Validatio Exceptios com.beasys.commerce.ebusiess.customer.webflow. UpdatePaymetIfoIP Processes the customer s iput from profileewcc.jsp ad profileeditcc.jsp. Creates a CustomerValue object i the Pipelie sessio cotaiig the ew iformatio. CUSTOMER_CREDITCARD_TYPE CUSTOMER_CREDITCARD_HOLDER CUSTOMER_CREDITCARD_NUMBER CUSTOMER_CREDITCARD_DISPLAY_N UMBER CUSTOMER_CREDITCARD_MONTH CUSTOMER_CREDITCARD_YEAR CUSTOMER_CREDITCARD_ADDRESS1 CUSTOMER_CREDITCARD_ADDRESS2 CUSTOMER_CREDITCARD_CITY CUSTOMER_CREDITCARD_STATE CUSTOMER_CREDITCARD_ZIPCODE CUSTOMER_CREDITCARD_COUNTRY PipelieSessioCostats.USER_NAME PipelieSessioCostats.CUSTOMER PipelieSessioCostats.CREDITCARD_KEY Noe Verifies that the required fields cotai values, ad verifies that the legth of the credit card umber is ot less tha 16 digits (15 digits for AMEX). IvalidIputExceptio, throw if the required fields do ot cotai values or the credit card umber is less tha the miimum required for the type. IvalidSessioStateExceptio, throw whe the sessio is uavailable or has expired. Registratio ad User Processig Package 3-63

120 3 Customer Profile Services UpdateShippigIfoIP Class Name Descriptio Required HTTPServletRequest Parameters Required Pipelie Sessio Attributes Updated Pipelie Sessio Attributes Removed Pipelie Sessio Attributes Validatio Exceptios com.beasys.commerce.ebusiess.customer.webflow. UpdateShippigIfoIP Processes the customer s iput from the profileeditaddress.jsp. Creates a CustomerValue object i the Pipelie sessio cotaiig the ew iformatio. CUSTOMER_SHIPPING_ADDRESS1 CUSTOMER_SHIPPING_ADDRESS2 CUSTOMER_SHIPPING_CITY CUSTOMER_SHIPPING_STATE CUSTOMER_SHIPPING_ZIPCODE CUSTOMER_SHIPPING_COUNTRY PipelieSessioCostats.USER_NAME PipelieSessioCostats.CUSTOMER Noe Verifies that the required fields cotai values. IvalidIputExceptio, throw whe the required fields do ot cotai values. IvalidSessioStateExceptio, throw if the sessio is uavailable or is expired Registratio ad User Processig Package

121 Pipelie Compoets Pipelie Compoets This sectio provides a brief descriptio of each Pipelie compoet associated with the Customer Profile Services JSP template(s). Note: Some Pipelie compoets exted other, base Pipelie compoets. For more iformatio o the base classes, see the Javadoc. UpdateBasicIfoPC Class Name Descriptio Required Pipelie Sessio Attributes Updated Pipelie Sessio Attributes Removed Pipelie Sessio Attributes Type JNDI Name Exceptios com.beasys.commerce.ebusiess.customer.pipelie. UpdateBasicIfoPC Updates the Customer object for chages made by UpdateBasicIfoIP. This Pipelie compoet must stay i syc with the the UpdateBasicIfoIP iput processor. Noe Noe Noe Java class Noe PipelieFatalExceptio, throw whe the Pipelie compoet is ot able to set the customer s properties. Registratio ad User Processig Package 3-65

122 3 Customer Profile Services UpdatePaymetIfoPC Class Name Descriptio Required Pipelie Sessio Attributes Updated Pipelie Sessio Attributes Removed Pipelie Sessio Attributes Type JNDI Name Exceptios com.beasys.commerce.ebusiess.customer.pipelie. UpdatePaymetIfoPC Updates the Customer object for chages made by UpdatePaymetIfoIP. This Pipelie compoet must stay i syc with the the UpdatePaymetIfoIP iput processor. Noe Noe Noe Java class Noe PipelieFatalExceptio, throw whe the Pipelie compoet is ot able to set the customer s properties. UpdateShippigIfoPC Class Name Descriptio Required Pipelie Sessio Attributes com.beasys.commerce.ebusiess.customer.pipelie. UpdateShippigIfoPC Updates the Customer object for chages made by UpdateShippigIfoIP. This Pipelie compoet must stay i syc with the the UpdateShippigIfoIP iput processor. Noe 3-66 Registratio ad User Processig Package

123 Pipelie Compoets Updated Pipelie Sessio Attributes Removed Pipelie Sessio Attributes Type JNDI Name Exceptios Noe Noe Java class Noe PipelieFatalExceptio, throw whe the Pipelie compoet is ot able to set the customer s properties. UpdatePasswordPC Class Name Descriptio Required Pipelie Sessio Attributes Updated Pipelie Sessio Attributes Removed Pipelie Sessio Attributes Type JNDI Name Exceptios com.beasys.commerce.ebusiess.customer.pipelie. UpdatePasswordPC Retrieves the USER_NAME ad PASSWORD from the Pipelie sessio ad updates the password for the user. PipelieSessioCostats.CUSTOMER PipelieSessioCostats.PASSWORD Noe PipelieSessioCostats.PASSWORD Java class Noe PipelieFatalExceptio, throw whe the Pipelie compoet is ot able to set the customer s properties. Registratio ad User Processig Package 3-67

124 3 Customer Profile Services 3-68 Registratio ad User Processig Package

125 CHAPTER 4 Customer Self-Service Customers who make purchases from a e-commerce site ofte wat access to their order ad paymet history. I may cases, customers expect to have this iformatio available. To meet this eed, the Registratio ad User Processig package provides you with a series of JSPs desiged specifically for this purpose. The customer self-service pages allow registered customers who have previously placed orders with your e-busiess to locate iformatio about their past orders ad paymets, ad to check o the status of these orders. The customer self-service pages ca help you maitai a high level of service for all your customers by givig them the iformatio they require. This topic describes each of the customer self-service pages i detail. This topic icludes the followig sectios: JavaServer Pages (JSPs) l mai.jsp Template l orderhistory.jsp Template l orderstatus.jsp Template l paymethistory.jsp Template Iput Processors l SelectOrderForViewigIP Pipelie Compoets l RefreshOrderHistoryPC l RefreshPaymetHistoryPC Registratio ad User Processig Package 4-1

126 4 Customer Self-Service JavaServer Pages (JSPs) Like the other services available i the Registratio ad User Processig package, customer self-service is implemeted through a umber of JavaServer Pages (JSPs). You ca use these JSPs as a out-of-the-box solutio, or customize them to meet your uique busiess requiremets. This sectio describes each of these pages i detail. Note: For a descriptio of the complete set of JSPs used i the WebLogic Commerce Server Web applicatio ad a listig of their locatios i the directory structure, see the Summary of JSP Templates documetatio. mai.jsp Template The gateway ito the customer self-service pages is via the mai.jsp template (show i Figure 4-1), or the home page for the product catalog. A customer must be logged ito your e-commerce site for the customer self-service optios to be available. For more iformatio about the mai.jsp template, see The Product Catalog JSP Templates ad JSP Tags i the BEA WebLogic Commerce Server Product Catalog Maagemet documetatio. 4-2 Registratio ad User Processig Package

127 JavaServer Pages (JSPs) Figure 4-1 The mai.jsp Template s Customer Self-Service Sectio Registratio ad User Processig Package 4-3

128 4 Customer Self-Service orderhistory.jsp Template Sample Browser View The orderhistory.jsp template (show i Figure 4-2) displays a list of order summaries (icludig order date, order umber, ad order amout) for each of the customer s orders. It also provides the customer with a View butto for each order i the list, which allows the customer to view details about the order, icludig its status. Figure 4-2 shows a aotated versio of the orderhistory.jsp template. The dashed lies ad umbers i the diagram are ot part of the template; they are refereced i the explaatio that follows the scree shot. Figure 4-2 Aotated orderhistory.jsp Template 4-4 Registratio ad User Processig Package

129 JavaServer Pages (JSPs) The umbers i the followig list refer to the umbered regios i the figure: 1. The page header (top baer) is created from a import of the header2.jsp template. This is stadard across may of the JSP templates provided by WebLogic Commerce Server. The import call is: <%@ iclude file="/commerce/icludes/header2.jsp" %> 2. This regio is the mai cotet area for the page, which cotais dyamically-geerated data about the customer s order history. The dyamic cotet o orderhistory.jsp is obtaied usig Pipelie JSP tags ad displayed by iteratig through the orders usig WebLogic Server JSP tags. For the orderhistory.jsp template, the oly form posts are View (per order), allowig customers to locate more detailed iformatio about a particular order i their order history. 3. The orderhistory.jsp template s cotet i regio 3 cotais the icluded footer2.jsp template. The iclude call i orderhistory.jsp is: <%@ iclude file="/commerce/icludes/footer2.jsp" %> footer2.jsp cosists of the horizotal footer at the bottom of the page, plus the right-side vertical colum that describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. I the footer2.jsp file, the right-side vertical colum is a iclude file: <%@ iclude file="/commerce/icludes/rightside.jsp" %> Locatio i the WebLogic Commerce Server Directory Structure You ca fid the orderhistory.jsp template file at the followig locatio, where WL_COMMERCE_HOME is the directory i which you istalled WebLogic Commerce Server: %WL_COMMERCE_HOME%\server\webapps\wlcs\commerce\order\ orderhistory.jsp (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/commerce/order/ orderhistory.jsp (UNIX) Registratio ad User Processig Package 4-5

130 4 Customer Self-Service Tag Library Imports The orderhistory.jsp template uses WebLogic ad Pipelie JSP tags. Therefore, the template icludes the followig JSP tag libraries: taglib uri= weblogic.tld prefix= wl %> taglib uri= pipelie.tld prefix= pipelie %> Note: For more iformatio about the Pipelie JSP tags, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. For more iformatio o the WebLogic Server JSP tags, see JSP Tag Referece i the BEA WebLogic Persoalizatio Server documetatio. These files reside i the followig directory for the WebLogic Commerce Server Web applicatio: %WL_COMMERCE_HOME%\server\webapps\wlcs\WEB-INF (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/WEB-INF (UNIX) Java Package Imports The orderhistory.jsp template uses Java classes i the followig packages ad therefore icludes these import statemets: <%@ page import="java.util.*" %> <%@ page import="java.text.*" %> <%@ page import="com.beasys.commerce.foudatio.pipelie.*" %> <%@ page import="com.beasys.commerce.axiom.uits.*" %> <%@ page import="com.beasys.commerce.ebusiess.shippig.*" %> <%@ page import="com.beasys.commerce.ebusiess.order.*" %> <%@ page import="com.beasys.commerce.ebusiess.customer.*" %> <%@ page import="com.beasys.commerce.webflow.*" %> Locatio i Default Webflow Customers arrive at the orderhistory.jsp template from the product catalog home page (mai.jsp). From here, customers ca retur back to the product catalog home page, or display the details of a specific order by selectig it (orderstatus.jsp). Note: For more iformatio about the default Webflow, see Overview of the Registratio ad User Processig Package o page Registratio ad User Processig Package

131 JavaServer Pages (JSPs) Icluded JSP Templates The followig JSP templates are icluded i the orderhistory.jsp template: header2.jsp, which creates the top baer. footer2.jsp, which creates a horizotal footer at the bottom of the page, ad also icludes the rightside.jsp template. rightside.jsp describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. Evets Every time a customer clicks a butto to view more detail about a order, it is cosidered a evet. Each evet triggers a particular respose i the default Webflow that allows them to cotiue. While this respose ca be to load aother JSP, it is usually the case that a iput processor ad/or Pipelie is ivoked first. Table 4-1 provides iformatio about these evets ad the busiess logic they ivoke. Table 4-1 orderhistory.jsp Evets Evet Webflow Respose(s) -- RefreshOrderHistory butto(vieworderstatus) SelectOrderForViewigIP Table 4-2 briefly describes each of the Pipelies from Table 4-1, as they are defied i the pipelie.properties file. For more iformatio about idividual Pipelie compoets, see Pipelie Compoets o page Table 4-2 Order History Pipelies Pipelie RefreshOrderHistory Descriptio Cotais RefreshOrderHistoryPC ad is ot trasactioal. Registratio ad User Processig Package 4-7

132 4 Customer Self-Service Note: Although the RefreshOrderHistory Pipelie is associated with the orderhistory.jsp template, it is ot triggered by a evet o the page. Rather, the RefreshOrderHistory Pipelie is executed before the orderhistory.jsp is viewed, to locate the orders associated with the customer requestig the iformatio. Dyamic Data Display Oe purpose of the orderhistory.jsp template is to display the data specific to a customer s orders for their review ad possible selectio. This is accomplished o orderhistory.jsp usig a combiatio of WebLogic Server JSP tags, Pipelie JSP tags, ad attributes/methods. First, the getpipelieproperty JSP tag retrieves the ORDER_HISTORY attribute from the Pipelie sessio. Table 4-3 provides more detailed iformatio o this attribute. Table 4-3 orderhistory.jsp Pipelie Sessio Attributes Attribute Type Descriptio PipelieSessioCostats.ORDER_HISTORY List of com.beasys.commerce. ebusiess.order.ordervalue List of the orders available for the customer. Listig 4-1 illustrates how this attribute is retrieved from the Pipelie sessio usig the getpipelieproperty JSP tag. Listig 4-1 Retrievig the Order History Attribute <pipelie:getpipelieproperty propertyname="<%=pipeliesessiocostats.order_history%>" returname="orderhistory" returtype="java.util.list"/> Note: For more iformatio o the getpipelieproperty JSP tag, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. 4-8 Registratio ad User Processig Package

133 JavaServer Pages (JSPs) The data stored withi the Pipelie sessio attribute is the accessed by usig accessor methods/attributes withi Java scriptlets. Table 4-4 provides more detailed iformatio about these methods/attributes for OrderValue. Table 4-4 OrderValue Accessor Methods/Attributes Method/Attribute createddate idetifier gettotal(it totaltype) Descriptio The date the customer s order was created. Key i the database for the order. The total amout specified by the totaltype parameter. Valid parameters iclude: OrderCostats.LINE_UNIT_PRICE_TIMES_QUANTITY OrderCostats.LINE_SHIPPING OrderCostats.LINE_TAX Note: The gettotal() method also allows you to combie differet total types. For more iformatio, see the Javadoc. Listig 4-2 illustrates how these accessor methods/attributes are used withi Java scriptlets alog with the WebLogic Server JSP tags to display the iformatio. Listig 4-2 Usig Accessor Methods/Attributes Withi orderhistory.jsp Java Scriptlets <wl:repeat set="<%=orderhistory%>" id="ordervalue" type="ordervalue" cout="100"> <table> <tr> <td> <div class="tabletext"><%=ordervalue.createddate%></div> </td> <td> <div class="tabletext"><%=ordervalue.idetifier%></div> </td> <td> <div class="tabletext"> <% Moey total = Registratio ad User Processig Package 4-9

134 4 Customer Self-Service ordervalue.gettotal(ordercostats.line_unit_price_times_quantity + OrderCostats.LINE_SHIPPING + OrderCostats.LINE_TAX); %> <%=total.getcurrecy()%> <%=WebflowJSPHelper.priceFormat(total.getValue())%> </div> </td> </tr> </table> </wl:repeat> Note: For more iformatio o the WebLogic Server JSP tags, see JSP Tag Referece i the BEA WebLogic Persoalizatio Server documetatio. Form Field Specificatio No form fields are used i the orderhistory.jsp template Registratio ad User Processig Package

135 JavaServer Pages (JSPs) orderstatus.jsp Template Sample Browser View The orderstatus.jsp template (show i Figure 4-3) displays a variety of iformatio for the order summary the customer selected from the list preseted o the orderhistory.jsp template. This order iformatio icludes the order cofirmatio umber, the order status, the date the order was placed, splittig istructios, special istructios, the shippig address, iformatio related to the specific shoppig cart items (ame, descriptio, quatity, uit price), ad total amouts (shippig ad hadlig, tax, ad total order cost). Figure 4-3 shows a aotated versio of the orderstatus.jsp template. The dashed lies ad umbers i the diagram are ot part of the template; they are refereced i the explaatio that follows the scree shot. Registratio ad User Processig Package 4-11

136 4 Customer Self-Service Figure 4-3 Aotated orderstatus.jsp Template 4-12 Registratio ad User Processig Package

137 JavaServer Pages (JSPs) The umbers i the followig list refer to the umbered regios i the figure: 1. The page header (top baer) is created from a import of the header2.jsp template. This is stadard across may of the JSP templates provided by WebLogic Commerce Server. The import call is: <%@ iclude file="/commerce/icludes/header2.jsp" %> 2. This regio is the mai cotet area for the page, which cotais dyamically-geerated data about a particular order the customer selected from the orderhistory.jsp template. The dyamic cotet o orderstatus.jsp is obtaied usig Pipelie JSP tags ad displayed by iteratig through the shoppig cart items usig WebLogic Server JSP tags. 3. The orderstatus.jsp template s cotet i regio 3 cotais the icluded footer2.jsp template. The iclude call i orderstatus.jsp is: <%@ iclude file="/commerce/icludes/footer2.jsp" %> footer2.jsp cosists of the horizotal footer at the bottom of the page, plus the right-side vertical colum that describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. I the footer2.jsp file, the right-side vertical colum is a iclude file: <%@ iclude file="/commerce/icludes/rightside.jsp" %> Locatio i WebLogic Commerce Server Directory Structure You ca fid the orderstatus.jsp template file at the followig locatio, where WL_COMMERCE_HOME is the directory i which you istalled WebLogic Commerce Server: %WL_COMMERCE_HOME%\server\webapps\wlcs\commerce\order\ orderstatus.jsp (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/commerce/order/ orderstatus.jsp (UNIX) Registratio ad User Processig Package 4-13

138 4 Customer Self-Service Tag Library Imports The orderstatus.jsp template uses WebLogic ad Pipelie JSP tags. Therefore, the template icludes the followig JSP tag libraries: taglib uri= weblogic.tld prefix= wl %> taglib uri= pipelie.tld prefix= pipelie %> Note: For more iformatio o the WebLogic Server JSP tags, see JSP Tag Referece i the BEA WebLogic Persoalizatio Server documetatio. For more iformatio about the Pipelie JSP tags, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. These files reside i the followig directory for the WebLogic Commerce Server Web applicatio: %WL_COMMERCE_HOME%\server\webapps\wlcs\WEB-INF (Widows) $WL_COMMERCE_HOME/server/webapps/wlcs/WEB-INF (UNIX) Java Package Imports The orderstatus.jsp template uses Java classes i the followig packages ad therefore icludes these import statemets: <%@ page import="java.util.*" %> <%@ page import="java.text.*" %> <%@ page import="com.beasys.commerce.webflow.*" %> <%@ page import="com.beasys.commerce.axiom.uits.*" %> <%@ page import="com.beasys.commerce.axiom.cotact.*" %> <%@ page import="com.beasys.commerce.ebusiess.order.*" %> <%@ page import="com.beasys.commerce.ebusiess.paymet.*" %> <%@ page import="com.beasys.commerce.foudatio.pipelie.*" %> Locatio i Default Web Flow Customers arrive at the orderstatus.jsp template from the page that displays summaries of their past orders (orderhistory.jsp). The default Webflow does ot defie a subsequet JSP template. Note: For more iformatio about the default Webflow, see Overview of the Registratio ad User Processig Package o page Registratio ad User Processig Package

139 JavaServer Pages (JSPs) Icluded JSP Templates The followig JSP templates are icluded i the orderstatus.jsp template: header2.jsp, which creates the top baer. footer2.jsp, which creates a horizotal footer at the bottom of the page, ad also icludes the rightside.jsp template. rightside.jsp describes (for the beefit of you ad your developmet team) the ame of the curret template ad liks to its About iformatio. Evets Dyamic Data Display There are o evets o the orderstatus.jsp template. The purpose of the orderstatus.jsp template is to display the data specific to a customer s order for their review. This is accomplished o orderstatus.jsp usig a combiatio of WebLogic Server JSP tags, Pipelie JSP tags, ad accessor methods/attributes. First, the getpipelieproperty JSP tag retrieves the SELECTED_ORDER attribute from the Pipelie sessio. Table 4-5 provides more detailed iformatio o this attribute. Table 4-5 orderstatus.jsp Pipelie Sessio Attributes Attribute Type Descriptio PipelieSessioCostats.SELECTED_ORDER com.beasys.commerce. ebusiess.order.ordervalue Cotais a variety of iformatio about the order selected by the customer. Listig 4-3 illustrates how this attribute is retrieved from the Pipelie sessio usig the getpipelieproperty JSP tag. Registratio ad User Processig Package 4-15

140 4 Customer Self-Service Listig 4-3 Retrievig the Selected Order Attribute <pipelie:getpipelieproperty propertyname="<%=pipeliesessiocostats.selected_order%>" returname="ordervalue" returtype="com.beasys.commerce.ebusiess.order.ordervalue"/> Note: For more iformatio o the getpipelieproperty JSP tag, see BEA WebLogic Commerce Server Webflow ad Pipelie Maagemet. The data stored withi the Pipelie sessio attribute is the accessed by usig accessor methods/attributes withi Java scriptlets. Table 4-6 provides more detailed iformatio about these methods/attributes for OrderValue. Table 4-6 OrderValue Accessor Methods/Attributes Method/Attribute createddate idetifier orderstatus splittigpreferece specialistructios shippigaddress orderlies gettotal(it totaltype) Descriptio The date the customer s order was created. Key i the database for the order; the order cofirmatio umber. The status of the order. The splittig preferece for the order. Ay special istructios for the order. The shippig address for the order. A collectio of the lies i the shoppig cart that make up the customer s order. The total amout specified by the totaltype parameter. Valid parameters iclude: OrderCostats.LINE_UNIT_PRICE_TIMES_QUANTITY OrderCostats.LINE_SHIPPING OrderCostats.LINE_TAX Note: The gettotal() method also allows you to combie differet total types. For more iformatio, see the Javadoc Registratio ad User Processig Package

141 JavaServer Pages (JSPs) Table 4-7 describes the accessor methods/attributes available withi the shippigaddress attribute of OrderValue. Table 4-7 shippigaddress Accessor Methods Method/Attribute getstreet1() getstreet2() getcity() getcouty() getstate() getpostalcode() getcoutry() Descriptio The first lie of the customer s street address. The secod lie of the customer s street address. The city i the customer s address. The couty i the customer s address. The state i the customer s address. The zip/postal code i the customer s address. The coutry i the customer s address. Table 4-8 describes the accessor methods/attributes available for each OrderLie of the OrderLies attribute. Table 4-8 OrderLie Accessor Methods Method/Attribute getproductidetifier() getdescriptio() getquatity() getuitprice() Descriptio The ame (idetifier) for the shoppig cart item. A descriptio of the shoppig cart item. The quatity of the shoppig cart item. The uit price for the shoppig cart item. The getuitprice() method also has accessor methods/attributes that you ca use. These are show i Table 4-9. Table 4-9 getuitprice() Accessor Methods/Attributes Method/Attribute getcurrecy() Descriptio Obtais the currecy associated with the amout. Registratio ad User Processig Package 4-17

142 4 Customer Self-Service Table 4-9 getuitprice() Accessor Methods/Attributes Method/Attribute getvalue() Descriptio Obtais the value of the amout. Listig 4-4 illustrates how these accessor methods/attributes are used withi Java scriptlets alog with the WebLogic Server JSP tags to display the iformatio. Listig 4-4 Usig Accessor Methods/Attributes Withi orderstatus.jsp Java Scriptlets <table border="0" width="90%" cellpaddig="5" cellspacig="0"> <tr> <td><div class="tabletext"><b>cofirmatio umber</b></div></td> <td><div class="tabletext"><%=ordervalue.idetifier%></div></td> </tr>... <tr> <td><div class="tabletext"><b>shippig address</b></div></td> <td><div class="tabletext"> <%=ordervalue.shippigaddress.getstreet1()%><br> <%=ordervalue.shippigaddress.getstreet2()%><br> <%=ordervalue.shippigaddress.getcity()%><br> <%Strig statezip = ordervalue.shippigaddress.getstate()+ "-" + ordervalue.shippigaddress.getpostalcode();%><br> <%=statezip%></div> </td> </tr> </table>... <wl:repeat set="<%=ordervalue.orderlies.iterator()%>" id="orderlie" type="orderlie" cout="100"> <table> <tr> <td> <div class="tabletext"> <%=orderlie.getproductidetifier()%> 4-18 Registratio ad User Processig Package

143 JavaServer Pages (JSPs) </div> </td> <td> <div class="tabletext"><%=orderlie.getdescriptio()%></div> </td> <td alig="right"> <div class="tabletext"> <%=quatityformat.format(orderlie.getquatity())%> </div> </td> <td alig="right"> <div class="tabletext"> <%=orderlie.getuitprice().getcurrecy()%> <%=WebflowJSPHelper.priceFormat(orderLie.getUitPrice(). getvalue())%> </div> </td> </tr> </table> </wl:repeat> Note: For more iformatio o the WebLogic Server JSP tags, see the JSP Tag Referece i the BEA WebLogic Persoalizatio Server documetatio. Form Field Specificatio No form fields are used i the orderstatus.jsp template. Registratio ad User Processig Package 4-19

144 4 Customer Self-Service paymethistory.jsp Template Sample Browser View The paymethistory.jsp template (show i Figure 4-4) allows the customer to view iformatio regardig the paymets that have bee made. This iformatio icludes the date, the paymet trasactio ID, the credit card used, ad the amout that was billed to the credit card. Figure 4-4 shows a aotated versio of the paymethistory.jsp template. The dashed lies ad umbers i the diagram are ot part of the template; they are refereced i the explaatio that follows the scree shot. Figure 4-4 Aotated paymethistory.jsp Template 4-20 Registratio ad User Processig Package