1 / 47

The Portal Installation Process

The Portal Installation Process. Installation SAPNetweaver 2004s Usage Type EP and EPCore With database SQL Server 2005. The Portal Installation Process. Important is the setting for SQL collations. The Portal Installation Process JAVA SDK and Database Client.

igor-valdez
Download Presentation

The Portal Installation Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Portal Installation Process • Installation SAPNetweaver 2004s Usage Type EP and EPCore • With database SQL Server 2005

  2. The Portal Installation Process • Important is the setting for SQL collations

  3. The Portal Installation Process JAVA SDK and Database Client • Installation of JAVA SDK 1.4.2.13 and Database Client on all involved hosts • Central Services Instance Host • Database Instance Host • Central Instance Host • Dialog Instance Host

  4. The Portal Installation Process SAPInst Installation as Domain Administrator Call SAPInst on the global host

  5. The Portal Installation Process SAPInst on SAP global Host • Necessary software packages • Installation Master • Unicode Kernel • SQL Server 2005 Client Install

  6. The Portal Installation Process SAPInst Choose Custom Installation  SAP System ID and Installation Drive

  7. The Portal Installation Process SAPInst Local Installation only for a single Instance Installation Passwords for user <SID>adm and user SAPService<SID>

  8. The Portal Installation Process SAPInst SCS Instance Number Don‘t use: 43 ( used by MSCS ) 60 ( used by iSCSI ) 89 ( used by Windows Terminal Server The internal SCS Messaging Service Port is listening on Port 39<Instance Number> ( Is needed for internal communications )

  9. The Portal Installation Process SAPInst Starting Tasks Installation is complete

  10. The Portal Installation Process SAPInst on Database Instance Host • Necessary software packages • Installation Master • Unicode Kernel • Java Component NW2004s • JCE Unlimited Strength Jurisdiction Policy Archive

  11. The Portal Installation Process SAPInst Profile directory of the SAP system Master Password for all J2EE-Users

  12. The Portal Installation Process SAPInst Database Connection Password for database schema user

  13. The Portal Installation Process SAPInst Database Files Temp Database Files

  14. The Portal Installation Process SAPInst Key Phrase for generating of Keypair Tasks are running

  15. The Portal Installation Process SAPInst on SAP Central Instance • Necessary software packages • Installation Master • Unicode Kernel • JAVA Component NW2004s

  16. The Portal Installation Process SAPInst on SAP Central Instance • Usage Type • EP and • EP Core

  17. The Portal Installation Process SAPInst on SAP Central Instance Instance Number Central Instance UME Configuration

  18. The Portal Installation Process SAPInst on SAP Central Instance Passwords for J2EE engine Users NWDI Integration

  19. The Portal Installation Process SAPInst on SAP Central Instance SLD Configuration Password for SLD User

  20. The Portal Installation Process SAPInst on SAP Central Instance Tasks starting • Provide the Solutionmanager Key • System has to be created with • TA SMSY in the Solutionmanager • before

  21. Directory Structure for a distributed System

  22. SAP Enterprise Portal Start Page URL: http://<hostname.domain>:5<Instancenumber>00/irj

  23. SAP Enterprise Portal Start Page

  24. The Portal Promise • User-Centric, Role-Specific Webtops

  25. Software Architecture of SAP Enterprise Portal

  26. Scaleable SAP Enterprise Portal Infrastructure

  27. Secure Network Architecture

  28. SAP Portal Landscape Network Communications using a DMZ

  29. Security TCP / IP Ports Protocols Communication Single-Sign On

  30. SSO variants within the EP framework • SSO with SAP Logon Tickets • Without User Mapping (preferred, when possible) • With User Mapping • SSO with User ID and Password

  31. SSO variants outside the SAP Portal Framework • X.509 digital certificates • SPNego ( Kerberos Authentication )

  32. What are SAP Logon Tickets? • They represent the user credentials • They are implemented as a non-persistent cookie in the client web-browser • They are sent with each request of the client to a web server in the same domain as the portal server that issued the ticket • They can be used by connected external systems to authenticate the portal user to those systems without any further logons

  33. The SAP Logon Ticket contains • Portal user ID and if required, one mapped user ID for external applications • Highest authentication scheme of the user • Ticket Validity period (default value = 8 hours) • Information identifying the issuing system (the unique credentials of the portal) • Digital signature • The Portal Server issues a SAP logon ticket for the Internet domain or the Internet sub-domain of the Portal Server only.

  34. The SAP Logon Ticket SSO Process

  35. The SAP User Management Architecture

  36. 3rd PartyTools SAP Solution Manager CCMS Monitoring Architecture Overview Non-SAP Component Other SAP Components (EP6.0) SAPCCMSR SAPCCMSR Shared Memory Segment Shared Memory Segment Push Central Monitoring SAP Web AS  6.20 SAP Web Application Server SAP Web Application Server Push SAP Instance SAP Instance SAPCCM3X SAPCCM4X Shared Memory Segment Shared Memory Segment

  37. Availability Monitoring Using GRMG: Overview HTTP-Request HTTP-Response SAP Web AS Central Monitoring System GRMGApplication SAP J2EE Engine Solution Manager CCMS GRMGInfrastructure GRMGApplication Other Components SAP System GRMGApplication LocalCCMS

  38. Web Dynpro – Main Goals Deliver an Enterprise Quality Web Development Environment • minimize coding, maximize design • support reuse of components • separate layout and logic • support arbitrary backends Achieve Independence... • from platform • from UI technology Improve User Experience through a "High Fidelity Web UI" • browser based, zero footprint • screen updates w/o page reloads • client-side dynamics • performance through caching • personalization • 508 accessibility compliance Web DynproTools Web DynproMeta-Data Web Dynpro Runtime J2EE ABAP Multi Device Internet

  39. Easy integration into SAP Enterprise Portal Adapt Portal theme for Web Dynpro application The user-interface technology for SAP EP Sophisticated businessWeb applications Wizards andgraphical tools Efficient tools within SAP NWDeveloper Studio & ABAP Workbench Integration intoSAP Web AS Performant user-interface development services Declarativeprogramming Platform-independentmetadata generation Development Layers: Advantages and Examples

  40. Model View Controller (MVC) • Design pattern for decoupling presentation and logic of an application • Handles events • Updates application data • Defines control flow Controller Request • Defines application data • Usually connected to business functionality Model View Response • Visualizes the application data

  41. Web Dynpro Component Based UI Design View • Web Dynpro Component • View • Predefined UI Elements • Constitute the look & feel • Build-In functions in UI Elements • Controller • Graphical Navigation flow • Graphical Data flow – automatic data transport • Model • ABAP • Java • Web Services • Graphical modeling tools replace code editors • more design, less maintenance UI Elements Controller Data Navigation Model ABAP Java DB Web Service

  42. SAP Portal: Content • Portal Content Studio • provides a central environment for developing and managing the following types of portal content • iViews • Pages • Roles • Worksets • Layouts • Folder • Content management • browse and search tool enables you to view and manage portal content stored in the Portal Content Directory (PCD) • Content maintainance • wizards, editors and user interfaces enable you to create and edit portal content

  43. SAP Portal: iViews • iViews (integrated View) • is a logical portal content building block representing a visual application or part thereof • assigned to a portal page; page is then assigned to any number of user roles or worksets • assigned via Copy-Paste or Copy-Paste as Delta Link • Portal components from PAR files (portal archives) • Types: Web Dynpro (Java, ABAP), Web based URL, XML, SAP BSP-iView, SAP transaction, etc. • Properties: Isolation method (embedded, URL), Cache level (None, Session, User, Shared, Roles)

  44. SAP Portal: Content • Portal Content Studio • provides a central environment for developing and managing the following types of portal content • iViews • Pages • Roles • Worksets • Layouts • Business objects • Business object operations • Content management • browse and search tool enables you to view and manage portal content stored in the Portal Content Directory (PCD) • Content maintainance • wizards, editors and user interfaces enable you to create and edit portal content

  45. SAP Portal: User Administration User Management Engine (UME) • support multiple data sources: e.g. LDAP directory, database of the SAP NetWeaver Application Server, ABAP system • manage users, groups, roles and additional data • support mapping of portal user IDs (SSO)

  46. EP Praxis: KAGes

  47. EP Praxis: KAGes

More Related