Documente Academic
Documente Profesional
Documente Cultură
SAP NetWeaver EP
Agenda
2
Agenda
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.
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.
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
DB and OS Abstraction
8
Main components of the Enterprise Portal
– Secure environment
• Open KM Platform Applications / Repositories
– Applications around unstructured
information • Open Development Platform
– People-centric collaboration
– Web-based definition of worksets,
– Enterprise content management roles, layout, etc.
• Patented Unification Technology – Portal Content Studio for code-free
development of portal content
– Drag&Relate operations
between heterogeneous apps – Portal Development Kit for
developing portal content
10
Logical Components
Browser, Devices
Application
Unifiers
Connector Framework
Connectors User Management
Engine
User Persistence
Store
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
Load Balancer
*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
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
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
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
Persistence Database LDAP SAP External
Adapters System
18
Persistence Manager
User Management
Persistence LDAP SAP Database
Adapters
System
19
Replication Manager
User Management
Persistence External
Adapters System
20
User Management Architecture: Data Store
Portal
21
Secure Network Architecture – Enterprise
Portal 6.0
Application
Servers
Retrieval &
Classification
(TREX)
22
Exercise 1
23
Agenda
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.
29
Naming Standards
30