|Home • Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
Basics of Enterprise Portal development using Java
By Swetabh Shukla, Infosys Technologies Ltd
Some basic terminologies
Perspectives in SAP
Netweaver Developer Studio
A Perspective is group of editors and views in the workbench window.
Eclipse has several default perspectives that provide easy access to functions and editors for specific purposes:
It defines user access rights. Every portal object can be assigned to an user or a group of users through user groups and roles. Role is collection of information, services and tasks that are available to a group of users.
iView (Integrated Views)
An iView is a portal content building block. Each iView has a set of properties which are used at runtime. These properties differentiate one iView from other iView. Also an iView can be based on other iView and can inherit properties or can overwrite some properties of parent iView on which it is based.
Users can access iViews assigned to their roles. iView can be assigned to portal pages. These pages can be further assigned to any number of user roles. A user can access all the iViews contained on that page to which his roles have access rights. iViews can also be assigned directly to user role.
Working with components organizes the application and also divides the application into reusable units. Components provide encapsulation. The Outside world has no knowledge about the objects in a component. In EP mostly classes are embedded in Netweaver component. These classes are not visible to outside user. These classes are only visible to outside user if they are added in public part of component.
Now a portal component is a Java class written and packaged specifically to run in the portal.
of all why we need to know about API. The answer is, it is required to add
functionalities in our netweaver applications. Here we are concerned mostly
about EP development using Java.
API has a list of all Java packages, classes, and interfaces; along with all of
their methods, fields and constructors; and also with information on how to use
developing enterprise portals through SAP Netweaver using JAVA we need to use
the packages, classes or interfaces provided in the API.
are various APIs provided by SAP to help in development of Netweaver
applications using JAVA.
Here I will try to discuss Enterprise Portal APIs. They are used in development of enterprise portals.
The following three APIs are most commonly used while developing an Enterprise portal:-
are various packages in Enterprise Portal API which provides classes and
interfaces for implementing Portal runtime, Page builders, wizards , dynamic
system resolutions etc.
We will discuss few useful classes and interfaces generally used in EP development.
present in package com.sapportals.portal.prt.component
Portal Components implement this interface either directly, or more commonly by
extending a class that implements this interface.
implemented by class AbstractPortalComponent
This interface contains 3 methods :
void service(IPortalComponentRequest request,
IPortalComponentResponse response) throws PortalComponentException
parameter – client’s request
parameter- server’s response
is present in package com.sapportals.portal.prt.component
AbstratPortalComponent class implements following interfaces :
It provides portal Edit, Help etc modes.
For this it has many methods like doHandleEditData(), doHelp(), doPreview() and many other methods.
Creating a simple portal application project
We will create a simple portal application project and then we will use this project to create iView, page and roles on EP.
Create a Portal Application Project
Click the Create Portal Application
Project icon or use menu path.
File -> New -> Other -> Portal Application -> Create
Portal Application Project
name of project and directory where you want to store the project and click
click on icon Create Portal Application Objects
select the project you created and click next.
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM
©2006-2007 SAPTechnical.COM. All rights reserved.
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
Graphic Design by Round the Bend Wizards