02 SAP NetWeaver Web Dynpro for Java © 2008 SAP AG © 2008 William D. Haseman 1 Lecture 01 Overview of SAP NetWeaver Overview of Enterprise Portals SAP

02 SAP NetWeaver Web Dynpro for Java

© 2008 SAP AG© 2008 William D. Haseman1

Lecture 01

Overview of SAP NetWeaverOverview of Enterprise Portals

SAP NetWeaver Web Dynpro for Java

Lecture 01 – Background

02 SAP NetWeaver Web Dynpro for Java© 2008 SAP AG

© 2008 William D. Haseman2

SAP NetWeaverTM




SAP NetWeaver

SAP NetWeaver is a single integration platform Leverages core SAP’s strengths

Proven, missions critical Integrated out of the box

Low TCO Delivers the foundations for all application needs

Complete Built to extend SAP and to integrate non-SAP

Open, standards-based




NetWeaver Components

1

2

3

4

5

6

7 8




1. SAP Web Application Server (WAS)

Application Platform Provides a way to develop JAVA applications

and ABAP applications that can easily reach back into the world of ABAP code

Provide the premier interactive development for the J2EE platform




WAS Features

SAP NetWeaver Developer Studio Eclipse-based IDE (JAVA based) Environment is enhanced with plug-ins that provide

specific functions for developers A PDK which plugs into Visual Studio for .NET

developers J2EE 1.3 Support

Release 6.40 provides full support for the J2EE 1.3 platform

ABAP Engine Allows you to develop and run ABAP applications

within the server




WAS Features

Web Dynpro Creates professional user interfaces while

minimizing manual coding Uses visual design tools and reuses UI components Users Model-View-Controller architecture, clear

separation between UI and backend services Open SQL

An abstraction of the database that allows more platform independence than JDBC

Allows a direct relational interface or an object-based interface to access data with little work on the part of the developer




WAS Features

Java Dictionary Incarnation of the ABAP dictionary in the

J2EE world Java Development Infrastructure

Overcomes the limitations of file-based control systems

Uses design time repository and component build services to eliminate complete recompiles for small code changes




2. Exchange Infrastructure (XI)

A platform for process integration based upon the exchange of XML messages Provides a technical infrastructure for XML-based

messages exchanges in order to connect SAP components with each other, as well as non-SAP components

Delivers business-process and integration knowledge to the customer, in the form of SAP predefined business scenarios

Provides a tool set for building new scenarios




XI




3. Master Data Management (MDM)

Is designed to provide a unified view of data from a distributed and heterogeneous environment

It is a tool kit to do any or all of these Have a central repository that is a master

copy of all the data Have a virtual master or central copy of all

the data in a unified schema




MDM




4. BI - The Solution at a Glance




Key Capabilities

Data Warehousing – BW Administrative Workbench Extraction, transformation and loading Data warehouse management Business modeling

BI Platform Online analytical processing (OLAP) Data mining Alerting Meta data repository Planning framework




Key Capabilities

BI Suite of Tools – BW Business Explorer Query design Managed reporting and analysis Visualization – web application design Collaboration

Pre-configured Business Content




5. SAP Enterprise Portal (EP)

Provides an integrated, single point of access to heterogeneous IT systems

Role-based content and collaboration tools Integrates people with information - knowledge

management of unstructured data and unification of structured data

Provides window to data both inside and outside their organization and provides tools for managing it

Provides predefined content (Business Packages) and building blocks (templates)




EP Components

iView technology For creating and administering iViews Customers can used iViews delivered by SAP or

create their own graphically or using JAVA, JSP, .NET, ASP languages

Role technology Portal pages (made of iViews) of a particular task or

area are bundled as roles Individuals can be assigned one or more roles,

gaining access to those pages that are appropriate




EP Components

Unification technology Facilitates unified access to enterprise applications

to enable Drag and Relate operations Page builder

Renders HTML pages which allows user interaction User management

Single sign on to all systems Use role management

Create users and assign then roles




Example iViews




EP Screen




Enterprise Portal Design Tools




Portal Content Studio




Visual Composer




Developer Studio (Web Dynpro)




Developer Studio (JAVA/PDK)




Visual Studio (.NET PDK)




Knowledge Management

To tap the contents of text documents by structuring and classifying them so relevant information is available Content management – functions for

authoring and publishing information in portals – uses WevDAV and XML

TREX – information retrieval solution – finds text quickly and builds taxonomy tree

Collaboration Room and Real-time collaboration (RTC) – supports teams




Different Users Need Different Information




SAP EP is that Central Point




SAP NetWeaver KM

“It is impossible to centralize all the information in a single repository”

Knowledge Management provides One search capability One unified navigation scheme One look and feel One access to KM services on top of distributed

repositories KM consists of

Content Management Search and Classification (TREX)




6. Solutions for Mobile Business




7. CAF

Composite Application Framework

