IT Scenario Overview <insert scenario name>

Transcription

1 SAP NetWeaver IT Scenario Overview <insert scenario name> Know-How Network Call SAP NetWeaver External-Facing Portal Introduction John Polus SAP NetWeaver Regional Implementation Group, SAP Labs LLC

2 Overview Scenario Orientation IT Scenario Benefits Release time line Road Map Features & Functions

3 Overview Scenario Orientation IT Scenario Benefits Release time line Road Map Features & Functions

4 Motivation for implementing the scenario The SAP NetWeaver Portal is the standard scenario for exposing organizational content. It supports applications with high functionality that sometimes results in heavy resource consumption. Customers want to use SAP NetWeaver Portal to expose applications, services and information over the internet, in a manner similar to a standard, customizable, web site. Implementing a Web portal which performs well in low bandwidth networks and over dial up internet connections. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 4

5 Scenario Variant Implementing an External-Facing Portal With the SAP NetWeaver Portal component, organizations can implement a public Web portal that performs well in low bandwidth networks and operates in a manner similar to a standard, customizable, Web site. Although not always appropriate for certain resourcerich applications, the external-facing portal can boost ROI by using the same platform for the company's Internet and intranet implementation. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 5

6 Current implementation of portals over the Web Today, it is possible to expose a portal over the web in the following ways: Implementing the external-facing portal Scenario variant Exposing the portal in the WWW as is The disadvantages of this implementation are: Performance over WAN might be poor. Web-site-like behavior in not supported. Development of new navigation iviews is complex. Custom-development of an External Facing Portal Solution The disadvantages of this implementation are: This is not the standard way of using the portal. It requires deep knowledge of the portal navigation API. It requires drastic code changes to the portal and complicated custom development. It requires an ongoing consultant support. These changes are not always supported when upgrading. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 6

7 Exampels of Portals Over the web SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 7

8 Overview Scenario Orientation IT Scenario Benefits Release time line Road Map Features & Functions

9 Scenario Orientation SAP introduces with SAP NetWeaver a process-driven, scenariooriented view of the technology platform. An IT scenario consists of multiple IT processes which are precisely grouped into scenario variants to attain a defined business goal. IT Scenario Running an Enterprise Portal Scenario variant Providing Uniform Content Access Scenario variant Implementing a Multitenant Portal Scenario variant Implementing a Federated Portal Network Scenario variant Implementing an External-Facing Portal SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 9

10 SAP NetWeaver IT Practices and IT Scenarios IT Practices IT Scenarios User Productivity Enablement Running an Enterprise Portal Enabling User Collboration Business Task Management Mobilizing Business Processes Enterprise Knowledge Management Data Unification Master-Data Harmonization Master-Data Consolidation Central Master-Data Management Enterprise Data Warehousing Business Information Management Enterprise Reporting, Query, and Analysis Business Planning and Analytical Services Enterprise Data Warehousing Business Event Management Business Event Resolution Business Task Management End-to-End Process Integration Enabling Applicationto-Application Processes Enabling Business-to- Business Processes Business Process Management Enabling Platform Interoperability Business Task Management Custom Development Developing, Configuring, and Adapting Applications Enabling Platform Interoperability Unified Life-Cycle Management Software Life-Cycle Management SAP NetWeaver Operations Application Governance & Security Authentication and Single Sign-On Integrated User and Access Management Consolidation Enabling Platform Interoperability SAP NetWeaver Operations Master-Data Consolidation Enterprise Knowledge Management Enterprise Service Architecture Design & Deployment SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 10 Enabling Enterprise Services New SAP NetWeaver Technology Map as of April 2005

11 Overview Scenario Orientation IT Scenario Benefits Release time line Road Map Features & Functions

12 Implementing an External-Facing Portal - Processes Configuring an Externalfacing portal Creating External- Facing Portal content Maintaining an External- Facing Portal Using an Externalfacing portal SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 12

