Business Package for Portal Development Kit 60.3.0

The public version of the Portal Development Kit for Java (PDK) Business Package is now available for SAP Enterprise Portal 6.0 SP4 on iviewstudio for download. PDK 60.3.0 is based on EP 6.0 SP4 (NetWeaver 04), but It may be also imported and installed on SP3 with limitations.

Remarks

PDK 60.3 does not contain anymore development plugins for eclipse. From EP 6.0 SP3 on, you PDK plugins are already integrated into SAP NetWeaver Developer Studio (available with SAP Web Application Java Server 6.40)

http://www.iviewstudio.com/ –> login –> Content Catalog –> Specialist –> Other –> Portal Development Kit

Prerequisites

You have installed a standard SAP Enterprise Portal 6.0 SP4 either locally on your personal PC or on a test server.

Management Summary

The Business Package for Portal Development Kit offers a collection of information and tools enabling developers to develop content for SAP Enterprise Portal. It consists of tutorials that explain how to develop portal components using the public Java API (application programming interface) of SAP Enterprise Portal and tools for deploying and testing portal components in a running portal. It also offers a range of Eclipse tools for developing portal applications and JCA (Java Connector Architecture) connectors.

Business Value

The Business Package for Portal Development Kit is intended for skilled Java developers that write custom content for SAP Enterprise Portal. Developers can write their Java code using any development environment. The Business Package for Portal Development Kit works together with the SAP NetWeaver ’04 Developer Studio, that includes wizards that automate tasks such as compiling Java classes, creating a Portal Archive, and uploading the Portal Archive directly into the portal.

The Business Package for Portal Development Kit provides tools for the following tasks:

Uploading Portal Archive files from a local directory into the portal Portal Archive files contain the collection of java classes and other information required to produce content in the portal.

Deleting Portal Archive files from the portal

Viewing detailed information, such as configuration files, for all portal applications available in the portal

Viewing source code of example portal components shipped with the business package

Creating roles, worksets, and pages using the Portal Content Studio In addition, it provides:

Tutorials and example source code to assist developers in the development process

Documentation for all public portal APIs (application programming interfaces)

Plug-Ins for Eclipse containing Portal Archive wizards, connector framework wizards, and so on

Technical Data

Availability	SAP Enterprise Portal 6.0 SP2
Browser Recommendation	See Product Availability Matrix for SAP Enterprise Portal 6.0 SP2 at service.sap.com/ep → Product Information → Enterprise Portal 6.0 → Product Availability Matrix.
Languages	EN English
Data Source	SAP System greater than or equal to 4.0B that fulfils the prerequisites for Single Sign-On with SAP logon tickets. For more information on these prerequisites, see Enterprise Portal Administration Guide 5.0 → Security → Single Sign- On → Single Sign-On with SAP Logon Tickets → Configuring SAP Systems to Accept and Verify SAP Logon Tickets
Support Component	EP-PDK

Supported Roles

This business package contains the Java Developer role which consists of the following worksets:
• Development
• Documentation
• Examples

These worksets are described in more detail below.

Development

This workset guides the developer through the steps required after writing the code for portal
content. It contains the following pages:

Component Manager: Allows you to upload Portal Archive files in to the portal or delete them from the portal

Component Inspector: Lists all portal applications available in the portal                             and allows you to:
      View all portal components contained in a portal application
      View the configuration file for a portal application
      View the source code for portal components shipped     with this business package
      Define portal applications as favorites
      Launch portal components from the list

Component Starter: Displays a list of all portal components in the portal and allows you to launch them directly from the list

Portal Content: Displays Portal Content Studio which provides a central environment for developing and managing all types of portal content, such as iViews, pages, layouts, worksets, roles and packages. For more information, see Enterprise Portal Administration Guide 6.0 → Portal Platform → Content Administration → Portal Content Studio.

Support Desk: Helps you perform initial troubleshooting for your Enterprise Portal.

Download: Provides plug-ins for Eclipse to allow for an integrated development environment and a script file to build Portal Archive files.

Documentation

