SAP EP in Detail - Portal Administrators

8/13/2019 SAP EP in Detail - Portal Administrators

http://slidepdf.com/reader/full/sap-ep-in-detail-portal-administrators 1/83

SAP EP in Detail

1 Version 1.0



13 November 2009

Definition of SAP Enterprise Portal

2

Version 1.0

SAP Enterprise Portal is SAP's strategic platform to access all SAP

applications from a Web Browser.

Sap's strategy as part their NetWeaver technology stack to

provide the end user with a web-based single integrated point of

entry for their business applications, documents, and

collaboration.

It provides you the tools to manage this knowledge, to analyze

and interrelate it, and to share and collaborate on the basis of it.



13 November 2009

Where Portal fits in SAP NetWeaver Stack

3

Version 1.0



13 November 2009

Basic Portal Navigation

4

Version 1.0



13 November 2009

Portal AdministrationThe portal provides a complete set of tools to administer, manage and monitor

the portal within one coherent environment, the following are the basic roles for

Portal Development and Administration:

Content Administrator

User Administrator

System Administrator

5

Version 1.0



13 November 2009

Portal > Content Admin

6

Version 1.0



13 November 2009

Portal > Content Admin Cont..

Portal Content Admin is referred as Portal Content Studio which consists of:1. Standard Portal Content by SAP

2. Portal Object Created by User

The Portal Content Studio provides a central environment for developing andmanaging the following types of portal content:

iViews

pages

layouts roles

worksets

business objects

7

Version 1.0



13 November 2009

What is an iView, Page, Workset & Role?

iViews: An iView is the basic unit of portal content – a small application

that displays information

iView information can be in any format (texts, figures, graphs, reports, tables,charts etc.)

iViews can be interactive, allowing you to perform business functions

Pages: A portal page holds iViews and other pages containing iViews, organized in a

layout. iViews retrieve information from various sources, helping users perform their

business functions.

Pages are one means of assigning the iViews to users and roles, and displayingthe information that is retrieved.

8

Version 1.0



13 November 2009

Cont..!

9



13 November 2009

Portal Roles Hierarchy

10



13 November 2009

Create Object in Portal Content

11

Path: Content Admin > Portal Content >

Naga > Create New Object of the abovetypes.

Other Sub-Lever Navigation: KM Content

Collaboration Content Web Dynpro Console Workflow Content etc..



13 November 2009

iViews in Detail

12

Version 1.0

Data Flow of iView:

1. The portal client’s Web browser sends a request todisplay an iView.2. The iViewServer calls the iView application through aURL.3. The iView application reads the data from the data

source and processes it.4. The iView application sends the result to theiViewServer in HTML/XML format.5. The iViewServer sends HTML to the Portal client.

Note: When the iViewServer receives SAP Portals XML, itfirst translates it to HTML before sending the data to theclient.6. The portal client displays the iView in the Web browser.



13 November 2009

iViews in Detail > iView Template

IView Categories:

iView Templates

Portal Component – PAR iView

Web Dynpro Java Application – Web Dynpro Java iView

13

Version 1.0



13 November 2009

iViews in Detail > URL iView

14

Version 1.0

There are various types of iViewTemplates available:SAP BSP iViewsSAP RFC iViewsKM iViews (many)

App Integrator iViewsURL iViewsSAP BW iViews etc..,

For Ex: URL iView



13 November 2009


15

Version 1.0

iView General Properties:

iView Name: Google iView

iView ID: google_iview



13 November 2009


16

Version 1.0

Data Source for URL iView:

URL: http://www.google.com then click Next

http://www.google.com/

http://www.google.com/



13 November 2009


• Will show the google website

17

Version 1.0

Open URL IView for editing, preview & change properties.



13 November 2009

iViews in Detail > Web Dynpro iView

18

Version 1.0

Web Dynpro IView:

Select the Web Dynpro Java Application – Web Dynpro JavaiView for creating Web Dynpro iViews



13 November 2009

iViews in Detail > Web Dynpro iView

19

Version 1.0





13 November 2009

iViews in Detail > KM iViews

• KM iViews:

– KM Document iView

– KM Navigation iView

– KM Quick Poll iView

– KM Notifications iView

– KM Search iView – KM Subscription iView

– KM Discussion iView

For Ex: KM Navigation iView

21

Version 1.0



13 November 2009

iViews in Detail > KM Navigation iView

22

Version 1.0

Define the KM Navigation iViewName & ID.

For ex: Naga_Docs



13 November 2009


Two Properties are

important for

Navigation iView:

. path to Initial Displayed

Folder

. path to Root Folder

For ex: documents/Naga’s

Documents

23

Version 1.0



13 November 2009


After providing the basic properties click on Preview will show the

above results.

- You can see 2 folders listed under Naga’s Documents

24

Version 1.0



13 November 2009

Pages in Detail > New Page

• Create Page: New > Page > Page Wizard

25

Version 1.0

Enter the following:

Page Name, Page ID





13 November 2009

Pages in Detail > Page Layout

• Choose Page Layouts > 1 Column (for ex).

