Welcome to EP200 (Day 1)

SAP NetWeaver EP
Agenda

• Enterprise Portal Overview

• Technical Architecture
• Portal Content Directory
• Portal Objects
• Business Packages

2
Agenda

• Enterprise Portal Overview

• Technical Architecture
• Portal Content Directory
• Portal Objects
• Business Packages

3
What is an Enterprise Portal?

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.

The Portal: single entry point

Corporate desktop: with organized, integrated,
Many isolated windows and personalized portal
siloed applications
No windows based
interface
User Experience
1980’s 1990’s 2001

4
 The Enterprise Workspace

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.

Enterprise Portal
Enterprise Workspace
Business Business Business
To To To Business
Employee Consumer
B2B
Allows two or more
B2E organizations to conduct
Allows employees to conduct daily business together via an online
B2C
tasks, keep up on organizational news interface.
Allows a business to interact
and complete self service functionality
directly with its customer via an
via an online interface.
online interface.

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.

5
 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….

6
 Enterprise Portal Powered by SAP Netweaver

SAP NetWeaver™ •SAP Enterprise Portal Powered by

PEOPLE INTEGRATION
SAP NetWeaver
Multi channel access – Web-based, role-based, secure
access
Portal Collaboration
Composite Application Framework

– Integrating any kind of structured

INFORMATION INTEGRATION information
Bus. Intelligence Knowledge Mgmt – The frontend to the SAP World

Life Cycle Mgmt

Master Data Mgmt – Sophisticated navigation possibilities

PROCESS INTEGRATION – Wide platform support, wide

language support
Integration Business
Broker Process Mgmt – Built on open standards
APPLICATION PLATFORM – SAP EP encompasses portal, KM
J2EE ABAP and Collaboration

DB and OS Abstraction

Content Provided by SAP

7
Agenda

• Enterprise Portal Overview

• Technical Architecture
• Portal Content Directory
• Portal Objects
• Business Packages

8
 Main components of the Enterprise Portal

Portal Platform Knowledge Management

Platform

Portal Retrieval & Real-Time

Framework Classification Collabo-
(TREX) ration
Content
Unification
Management
(CM)
Connector
Framework

Content Provided by SAP

9
 SAP Enterprise Portal 6.0 - Architecture
Browser,
Devices

• Open Portal Platform SAP Enterprise Portal

– Support of Internet standards ICE Knowledge Management Unification LDAP

like LDAP, Java, X.509,.Net, Content Retrieval&

Database Real-time Database Application
XML, JCA, JAAS. Mngmt. Unifier
Classif. Collaboration Unifier Unifiers
WebDAV SOAP
– Web service support Portal Content Catalog
(SOAP, UDDI)
JDBC System XML
iViews Pages Roles Worksets Layout
– Portal services like auditing, Landscape
logging, caching, rendering,
personalization service. Technical Portal Services HTTP/
FTP
Audit, Log, User Mngmt. Personaliz. HTTPS
Caching Notification Rendering
– Open APIs Monitoring Service Service Service Service Service

– Secure environment
• Open KM Platform
– Applications around unstructured
information
– People-centric collaboration
– Enterprise content management
• Patented Unification Technology
– Drag&Relate operations
between heterogeneous apps
Applications / Repositories
• 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
10
 Logical Components
Browser, Devices

SAP Enterprise Portal 6.0

Knowledge
Portal Framework Management
Portal Components Portal Services TREX Real-Time
Page Admin Collabo-
Portal Content User CM
Builder Tools ration
Directory Management

Portal Runtime Unification

Database Unifier

Application
Unifiers
Connector Framework
Connectors User Management
Engine

User Persistence
Store

SAP R/3 EIS Databases Web Documents Apps Portal

Information Sources Database
Backend Systems 11
Technical Components
Browser, Devices

SAP Enterprise Portal 6.0

Web Server

Portal Retrieval &

Classification
Unification Web Server
Portal Runtime
Web Web Index
Server Server Content Management Server
Unifier 1 Unifier 2
Unification Server Connector Framework
Real-Time
Java App Server (SAP J2EE engine) Collaboration

Portal
Database

User
Applications, Information, Services Persistence Store
Backend Systems Persistence
12
Portal Landscape: Example

Unification Host
Portal Host 1 Portal Host N
Unification Server
SAP J2EE Cluster SAP J2EE Cluster
Unifier for SAP R/3
Portal Runtime Portal Runtime
iView iView
Unifier for SAP BW
Runtime Java Runtime Java
(IRJ) application (IRJ) application Windows
Content Mangmnt. Content Mangmnt.
Connector 1 Connector 1
TREX Host
Connector 2 Connector 2
TREX
Unix / Windows Unix / Windows Unix / Windows

