Sap Ep 6

Delegated Administration and
Distributed Development in
EP6.0
Nadav Levy,
NetWeaver Product Definition, SAP AG.
Session code: 1010
Disclaimer:
This Presentation represents current planning and can be subject to
further changes without prior notice!
SAP AG 2002, Title of Presentation, Speaker Name / 2
Delegated Administration & Distributed Development in EP6.0
Problem Description Problem Description Problem Description Problem Description
EP6 8olutions EP6 8olutions EP6 8olutions EP6 8olutions
Role Delegation Role Delegation Role Delegation Role Delegation
Permission Delegation Permission Delegation Permission Delegation Permission Delegation
Navigation implications Navigation implications Navigation implications Navigation implications
8ummary 8ummary 8ummary 8ummary

8cenario {1/5} - Distributed Ownership
Company ABC, Is implementing a portal
for their organization.
>100,000 users.
>1000 content providers and
developers.
There are number of sub-
companies and departments in the
company.
All sub companies run on the same
portal platform.
Each sub-company manages its
own portal resources, users and
content.
Company
Sub Company 1 Sub Company 2
UM
Landscape
Branding
Content
UM
Landscape
Branding
Content
Sharing
8cenario {2/5} - Restrict administrative authority
Company ABC wants to customize the admin roles into
narrower administration tasks and responsibilities
John
Sara
Frank
8cenario {3/5} - Multi Development - Own & 8hare
Content is provided from different sources:
iViewStudio / SDN
Developers from different groups in the organization
Developer creates the object and owns it.
Other developers can reuse the object to create new objects.
I created an iView I
want to let other
admin use it. They
should not be able
to change the
original object.
iView
Im creating a page. I want to
use Johns iView changing
one of the properties. The
other properties will change
when John will update them.
John
Sara
8cenario {4/5} - Multi Development - Weaving Content
iViews sometimes contain links to other portal objects
Page 1
Page 2
Page 3
Work set 1
Work Set 2
Sales Role
Page 4
D
e
p
a
r
t
m
e
n
t

A
D
e
p
a
r
t
m
e
n
t

B
iView 1
iView 3
iView 2
iViews can cross reference within boundaries of a development project
iViews can cross reference across boundaries of a development project
8cenario {5/5} - Multi Development - Matrix Development
Matrix Development Models for Content Creation
The company wants to create one Sales role. They want number of departments
to contribute to this role.
Each department controls its content. It is encapsulated and isolated from the
other departments.
Page 1
Page 2
Page 3
Work set 1
Work Set 2
Sales Role
Page 4
D
e
p
a
r
t
m
e
n
t

A
D
e
p
a
r
t
m
e
n
t

B

Delegated Admin - Admin Tasks
Admin Role
Admin interfaces are available as iViews and Pages.
The admin interfaces are organized in work sets.
Work sets are assigned to predefined admin roles
Customer flexibility Admin role customization.
Create new admin roles.
Modify admin roles with the role editor.
System Admin
Permissions Sys Config Transport
Transport Admin
Transport
Permissions Admin
Permissions

Delegated Ownership - Portal Content 8tudio
Portal
Catalog
Object
Editor
Delegated Ownership - Portal Catalog
Provide a structure to store and
organize the portal objects.
Customer can organize the structure
according to his business scenarios.
Customer delegates administration
permissions on the structure.
One consistent Framework for object
creation and modification.
Integration of objects from other
application such as KM and
Unification.
Delegated Ownership - Permission Editor
Permission Model - nheritance
Permission can be given to all objects in
the catalog, folders and content objects.
The catalog is organized in hierarchical
model. The permissions are inherited to
the objects below.
The permissions defined for an object
overrules the inherited permissions.
Company 1 - Read
Department A
Full control
Inheritance
Permission Model - Permissions
Permissions Hierarchy:

Administrator Mode End-User Mode

Owner
Read/Write
Full-Control
Write Read
Read
Two hierarchical permission realms:
Administration permissions for content creation in design time
End user permissions for content execution and personalization in run time
Each permissions allows what the one beneath it does + some more
Permission Model - and Portal Content Ob]ect Model
Delegated development model
Developer creates the object and owns it.
Other developers can use the object to create new objects.
iView Template
iView
iView Instance
Page
Developer 1 Developer 2 Developer 3 User
Full Control
Admin
Read
Full Control
Full Control
Full Control
End User
Read
Create
Instance
Add to page
Create by
Template
Owner
Content
Maker
Content
Assembler
Content
User
Admin
Read
End User
Read
8cenario - Editing a Role - Full Process.
User Management
Content manager role
Content Manager
Portal Content studio
Interface
Member of the
content
management
Role
Content
Manager
Work Set
assigned to
the role
John has access to the Content Studio
interface since he is a member of the
Content management role.
Portal Content Studio
Portal
Catalog
Role A Role A Role A Role A
Role Editor
Johns Application Designer Interface
John
Portal Content Studio
Project 1
User management
Content
Roles
Role A
Role B
Full Control
Permission
On Role A
He can edit only Role A according to
the permissions he has in the portal
catalog.

