SAP Netweaver Portal-Journey From Beginners To Masters

SAP NetWeaver Portal A Journey
from beginners to Masters.
Applies to:
SAP Enterprise Portal 7.0. For more information, visit the Portal and Collaboration homepage.
Summary
This article is to help all SAP developers who are new to Portal and wish to expertise in the SAP EP module.
As I was going across many blogs and articles for understanding Portal, I observed it is more distributed than
compressed. So this made me to pile up all required information for user who wishes to learn Netweaver
Portal.
Author:
Shaila Kasha
Company: Satyam Computers Services Limited

Created on: 04 June 2009
Author Bio
Shaila Kasha working as SAP Netweaver Portal Technical Consultant for Satyam ComputersHyderabad. Having an experience of 3 years in SAP and J2EE Technologies and well versed in
SAP Enterprise Development objects, HTMLB and hands on in PDK. Active SDN contributor.
SAP COMMUNITY NETWORK

2008 SAP AG
SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

1
SAP NetWeaver Portal A Journey from beginners to Masters.
Table of Contents
Introduction .........................................................................................................................................................3
Concept 1:...........................................................................................................................................................3
What does SAP NW Portal mean and its components?.................................................................................3
Concept 2:...........................................................................................................................................................4
Need for SAP NW Portal.................................................................................................................................4
Concept 3:...........................................................................................................................................................4
Components of SAP EP..................................................................................................................................4
Portal Framework:........................................................................................................................................................5
Unification ....................................................................................................................................................................5
Connector Framework .................................................................................................................................................5
Knowledge Management (KM).....................................................................................................................................5
Collaboration................................................................................................................................................................6
Concept 4:...........................................................................................................................................................6
PCD objects ....................................................................................................................................................6
iView ............................................................................................................................................................................6
Page ............................................................................................................................................................................7
Workset........................................................................................................................................................................7
Role .............................................................................................................................................................................8
Concept 5:...........................................................................................................................................................9
Enterprise Portal Development .......................................................................................................................9
Concept 6:...........................................................................................................................................................9
Getting started.................................................................................................................................................9
Concept 7:.........................................................................................................................................................10
Customizing Portal ........................................................................................................................................10
SLD: ...........................................................................................................................................................................10
Landscapes:...............................................................................................................................................................10
Software Catalog: ......................................................................................................................................................10
Concept 8:.........................................................................................................................................................11
Business Packages.......................................................................................................................................11
Concept 9:.........................................................................................................................................................11
Connectivity through system objects ............................................................................................................11
Concept 10: ......................................................................................................................................................12
Portal Development Kit .................................................................................................................................12
Concept 11: ......................................................................................................................................................13
Java Connector (JCO) ..................................................................................................................................13
Java Connector Architecture (JCA)............................................................................................................................13
Differences between JCO and JCA ...........................................................................................................................14
Concept 12: ......................................................................................................................................................15

Enterprise Portal Client Framework (EPCF) .................................................................................................15
Related Content................................................................................................................................................17
Disclaimer and Liability Notice..........................................................................................................................18

2008 SAP AG

