EP200 Day 1

Welcome to EP200 (Day 1)

SAP NetWeaver EP

2

Agenda

• Enterprise Portal Overview

• Technical Architecture

• Portal Content Directory

• Portal Objects

• Business Packages

3

Agenda




• Portal Objects


4

Enterprise Portals are revolutionizing the corporate desktop by replacing the windows based, single user interface with a web-based collaborative interface. Today, portals provide “at the glass integration” and a single point of entry to all information, people and tools a person needs to do his/her job.

Corporate desktop:Many isolated windows and siloed applications

No windows based interface

The Portal: single entry point with organized, integrated, personalized portal

User Experience1980’s 1990’s 2001

What is an Enterprise Portal?

5

A robust Enterprise Portal enables an enterprise workspace in which employees, customers, and suppliers have anytime, anywhere access to the information, people, and tools they need to conduct their business with the enterprise. All that will be required is a

web-enabled device.

BusinessTo

Employee

BusinessTo

Consumer

BusinessTo Business

Enterprise Workspace

B2CAllows a business to interact directly with its customer via an online interface.

B2BAllows two or more organizations to conduct business together via an online interface.

B2EAllows employees to conduct daily tasks, keep up on organizational news and complete self service functionality via an online interface.

Enterprise Portal

The internet has expanded the bounds of enterprise computing, forcing enterprises to extend the reach for their systems to customers and suppliers. We refer to this new paradigm as the Enterprise Workspace.

The Enterprise Workspace

6

History of the SAP Enterprise Portal

– Originally, TIBCO Corporate Yahoo! Portal was to be the SAP Enterprise Portal.

– In 2000, SAP purchased TOPTier to provide platform for the Enterprise Portal.

– SAP purchased InQMy to provide J2EE Engine.

– Enterprise Portal 5.0 utilizes TopTier architecture. Later service packs utilize InQMy J2EE engine. Portal platform is Windows only.

– Enterprise Portal 6.0 is supported on both Unix and Windows. TOPTier architecture is phased out.

• Enterprise Portal no longer requires combination of file system, LDAP and database to store data.

• Enterprise Portal no longer requires lock-server to manage file system in a clustered environment.

– Netweaver solution offered by SAP featuring Enterprise Portal….

7

Enterprise Portal Powered by SAP Netweaver

SAP NetWeaver™

Co

mp

os

ite

Ap

pli

ca

tio

n F

ram

ew

ork

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus. Intelligence

Master Data Mgmt

PROCESS INTEGRATION

Integration Broker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAP

Life

Cy

cle

Mg

mt

•SAP Enterprise Portal Powered by SAP NetWeaver

– Web-based, role-based, secure access

– Integrating any kind of structured information

– The frontend to the SAP World

– Sophisticated navigation possibilities

– Wide platform support, wide language support

– Built on open standards

– SAP EP encompasses portal, KM and Collaboration

Knowledge Mgmt

Content Provided by SAP

8

Agenda




• Portal Objects


9

Main components of the Enterprise Portal

Portal PlatformPortal Platform Knowledge ManagementPlatform

Knowledge ManagementPlatform

Portal Framework

Portal Framework

Unification Unification

Connector FrameworkConnector Framework

Real-Time Collabo-ration


Retrieval & Classification

(TREX)


(TREX)

Content Management

(CM)

Content Management

(CM)

Content Provided by SAP

10

SAP Enterprise Portal 6.0 - Architecture

• Open Portal Platform

– Support of Internet standards like LDAP, Java, X.509,.Net, XML, JCA, JAAS.

– Web service support (SOAP, UDDI)

– Portal services like auditing, logging, caching, rendering, personalization service.

– Open APIs

– Secure environment

• Open KM Platform

– Applications around unstructured information

– People-centric collaboration

– Enterprise content management

• Patented Unification Technology

– Drag&Relate operations between heterogeneous apps

• Open Development Platform

– Web-based definition of worksets, roles, layout, etc.

– Portal Content Studio for code-free development of portal content

– Portal Development Kit for developing portal content

Technical Portal Services

User Mngmt.Service

Audit, Log,Monitoring

Personaliz.Service

SOAP

CachingService

Portal Content Catalog

WorksetsRolesPages LayoutiViews SystemLandscape

NotificationService

RenderingService

LDAP

XML

HTTP/HTTPS

Unification

Database Unifier

Database Unifier

ApplicationUnifiers

Knowledge Management

Real-timeCollaboration

Retrieval&Classif.

ContentMngmt.

WebDAV

ICE

JDBC

FTP

SAP Enterprise Portal

Browser,Devices

Applications / RepositoriesApplications / Repositories

11

Portal FrameworkPortal Framework


ConnectorsConnectors

Information SourcesDocumentsDocuments AppsAppsSAP R/3SAP R/3 EISEIS DatabasesDatabases WebWeb