Matrix Development Model
Matrix Development Models for Content Creation
The company wants to create one Sales role. They
want number of departments to contribute to this role.
Each department controls its content. It is
encapsulated and isolated from the other departments.
Page 1
Page 2
Page 3
Work set 1 / Role 1
Sales Role
Page 4
D
e
p
a
r
t
m
e
n
t

A
D
e
p
a
r
t
m
e
n
t

B
Work set 2 / Role 2
Delegation of permissions: Each department has it own folder in the catalog.
They will create their own content objects (iViews, Pages, Roles). Each Department
controls its own content.
Department A
Role A
Page A
Department B
Role B
Page B
Portal Catalog
Bob
John
Full Control
Permission
On Role A
Full Control
Permission
On Role B
Department A
Role A
Page A
Department B
Role B
Page B
Portal Catalog
Role A
My Work
Page A
Unique Entry
Role B
My Work
Page B
Unique Entry
Role Editors
Bob
John
In run time, a user who belongs to Role A and B will have two My Work Top Level
Navigation entries.
Department A
Role A
Page A
Department B
Role B
Page B
Portal Catalog
Role A
My Work
Page A
Unique Entry
Role B
My Work
Page B
Unique Entry
Role Editors
Run Time
A
The unfavorable result
My Work My Work
In run time, a user who belongs to Role A and B will have a single entry named
My Work with Page A and B.
Department A
Role A
Page A
Department B
Role B
Page B
Portal Catalog
Role A
My Work
Page A
Unique Entry
Role B
My Work
Page B
Unique Entry
Role Editors
Run Time
My Work
A B
The desired result EPs Smart Merging feature
Each role has an entry with a reference to the same merge entry ID.
Another way to integrate content from different groups:
Department C creates a work set. Department C will give department A read
permissions on Work Set C. The admin of department A will add Work Set C as an
instance. Every change done on work set C by department C will be influenced in
Role A.
Department A
Role A
Page A
Department B
Role B
Page B
Portal Catalog
Role A
My Work
Page A
Unique Entry
Role B
My Work
Page B
Unique Entry
Role Editors
Run Time
My Work
A B
Department C
Work Set C
Work Set C
C
Weaving Content - 8cenario
iViews sometimes contain links to other portal objects
iViews can cross reference within or across workset boundaries
Simplest link uses the objects full path in the content catalog
(a.k.a Hard Link)
Problem full path in RT is not necessarily known in design time
Its a different development group
It depends on package location after import
Objects in the content catalog can be moved from folder to folder
Page 1
Page 2
Page 3
Work set 1
Work Set 2
Sales Role
Page 4
D
e
p
a
r
t
m
e
n
t

A
D
e
p
a
r
t
m
e
n
t

B
iView 1
iView 3
iView 2
Weaving Content - Relative Navigation
Relative Navigation aims to solve the Hard Link problem
An object can point to another object using a relative link
For example: iView3 to iView1 relative link:
..\..\Page3\iView1
Relative Navigation cannot exit the boundaries of a workset/role
Workset 2 can be used in roles developed by other departments. The
soft link from iView3 to iView1 will always work.
Page 3 Work Set 2
Sales Role
Page 4
D
e
p
a
r
t
m
e
n
t

B
iView 3
iView 2
iView 1
Weaving Content - Ob]ect Link Navigation
Navigate to another portal object, or trigger an operation, based
on the business context.
The same action on the same iView can lead to different results
based on:
Page/Workset/Role the iView is in
Combination of roles the end user is assigned to
Soft target link
The target link is a request for a business operation
Calculated at runtime by the portal
Developers need to understand the business concepts, not the
detailed content structure
The Object Link, as a soft link, can be used in content developed by
other departments.
Weaving Content - Ob]ect Link Navigation 8cenario
iView
List of Opportunities
iView
Customer Details
user
Sales Person
Sales Manager
user
iView
Customers List
Account
Number
0000001
0000002
0000003
Zoom
Zoom
Zoom
Zoom

8ummary
Delegated administration
Flexible administration roles
Powerful and intuitive permission model
Delegated ownership of content
Selective access to content
Distributed development
Matrix development model
Content cross reference
O & A
Thank you for attending!
Please remember to complete
and return your evaluation form
following this session.
Session Code: 1010

Sap Ep 6

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Sap Ep 6

Загружено:

Авторское право:

Доступные форматы

Delegated Administration and

Вам также может понравиться