2
Introduction
As I was going across many blogs and articles for understanding Portal, I observed it is more distributed than
compressed. So here it is a complete journey through Portal with all required information for user who wishes
to Expertise.
SDN is filled with many informatics articles on portal explaining its features and capabilities. But what I
needed was a complete flow in which a beginner can not only understand but also expertise and know the
concepts very well. I thought it would be better if it was in a questionnaire manner or concept based and also
helpful for questionnaire at any interview, so that it helps in easy learning of the subject.
Concept 1:
What does SAP NW Portal mean and its components?
The most basic question arises is what do we mean by SAP NetWeaver portal and what components exist in
the Portal architecture. Coming to the definition of SAP Enterprise Portal also can be called as SAP
Netweaver Portal. As we all are aware of the fact that SAP Netweaver Portal comes under the People
Integration and Information Integration in the SAP Architecture Stack.
In simpler terms its the method to show case the connectivity between various SAP or Non-SAP systems
and hence provide a single authentication at the same time providing high security for the viewed data.
SAP NetWeaver Portal is a J2EE application (irj- iview runtime for Java) that is designed to handle HTTP
requests for portal components. A portal component is a Java class written and packaged specifically to run
in the portal.
The Key parts of Portal being
1.
Portal Runtime Engine
2.
Portal Applications
3.
PCD
4.
J2EE Engine
All the above new terms are explained in detail as we proceed with the article. So here only a brief
description has been provided.
The Portal Runtime Engine is able to run portal components and send back to the response the HTML
produced by the component. The Portal Runtime includes a dispatcher servlet, which receives HTTP
requests for portal components and starts the request cycle.
Portal Application is a collection of components and services written specifically to be run in the portal. The
portal comes with out-of-the-box applications for example, for displaying navigation hierarchies or for
creating iViews and developers can create and deploy their own applications.
Here is a new term iViews, these are the basic building block for portal. We display information or formatted
data with the help of iviews. There are several types of iviews available at Portal which will be summarized
as we proceed with the article.
A portal application is a compressed file with a .par extension (Portal Archive) that contains Java class files,
an application descriptor and other resource files, as needed. Applications define the Components and
services which are only deployed as part of a portal application
PCD (Portal Content Development) is a repository for portal semantic objects (such as iViews, pages,
systems, and transport packages). The data about portal objects is stored in the J2EE Engine database.
The Portal Runtime engine runs within the J2EE Engine, which also hosts other applications and services
required by the portal, such as the Connector Framework and User Management Engine.

2008 SAP AG

3
Concept 2:
Need for SAP NW Portal
Why do we need SAP Netweaver portal though we have many front-end GUIs available in the market.
The question is not as simple as it looks to be. We need SAP NW Portal as a way to unify frontends for
different backend and deliver additional tools to desktops in a browser environment. The security features
makes it hot in SAP module. Hence the integration of SAP Portal with other modules have been the most
vital and crucial advantage of SAP NW Portal.
As mentioned earlier, EP is running on WebAS. This means by using WebAS technology we can of course
do everything in the portal too. The portal gives you a frame with some functional additions (like unified login)
that we then don't have to program.
There are few basic features of Portal which are of great importance for handling any implementations and
its feature of single authentication is key factor for its popularity. Here on I shall present blogs or articles for
each and every part of portal which makes it really easier way of learning Portal.
Concept 3:
Components of SAP EP
PORTAL FRAMEWORK
Unification
Connection
framework
KM
Plug-in
Collaboration
Extended Server
JCA
JCo
The components listed are

1.
Portal Framework
2.
Unification
3.
Connector Framework
4.
Knowledge Management (KM)
5.
Collaboration

2008 SAP AG

4
Portal Framework:
Portal Runtime
Portal Components
Portal Runtime
Portal Services
Page Builder
Admin tools
PCD
User Mgnt
Portal Components
1.
Page Builder
It is component under portal framework which is having page templates depending on the user request it
builds the page.
2.
Admin tools
To maintain the end-user logon credentials

Portal Services
1.
Portal Content Directory (PCD)
It holds all SAP provided templates as well as user components.

It is central storage device which stores the components, SAP provided as well as user-defined components
It is root directory.
2.
User Management
It is responsible to maintain portal user information as well as external system login information.
Main responsibility is authentication.
It internally connects with user persistent store.
Portal Run-time
It acts as a gateway between portal user and to portal server.
Unification
It is an external server. It provides a facility of Drag & Relate. It provides Drag & Relate feature to get the
reports from other landscapes by dragging on-to portal screens. The template will be populated on-to portal
server.
Connector Framework
To communicate with other landscapes, SAP-provided two connectors like JCO, JCA.
Knowledge Management (KM)
SAP provides a separate plug-in to have the feature of search engine. This plug-in can be attached to portal
server.