User Management Engine


UnificationUnification

Application Unifiers

Application Unifiers

Database UnifierDatabase Unifier

Knowledge ManagementKnowledge Management



TREXTREX

CMCM

Portal RuntimePortal Runtime

Portal Components Portal Services

Logical ComponentsBrowser, Devices

User Persistence Store


PortalDatabase

PortalDatabase

Backend Systems

SAP Enterprise Portal 6.0

Portal Content Directory

Page Builder

UserManagement

Admin Tools

12

Technical Components

Web ServerWeb Server

Unification



Portal

Content Management


Web ServerWeb

Server

Unifier 1Unifier 1

Web ServerWeb

Server

Unifier 2Unifier 2

Real-Time Collaboration

Real-Time Collaboration


PortalDatabase

PortalDatabase

Persistence

Applications, Information, Services

Unification Server

Index ServerIndex Server

Web ServerWeb Server


Java App Server (SAP J2EE engine)

Backend Systems

SAP Enterprise Portal 6.0

Browser, Devices

13

Unification HostUnification Host

Unification ServerUnification Server

Unifier for SAP BWUnifier for SAP BW

Unifier for SAP R/3Unifier for SAP R/3

Windows

Unix / Windows

Portal Runtime

iView Runtime Java

(IRJ) application

iView Runtime Java

(IRJ) application

TREX HostTREX HostTREXTREX

Unix / Windows

Shared Resource Host

Portal DatabasePortal Database

Unix / Windows

Portal Host 1

SAP J2EE Cluster

Portal Landscape: Example

Portal Runtime

iView Runtime Java

(IRJ) application

iView Runtime Java

(IRJ) application

Content Mangmnt.Content Mangmnt.

Connector 1Connector 1


SAP J2EE Cluster

Unix / Windows

Portal Host N



Content Mangmnt.Content Mangmnt.



14

Setting up a Portal Cluster

Inner Firewall

Outer Firewall

Web ServerWeb

ServerWeb

ServerWeb

ServerWeb

ServerWeb

Server

Portal RunTime(incl. CM)






Notification

http/https

Web ServerWeb

Server

UnificationServer*

UnificationServer*

Retrieval &Classificatio

n

Retrieval &Classificatio

n

Load BalancerLoad Balancer

Web ServerWeb

Server

http/https http/httpshttp/https http/https

Persistence

Engines

http/https

Browser, DevicesBrowser, Devices

Clustered User Persistence StoreClustered User

Persistence StoreClustered Portal

DatabaseClustered Portal

DatabaseTREX IndexTREX Index

*Unification will be ported to Java in 2003 and will be available as a Portal Service on the PRT.

15

Portal FrameworkPortal Framework


Portal Components

URL request

HTML

Flow of a Request In the Portal

Web serverWeb server

Portal Services

User Management

Page Builder

Portal Client

User Persistence

Store

User Persistence

Store



Portal System Database

Portal System Database

1

2

3

4

5


16

Header Area

Navigation Panel

Content Area

Drag&Relate Targets

Drag&Relate Targets

iView 1 iView 2

iView 4iView 3

Page

Detailed Navigation

Related Links

Header (Logo)

Top-Level Navigation

Components of the Portal Desktop

iViewsiViews

Portal DesktopPortal

Desktop

ContainerContainer

17EP Admin Framework

Design Time - Setting Up Portal Content

Portal DesktopPortal Desktop

Style Editor

Style Development

PortalStylesPortalStyles

iViewStudio

iViewsiViews

Content Delivery

Document Management

Resources/DocumentsResources/Documents

TaxonomiesTaxonomies

KM Admin

Collab. RoomsCollab. Rooms

Collab. Room Building

Template Builder

WorksetsWorksets

Role Building

RolesRoles

SystemsSystems

System Integration

Content Building

PagesPages

iView Templates

iView Templates

iViewsiViews

Portal Dev. Kit

Content Development

iViewsiViews

Portal Content Studio

Content Delivery

18

SAP Enterprise

Portal

Applications Accessing User Management

User Management Core Layer

Persistence Manager Replication Manager

User Management Persistence Adapters

User API

User Account

API

User Account

API

Group API

Role API

Architecture Overview – User Management Engine

ExternalExternalLDAPLDAPDatabaseDatabase SAP System

SAP System

19

Persistence Manager

• Central place for reading and writing user-specific data

– Users

– Groups

– Role assignments

• Uses Persistence Adapters to read/write data

• Supports database, LDAP directory and SAP system as repository


Persistence Manager

User Management Persistence

AdaptersDatabaseDatabaseLDAPLDAP SAP

SystemSAP

System

20

Replication Manager

• Replication of user data to external systems

• Provisioning for external systems that cannot use supported user repositories

• Notification when users are created or modified

• Data exchange via XML documents

• One-way replication of user data (Portal External System)

Replication Manager

