04 Sample Application Overview

Broadvision 8.1 Kukini Development

Lesson 4 –Sample Application Overview

© Copyright 2007, BroadVision Inc. All Rights Reserved Company Confidential and Proprietary

Course Agenda

• Lesson 1 Introduction and Overview• Lesson 2 System Configuration• Lesson 3 Developement Architecture• Lesson 4 Sample Application Overview• Lesson 5 Foundation Components Overview• Lesson 6 Building New Features• Lesson 7 Integrating to Foundation App/Website• Lesson 8 Best Practices

© Copyright 2007, BroadVision Inc. All Rights Reserved Company Confidential and Proprietary3

Agenda

• Overview• Setting up the Sample Application• Site Structure• Kukini Commerce Pack• Foundation AA’s• Summary


Overview


Overview

• The kukini-commerce sample application is afictional commerce site that allow users to shop foritems, perform searches, register, login, andpurchase goods. These functionalities were builtusing the XFlows, automated actions, and XFormsin the kukini-commerce pack.

• The application is included with a copy of KukiniWorkbench.


Overview

• Use Kukini-commerce sample application,– To reuse the out of the box Automated Actions– To understand best practices for developing a site

using Kukini Workbench


Setting Up the Sample Application


Setting up the sample application

• Run ‘load_shell’ script• Windows

– $BV1TO1/apps/shell/setup/bin/load_shell.cmd• Unix

– $BV1TO1/apps/shell/setup/bin/load_shell.sh


Site Structure


Kukini Sample Application – Home Page

Header

Zone2 Zone4

Zone3 Zone5

Footer

Zone 0

Zone1

Main Navigation Menu


Site Structure

• User templates– To define basic configuration parameters for user

and visitor accounts. A user template determinesaccess to top-level pages (the menu items in thekukini-commerce sample application).

• Channels– Channels are represented in the kukini-commerce

sample application as top-level pages . Sub-channels can also be created in the kukini-commerce sample application and are displayedas menu items below the selected menu item(channel) as you navigate through the site.


Site Structure (Continued)

• Display templates– To render the contents of top-level pages using

Div mapping and by referencing XFlows. The useof display templates facilitates XFlow selection forchannel and program administrators by includingdescriptive information about the content theyrender.

• Programs– To deliver information. Channels and sub-

channels contain these programs.


Main Navigation Menu

• The channels associated to the User Template isdisplayed as the Main Navigation menu (underheader)

Note:- Page types are not used in the sampleapplication. Instead channels are linked to UserTemplates and appear as the Main NavigationMenu


Body

• The Body is divided into 6 zones(zone0…zone5). When user clicks on a channelfrom Main Navigation menu, the programsmapped under the DIV mapping of the channelwill be displayed inside the body into theirrespective zones.


Channel DIV Mapping -BVMC


Channel DIV Mapping –Sample Application


Kukini Commerce Pack


Kukini Commerce Pack

• The kukini-commerce pack can assist developers increating applications by eliminating the need tocreate code for commonly required functionalities.

• The pack consists of:– The sample application that demonstrates what

you can do with Kukini– XFlows for commonly-needed application feature

flows.– Automated actions for routine tasks, such as

authorizing users.– XForms to present information.


Foundation AA’s


Foundation AA’s

• Included in the kukini-commerce application pack• Can be considered working samples• Show best practices• Implement frequently needed functionality• Allows customers to jump-start their own application

packs


Content AAs

• CategoriesReadAction– Retrieves a list of child categories for a specified parent.

• ContentReadAction– Retrieves the XML for a specific content item.

• ContentsReadAction– Reads and returns the contents of a category as a paginated list.

• DataByQueryAction– This Foundation AA enables the retrieval of database records usingSQL statements.– Can use pageflow variables in SQL statement.

• RuleSetReadAction– Executes a rules set and returns the results as a paginated list.


Navigation AAs

• CategoryBrowseAction– Retrieves a category tree suitable to displaying a categorybrowse.

• very similar to CategoriesReadAction• ChannelBrowseAction

– Retrieves a channel tree suitable for displaying a channelbrowse.• indicates whether channel/program is selected.• constructs a pageflow URL with parameters

• ProgramReadAction– Reads the details about a specific program, it also allowsthe content pointed to by the program to be retrieved.


Summary

• Overview• Setting up the Sample Application• Site Structure• Kukini Commerce Pack• Foundation AA’s

04 Sample Application Overview

Documents

Transcript of 04 Sample Application Overview