27

Version 1.0

We can Add morethan One PageLayouts. But onlyOne will be the

Default Layout



13 November 2009

Pages in Detail > New Page

• New Page > Page Wizard Summary

28

Version 1.0



13 November 2009

Pages in Detail > Add iViews to Page

• 1. Open the Page (see the screen). 2. Add the iView (Delta Link or Copy). 3. We canalso Add a Page to Page (Delta Link or Copy)

29

Version 1.0



13 November 2009

Pages in Detail > Add iViews to Page

• iView Properties is Page: 1. Visible 2. Fixed

30

Version 1.0



13 November 2009

Pages in Detail > Page Layouts

• 1. Click on Page Layout. 2. Select the layouts as per the requirements.3. Preview to see the Results.

31

Version 1.0



13 November 2009

Pages in Detail > Add Page to Role/WS

• From the Portal Content: 1. Open Role/Workset. 2. Add Page toRole/Workset (Delta or copy)

32

Version 1.0

Where Pages can be added:

1. We can Add Page to Page

2. We can Add Page to Workset3. We can Add Page to Role

All the above can be Delta orCopy action.



13 November 2009

Pages in Detail > Page Preview

• Once we’ve added the Page with Layout defined, we can see thepreview of the page. See the screen for ex.

33

Version 1.0



13 November 2009

Worksets in Detail > New Workset

• Portal Content > Naga > New > Workset

34

Version 1.0

Properties of Workset:

1. Workset Name

2. Workset ID



13 November 2009

Worksets in Detail > Workset Summary

• Screen 1: Once create the Workset, you will see the Summary of theSame.

• Screen 2: We can open the object for Editing/Adding/Creating new

Object etc

35

Version 1.0



13 November 2009

Worksets in Detail > Adding Page to WS

• From Portal Content: Adding Page to Workset (Delta or Copy)

36

Version 1.0



13 November 2009

Worksets in Detail >Adding iView to WS

• From Portal Content: Adding iView to a Workset (Delta or Copy)

37

Version 1.0



13 November 2009

Worksets in Detail > WS with Objects

38

Version 1.0

After adding all the identified objects

(iView, Pages, WS), you will see thefollowing Screen with objects in it.This depicts like the WindowsExplorer.

Note: 1. You can see the a worksetadded to another workset.

2. Can move the objects Up / Down



13 November 2009

Roles in Detail > Role Preview

39

Version 1.0

The Procedure for creatingRoles are same as Worksets.

You can see preview of allthe objects added to theRole MyTab.

We can Add a Role to Role.This is One Dimension ofhaving Roles in EP.





13 November 2009

Portal > User Admin

SAP systems within the SAP NetWeaver platform perform authorizations using arole-based identity management approach. This means that User Administration

assign authorizations to users based on the job they perform using the

particular system. In the portal, all user management functions related to users

and groups are provided by the User Management Engine (UME).

Sub-Lever Navigations:

Identity Management

Import Activity Reports

41

Version 1.0



13 November 2009

Portal > User Admin > IM

42

Version 1.0



13 November 2009


• Creating New Users:

43

Version 1.0

The following can beperformed on Users:

~ Lock/Unlock

~ Set New Password

~ Export



13 November 2009


• Creating New Roles:

• Creating New Groups:

44

Version 1.0



13 November 2009

Portal > User Admin > Import

• Sap EP provides the Uploading of User/Group/Role data to the existing

portal catalog.

45

Version 1.0



13 November 2009

Portal > System Admin

• The system administrator is responsible for the configuration andongoing support of the portal and its landscape. This role therefore

contains configuration, maintenance, and support related functionalities.

System Admin in Detail: Transport

Monitoring

Permissions

System Configuration

Portal Display

Support

46

Version 1.0



13 November 2009

Portal > System Admin > Transport

Transport: Transport of Portal Objects

Upload Content & Actions

Role Upload

Content Mirroring

47

Version 1.0



13 November 2009


48

Version 1.0



13 November 2009


• Transport Portal Object: 1. Import 2. Export

49

Version 1.0



13 November 2009


• Add all the required Portal Objects into Transport for Exporting. Refer tothe following screen shot with portal objects added for exporting.

50

Version 1.0



13 November 2009


51

Version 1.0

Adding Users/Groups toExport:

We’ve an option to add Users and

Groups to the existing TransportPackage.

See the Group: sap_team added.





13 November 2009


• Status of the Exporting Package:

53

Version 1.0



13 November 2009


• Export Summary: 1.Summary of Objects 2. Option to Download theExported File from Server.

54

Version 1.0



13 November 2009


• Import Package: 1. Client 2. Server 3. File Location (Browse the File fromFile System)

55

Version 1.0



13 November 2009


56

Version 1.0

l d



13 November 2009


57

Version 1.0

Import Summary:Once you are donewith the Import, youwill see the Import

Summary withObject level details.

P l S d



13 November 2009


Upload of Roles from ABAP-Based Systems:• You can use existing single and composite role menus as well as authorization