13 Implementing an External-Facing Portal Configuring the External-Facing Portal Creating External- Facing Portal content Maintaining the External-Facing Portal Using the External-Facing Portal End User (12) Self Register (optional) (13) Logon to the portal (optional) (14) Work with the portal Content Admin (5) Customize the light Framework page (9) Define content for external-facing portal usage (10) Define application Quick Links (optional) User Admin (1) Define user profiles (2) Assign permissions System Admin (3) Configure navigation cache (6) Customize styles (optional) (11) Monitor performance and usage statistics (7) Assign Light Framework Page to Users/Groups/Alias Dev (4) Create/modify Navigation iviews (8) Create light content SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 13

14 Process Description I Configuring an External-Facing Portal The portal administration environment provides tools for configuring and setting up a portal over the internet, for external users, using the standard SAP NetWeaver portal tools. The IT process steps run as follows: 1. Define user profiles 2. Assign permissions 3. Configure navigation cache 4. Create/modify Navigation iviews 5. Customize the light Framework page 6. Customize styles (optional) 7. Assign Light Framework Page to Users/Groups/Alias SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 14

15 Process Description II Creating External-Facing Portal content The Portal Content Studio provides a central administrative environment for creating and assigning light content for external-facing portal usage. The IT process steps run as follows: 8. Create light content (Content which does not require a lot of resources) 9. Define content for external-facing portal usage SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 15

16 Process Description III Maintaining an External-Facing Portal The portal provides a complete set of tools to maintain, manage and monitor the external-facing portal usage and users within one coherent environment. The IT process steps run as follows: 10. Define application Quick Links (optional) 11. Monitor performance and usage statistics SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 16

17 Process Description IV Using an External-Facing Portal The portal runtime environment offers users a single point of access over the internet to information which is relevant to the external user. The IT process steps run as follows: 12. Self register (optional) 13. Logon to the portal (optional) 14. Work with the portal SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 17

18 Overview Scenario Orientation IT Scenario Benefits Release time line Road Map Features & Functions

19 External-Facing Portal benefits (1/2) The benifits from using SAP NetWeaver External-Facing Portal Performance Web-like Behaviour Ease of Customization - Reduce Network traffic (Java script files, CSS, HTML) - Reduce clientserver round trips - Support of standard browser buttons - Search Engine Indexing - Navigation via Standard URLs - Openness to browsers Tag Libraries enable easy customization of navigation iviews and iview trays SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 19