Shared Resource Host

Portal Database User Persistence

Store
Unix / Windows
13
 Setting up a Portal Cluster
Browser, Devices
Outer Firewall
http/https

Load Balancer

Web Web Web Web

Server Server Server Server
http/https http/https http/https http/https http/https
Inner Firewall

Portal Portal Portal Retrieval & Web

RunTime RunTime RunTime Classificatio Server
(incl. CM) (incl. CM) (incl. CM) n Engines
Unification
Server*
Notification

Clustered User Clustered Portal TREX

Persistence
Persistence Store Database Index

*Unification will be ported to Java in 2003 and will be available as a Portal Service on the PRT. 14
Flow of a Request In the Portal
1
Web server
URL request
2

Portal Framework
Portal Runtime

Portal Client Portal Services Portal System

Portal Database
Components

HTML Portal Content 3

Directory

5
Page Builder
User Management
User Management Engine

4 User Persistence

Store
15
Components of the Portal Desktop
Header Area
Header (Logo)
iViews
Top-Level Navigation

Navigation Content Area

Panel Page

Detailed
Navigation
iView 1 iView 2
Portal
Desktop
Drag&Relate
Targets

iView 3 iView 4
Related Links

Container
16
Design Time - Setting Up Portal Content
Portal Desktop

Template Portal Content

Builder Studio
Collab. Roles
Rooms
Collab. Room
Worksets iViewStudio
Building
Role Building
iViews
KM Admin
Content Delivery
Taxonomies Pages

Resources/ iViews
Documents
Document iView Portal Dev. Kit
Management Templates
Content Building iViews
Style Editor
Portal Content Development
Styles Systems
Style Development System
EP Admin Framework Integration Content Delivery 17
 Architecture Overview – User Management
Engine

Applications SAP
Accessing User Enterprise
Management Portal

User Management User User Group Role

Core Layer API Account API API
API

Persistence Manager Replication

Manager

User Management
Persistence Database LDAP SAP External
Adapters System

18
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

User Management Persistence Manager

Core Layer

User Management
Persistence LDAP SAP Database
Adapters
System

19
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)

User Management Replication Manager

Core Layer

User Management
Persistence External
Adapters System

20
User Management Architecture: Data Store

Portal

User • LDAP Directory Portal Store portal-

Persistence
• Database
Database specific data
• SAP System
Store
UM Instance PCD Instance

Basic user data User/group  role User roles

assignment (metadata)
Basic group data
User mapping (for Content  role
User  group
SSO purposes) assignment
assignment
User’s
personalization
data

21
Secure Network Architecture – Enterprise
Portal 6.0

Front End DMZ Intranet Backend

Application
Servers

Retrieval &
Classification
(TREX)

External Internal Firewall

Client
Firewall Firewall

Web Servers Database

(with Plug-In)
Portal Servers Servers
(incl. Content
Management)

Persistence Layer Corporate

Directory Server

22
Exercise 1

23
Agenda

• Enterprise Portal Overview

• Technical Architecture
• Portal Content Directory
• Portal Objects
• Business Packages

24
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.

25
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

26
 Portal Content Directory

•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

27
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.

28
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.

29
Naming Standards

Object ID Prefix ID User Group Examples

•Guiding Principles:
Page Pg_ xxx OR pur OR Pg_cpc_MyTransa
– There are no maximum or <blank> ctions; Pg_Login
minimum length restrictions on
the total number of characters iView Iv_ xxx OR xx2 OR Iv_pur_PORT
pertaining to an ID aside from <blank>
any limitations imposed by the Role Ro_ xxx OR xx2 OR Ro_cpc_admin
Enterprise Portal software <blank>
Workset Wk_ xxx OR xx2 OR Wk_pur_home
– ID User Groups are either “xxx” <blank>
(client), “xx2” (client 2) or
Folder Fd_ xxx OR xx2 OR Fd_Test
<blank> (shared object) <blank>
– The naming standards will not Theme Th_ xxx OR xx2 OR Th_cpc_internalus
be applied to existing objects <blank> er
and content provided by SAP Desktop Dt_ xxx OR xx2 OR Dt_pur_internalus
<blank> er
Rules Collection Rc_ xxx OR xx2 OR Rc_cpc_internalus
<blank> er
Framework Fw_ xxx OR xx2 OR Fw_allusers
<blank>
System File Sy_ xxx OR xx2 OR Sy_R3connection
<blank>

30