sap enterprise portal 5 0 the iview advantage

7/22/2019 SAP Enterprise Portal 5 0 the IView Advantage

http://slidepdf.com/reader/full/sap-enterprise-portal-5-0-the-iview-advantage 1/80

SAP AG 2002, Title of Presentation, Speaker Name 1

Version: July 01, 2002

The iView Advantage

Features and Technology of the iViewServer as part of the SAP Enterprise Portal 5.0

Please download the presentation to get access to the notes!




Content

iView Technology: Overview and Benefits

Downloading iViews from the SAP iViewStudio™

Importing / Exporting iViews

Creating iViews using the iViewCatcher

Developing .Net and Java iViews

Creating iViews using the iViewEditor

The Master iView Concept

Integrating Third Parties: Examples




Content












What is an iView?

An iView is a sel f-contained, .NET or Java based presentation

element.

Is a the basic unit of portal content – a small application that displays

information

iView information can be in any format

(texts, figures, graphs, reports , tables, charts etc.)

iViews can be interactive, allowing you to perform business functions

iViews can display information from any data source (corporate

systems, databases, the Internet, Yahoo! etc.)




The iView Advantage

iViews go far beyond just pushing static content to the user. iViews

allow users to ask questions, such as:

„ Show me the top ten customers where the shipment is late“

„ Show me last year’s sales figures for my district“

„ Give me a list of customers who have not ordered a product in the past

three months“

iViews help users to find related data in other applications by using

SAP’ patented Drag and Relate technology

iViews have a consistent look and feel

iViews are based on a platform that insulates

developers and users from any complexity

Hundreds of available iViews can be downloaded

from the iViewStudio




iViews: Business Benefits

User

iViews can answer very complex questions = real added value for the

portal user!

Users can customize iViews without any programming ski lls!

Developer

iViews can easily be downloaded from the iViewStudio:

Hundreds of iViews available!

No development effort at customer site

iViews can be developed in any programming language you want

Technology

iViews are processed simultaneously, both on theclient and server side (“ parallel processing” )

iViews are based on open standards




Examples of iViews

iViews are designed to provide useful

information and business data.

iViews are designed to provide useful

information and business data.




Examples of Mobile Applications (iViews)

ReportsReports

Self-ServicesSelf-Services




Types of iViews (1)

.Net iViews

.NET iViews are written in a programming language which support the

.NET platform, typically XML and ASP.

Yahoo! categories can be imported into the Enterprise Portal as .NET

Custom iViews.

The iViewCatcher enables you to capture predefined HTML content