profiles from ABAP-based SAP systems when you use SAP Enterprise Portal.

Within portal administration, you can use an upload tool to upload objects (such

as roles and transactions) from ABAP-based SAP systems. The authorization

profiles remain in the backend system and can, for example, be used when you

call a transaction from the portal.

• You must start the upload manually; an automation of the process is currently

not available.

• The uploaded objects are converted into portal objects.

58

Version 1.0

P l S Ad i T



13 November 2009


• Flow of uploading Roles from ABAP-Based Systems:

59

Version 1.0



P l S Ad i T



13 November 2009


Delta Copy Vs Content Mirroring:

61

Version 1.0

P t l S t Ad i P i i



13 November 2009

Portal > System Admin > Permissions

Permissions:• Portal permissions define user access rights to objects in the Portal Content

Directory (PCD). Permissions in the portal are based on access control list

(ACL) methodology.

• Essentially, every portal object can be assigned directly to an individual user orcollectively to groups of users through user groups and roles.

• Folders and objects in the Portal Catalog each have the following permission

levels:

Administrator: Administrator permissions determine which content in the Portal Catalog isavailable to a portal user in the design-time environment.

End User: End user permissions determine which content is available to a portal user in the

run-time environment.

Role assigner (valid for role objects only): Determines which users, groups or role principles

are able to perform role assignments (that is, the assignment of users and groups toroles, and vice versa) for a particular role.

62

Version 1.0



P t l S t Ad i S t L d



13 November 2009

Portal > System Admin > System Land

System Landscape:

• The portal system landscape is a collection of systems. A system is a portalobject comprised of a set of properties that represent an external, or back-end,application. Systems enable a connection to these applications and the retrievalof data from their information stores.

• Some external applications to which you want to connect must have in theportal system a representative connector , the middleware through which theportal content accesses the application.

• The portal provides an SAP connector for accessing SAPsystems, and aDatabase (JDBC) connector for accessing generic databases. These twoconnectors are automatically installed to the Web application server duringportal installation.

64

Version 1.0

P t l > S t Ad i > S t L d



13 November 2009

Portal > System Admin > System Land

• You create a system in order to connect to a specific back-end application

65

Version 1.0

System PAR: The new system

inherits all the global propertiesdefined in the PAR file component.It inherits property names, metaattributes and any default property

values.

System Template: If thetemplate was created directly fromthe PAR file, the new system isidentical to the one generated bythe first method. If the templatehas undergone changes, thesystem inherits the changes madeto the property attributes in thetemplate.

Portal > S stem Admin > S stem



13 November 2009

Portal > System Admin > System

• New System Properties

66

Version 1.0




13 November 2009


Connection Properties:

Connection Properties for

connecting to the back-endsystems.

67

Version 1.0




13 November 2009


• Need to provide the necessary

properties, this will vary

depends on the connectiontype.

68

Version 1.0




13 November 2009


69

Version 1.0

Access to a system isthrough a system alias,a name by which portalcomponents canreference a specific

system.

Portal > System Admin > System L Ovr



13 November 2009

Portal > System Admin > System L Ovr

• System Landscape Overview:We can see the all available systems in the

portal.

70

Version 1.0

Portal > System Admin >UME Config



13 November 2009

Portal > System Admin >UME Config

• UME Configuration > Data Sources:It’s a place where admin will configure the UME source for the portal. Portal can have the following

UME as sources:

Portal Database

ABAP Users

Integrating Active Directory Users using LDAP

Etc,.

71

Version 1.0

System Admin > Web Dynpro Console



13 November 2009


72

Version 1.0




13 November 2009


Web Dynpro Console:

The Web Dynpro Console offers a number of functions for monitoring the Web

Dynpro applications that were deployed to the J2EE Engine and for displaying

the configuration settings of the Web Dynpro runtime environment.

You can also perform Performance Measurements with this tool. Performance

measurements are necessary if you developed a Web Dynpro application

whose response times are longer than users expect.

73

Version 1.0

System Admin > KM



13 November 2009

System Admin > KM

74

Version 1.0

System Admin > Collaboration



13 November 2009

System Admin > Collaboration

75

Version 1.0

Same as theCollaborationRole assignedto user.



Collaboration > Rooms



13 November 2009

Collaboration > Rooms• Collaboration < Rooms > Room Types

77

Version 1.0

Room Types:

Private: Registration bythe room owner (andinvitation to the new

member)Restricted: Registration bythe room owner based on arequest for membership

Private: Self-registrationor automatic registrationwhen entering the room




13 November 2009


• On Click on a room > SAP_Team_Room > Project Home

78

Version 1.0

User Navigation:

1. Project home

2. Docs and Links3. Tasks




13 November 2009


• SAP_Team_Room > Docs and Links

79

Version 1.0




13 November 2009


• SAP_Team_Room > Tasks (only to room members)

80

Version 1.0




13 November 2009


Room Admin >

General: details of room

81

Version 1.0




13 November 2009


Room Admin >

Members: Addition/Deletion of

Members and role assignments.

82

Version 1.0

Q & A’s:



Q & A s: