How to Create New Portal Display Rules

Transcription

1 How to Create New Portal Display Rules ENTERPRISE PORTAL 6.0 ASAP How to Paper Applicable Releases: EP 6.0 SP2 April 2004.

2 1 INTRODUCTION PORTAL DISPLAY RULES: INTRODUCTION THE STEP BY STEP SOLUTION Defining the Default Framework Page Defining Themes Defining the Portal Desktop Defining Portal Display Rules SAP AG 1

3 1 Introduction This document is a supplement to the standard documentation on Portal Display (Framework Pages, Portal Themes, Portal Display Rules, Portal Desktops) which can be found on the SAP Help Portal at help.sap.com/ep. The current documentation is for Release EP 6.0 SP2. In the English version, the documentation is under Administration Guide -> Portal Platform -> System Administration -> Portal Display. This How to document is a basic guide for creating display rules and does not discuss planning and conceptual concepts. It is highly recommended that implementers read the standard documentation first before going ahead and creating a display rule. This document using screenshots shows an example of how to create a new desktop rule along with supporting components SAP AG 2

4 2 Portal Display Rules: Introduction A desktop rule consists of a default framework page and at least one theme. The rule is applied to a user, group, role, bandwidth or browser type. The default framework page can consist of multiple iviews and pages. The default framework page by default consists of (images of examples) the following parts: Masthead iview: includes the top layer of the portal which includes the Welcome header, logo, and links Tool Area (this is optional and can be hidden): includes the KM Search input box and button. Other items can be added to this thin area. Top-Level Navigation: can have 2, 1, or 0 levels displayed. Desktop Innerpage (image shows empty content) 2004 SAP AG 3

5 3 The Step by Step Solution 3.1 Defining the Default Framework Page The default framework page has the standard page layout of iviews. A copy of the default framework page will be used to save on development time. The new framework page will be assigned to the main rule. Then all users who the rule applies to will have their portal pages displayed using the new framework page. 1. Do not change the out-of-the-box framework page as other elements may depend on this one. Instead copy the default framework page in the Portal Catalog located under Portal Users -> Standard Portal Users. 2. Paste into new folder (do not paste as delta link!). The folders Admin Content > Systems > Portal Desktop were created for this scenario SAP AG 4

6 3. Click Yes to copy the default framework page. 4. Edit object to open the new default framework page. 5. Rename the page for future reference. On the left side will be a property editor. Make sure that frameworkpage is the display object ID. Then scroll to Page Name in the Property List SAP AG 5

7 6. Click Save. New name will automatically appear in the Portal Catalog. 7. Each element has properties that can be edited. 8. As an example, the top-level navigation can be change to allow hovering SAP AG 6

8 3.2 Defining Themes The next part of the desktop is the theme that will be applied to the default framework page. To create new themes, choose System Administration > Portal Display > Theme Editor. More information on how to create a new theme can be read in the EP 6.0 SP2 Administration Guide SP SAP AG 7

9 1. Create a new Portal Desktop. Choose System Administration -> Portal Display -> Desktops & Display Rules. 3.3 Defining the Portal Desktop In the Portal Desktop Editor, the customer desktop and the themes can be combined: 2. Save the new portal desktop. The name Customer Desktop was used in this example. Add the Framework Page for Customer to this desktop SAP AG 8

10 3. Add the themes that you would like to have available to the role that will be assigned this portal desktop. 4. Set as default both a frameworkpage and a theme and save the portal desktop SAP AG 9

11 3.4 Defining Portal Display Rules Finally, the portal desktop needs to be applied to a role, group, user, element or multiple combinations. This is done by creating rules in the main_rules. The "main_rules" object is mandatory for the portal. Other rule collection objects can be created and nested inside the "main_rules" object. 1. Edit the object main_rules (Master Rule Collection) by choosing in the Portal Catalog: Content Administration -> Portal Content -> Portal Administrators -> Super Administrators -> main_rules. 2. Note: It is very important to keep the User =* rule at the end of the list thus providing a fallback option if the rule collection does not specify a desktop assignment for every possible user or scenario. If there are no rules that apply to a user, then no users will be able to access the portal. 3. Add the IF Expression. If this is not done, the USER = * role will be edited SAP AG 10

12 4. Select the IF Condition that will be in effect. To the right are examples: User = i (the ID of the user) Role = pcd:(location of role definition) Group = Customers (group name) Bandwidth: Browsertype: 5. Next with the flashing curser in the expression input box, right click on the role that will be part of the expression. 6. Apply the condition. 7. Click on the THEN Portal Desktop expression. Delete the expression to the right of the = character. Then add the customer desktop to the expression. 8. Apply the Then Expression. 9. Save the object main_rules SAP AG 11

13 Note: If multiple conditions apply to a user, the rule that is listed first will be applied when the user logs in. Note: When assignment to a new rule has been made to a user who has previously logged in, the theme may not immediately be seen. Once the Portal has been restarted, the default theme will be displayed SAP AG 12

14 No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are trademarks of their respective companies SAP AG 13