objects from permitted Web sites (such as your organization 's intranet)

to create .NET iViews based on these objects.

Java iViews

Java iViews are written in a programming language which supports the

Java platform, JSP or Java.

Java iViews run on the Java iView Runtime

SAP ships Java iViews with its Business Packages




Types of iViews (2)

External Services

External Services are normally displayed in the Portal as

full-page iViews, unlike most Java iViews.

External Services are not run by the iViewServer Runtime. For example,

an External Service presenting an R/3 transaction, runs on an InternetTransaction Server (ITS).

Master iViews Master iViews are not displayed in a page of the Enterprise Portal.

Both Java iViews and External Services inherit their properties from the

Master iView upon which they are based.




Personalizing iViews

The user can personalize iViews to see the precise information they

want, such as show me my customers where the shipment is late.

Benefits

No programming skills necessary

High user satisfaction because the user can customize

the portal without any programming effort.

Due to this satisfaction the portal is highly accepted.

The portal brings added value to the user because the

user gets exactly the information that he or she needs.




Examples of Personalized iViews

MyWeather MyWeather

Birthday List of My TeamBirthday List of My Team

Show me all my customerswhere the shipment is late

Show me all my customerswhere the shipment is late

Show me last year’s sales

figures for my district

Show me last year’s sales

figures for my district




Personalizing Java iViews: Process

3

2Birthday

2002-01-21 to 2002-03-03

Birthday

2002-01-21 to 2002-03-03

1

Birthday

2002-01-21 to 2002-04-28

Birthday

2002-01-21 to 2002-04-28




Personalizing Yahoo! iViews: Process

PortalPortal

Link to

myYahoo! User

Link to

myYahoo! User

1

2 3




Moving Beyond Static Content (Eventing)

Eventing allows iViews to exchange data with each other, for

example, you choose a material in one iView and the bill of materialsand the technical drawing appear in a second and third iView.

Benefits:

The portal page shows the exact content that the user needs. Consistent, real-time data iViews are not isolated from each other.

Thus, if one iView is refreshed, the other iViews do

not become invalid.




Moving Beyond Static Content (Eventing) (1)

Choose material

(PLM system)

Choose material(PLM system)

Material (structure and details)

appears automatically.

Material (structure and details)

appears automatically.

1

2




Moving Beyond Static Content (Eventing) (2)

Documents attached to the

material appear automatically.

Documents attached to the

material appear automatically.

Choose materialChoose material 3

4




Content












The iViewStudio

The iViewStudio is a Web site where users can download content

and developers can share content and access information about allaspects of creating iViews.

Benefits

Business Packages available for download without any programingeffort

iViews cover both Web services and enterprise applications

iViews were designed by experienced consultants and

provide unparalleled added business value

Developers can share information among each other

Informations how to build your own portal content




Information about EP 5.0,

Content and iViewStudio

Predefiend content for EP 5.0,

mySAP workplace and EP 4.0/4.5

Information and Tools

for content developers

our partner program

informations & benefits

Information about OEM partnershipsSign in to iViewStudio

iViewStudio Overview

iViewStudio - the Leading Portal Content MarketplaceiViewStudio - the Leading Portal Content Marketplace




Example: Business Package for Manager Self Services

Target audience

Managers with line and staff

responsibilities

Suitable for every industry

People / Target Group

Team leaders

Project leaders

Department heads

...

Content

People management

Budget management




Content












Importing and Exporting iViews

iViews can be imported from and exported to

The iViewStudio

Another deployed Enterpr ise Portal

Yahoo! categories can be imported as iViews

Benefits Customers can download iViews from the iViewStudio and

import them very easiliy to the Enterprise Portal

Developers can export and import iViews from a test

portal to a productive portal

Import of Yahoo! categories without advertisement




Importing and Exporting Content: Overview

File system, CDFile system, CD

iViewServer Database

Application 1 Application 1 Appl icat ion 2 Appl icat ion 2

http://www.iViewStudio.comhttp://www.iViewStudio.com

iView connector iView connector iView connector iView connector

Export of iViewsto another

deployed portal

Export of iViewsto another

deployed portal

Import

http://www.iviewstudio.com/







Importing Content from the iViewStudio

The following objects can be imported via the Role Editor

Roles, Worksets, Pages, Java iViews, .Net iViews, External Services,Master iViews

File System

Import iViewImport iView

Download

Content

Download

Content

www.iViewStudio.comwww.iViewStudio.com








Importing Yahoo Categories using the iViewEditor

Read-in

Categories

(on-the-fly)

Read-in

Categories

(on-the-fly)

Yahoo! iViewsYahoo! iViews




Exporting Objects via the PCD

The following objects can be exported from the Portal Content

Directory (PCD) Roles, Worksets, Pages, External Services, Master iViews

Export is done through a package (.pkg)

Dependent PCD objects

can be exported

Dependent PCD objects

can be exported




Content












iViewCatcher

The iViewCatcher enables administrator and developers to create

.Net iViews based on permitted Web sources such as Corporate Intranet

Corporate Web applications

Permitted Web Sites

The iViewCatcher must not be used to capture content from non-

permit ted (Web) sources!

Benefits

Content of existing Intranet or Extranet pages can easily

be integrated – without any programming skills.

The captured iView always displays the actual content

(no copying of the content!)

Rendering is also possible for captured iViews to

get a consistent look and feel of the Portal




iViewCatcher: Browse Mode

SAP Help Portal

http://help.sap.com

SAP Help Portal

http://help.sap.com

http://help.sap.com/







iViewCatcher: Capture Mode

Simply mark the

area to be captured

Simply mark the

area to be captured

Reduces or expands

the focus of the

selceted object

Reduces or expands

the focus of the

selceted object




iViewCatcher: Copyright Conditions

SaveSave

Note: The iViewCatcher enables the creation of iViews based on permitted Web sources.Content made available on many external web sites are protected by copyright laws.Copyright laws prohibit the copying, redistribution, retransmission, or publication of

material, unless otherwise permitted by the copyright ow ner!

Note: The iViewCatcher enables the creation of iViews based on permitted Web sources.Content made available on many external web sites are protected by copyright laws.Copyright laws prohibit the copying, redistribution, retransmission, or publication of

material, unless otherwise permitted by the copyright ow ner!




iViewCatcher: Result

Captured iViewCaptured iView

Copyright protectionCopyright protection




Content












What is the iView Editor?

SAP' iView Editor allows users to quickly and easily create iViews for

enterprise portals: .Net iViews

Java iViews

External Services

Like a wizard, developers can easily create iViews that access

structured data from enterprise applications, as well as legacy

applications or Web resources.

Benefits

Simple creation of iViews, no special programing

skills necessary

One central place for administrating all of the

metadata of an iView

Developer can determine the level of

iView personalization




Creating a Java iView Using the iViewEditor:Enter Name and Title, Choose Channel

2




Creating a Java iView Using the iViewEditor:Set Width and Height

Display of the

iView title bar

Display of the

iView title bar

Defines the heightof the iView

Defines the heightof the iView

Defines the width of the iView

in relation to the width

of the Portal content area

Defines the width of the iView

in relation to the width

of the Portal content area




Creating a Java iView Using the iViewEditor:Define Cache and iViewServer Parameters

Determines how the

Portal server handles

requests from the iView

Determines how the

Portal server handles

requests from the iView

Defines how the iView is

handled by the iViewServer

Defines how the iView is

handled by the iViewServer




Creating a Java iView Using the iViewEditor:Choose SAP Transaction and Logical System

Choose SAP

Transaction

Choose SAP

Transaction

Choose SAPLogical SystemChoose SAP

Logical System




Creating a Java iView Using the iViewEditor:Choose SAPGUI and Enter Transaction

Choose

SAPGUI Type

Choose

SAPGUI Type

Enter Transaction

Enter Transaction




Creating a Java iView Using the iViewEditor: Result

iViewiView




Creating a .Net iView Using the iViewEditor (1)

General

information

General

informationSupported

browsers

Supported

browsers

Data source

for user

mapping

Data source

for user

mapping





Look and

Feel of the

iView

Look and

Feel of theiView

Fine tuning of

the iView

performance

Fine tuning of

the iView

performance

Caching: successive

identical requests are

loaded from the cache

Caching: successive

identical requests are

loaded from the cache

Refresh rate for

each iView

Refresh rate for

each iView




ht t p: / / www. f edex. com/ cgi - bi n/ t r acki ng?t r acknumber s=#t r acki ng#&act i on=#act i on#&l anguage=#l anguage#&cnt r y_ code=#cnt r y_ code#


Location of

the iView

Location of

the iView

Enter the URL and

Parameter from where the

iView gets its content

Enter the URL and

Parameter f rom where the

iView gets its content

http://www.fedex.com/cgi-bin/tracking?tracknumbers=

http://www.fedex.com/cgi-bin/tracking?tracknumbers=





Default value

provided for the

parameter

Default value

provided for the

parameter

Parameters

defined as URL

arguments

Parameters

defined as URL

arguments

Defining the

PersonalizationParameters

Defining the

PersonalizationParameters

Specifies whether the user will

be able to edit the parameter in

the personalitzation dialog

Specifies whether the user will

be able to edit the parameter in

the personalitzation dialog





The range of possible values for personalization parameters are

defined in the Parameter Editor.

If no values are defined the user can choose any value.

Al lows the user

to choose any

number between

500 and 2000

Allows the user

to choose any

number between

500 and 2000

Define range

of values

Define range

of values




Creating a .Net iView using the iViewEditor (6)

Text Box

Radio Button

Popup List

PersonalizePersonalize




Content












What are .Net iViews?

A .Net iView is an open feature for integrating data f rom a variety of

data-sources into the Enterprise Portal based on Microsoft’s .NetPlatform.

Types of .Net iViews in the Enterprise Portal:

"As is“ .Net Custom iView

Rendered .Net Custom iView

Benefits

The SAP iViewServer runs both.NET iViews

as well as Java iViews

Developers can develop their iViews in their preferred

programming language (for example: ASP)

SAP provides the SAP XML to get

a consistent look and feel of all .Net iViews




.Net iViews: "As is" iViews vs. Rendered iViews

"As is" Custom iViews retrieve information and display it as it

appears on the source site. Data will not have the SAP Look and Feel

Rendered Custom iViews retrieve data from a data source and

display it with the SAP look and feel.

Precondition: the iView must format the results as SAP XML

Page Builder

.Net iViews

"As is" Rendered

SAP

XML

iViewServer




.Net iViews: Examples

Free Text

Matrix

Single Field

Rendered

iView

Rendered

iView

"As is"

iView

"As is"

iView




.Net iViews: The SAP XML

<busdoc>

<header/><dataset>

<constructor language="HyperRelational">

<properties>

<name>Employees</name>

</properties>

<return>

<HRRow id="matrix" position="0" dispRows="3" useScroll="1">

<HRField><aliasName>Full_Name</aliasName>

<label>Full Name</label>

<type>string</type>

</HRField>

<HRField>

<aliasName>Salary</aliasName>

<label>Salary</label>

<type>number</type></HRField>

</HRRow>

<controlStrip type="toptier" counter="yes" firstRec="yes" position="right" />

</return>

SAP created its ‘flavor’ of XML, for

the purpose of sending data to thePortal.

SAP XML gives you the power to

turn data from other applications to

HyperRelational.

SAP created its ‘flavor’ of XML, for

the purpose of sending data to thePortal.

SAP XML gives you the power to

turn data from other applications to

HyperRelational.




What are Java iViews?

Java iViews are independent units of deployment and execution that

are assembled from three parts: Java code

Profile

Resources

Benefits

The SAP iViewServer runs both.NET iViews

as well as Java iViews

Developers can develop their iViews in their preferred

programming language (for example: Java, JSP)

SAP provides a rendering mechanism for allJava iViews to get a cons istent look and feel of all Java iViews




Hello World...

publ i c cl ass Hel l oWor l dComponentextends Abst r act Por t al Component

{

publ i c voi d doContent (I Por t al Component Request r equest ,I Por t al Component Response r esponse)

{r esponse. wr i t e( "Hel l o Wor l d" ) ;

}

}




Language Support

publ i c cl ass Hel l oWor l dComponentextends Abst r act Por t al Component

{publ i c voi d doContent (

I Por t al ComponentRequest r equest ,I Por t al Component Response r esponse)

{/ / f et ch t he cur r ent r esour ce bundl e

ResourceBundl e bundl e = r equest . get Resour ceBundl e( ) ;r esponse. wr i t e( "<t abl e><t r ><t d>") ;r esponse. wr i t e(bundl e. get St r i ng( STRI NG_CUSTOMNOTE) ) ;r esponse. wr i t e( "</ t d></ t r ><t r ><t d>") ;

}




Java iViews APIs

Set of interfaces defining the interaction between Java iViews and

Java iView Runt ime: Component

Display content, read request input parameters

Profile

Read/Store iViews’ prof ile.

Logger/Monitor

Log messages,

Monitor iViews activi ties and performance

Eventing

client/server eventing

Server/server eventing

CachingCaching content of iViews

Resources

Accessing external publ ic /pr ivate resources




Java iViews Look and Feel (HTMLB for Java)

The Java iView Runtime provides a set of standard elements for

applications based on servlets and JSPs. Uniform look and feel of Java iViews

No HTML within application

Browser independence




Content












What are Master iViews?

You use master iViews as a type of template for creating External

Services and Java iViews. Each Java iView and External Service is based on a Master iView

Benefits

You can create Master iViews serving as templates for

Java iViews

The adminis trator can preconfigure Master iViews so that

the properties are inherited to all Java iViews/External Services

based on those Master iViews (without any programming skills)

For example: you can assign a background color to the Master iView - > all

Java iViews based on that Master iView have the same background color

You can define the inheritance of properties between

a Master iView and a Java iView/External Service




Java iViews and Master iViews: Overview

You use master iViews as a type of template for creating External

Services and Java iViews.

The master iView knows which coding should be started when an

iView is called in the Portal. For example, a Java iView refers to a

master iView that knows that a transaction now has to be started in

the Portal.

The user can only see the Java iView or External Service in the

Portal. Once the master iView is in the PCD, you can access it by

using the following administration tools:

iView Editor (Content Admin iViews entry in the administrator role)

Role Editor (Content Admin Roles entry in the administrator role)




iView Editor: Java iView Wizard

Wizard offers generic templates for backend integration:

SAP Transactions SAP IAC‘s (Internet Application Component), SAP Miniapps

Business Warehouse Web Appl ications

Crystal Reports

BSP (Business Server Pages) Applications

and Integration of Web Adresses

Each Java iView is

based on a Master iView

Each Java iView is


Wizard for

creating Java

iViews basedon Master

iViews

iViewEditor iViewEditor




Role Editor: Wizard for External Services

Wizard offers generic templates for Backend Integration:

SAP Transactions SAP IAC‘s

SAP Miniapps

Business Warehouse

Web Applications

Crystal Reports

BSP (Business Server Pages)

Applications

and Integration of Web Adresses

Each External Service is


Each External Service is


Role Editor Role Editor

Wizard for

creating External

Services based on

Master iViews




Portal Component example: Hello World

Implementation Class: HelloWorld.java

Java iView Prof ile: default.properties

import com.sapportals.portal.prt.component.*;

public class HelloWorldextends AbstractPortalComponent {

public void doContent(IPortalComponentRequest request,

IPortalComponentResponse response){response.write("Hello World");

}

}

ClassName.value=HelloWorld

Title.value=Hello World Component

Deployment of Portal Components (1)




Deployment of Portal Components (1)(How Comes a Master iView Into the Portal?)

Once you develop a Java iView (e.g. in the PDK) and upload it into

the portal, a master iView is created.

To display that iView in the portal, you have to create

an iView using the iView Editor (the iView Editor creates the IVU file), or

An External Service us ing the Role Editor

Once a customer imports a Business Package, the IVUs fi les are

imported as well

-> No need to create a Java iView

-> The Java component appears both as Master iView as well as Java

iView (or External Service)

Deployment of Portal Components (2)




Deployment of Portal Components (2)(How Comes a Master iView Into the Portal?)

Portal Component

classes

profiles

mimes

(images,

scripts, ...).par (Portal Archive)

zip

Portal Content Directory

PAR Upload Tool

iView Runtime for JavaiView Runtime for Java

iView Runtime for Java

D

ownl o a d

( l o c al u p gr a d e )




Configuring the Parameters of Master iViews

Configuring a

Master iView

Configuring a

Master iView

The settings of master iViews can

be changed in the role editor




Configuring the Parameters of an External Service

LaunchTarget

LaunchTarget

If you create an External Service or Java iView from the

master iView, the values defined in the master iView are copied to the

External Service or Java iView.

Inheritance of Properties (Passing Properties to




Inheritance of Properties (Passing Properties toExternal Services and Java iViews)

Master iView M1

External Service S1 Java iView J1

..........External Service S11

in Role R1

External Service S12

in Role R2

Master iView passed properties to

External Service which

passes properties to

External Service

in role/workset




Portal Content Directory

property1=value1

property2=value3

property3=value4

Java iView 2

Java iView: Concept of Inheritance

iView Runtime for Java

PRT

Portal Services

API

Portal Component

Resources/Classes

Master iView

Java iView 1

MasterLink

Examples.WeatherComponent

PageBuilder /

.NET iViewServer

C o d e L i n k

property1=value1

property2=value2

property1=value1

property2=value3




Properties Maintenance

The properties of Master iView (prof iles) are stored in property files.

Types of properties:

Portal Component Properties (cannot be modif ied by the administrator)

Used by the Runtime for Java to determine how the component should be

executed (for example as a JSP or as a servlet)

Self-Defined Properties (can be modif ied by the administ rator):

Read and store user personalisation data

P t l C t P ti E l




Portal Component Properties: Examples

Contains a URL pointing to a page that allows to reach a specificEnd-User personalization dialog servi ce

PersonalizationLink

Contains a name of a class implementing IPortalComponent to

delegate personalization dialogue handling to

PersonalizationClass

The name of the component's resource bundle. Defaults to

"localization"

ResourceBundleName

Determines a binary parent reference onto another PortalComponent packageSharingReference

Title of the iViewTitle

Declares references onto Portal Services by a comma separated

list of serv ice names

ServicesReference

Determines access to this package using the SharingReference

property. Can be "shared" or "final"

SharingAccess

DescriptionProperty Name

* Group-specific properties must be defined in the group’s default profile ("default.properties")

S lf d fi d P ti E l




Self defined Properties: Examples

DescriptionPossible values Attr ibute name

non-final (default): Value can be changed by property

sets that follow in the MasterLink chain.

non-final

final: Value can not be changed by property sets that

follow in the MasterLink chain.

finalinheritance

The property values are stored only once (globally)

and not by user. Value is maintained by the

administrator.

none

The property is not visible in a generic

personalization dialog, but in a more compl icated

personalization d ialog (for example a wizard). Default

Values can also be changed by the administrator.

no_dialog

The property is shown by generic personalizationdialogs and stored for each user. Default Value for

personalization dialog can be changed by the

administrator.

dialogpersonalization

P idi P li ti




Providing Personalization

Three types of Personalization:

Standard personalization (generic dialog) Own implementation of a personalization dialog

Use an URL that point to an exterior si te with a personalization of its

own (for example Yahoo!)

Hello Person…: Example of Personalization in a




Hello Person…: Example of Personalization in aProperty File

import com.sapportals.portal.prt.component.*;

import com.sapportals.portal.prt.session.IUserContext;

public class HelloPersonextends AbstractPortalComponent {

public void doContent(IPortalComponentRequest request,IPortalComponentResponse response){

IPortalComponentProfile userProfile =request.getComponentContext().getProfile();

String userName =userProfile.getProperty( userName );

response.write( Hello +userName);}

}

ClassName.value=HelloPerson

Title.value=Hello Person Component

userName.value=Surname

userName.personalization=dialog

Implementation Class

Property File

Personalization of User Name

appears in generic dialog.

C t t




Content









Integrating Third Parties




Integrating Third Parties

SAP does not only display third-party functionality or content. SAP

integrates them in the user’s workflow in the Portal. For example: WebEx meetings are scheduled using the user’s Outlook

account.

SAP offers

Integration by means of iViews into the portal platform

Integration into SAP’ KM Platform For example: Documentum documents can be managed and retrieved by the

Content Management and Retrieval and Classification functionality.

Benefits

Using applications in the Enterprise Portal

is much more beneficial than using them separately. The integration of third parties is offered as out-of-the-box functionality.

Example: Integration of MS Exchange and Lotus




p g gDomino

Par t of the Communication Package

http:/ / w w w .iV iew Studio.com

Par t of the Communication Package

http:/ / w w w .iV iew Studio.com

E-Mail ListE-Mail List

E-Mail

Folder List

E-Mail

Folder List

E-Mail

Details

E-Mail

Details

Calendar Calendar

Example: Integration of Documentum




Example: Integration of Documentum

Par t of the Business Package f or

Documentum Connectiv ity http:/ / w w w .iV iew Studio.com


Documentum Connectiv ity http:// w w w .iV iew Studio.com

Documentum

Inbox

Documentum

Inbox

Example: Integration of Oracle Applications
































































Example: Integration of Oracle Applications

Dicussion

Center

Dicussion

Center

Expense

Report History

Expense

Report History


Or acle Connectiv ity http:/ / w w w .iV iew Studio.com


Or acle Connectiv ity http:// w w w .iV iew Studio.com

All Assets All Assets

Copyright 2002 SAP AG All Rights Reserved



























































© Copyright 2002 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express

permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other

software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of

Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®,

OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix

and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and

other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium,

Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented andimplemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI,

SAPPHIRE, Management Cockpit, mySAP, mySAP.com, and other SAP products and services mentioned herein as

well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other

countries all over the world. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Markets and

Commerce One. All other product and service names mentioned are the trademarks of their respective owners.

Copyright 2002 SAP AG. All Rights Reserved