the portal installation process

SAP Österreich GmbH 2007, Andreas Lindenbauer, Karl M. Falb / 1

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

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


The Portal Installation Process SAPInst

Installation as Domain AdministratorCall SAPInst on the global host


The Portal Installation Process SAPInst on SAP global Host

Necessary software packages• Installation Master• Unicode Kernel• SQL Server 2005 Client Install



Choose Custom Installation SAP System ID and Installation Drive



Local Installation only for a single Instance Installation

Passwords for user <SID>adm and user SAPService<SID>



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 )



Starting Tasks

Installation is complete


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



Profile directory of the SAP system

Master Password for all J2EE-Users



Database Connection

Password for database schema user



Database Files

Temp Database Files



Key Phrase for generating of Keypair

Tasks are running


The Portal Installation Process SAPInst on SAP Central Instance

Necessary software packages• Installation Master• Unicode Kernel• JAVA Component NW2004s



Usage Type• EP and • EP Core



Instance Number Central Instance

UME Configuration



Passwords for J2EE engine Users

NWDI Integration



SLD Configuration

Password for SLD User



Tasks starting

Provide the Solutionmanager Key

• System has to be created with TA SMSY in the Solutionmanager before


Directory Structure for a distributed System


SAP Enterprise Portal Start Page

URL: http://<hostname.domain>:5<Instancenumber>00/irj


SAP Enterprise Portal Start Page


The Portal Promise

User-Centric, Role-Specific Webtops


Software Architecture of SAP Enterprise Portal


Scaleable SAP Enterprise Portal Infrastructure


Secure Network Architecture


SAP Portal Landscape Network Communications using a DMZ

TCP / IP Ports

Protocols

Communication

Single-Sign On

Security


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


SSO variants outside the SAP Portal Framework

X.509 digital certificates

SPNego ( Kerberos Authentication )


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


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.


The SAP Logon Ticket SSO Process


The SAP User Management Architecture


CCMS Monitoring Architecture Overview

SAPSolution Manager

3rd PartyTools

Non-SAP ComponentNon-SAP Component

SAP InstanceSAP Instance SAP InstanceSAP Instance

SAP Web Application Server

Other SAP Components (EP6.0)Other SAP Components (EP6.0)

Shared MemorySegment




Central Monitoring

SAP Web AS 6.20

SAPCCMSR SAPCCMSR

SAPCCM3X SAPCCM4X

SAP Web Application Server

Push

Push


Solution Manager

GRMGInfrastructure

GRMGApplication

SAP J2EE Engine

CCMS

Central Monitoring System

SAP System

Other ComponentsGRMGApplication

SAP Web AS

LocalCCMS

GRMGApplication

HTTP-Request

HTTP-Response

Availability Monitoring Using GRMG: Overview


Web Dynpro – Main Goals

Web DynproMeta-Data

Web DynproTools

Web Dynpro Runtime

J2EE ABAP

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

Multi Device Internet


Development Layers: Advantages and Examples

EP

WDApplication

Web DynproDesigntime

Web Dynpro Runtime

Web Dynpro Metadata

Easy integration into SAP Enterprise Portal

Sophisticated businessWeb applications

Efficient tools within SAP NWDeveloper Studio & ABAP Workbench

Performant user-interfacedevelopment services

Platform-independentmetadata generation

Adapt Portal theme for Web Dynpro application

The user-interface technology for SAP EP

Wizards andgraphical tools

Integration intoSAP Web AS

Declarativeprogramming


Design pattern for decoupling presentation and logic of an application

Request

Response

Handles events Updates application data Defines control flow

Model View Controller (MVC)

Controller

Model

View

Defines application data Usually connected to

business functionality

Visualizes the application data


Web Dynpro Component Based UI Design

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

View

UI Elements

Navigation

Controller

ModelWeb Service

JavaABAPDB

Data


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


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)


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


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)


EP Praxis: KAGes

the portal installation process

Documents

sap portal framework

irjsap enterprise portal

portal promise usercentric

sap central instancepasswords

sap systemmaster password

sap logon tickets

user id

user adm