day4 portal
TRANSCRIPT
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 1/40
Massachusetts Institute of Technology
Web Dynpro for ABAP
Volume IV: Portals and integration
27 January 2011
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 2/40
27 January 2011 2
Agenda
Purpose
Portal components
Roles
Creating Portal Components
Security and Permissions
Determining referenced Web Dynpro applications
Portal eventing (and implementation considerations)
Understanding Object Based Navigation
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 3/40
Provide a single point of access to SAP and non-SAP information and applications
Information sharing and collaboration
Role-based content
End-User Personalization
Portal Federation:
Provide a single portal access point for distributed installations minimizing administration
Producer portal: Portal installation providing other (consumer) portals with remote accessto its locally deployed applications
Consumer portal: Portal installation which accesses remote applications provided by aproducer portal
Business Packages:
Predefined SAP content comprising business applications and solutions
Tight integration with ECC
Examples: ESS, MSS, Learning Solution, HR Administration
Purpose
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 4/40
Architecture
Applica'onPla,orm
Informa'onIntegra'on
PeopleIntegra'on
DBandOS
J2EE
Collabora'on
Portal
KnowledgeManagement
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 5/40
Portal components
Role WorksetPage
iView
iView
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 6/40
Role: Usually the name of the tab
Workset: Organizes content
Folder: Further organizes content
Page: Container for one or more iViews
iViews Applications
Roles control what is visible in the portal
Roles contain several elements that contribute to what is seen in different ways
Role-specific customization to the navigation is available
Portal components
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 7/40
Portal components
Role
Workset
Page
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 8/40
Maintained in Content Administration tab
Controls:
Navigation
Access to applications
Layout
Assigned through User Administration (or other user management tools)
Does not grant access to:
Data in the back end
SAP GUI transactions
Portal components: roles
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 9/40
Pages or iViews can be added to the Role
iViews exist inside of Pages and are not navigated to directly from the Role
To access an iView, open the Page within the Role
Portal components: pages and iViews
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 10/40
Folders:
Group content elements
e.g. Separate content by country
Can be to show groups of content in the left
navigation panel
Portal components: folder and service maps
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 11/40
Service Map / Workset Maps:
Presents a graphical representation of the contents of folders and worksets
Is an easy alternative to using the Homepage Framework
Portal components: folder and service maps
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 13/40
Steps common to all Portal Objects:
Launch Portal Content Administrator
Locate the appropriate folder
Creating a Web Dynpro iView (Step 1):
Initiate iView wizard using right-click on Folder
Select one of three options:
− iView template: Provides options for most scenarios
− Portal component: From deployed portal archive (PAR file)
− Web Dynpro Java application
Select SAP Web Dynpro iView from provided list
Creating portal objects
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 14/40
Creating a Web Dynpro iView (Step 2):
Provide the general properties:
− iView Name: Shown on iView Tray or as
Window title
− ID: Generally same as the name only
lowercase using underscores for spaces
− Prefix: Used similarly to development
namespaces and forms part of the iView’s ID,
e.g. mit.edu.iviews.wda_demo
− Prefixes allow for the unique identification of components and is useful when performing
Portal Transports
Creating portal objects
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 15/40
Creating a Web Dynpro iView (Step 3):
Select the Web Dynpro platform (ABAP or Java)
Creating a Web Dynpro iView (Step 4):
Provide the Web Dynpro parameters
− Select the ECC System alias as defined by Basis
− Provide the application namespace, usually sap
− Provide the Application name (not Component
name)
− Optional: Provide the name of the Application
Configuration and any Application Parameters
Creating a Web Dynpro iView (Step 5):
Confirm entries and alter any general iView properties
as required
Creating portal objects
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 16/40
Creating a Web Dynpro Page (Step 1):
Initiate iView wizard using right-click on Folder
Provide the general Page attributes
Creating a Web Dynpro Page (Step 2):
Select the Page template: (default or WebDynpro Proxy)
Creating a Web Dynpro Page (Step 3):
Create the available Page layouts
− e.g. 1 Full-width column or a T-layout
− Usually depends on the expected number of
iViews on the Page
− Allows user to customize the Page
Creating portal objects
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 17/40
Creating a Web Dynpro Page (Step 4):
Confirm entries
Creating a Web Dynpro Page (Step 5):
Edit the page to add Page Content
Right-click on iView, select Add iView to Page (Delta link or Copy)
Creating a Web Dynpro Page (Step 6): optional – only if multiple iViews or
layouts are used
For each layout, drag to rearrange iViews in correct order
Define new Layouts
Creating portal objects
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 18/40
What’s the difference?
Copy
− Makes a copy of the element that exists independently of the original
Delta link
− Makes a copy of the element that is tethered to the original
− Changes to the original are reflected in the version that exists in the role
Creating objects: copy or delta-link?
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 19/40
Why should I care?
Is the original a standard SAP element?
− Changes due to patches affect only the original and not a copy
− However, delta linked elements pick up the changes
− Delta link everything that is based on standard
Why would I use copy?
− Sometimes personalization can have issues with delta link when something is updated
– Could lose your changes
− If anything that has major changes to the standard that would be broken by an update
− Custom development, sometimes
Creating objects: copy or delta-link?
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 20/40
Parameters for controlling navigation can be set on the role
Open in a new window
Navigation panel open or closed
Entry points
iView options can be restricted
Refresh
Add to favorites
Open in a new window
Display details
Report a problem
Navigation adjustments
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 23/40
Security concepts are split between the Portal and ECC
Portal roles:
Are more important from a usability perspective
Provides content organization
Most important piece for controlling navigation and layout
ECC roles:
Are more important from a security perspective
ECC roles allows access to transaction codes and reports in the backend
Security and permissions
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 24/40
Authorizations and content from both roles work together to form a
complete security solution:
Portal role is used to check for read permission on the Page, iView, and
Application components
When the application is loaded, the authorization to run the application ischecked on the ECC
When the application loads the data to be displayed, the user’s authorization to
view the data is checked on the ECC
When the user tries to save a change, an authorization check is performed, for example to write to Infotype 0006
Security and permissions
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 25/40
Why ECC roles are more important
Portal roles can be bypassed
− If the URL of an application is known, it can often be run without having the
portal role for it
− Use of permissions on the application is a potential solution
If someone manages to load an application, the back-end roles will prevent it
from loading or prevent the user from accessing data
− S_SERVICE controls access to the application on the back end
− Authorizations control access to the data
Back-end roles have the real power to secure applications and manage data
access
Security and permissions
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 26/40
Permissions can be set on each object and assigned at the role,
user, or group level
Accessed via Content Administration or System Administration
Each application used and the underlying components must allow
read access to the end user
Permissions are not the same thing as simply adding an iView to a
role
Adding to a role provides the navigation
Permissions provide the security
If permissions are not set, a user can still access an application once the
role is removed if he or she adds it to favorites or remembers the URL
Security and permissions
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 27/40
Best Practices:
Permissions are inherited and can also be reset to restore inheritance
− To simplify maintenance, maintain permissions at the highest level possible then
reset the child permissions
Security and permissions
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 28/40
Best practices:
Assign permissions to the portal role
− Ensures that all users who get the role have the
permissions
− Ensures that permissions are removed when the
role is unassigned
− Simplifies maintenance and enhances security
Security and permissions
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 29/40
Role assignments are maintained in the User Administration tab
Roles can be assigned:
Directly to users, or
User groups (recommended)
− Simplified management
− Users and roles are assigned to groups
− Maintenance efforts reduced
− For ESS and MSS, always assign users to groups for maintenance
User Administration
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 31/40
Option 1: Use iView/Page Details
Select Details from the Options popup menu on Page Tray
Provides the Portal Content Directory path for referenced iView
Format
− pcd:portal_content/<folder location>/...
Determining the used Web Dynpro application
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 32/40
Option 1: Use iView/Page Details
Select Details from the Options popup menu on Page Tray
Provides the Portal Content Directory path for referenced iView
Format
− pcd:portal_content/<folder location>/...
Option 2: Traverse the PCD Role
Follow the user’s navigation in the PCD
Determining the used Web Dynpro application
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 33/40
Purpose:
Different application technologies can be combined on the same portal Page
Portal eventing (or client-side eventing) facilitates communication between iViews
One to many communication
Limitations:
Functions only between iViews on the same browser window
All participating iViews must belong to the same domain due to JavaScript restrictions
Use:
Web Dynpro ABAP applications can:
− Register to receive portal events and thus react to an event that was triggered in
another iView in the portal
− Similarly to registration, a Web Dynpro application can raise a portal event
− For example:
WDR_TEST_PORTAL_EVENT_FIRE and WDR_TEST_PORTAL_EVENT_REC
Portal eventing
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 34/40
Examples:
System Administration -> Support
Ability to use Generic event Tester to test custom
WDA applications
Portal eventing
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 35/40
Essentially launches an iView based on a back-end business object, receiving real-
time information relevant to the user’s role
Navigation operation is directly attached to the Object:
Visually (using right-click navigation)
Logically (in the Portal Catalog)
Role-sensitive:
The navigation options offered depend on the user‘s Role
The same operation could have different outcomes depending on the user’s Role assignments
Often requires a complex combination of administrative tasks:
Editing permissions and roles
Importing business
Creating and editing iViews and operations, objects
Determining a complicated set of priorities
Object Based Navigation
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 36/40
Term DescriptionBusiness Object A Portal Platform entity representing a
business objects of a back end system
Operation Defines the connection between a businessobject and its implementing iViews
Source iView The iView from which an OBN operation isinvoked
Implementing iView Any iView or page attached to a businessobject operation (destination)
Object Based Navigation: Terminology
iView selection at runtime: Dependent on User role
Operation Priority
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 37/40
Operations:
Serves as the connection between the Business Object and the iView that implements it
Navigation is defined by means of operations attached to the business objects
Multiple operations may be assigned to a single business object
Numerical priorities are assigned to each operation to define default operation
Object Based Navigation
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 38/40
Defining an Operation
1. Create an Operation
Using the Business Object Editor
Content Administration Content Catalog: Right-click on any business object.
Note: Operation IDs cannot be changed
2. Implement the Operation
Provide the iView to be launched upon OBN request.
Operations and iViews can be connected to each other by:
− Selecting an iView from the PCD while editing the Operation (Business Object Editor)
− To modif the operations of a specific iView
− Selecting an operation while editing an iView (Object-Based Navigation Editor)
The administrator is in responsible for creating operations and attaching implementing
iViews.
Object Based Navigation
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 39/40
Defining an Operation
3. (Optional) Modify the operation from iView
Generally to override the existing priority or
Change the presented name of an operation for a specific role.
4. Add OBN calls to source iViews
Object Based Navigation
7/30/2019 Day4 Portal
http://slidepdf.com/reader/full/day4-portal 40/40
Content Administration
http://help.sap.com/saphelp_erp2004/helpdata/en/5a/0339000c0b11d7b84800047582c9f7/frameset.htm
Portal Developer Guide http://help.sap.com/saphelp_erp2004/helpdata/en/9f/fd4e41bbd1f423e10000000a155106/
frameset.htm
Object Based Navigation http://help.sap.com/saphelp_erp2004/helpdata/en/5c/
7392047a7546a7882dbba3e5f4744d/frameset.htm
References