External System


User Management Persistence

Adapters

21

User Management Architecture: Data Store

Basic user data

Basic group data

User group assignment

User/group role assignment

User mapping (for SSO purposes)

User roles (metadata)

Content role assignment

User’s personalization data

Portal

PCD InstanceUM Instance

• LDAP Directory• Database• SAP System

Store portal-specific data

User Persistence

Store

User Persistence

Store

Portal Database

Portal Database

22

DMZ BackendFront End

Client

Web Servers (with Plug-In)

ExternalFirewall

InternalFirewall

Intranet

Portal Servers(incl. Content Management)

Persistence Layer

Firewall

ApplicationServers

Retrieval & Classification(TREX)

DatabaseServers

Corporate Directory Server

Secure Network Architecture – Enterprise Portal 6.0

23

Exercise 1

24

Agenda




• Portal Objects


25

Portal Content Directory: Overview

• The PCD is a virtual layer holding portal services that interact with the portal database

– The PCD acts as a central persistence for portal objects such as roles, pages, system landscape, and many more. The details of such data are deployed on the portal in portal archive (PAR) files.

• All portal services storing persistent data on the portal database (can) use the PCD as storage mechanism

– Enables separation of data that describes content, such as, names, fields, values, etc., from the technical implementation of the content.

26

Where are Content Objects Stored?

– The Portal Content Directory (PCD) is the central persistence store for all portal objects. This includes, for example, storage of the metadata for the content objects (roles, worksets, etc.) and the relationship between the objects.

– The PCD provides the following functions for content objects:

• delta links for reuse of object instances

• creation of relationships between objects

• generic transport mechanism

• personalization

• object notification

• versioning

• permissions using access control lists (ACLs)

• filter mechanism and search

27


•Content Directory

– Stores all portal objects.

– To edit content objects, the PCD is accessed via

Content Administration > Portal Content

– To edit system objects, the PCD is accessed via

System Administration > System Configuration

– To edit Portal Themes, the PCD is accessed via

System Administration > Portal Display

•Out-of-box SAP Content is stored in the following folders.

– Content for Line Managers

– Content for Specialists

– Content Provided by SAP

– Portal Administrators

– Portal Users

28

Object Organization and Administration

•Object Organization

– Objects are organized via folders.

– There is not a limitation on where to store objects.

– Unless required for configuration purposes, SAP out-of-box folders and objects should not be modified.

•Object Administration.

– To access Portal Content Directory, the user must be assigned the Content Administration role.

– To create and/or modify System objects, the user must be assigned the System Administration role.

– New objects are created by right-clicking on the folder that will contain the object.

– A Wizard is launched to create the object.

– Objects can be referenced by a delta link, copied and deleted.

• If an object is copied, a new version is created.

• If a delta link is created to an object, the delta link points back to the object.

29

Guiding Principles.

• Separate customer objects and SAP objects.

• Any existing SAP objects leverage for developed content will be copied. Modifications pertaining to those objects will be made on copied versions.

• All objects should use customer prefix and not SAP prefixes.

• Utilize a standard format for object ids.

• Organize objects in a consistent folder pattern.

• Any objects that are encapsulated within another object (e.g. an iView that is assigned to a Page) will be linked using a “Delta Link“ rather than a copy. As a result, any modifications will be made by editing the original object. This will impact all objects containing a delta lik to the object.

• A test folder should be created in development to store any test functions. Objects can be moved from this folder into production folders prior to deployment. This approach will reduce risk pertaining to accidentally migrating in-progress development objects.

30

Naming Standards

Object ID Prefix ID User Group Examples

Page Pg_ xxx OR pur OR <blank>

Pg_cpc_MyTransactions; Pg_Login

iView Iv_ xxx OR xx2 OR <blank>

Iv_pur_PORT

Role Ro_ xxx OR xx2 OR <blank>

Ro_cpc_admin

Workset Wk_ xxx OR xx2 OR <blank>

Wk_pur_home

Folder Fd_ xxx OR xx2 OR <blank>

Fd_Test

Theme Th_ xxx OR xx2 OR <blank>

Th_cpc_internaluser

Desktop Dt_ xxx OR xx2 OR <blank>

Dt_pur_internaluser

Rules Collection

Rc_ xxx OR xx2 OR <blank>

Rc_cpc_internaluser

Framework Fw_ xxx OR xx2 OR <blank>

Fw_allusers

System File Sy_ xxx OR xx2 OR <blank>

Sy_R3connection

•Guiding Principles:

– There are no maximum or minimum length restrictions on the total number of characters pertaining to an ID aside from any limitations imposed by the Enterprise Portal software

– ID User Groups are either “xxx” (client), “xx2” (client 2) or <blank> (shared object)

– The naming standards will not be applied to existing objects and content provided by SAP

EP200 Day 1

Documents

Transcript of EP200 Day 1