A model-driven development environment that allows applications to be assisted by the use of modeling to describe the structure of the application so that code and interfaces of various sorts can be generated.




8. SAP Life Cycle Management

Standard off-the shelf process Code is written Code is documented Code is tested Bugs are found, new versions may be

published Code needs installation scripts Need the ability to apply patches




Overview of Enterprise Portals




Portal Content Objects

iView Program that retrieves data and displays it in the

content area Page

Contains layout and content (iViews) Workset

Collection of tasks, services and information that is part of a role

Role Collection of tasks, services and information

available for a group of users, determines what can be accessed, provides visualization and navigation




Portal Content Objects

Group

iView

WorksetUser

Role

Page

iView




Typical Object Assignments

Pages include iViews Worksets include iViews and pages Roles include worksets Groups include users Roles are assigned to users or groups




Portal Content Directory (PCD)

All content objects are stored in the PCD Delta links – object reuse Creation of relationships between objects Generic transport mechanism Personalization Object notification Versioning Permissions to use access control lists (ACLs) Filter mechanism and search




Hierarchical PCD Structure

Root Folder

Sub Folder 1

Sub Folder 2

Sub Folder 3

Sub Folder 3A

Sub Folder 3B

Page

Workset

iView





Content → Content Administration Navigation panel (left)

Tabs – Browse or searchPortal content tree – shows PCDQuick info – describes properties of object

selected





Editing area is displayedObject tabs – select one of multiple

objects you are editingObject editor tools – changing actions and

operationsObject editor – allows editing the objectChild object editor – edit child objectsProperty editor – customize the properties




Reusing Objects

Copy an object In the portal catalog, you can create a new

object by copying an existing object and pasting it elsewhere as an object

You can insert one content object into another object as a copy

Once the copy is made, there is no future relationship between the two objects




Reusing Objects

Create Delta Links Create an object based on a template – new

object inherits all the properties of the original and is delta linked

In the portal catalog, you can create a new object by copying and existing one and pasting them as a delta link

You can insert one content object into another object as a delta link




Delta Link

Properties are object parameters that permit the configuration and personalization of content in the portal

These properties get set in the property editor When a new object (target) is delta linked to

another (source), it inherits it’s properties If the properties of the source is changed, the

properties of the target will also change If you change the targets properties, those

properties will no longer be delta linked




iViews For SAP Applications

You can integrate the following SAP applications in SAP EP iViews SAP Transactions Internet Application Components (IACs) Business Server Pages (BSP) applications WebDynPro and Visual Composer applications SAP BW reports Generic databases RSS Feeds URLs




R/3 Transaction




Integrated SAP Systems

SAP Transaction – R/3 Transaction Codes SAP GUI for HTML SAP GUI for Java SAP GUI for Windows

SAP IAC – Internet Application Components ITS

SAP BSP – BSP’s with Web WAS 6.1 SAP WEB – Web Dynpro with WAS 6.3 SAP BW Report – SAP BW




Naming Conventions

Each PCD object has a unique name made up of the following: Complete path to the object

pcd:pottal_content/BusAdm746/S903000/…. Optimal namespace prefix (do not use in

this course) Base name of the ID

iView001




Demonstration

Browse portal catalog Create folder in the portal catalog Working with iViews

Use existing iViewsCopyDelta link

Create iViews (templates)Web-based URL iViewsR/3 Transaction




Working with Pages

A portal page holds iViews and pages organized in a layout

User can arrange content on the page by moving iViews (and pages) from one container to another (they can not alter arrangement of containers)

They can select a different layout, with a different arrangement of containers




Out of the Box Layouts

Predefined layouts: 1 column (full width) 2 columns (equal width) 2 columns (narrow:wide) 2 columns (wide:narrow) 3 columns (narrow:wide:narrow)

You can create new layouts based upon these




Demonstration

Creating a portal page




Roles

Role A role is defined to provide access to a set of

common tasks A user or group of users are then assigned to that

role Role is the largest semantic unit within content

objects A user can only access content for which they have

been assigned a role Role structure defines the navigation structure




Worksets

Lets you bundle iViews and pages in folder hierarchies

A workset is always part of a role A workset can belong to more than one role You can not assign worksets to users




Roles and Worksets

Role can contain the following objects: Roles Worksets Pages iViews Templates for pages and iViews

Worksets can contain the following objects: Worksets Pages iViews Templates for pages and iViews




Creating a System

A system definition provides the connector or “middleware” that allows that system to talk to EP

Methods for creating a system Existing template System Landscape wizard Copy and paste an existing system

Content developers reference a system through an alias




View a System in Landscape




System Property Editor




Your Turn – Lab 01

Portal structure Create folders Copy iViews Delta Link iViews Create web based iViews Create R/3 based iViews Create pages

Documents

02 SAP NetWeaver Web Dynpro for Java © 2008 SAP AG © 2008 William D. Haseman 1 Lecture 01 Overview of SAP NetWeaver Overview of Enterprise Portals SAP