20 External-Facing Portal benefits (2/2) Although the external-facing portal is not appropriate for all content types (for more information see note # ) it enables and facilitates the creation of an SAP NetWeaver portal over the Web to allow users access to information, applications and services. The external-facing portal: Improves the performance of the portal over the Web Provides portal behavior which is requested and expected from web sites (browser functionality, indexing by search engines, etc. ) Simplifies the customization of the portal look and feel Reduces TCO and increase ROI by using the same platform both for internal and internet portal. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 20

21 Overview Scenario Orientation IT Scenario Benefits Release time line Road Map Features & Functions

22 Release Time Line NW04 the External Facing Portal features were released as part of NW04 SP14. NW2004s the External Facing Portal features are planned to be released as part of NW2004s SPS6. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 22

23 Overview Scenario Orientation IT Scenario Benefits Release time line Road Map Features & Functions

24 Road Map KM and Collaboration rooms are in the process of being qualified on the light framework page. Currently there are no plans for enhancing the provided features. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 24

25 Overview Scenario Orientation IT Scenario Benefits Release time line Road Map Features & Functions

26 Configure Navigation Cache In order to improve performance and reduce network traffic the portal caches each set of navigation nodes required by a user. If a user has access to the same navigation hierarchy as a previous user, the portal can retrieve the navigation hierarchy from the cache instead of generating them again. Whenever a new entry point is added to an existing role, the cache is invalidated. You must clear the cache for the change to take effect. By default, caching is turned off. After the portal is set up and tested, turn on and configure caching by setting the appropriate J2EE parameters. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 26

27 Resource sensitive page builder The page builder was enhanced to provide: Web resources are loaded only on demand EP Java Script files HTMLB (HTML & CSS files) iview can be marked as Not using EP JavaScripts Page Builder automatically adjusts heaviness and functionality to content requirements Open Tray Tag Library enables the creation of light iview trays SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 27

28 Light Framework Page The light framework page provided which is a single-frame page enhances performance, reduces network traffic and enables Website-like behavior Content / User Roles can be displayed through both Standard and External Framework Pages Framework Page resolving by Portal Aliases & Desktop technology Standard Framework Page Light Framework Page SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 28

29 Light Framework Page (cont.) Company Employee Home / WAN Portal Reverse proxy Internet user LAN Standard Framework Page Light Framework Page SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 29

30 Light Framework Page (cont.) SP12 to SP14 Comparison Optimized Framework Only SP12 SP14 - SFW SP14 - LFW Uncompressed Compressed All numbers in Kb SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 30

31 Light Framework Page - Navigation by URL User can send links by mail or save to browser favorites Most navigation functionality is kept through URL parameters Supports search engine indexing Ability to copy/keep URL View navigation URL properties SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 31

32 Short Navigation URLs It is possible to configure the portal URL to be displayed as short URL. This functionality Reduces network traffic and enables browser cache utilization. Hides internal content structure. Supports HTTP GET request & Browser Cache utilization. Hashed URL SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 32

33 Navigation Quick Links Provides the ability to set specific quick links (i.e. URL shortcuts) to specific pages/iviews For Example - Navigation quick links SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 33

34 Setting Navigation Quick Links SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 34

35 Customizing Navigation, Framework, Layout Tag libraries enable quick and easy creation or customization of: Navigation iviews (masthead, TLN, DTN) iview trays Portal provides set of out-of-the box navigation iviews: Based on tag library Reduced JavaScripts Reduced CSS files Navigation links as standard URLs SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 35

36 Examples of Customized Page Layout SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 36

37 Create and assign content to users For the performance benefits of the external-facing portal light framework page to be fully utilized light content must be assigned to the external users Content that does not use a lot of resources is considered light To create light content: Use static content as much as possible. Avoid client-side eventing (specify in the portalapp.xml an EPCFLevel value of 0 for no eventing). Use page layouts with custom iview trays. The default iview tray uses HTMLB. Do not create Related Links for iviews and pages Make sure that any dynamic navigation iview for your content is also light. To allow anonymous usage (optional) configure the portal content to be accessible to anonymous and self-registered users Assign users to the content using the standard role assignment mechanism SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 37

38 Limitations (1/3) Session management is not supported. WorkProtect mode is not supported. Related Links and Dynamic Navigation Not Supported Related Links: The Related Links iview uses HTMLB and EPCM, so any page with a Related Links iview will not be light. Dynamic Navigation: Any Dynamic Navigation iview that uses HTMLB or EPCM causes pages on which they appear not to be light. App integrator iviews not supported When using the App integrator iviews back button is not functional. Content not supported Web Dynpro Business packages As they use session management and work protect mode. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 38

39 Limitations (2/3) KM and collaboration Although you can run KM iviews in the light framework page of an external-facing portal, a portal running these iviews might not fully enjoy the performance benefits of the light framework page. Browser functionality (that is, the use of the browser s navigational buttons, such as Back, Forward and Add to Favorites) is not supported within KM iviews. KM content may not be indexed by search engines. KM content cannot be accessed via the quick links implementation. Collaboration rooms are not supported Planed to be supported with SPS7. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 39

40 Limitations (3/3) Anonymous user support with hashed URLs general limitation until SPS16 - see note Planed to be fixed with NW2004s SPS7 (NW2004 SPS16) Names anonymous users general limitation until SPS16 - see note For the most updated list of limitations list see: External-facing portal central note NW2004s Central Note SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 40

41 Summary By implementing an internet site using the External Facing Portal you gain High performance over low-bandwidth connections Web Site like behavior Easy customization of Navigation iviews, Framework iviews and iview trays The external-facing portal reduces TCO and improves the portal ROI SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 41

42 Further Information Public Web: SAP Developer Network: SAP Service Marketplace: SAP corporate portal: PTU SAP NetWeaver product information Key Capabilities Portal IT Scenario SAP external-facing portal central note SAP external-facing portal documentation - SAP NetWeaver 2004s: SAP NetWeaver Library IT Scenarios at a Glance Running an Enterprise Portal Implementing an External-Facing Portal. SAP NetWeaver 04: SAP NetWeaver Library SAP NetWeaver People Integration Portal Special Topics Implementing an External-Facing Portal. Related SAP Education Training Opportunities SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 42

43 Overview Scenario Orientation IT Scenario Benefits Release time line Road Map Features & Functions FAQs

44 Overview The FAQ is was created to provide answers to common questions collected during customer meetings and events. The FQA is divided to the following categories: General Content Navigation and the Light Framework Page Tag Libraries SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 44

45 General (1/4) Q: What is an external-facing portal? A: An external-facing portal is an implementation of the SAP NetWeaver Portal as a public Web site. An external-facing portal is open to the internet, providing content to anonymous users, internal employees and business partners and enabling users to self-register in order to access additional content and to personalize the portal. An external-facing portal uses features of the portal that provide Weblike behavior (for example, use of the browser navigation buttons) and reduce the amount of resources required to view portal pages. Although not always appropriate for certain resource-rich applications, the external-facing portal can boost ROI by using the same platform for the company's internet and intranet implementations. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 45

46 General (2/4) Q: What version of NetWeaver do I need to implement an externalfacing portal? A: SAP NetWeaver 04 SPS 14 or higher, or SAP NetWeaver 2004s SPS 6 or higher. Q: Where can I find documentation about implementing an externalfacing portal using SAP NetWeaver Portal? A: The most current documentation is available on the Help Portal (help.sap.com) at: SAP NetWeaver 2004s: SAP NetWeaver Library IT Scenarios at a Glance Running an Enterprise Portal Implementing an External-Facing Portal. SAP NetWeaver 04: SAP NetWeaver Library SAP NetWeaver People Integration Portal Special Topics Implementing an External-Facing Portal. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 46

47 General (3/4) Q: Where can I find the limitations of implementing an externalfacing portal using SAP NetWeaver Portal? A: SAP Note and SAP Note Q: Why shouldn t I use the external-facing portal for internal implementations? A: It is recommended not to use this solution for internal use because some functionality that is commonly used for internal implementations is not supported. Specifically, session management and WorkProtect mode are not supported as they require the use of the client framework JavaScript. Therefore, some standard SAP content such as Web Dynpro, SAP business packages and KM (especially collaboration) that uses these features are also not supported. In addition, to get the full benefit of the performance improvements in an external-facing portal, the content must be light and supported by the light framework page. Content in internal implementations generally does not meet these requirements. For more information on recommended content for an external-facing portal, see the Content section. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 47

48 General (4/4) Q: Should I use the provided light framework page for my externalfacing portal implementations? A: Your external-facing portal should use the light framework page, but we recommend that you customize or replace the out-of-the-box navigation iviews within the light framework page. You can easily do this with the Navigation and Framework tag libraries.q: Why shouldn t I use the external-facing portal for internal implementations? SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 48

49 Content (1/3) Q: What content is recommended for an external-facing portal? A: Content within an external-facing portal must be supported by the light framework page. And in order to get the full performance benefits of an external-facing portal, content should also be light. Q: What content is not supported by the light framework page? A: Web Dynpro, SAP business packages, Collaboration rooms. Q: What content is considered heavy and not as suitable for an external-facing portal? A: HTMLB and KM iviews. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 49

50 Content (2/3) Q: What content is considered light? A: Content that does not use a lot of resources is considered light. The following are guidelines for creating light content: Use static content as much as possible. Avoid HTMLB. Avoid client-side eventing (specify in the portalapp.xml an EPCFLevel value of 0 for no eventing). Use page layouts with custom iview trays. The default iview tray uses HTMLB. Do not create Related Links for iviews and pages Make sure that any dynamic navigation iview for your content is also light. Avoid the out-of-the box Knowledge Management iviews. Q: Can I still use HTMLB and client-side eventing in an externalfacing portal? A: Yes, however, the portal will not enjoy the performance benefits from the light framework page. The performance impact from HTMLB is much more significant than from client-side eventing. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 50

51 Content (3/3) Q: Can I still use Knowledge Management (KM) in an external-facing portal? A: Yes, but with the following restrictions: KM iviews are considered heavy content. Although you can run KM iviews in the light framework page of an external-facing portal, a portal running these iviews does not enjoy the performance benefits of the light framework page. Browser functionality (that is, the use of the browser s navigational buttons, such as Back, Forward and Add to Favorites) is not supported within KM iviews. KM content may not be indexed by search engines. KM content cannot be accessed via the quick links implementation. Q: Are collaboration rooms supported in an external-facing portal? A: No,. Q: Can I run.net iviews in an external-facing portal? A: Yes, but some HTMLB and other JavaScript files will be loaded automatically, making such iviews not as light. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 51

52 Navigation and the Light Framework Page (1/3) Q: How is navigation different in an external-facing portal? A: In an external-facing portal, the light framework page displays portal pages in a single frame. When a user clicks on a navigation link, the following occurs: 1. The browser retrieves new content for the entire browser window. With the standard framework, new content is generally retrieved for the desktop innerpage only. 2. The URL for the current page is displayed in the browser address field. With the standard framework page, the URL for the portal s home page is generally displayed. Q: How is the light framework page assigned to users? A: Administrators create desktop rules to assign desktops to different users. A desktop is a combination of a framework page and a theme. Desktops can be assigned based on such parameters as the user name, the user groups to which the user belongs, the portal alias in the URL, or the bandwidth of the user's connection. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 52

53 Navigation and the Light Framework Page (2/3) Q: Is it possible to switch between the light and standard framework page while a user is logged in? A: No. As display rules are used to provide a user with the relevant desktop when logging on, the user receives a framework page that cannot change until the user logs off. If the user then logs on again, the user could receive a different framework page if a different user name or URL is used. Q: Will the pages in my external-facing portal be indexed by internet search engines? A: Yes. Since navigation links in an external-facing portal include a complete URL that uniquely identifies a specific navigation node, search engines will be able to index portal pages. However, KM content contained within KM iviews is not indexed. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 53

54 Navigation and the Light Framework Page (3/3) Q: Can I use styles that are set in the Theme Editor with my light navigation iviews? A: The default light navigation iviews that come with the portal contain styles that can be customized using the Theme Editor. These styles are listed in the Theme Editor under Light Top-Level Navigation and Light Detailed Navigation. You can create your own light navigation iviews by copying the default light navigation iviews and making modifications, while keeping the styles already defined in these iviews. In your light navigation iviews, you cannot use styles set in other areas of Theme Editor, nor can you create your own styles and link them to the Theme Editor. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 54

55 Tag Libraries Q: Can I use the Navigation, Framework and Layout tag libraries to create navigation iviews and custom layouts for the standard framework page? A: Yes SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 55

56 Copyright 2006 SAP AG. All Rights Reserved 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, Outlook, and PowerPoint 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, and Informix are trademarks or registered trademarks of IBM Corporation in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C 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. MaxDB is a trademark of MySQL AB, Sweden. SAP, 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 the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP AG 2006, SAP NetWeaver External Facing Portal Introduction, KHNC 56