This workset contains documentation and examples. It also includes documentation for all public portal APIs (application programming interfaces).

Examples

This workset consists of an iView that allows you to test the effects of setting different properties on the appearance of HTMLB controls. It will be extended to include other helpful tools in future releases.

Technical Description and Configuration Information

Purpose

The following procedure describes how to install the Business Package for Portal Development Kit in a portal and how to configure the portal so that the example iViews work correctly.

Prerequisites

You have installed a standard SAP Enterprise Portal 6.0 SP0 either locally on your personal PC or on a test server.

Process Flow

Import the Business Package for Portal Development Kit into your portal installation
The business package is delivered in SCA format and you must use the Software Deployment Manager (SDM) to install it. For more information, see SAP Note 731386.

Configure the portal for the Portal Development Kit

The example iViews in the Portal Development Kit connect to a SAP System with the system alias PDK_R3_BACKEND. For these examples to work properly, you must define a system object for a test SAP System in your system landscape and assign it the alias PDK_R3_BACKEND. For more information on creating system objects and assigning aliases, see Enterprise Portal Administration Guide 6.0 → Portal Platform → System Administration → System Landscape → System Landscape Editor.

To ensure that you have the correct permissions to run all the applications in the business package, you must be assigned to the following portal roles:

Role ID	Description
pcd:portal_content/administrator/super_admin/super_admin_role	Super Administration
pcd:portal_content/com.sap.pct/administrator/super_admin/com.sap.portal.super_admin_role	Super Administration
pcd:portal_content/com.sap.pct/Developer/Portal_Development_Kit/ Roles/com.sap.pct.portal.pdk.JavaDeveloper	Java Developer
pcd:portal_content/com.sap.pct/every_user/general/com.sap.portal.eu_role	Standard User Role
pcd:portal_content/com.sap.pct/specialist/com.sap.km.ContentManager/com.sap.km.ContentManager	Content Manager

Create user in SAP System

The example iViews connect to the SAP System using the user with which you are logged on to the portal. You must create a user in the SAP System with the same user ID as your portal user.

8 Comments

You must be Logged on to comment or reply to a post.

Pankaj Kumar May 11, 2004 at 12:48 pm

Oliver

While I like the release of latest BP for PDK. But how could this be useful to general public who is still on SP2 as SP4 I believe is still in RAMP-UP.

Regards
Pankaj

like (0)
1. Oliver Stiefbold Post authorMay 12, 2004 at 12:40 am
  
  thats true, SP4 is in Ramp-up. But we are going to offer it also as sneak preview soon.
  
  like (0)
  1. Pankaj Kumar May 12, 2004 at 4:45 am
    
    Yoohoo life would be so much worth living for 😉 I can’t wait to see that happen.
    
    Pankaj
    
    like (0)
  2. Former Member May 13, 2004 at 11:38 pm
    
    Hi Oliver,
    
    Is it possible to use this PDK with EP6 SP2 ?
    
    Regards
    Ahmet
    
    like (0)
    1. Oliver Stiefbold Post authorMay 15, 2004 at 2:48 am
      
      no, I cant imagine, we changed so much. I think already the import will not work, because the PCD transport API changed completely from SP2 to SP3
      
      like (0)
Gregor Wolf May 12, 2004 at 10:40 pm

Hello,

when will a standalone Portal Development Kit avaliable?

Regards
Gregor

like (0)
Former Member July 13, 2005 at 4:49 am

Hi ,
I have gone through this weblog.
we have a requirment , where developers will not be given system admin role but they should be able to deploy, browse, download and delete par applications. so PDK comes as a solution , it comes with java developer role which can handle these tasks .

But we need system admin role to use PDK, what is the use of having PDK ?
can you please let me know if we can use PDK with out system admin role…

Thanks,
Lakshmi

like (0)
1. Oliver Stiefbold Post authorJuly 15, 2005 at 12:36 am
  
  no, you need systemadmin role to delete .pars.
  By the way, you dont need necessarily PDK 60.9++ to develop on NW04. For NW04 PDK is just goody to ease developers live.
  
  like (0)