2008 SAP AG

5
Collaboration
It provides dynamic communication with other people which includes tools like chat rooms, discussion
rooms, application sharing etc. SAP provides this as a separate plug-in to have these features in EP.
Concept 4:
PCD objects
The most vital part of portal is the PCD, which help us in most of the Portal developments. As we have
already come across iviews, as the building block of portal. Let us elaborate on all the remaining components
or objects.
Overview:
Iview
Page
Workset
Role
iView
It is a portlet. We can use to communicate with n number of heterogeneous landscapes to fetch the data or
to process the information. It is a base component.
SAP WebDynpro
SAP Transaction
Standard
(SAP Provided
Templates)
DB JDBC (For RDBMS

SAP BSP
iView
URL
Yahoo
JSP (Eclipse / NWDS)

User Defined
BSP (SE 80)
.Net (.Net iView Studio)

2008 SAP AG

6
Page
It is a container which contains more than one iView.
Portal Desktop
Page
IView
Workset
It is also a container which can contain pages as well as worksets. To maintain the folder hierarchy we can
use worksets.
Workset
Page
iView
Iview
Page
Page
Workset
iView

2008 SAP AG

7
Role
A role is a collection of activities and functions that describes a certain work area of an SAP application.
Role is a final entity through which we can assign business activities to the user.
A portal role is a container for applications and information that can be assigned to a particular group of
users.
Technically a role is a hierarchy of folders containing other content objects.
Content Admin
Standard
User Admin
Role
Sys Admin
User Defined
Content Administrator
Super Admin
To design portal components like iView, Workset & role. Also used to make links between components.
User Administrator
Create users and assign roles to users. User mapping & locking the users.
System Administrator
Monitoring end users, create business packages & create system objects.
Super Administrator
It includes content administrator, user administrator and system administrator roles.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90b90eac-df95-2b10-76a9-b12aaee8ec70
Link for the Article on the basics for freshly created Portal.
In many situations we come across cases where we need to move the info from one server to another. Here
comes the major concept of Transport Packages. Here we just use the Transport feature available at Sys
Admin. We create Transport Packages, PCD objects which acts as the content carrier. It is saved as .EAR
file at our local hard disk and hence can be imported to any other portal server through the options available
i.e. import or export. Below link details us with the steps needed.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/EP/Transporting%2bPortal%2bContent

2008 SAP AG

8
Concept 5:
Enterprise Portal Development
As a beginner we always try to understand what comes under Enterprise Portal Development?
EP Development consists of developing applications (known as iViews) that run in the Portal. These
applications are typically built using Java technologies such as J2EE (JSP or Java Server Pages and EJBs
(Enterprise Java Beans), Web Dynpro, HTMLB for Java, XML, Web Services and more. Some development
is also done using the PDK for .Net. The applications have to be able to run in the Portal, which runs on a
Web Application Server, a J2EE engine that uses the Portal Runtime and, optionally, a Web Dynpro runtime.
This requires that the developer be fairly familiar with Java.
The following diagram depicts how content can be developed for the Portal and what skills are required for
each method.
The slide shows that developing custom content for the Portal requires skills in Java or .Net or ABAP/BSP,
where as the Visual Composer or Web Dynpro technologies auto-generate most of the code.
Concept 6:
Getting started
Every beginning developer needs the proper development environment for developing applications. The IDE
(integrated development environment) for Portal content is the NWDS (NetWeaver Developer Studio).
NWDS is built on the open-source IBM technology called Eclipse. In addition to NWDS, we also need access
to a Portal. At a minimum we need access as a Developer to be able to access the PDK (Portal
Development Kit) within the Portal and to deploy applications we build. We also might get Content
Administrator access to the Portal so we can see how iViews will look in the Portal once we have developed
them.
Here are few links which help us in the understanding and set up of NWDS.
https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2971
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/4d46fb8a-0b01-0010-9fbe-e4b96533b222

2008 SAP AG

9
Concept 7:
Customizing Portal
The most basic need for any developer is to get accustomed to customer requirement. Hence we might
require changing the way portal looks like and also add little functionality.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/cefee9ee-0901-0010-d891-f56ab1e20641
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d077fa17-7fbf-2a10-d983-fb12decf63c7
The above SAP articles are for changing look and feel of portal.
http://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3680
Above three are collections of blogs for Portal customization
For understanding the customization, we need to be well versed with the SLD, Admin roles of portal, their
functionalities and PAR files related to each portal page.
SLD:
SLD is the central information repository for our system landscape. It contains information about technical
systems, landscapes, business systems, products, and software components in our system landscape. This
information can be managed in the SLD.
Landscapes:
A landscape represents a logical, complex system, which consists of multiple, distributed components. Some
of these components may be systems; others may be services, installed products, or other managed
elements.
The following types of landscapes are defined in the SLD:
Administration: A system landscape, which is created for administration purposes, for example, for common
monitoring.
General: A system landscape, which can contain all types of application systems.
NWDI Systems: A system landscape that contains servers of the NWDI. The NWDI consists of a local client
the Integrated Development Environment (IDE) and some logical servers for processes like source
management, build tasks, transport, and name reservation. All servers work together and require a common
user base together with the IDE.
Scenario: A system landscape that is created for a specific business scenario. Scenario landscapes are used
in the Software Lifecycle Manager of SAP NetWeaver.
Transport: A system landscape that is created for transport purposes. For example, all SAP Web AS
systems that are connected by an ABAP transport path distributing the ABAP development.
Web Service: A system landscape that is created to collect systems offering Web services and their clients.
The hierarchy of these landscapes defines the Web service that is most appropriate for a given client.
Software Catalog:
The SLD contains a Software Catalog of all installable SAP products and software
components. The
Software Catalog includes information about support packages and dependencies between the products and
software components. This information is the basis for the description of the system landscape.
Portal Roles
As already explained about roles the below link will help in understanding more easily

2008 SAP AG

10
Intro to Portal System Objects:

Customizing portal login page as in Google accounts
Now, getting deeper to the code, an article which I wrote on customizing Portal look.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10649c90-24af-2b10-1086-ea0667ec3655
Concept 8:
Business Packages
Please check my wiki for the introduction to implementation of BP for SAP EP.
https://www.sdn.sap.com/irj/scn/wiki?path=/label/EP/ep_user_basics
Under Portal Content Development.
Concept 9:
Connectivity through system objects
System Object
SAP R/3 Dedicated
JDBC System
SAP Load Balancing
Yahoo Server
External System
iView Template
SAP R/3
SAP Transaction iView
SAP CRM
SAP DSP iView
SAP BW
SAP BW Report iView
Any RDBMS
Database JDBC iView
Web DynPro for ABAP
SAP Web DynPro iView
Web DynPro for Java

Yahoo Server
Yahoo iView
There are several templates of Objects available at System administration for external connectivity. For
interfacing with external systems, SAP has provided System Objects functionality.
Depending on the type of external system, a different type of system object has to be created there by
providing technical connection information of the external system.
One of my articles on Connectivity to Ext DB with JDBC is mentioned below for referral.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e03845f0-d1c2-2b10-5482-b28c59962231
Now coming to the most prominent aspect of SAP EP , The Single Sign On popularly called as SSO. It is a
facility to communicate with n number of system by entering single user id & password with providing further
authentications.
SAP R/3
UID
Portal
Server
CRM
HR

2008 SAP AG

11
System Obj
SQL
To achieve this functionality, we need to create a system object and in that system object we have to set the
properties like URL, driver classes of external systems.
Communication with external systems is via SAP protocol.
Check the below links for End to end implementation of SSO
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80955d0f-ae67-2b10-35a3-c2efec2ba42c
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0a5216a-349c-2a10-9baf-9d4797349f6a
Concept 10:
Portal Development Kit
As mentioned earlier the IDE for developing EP components or application is the SAP NWDS which has to
be separately installed with Plugins and which works on Eclipse.
SAP provided templates to process the information and to get the content from other sources by using
templates
Without using SAP templates if we want to create iViews, for that SAP provided PDK.
It provides different portal related components and connector framework.
Portal Components
Language
SDK
IDE Tool
JSP
PDK for JAVA
Eclipse / NWDS
.Net
PDK for .Net
.Net iView Studio
BSP
N/A
SE80
Major components in a Portal Application are as follows:

1.
iPortal Component
2.
Abstract Portal Component
3.
Page Processor component
4.
HTMLB Controls

2008 SAP AG

12
Concept 11:
Java Connector (JCO)
JCO is a middle-ware service. It provides communication from Java to SAP and vice-versa. To work with
JCO, the following package has to be imported com.sap.mw.jco.*
The following files have to be copied into System32 folder on remote machine: librfc32.dll and sapjcorfc.dll
Following JAR files have to attached to the project: sapjco.jar
getMiddlewareVersion method return version information of JCO.
disconnect method closes the connection with SAP system.
Steps to Create a JCO connection
Import package com.sap.mcojco.*
Attach JAR file sapjco.jar
Create Client
JCOClient client = JCO.createClient(<client>, <userid>, <password>, <language>, <system name>, <system
number>)
Establish connection
client.connect()
Java Connector Architecture (JCA)
It is an architecture introduced by Sun Microsystems through which we can communicate with SAP and nonSAP landscapes
JCA
SAP
Portal Server
JCA
Non-SAP
Platform
Independent
JCA 1.0 Uni-Directional ()
JCA 1.5 Bi-Directional ()
There are two ways to communicate with Java:

By Java
JCA
JAVA
ERP
JNDI Context Interface

2008 SAP AG

13
By SAP
Connector Gateway Server
Portal
Component
Portal
Sys Alias
JCA
ERP
XML
Sys Identifier = Sys Alias
SSO
While connecting using Connector Gateway Server, following JAR files has to be added:
com.sapportal.irs.connectorserviceapi.jar
connector.jar
genericconnector.jar
connectorhelper.jar
In the deployment descriptor (portalapp.xml), the following information has to be specified:
<component-profile>
<property name = SystemIdentifier value = Obj1Alias />
</component-profile>
Under application configuration node the following information should be specified:
<application-config>
<property name=ServiceReference value = com.sap.portal.irs.connectorservice />
<property name=releasable value = True />
</application-config>
Differences between JCO and JCA
JCO
JCA
Platform dependent
Platform independent
Non-secure
System alias secures login info
Only for connecting to SAP landscapes
For connecting from any landscape to any

landscape
Connecting from Portal Server to SAP

JCO.Function: It is a class which is responsible to execute RFCs on BAPI which are available in SAP.
JCO.Table: It is responsible to export and import of internal table to SAP system.
It is also a class.
iRepository: It is an interface which holds the connection information of SAP and it checks what are the
BAPIs and RFCs available in that client.

2008 SAP AG

14
iFunction Template: It is an interface which is responsible to check whether the particular RFC or BAPI is
available in repository. If it finds the function, it returns function name, otherwise it returns zero.
iScript Generator: It is an interface which converts the data in JavaScript and it provides raw text.
JCOTableViewModel: It is class which is responsible to build the table structure depending on the data
received from SAP.
Concept 12:
Enterprise Portal Client Framework (EPCF)
Purpose is data sharing between iViews on same page.
Page
Iview 1
Data Sharing
Data Sharing
Iview 2
To work with EPCF, following JAR file has to be attached, namely, com.sapportal.epcf.toolboxapi.jar
And HTMLB JARs. Deployment descriptor file (portalapp.xml) should specify the service reference in
application-config node.
Following constants are used to filter the events:
IClientEventReciever.EVENT_FILTER_ALL All events.
IClientEventReciever.EVENT_FILTER_ONE Only this clients events.
GetWrappedScript() This method retrieves data without javascript.
isRecieved() This method in receiver object. If the receiver object is subscribed to event and if it finds data
in client databag then this method return TRUE.
Client Databag
This is the object where data is stored (Java Object).
It maintains the information from an iView and it provides information to another iView.
Page
Iview 1
Iview 2
Sender
Receiver
Namespace Event Name

2008 SAP AG

15
IEPCF Toolbox:
It is an interface which is responsible to create client databag and maintain data in that object.
Procedure
Create Namespace and Event
Get EPCF Service
Create Sender object
Place the data into client databag
Raise the event
Receiver Side
Create same Namespace and event
Get EPCF Service
Create receiver object
Subscribe to the event
Get the data from client databag
Get EPCP Service
Create request
IPortalComponentRequest req = (IPortalComponentRequest)getRequest();
IEPCFTOOLBOX srv = req.getService(IEPCFTOOLBOX.key);
Create Sender Object
IClientEventSender sender = srv.getClientSender(<request>, <Namespace>, <Event>);
Place Data in Client Databag
sender.setParameter(<id>, <value>);
Create Receiver Object
IClientEventReceiver recv = srv.getClientReciever(<request>, <namespace>, <event>);
Get data from Client Databag
recv.getParameter(<id>);
Our journey through this article summarizes the details of SAP EP, scope of learning Enterprise portal,
developing Portal applications and working through the code. I hope it details the conceptual idea behind EP
and will solve many unanswered questions in SAP Netweaver Portal.
The main purpose was helping new SAP EP learners. The Architecture, the components, the feature, the
capabilities and applied fields have been summarized.
Wishing all the very best wishes for new learners.

2008 SAP AG

16
Related Content
http://help.sap.com/saphelp_nw04/helpdata/en/30/c4461ff69d5a438f1286e344b545fa/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/8b/91222fa9e611d6b28f00508b6b8a93/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f0/6ca84016631814e10000000a1550b0/frameset.htm

2008 SAP AG

17
Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not
supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,
and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or
code sample, including any liability resulting from incompatibility between the content within this document and the materials and
services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this
document.

2008 SAP AG

18

SAP Netweaver Portal-Journey From Beginners To Masters

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SAP Netweaver Portal-Journey From Beginners To Masters

Загружено:

Авторское право:

Доступные форматы

SAP NetWeaver Portal A Journey

from beginners to Masters.

Company: Satyam Computers Services Limited

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP NetWeaver Portal A Journey from beginners to Masters.

Concept 12: ......................................................................................................................................................15

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP NetWeaver Portal A Journey from beginners to Masters.

Portal Runtime Engine

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP NetWeaver Portal A Journey from beginners to Masters.

The components listed are

Knowledge Management (KM)

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP NetWeaver Portal A Journey from beginners to Masters.

To maintain the end-user logon credentials

Portal Content Directory (PCD)

It holds all SAP provided templates as well as user components.

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP NetWeaver Portal A Journey from beginners to Masters.

DB JDBC (For RDBMS

JSP (Eclipse / NWDS)

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP NetWeaver Portal A Journey from beginners to Masters.

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP NetWeaver Portal A Journey from beginners to Masters.

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP NetWeaver Portal A Journey from beginners to Masters.

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP NetWeaver Portal A Journey from beginners to Masters.

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP NetWeaver Portal A Journey from beginners to Masters.

Intro to Portal System Objects:

SAP R/3 Dedicated

SAP Transaction iView

SAP DSP iView

SAP BW Report iView

Database JDBC iView

Web DynPro for ABAP

SAP Web DynPro iView

Web DynPro for Java

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP NetWeaver Portal A Journey from beginners to Masters.

PDK for JAVA

PDK for .Net

.Net iView Studio

Major components in a Portal Application are as follows:

Abstract Portal Component

Page Processor component

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP NetWeaver Portal A Journey from beginners to Masters.