1 2 Previous Next

oliver.stiefbold

25 Posts
The tutorial is developed with  SAP NetWeaver 7.1. To retrace this blog you need to install the SAP NetWeaver   Application Server, Java EE 5 Edition  (https://www.sdn.sap.com/irj/sdn/javaee5) and you need  access to the ES Workplace  (https://www.sdn.sap.com/irj/sdn/developerareas/esa/esworkplace).        Part 1:    For pictured but different descritption see the following  {code:html}article{code}.      1. Navigate to SDN ES Workplace homepage http://erp.esworkplace.sap.com/socoview  (http://erp.esworkplace.sap.com/socoview).      2. Click the link +Enterprise Service Index+.     3. In the browser window insert the name of the Enterprise Service: +Find   Customer by Address+ into the field Search and click +Search in Enterprise   Service Index+.     4. In the browser window you get the result of the search. Click the link +Find Customer by Address+.   5. Now you can get detailed information about the Enterprise Service.    6. To open the WSDL file click the link on +Related Web Service   Definition+.  7. Logon with your user.     8 Copy the link {code:html}http://erp.esworkplace.sap.com/sap/bc/srt/xip/sap/ECC_CUSTOMER002QR?sap-client=800&wsdl=1.1{code} to your clipboard. Otionally you may save the WSDL locally in your file system. Eclipse based NetWeaver Developer Studio NWDS can handle both ways.        *Part 2: Test the WSDL*     1. Open theES Workplace  http://erp.esworkplace.sap.com/  (http://erp.esworkplace.sap.com/) in your Browser and click on Web Service Navigator.    2. Enter the WSDL, click next and logon with your credentials.   3. Click on "Test" in the navigation pane.    4. You see the Request Test Page for the wsdl:portType name="*CustomerSimpleByNameAndAddressQueryResponse_In*"     5. Enter e.g. "Julia" into xsd:element name="*FirstLineName*" and click "Send" button.    6. You will receive a Response list of customers. Look carefully at the nested structure of the Web Service reuest and response. We will need it for programming in the next part.  image

Java EE 5 and SOA@SAP, Part 2

 

Java EE 5 and SOA@SAP, Part 1

Tutorial, Beginner, ABAP, JAVA, SOA

Create an Enterprise Service in the Backend an a Java EE 5 Web Client, JSP

 

Prerequisites: Install NW 7.0 ABAP Trial (available on SDN), Java EE 5 Edition


Part 1: In the ABAP 7.0 backend system NSP


1. call transaction SE80.


2. Create new function module "Z_CURRENCY"


3. Define Local Interface - Import Parameter: EURO TYPE F DEFAULT 0


4. Define Local Interface - Export Parameter: DOLLAR TYPE F


5. Add some funny source code. E.g. DOLLAR = EURO * 2 . is fine for this introduction example.


6. Click on "test" button ("F8") if you like.


7. Choose "Create Web Service" from Context menu of your function module ZCONVERTER. the "Create service definition" wizard will popup it consist out 4 steps:


  • Create service: we call the service ZCCONVERTER

  • Choose endpoint: Choose function module ZCONVERTER

  • Configure service: we choose basic authentication

  • Complete





8. Switch ("/n") to transaction WSCONFIG. "Create" Service "ZCCONVERTER". Create means in this transaction "Release Web Service for SOAP Runtime". You can now use it. the standard url is:



    1. /sap/bc/srt/rfc/sap/ZCCONVERTER


9. Change to transaction WSADMIN. Look at the webservice. you may test the web service.


10. Switch to transaction SICF and enter ZCCONVERTER as service name. Click on "Display Service" in the context menu of the service. A detail screen will open. Cklick on the "Logon Data". Maintain here User and Password, so this web service does not need authentication from the web service client.


11. Click on the context menu on "Test Service". the endpoint opens in a browser. Add &wsdl=1.1 if you like to see the wsdl in document style or &wsdl=1.1&style=rpc if you want to see it rpc style. rpc contains less elements. You can also call the wsdl from the WSADMIN transaction.


Congratulation - you finished the ABAP part.


 

Create Java Web Service Client in Web 2.5 Project

 

1. Start SAP NetWeaver Developer Studio (DS) and check your Window --> preferences.

SAP AS Java should point to your message server port. Typically localhost:3600 or 3601.


2. Web Services --> Profile Compliance and Validation: switch on or off Wizard WSDL validation. Currently the WSDL validation cannot handel SAP specific tags.


3. Web Services --> Server and Runtime: Server should be "SAP Server" and WS runtime should be "SAP NetWeaver" if you want to consume ABAP web services with SAP datatypes. Standard AXIS cannot consume business data types.


4. Create a new Web project: File --> New --> Project. Choose Web -->Web 2.5 --> Dynamic Web Project 2.5.

(Alternatively you may follow Part I of the weblog series and create a simple Java client)


5. Enter Project name in the popup wizard: ZCConverterWeb. Choose "Add project to an EAR". Enter also a name: ZCConverterEar.


 

6. Mark ZCConverterWeb and open context menu: New>Other> Web Services --> Web Service Client. The Web Service Client Wizard pops up.


7. Enter service definition. Use the URL from the ABAP web service. E.g.: http://localhost:8000/sap/bc/srt/rfc/sap/ZCCONVERTER?sap-client=000&wsdl=1.1&style=rpc

&style=rpc is optional for slighter WSDls.


8. If you forgot to maintain user and password in ABAP you will be prompted for user and password. In that case you will have to add some lines of code for authentication lateron.


9. Check configuration is SAP and set the slider to "Start Client". "Test Client" does not work yet. You have to program the web tier manually.


10. Look at the generated web servcei client. you will notice that the ZCCONVERTERSERVICE_WSDL_LOCATION is null if you create the web service client in a web project. thsi is a kown "feature". You may create a 2nd WS client in a simple Java project an copy the following code by hand into the constructor:


/**

  1. Service implementation of (generated by SAP WSDL to Java generator).<br />
*/

@javax.xml.ws.WebServiceClient(name = "ZCConverterService", targetNamespace = "urn:sap-com:document:sap:rfc:functions", wsdlLocation = "WEB-INF/classes/wsdl/sap/bc/srt/rfc/sap/ZCCONVERTER/wsdlroot.wsdl")

public class ZCConverterService extends javax.xml.ws.Service {


private final static java.net.URL ZCCONVERTERSERVICE_WSDL_LOCATION;

/**

 
  1. Default service constructor. Usually this has to be done manually. As a workaround create this client in a Java project and * import it into web project. <br />
  */ static {
java.net.URL url = null;
try {
java.net.URL tmpUrl = Thread.currentThread().getContextClassLoader().getResource("wsdl/sap/bc/srt/rfc/sap/ZCCONVERTER/wsdlroot.wsdl");
url = new java.net.URL(tmpUrl.getProtocol(), tmpUrl.getHost(), tmpUrl.getPort(), tmpUrl.getFile());
} catch (java.net.MalformedURLException e) {
e.printStackTrace();
}
ZCCONVERTERSERVICE_WSDL_LOCATION = url;
}

11. Create a JSP page index.jsp for testing:

<%@ page language="java" contentType="text/html; charset=UTF-8"
pageEncoding="UTF-8"%>
<%@page import="com.sap.document.sap.rfc.functions.ZCConverterService"%>
<%@page import="com.sap.document.sap.rfc.functions.ZCConverter"%>

my first Web Service Client


<%

try {
ZCConverterService service = new ZCConverterService();
out.write("service called ");
ZCConverter converterSoapBinding = service
.getZCConverterSoapBinding();
out.write("service binded ");
float f = converterSoapBinding.zconverter(2f);
out.write("result: "+f);
out.flush();
} catch (java.net.MalformedURLException e) {
e.printStackTrace();
}
%>

12. run as --> run on server. the result will look like this:

my first Web Service Client
service called
service binded
result :4.0

Congratulations.!

(pictures will follow, Best Regards Oliver)

 

 

]]>

Part 1: Browse ES Workplace and select ECC_CUSTOMER002QR WSDL

 

 

The tutorial is developed with  SAP NetWeaver Java EE 5. To retrace this blog you need to install the SAP NetWeaver   Application Server, Java EE 5 Edition and you need a access to the ES Workplace .


 


Part 1:


 

For detailled and pictured descritption see the following How-To-Guide for consuming a Web Service with a standalone client using SAP NetWeaver Application Server Java(TM) EE 5 Edition .


 

1. Navigate to SDN ES Workplace homepage http://erp.esworkplace.sap.com/socoview .


 

2. Click the link Enterprise Service Index.


 

3. In the browser window insert the name of the Enterprise Service: Find   Customer by Address into the field Search and click Search in Enterprise   Service Index.


 

4. In the browser window you get the result of the search. Click the link Find Customer by Address.

5. Now you can get detailed information about the Enterprise Service.

  6. To open the WSDL file click the link on Related Web Service   Definition.

7. Logon with your user.


 

8 Copy the link http://erp.esworkplace.sap.com/sap/bc/srt/xip/sap/ECC_CUSTOMER002QR?sap-client=800&wsdl=1.1 to your clipboard. Otionally you may save the WSDL locally in your file system. Eclipse based NetWeaver Developer Studio NWDS can handle both ways.




 

Part 2: Test the WSDL


 

1. Open theES Workplace  http://erp.esworkplace.sap.com/ in your Browser and click on Web Service Navigator.


2. Enter the WSDL, click next and logon with your credentials.


3. Click on "Test" in the navigation pane.


 

4. You see the Request Test Page for the wsdl:portType name="CustomerSimpleByNameAndAddressQueryResponse_In"


 

5. Enter e.g. "Julia" into xsd:element name="FirstLineName" and click "Send" button.


6. You will receive a Response list of customers. Look carefully at the nested structure of the Web Service reuest and response. We will need it for programming in the next part.


!https://weblogs.sdn.sap.com/weblogs/images/70/ESW_ECCC002_NavTest_SDN.jpg|height=331|alt=image|width=600|src=https://weblogs.sdn.sap.com/weblogs/images/70/ESW_ECCC002_NavTest_SDN.jpg|border=0!


 

Part 3: Creating a standalone proxy

 

Use

 

This procedure enables you to generate a standalone Web Service   proxy for consuming a Web Service using the Web Service Client wizard.

Creating a Java project

 

Procedure

 

1. Choose File --> New --> Project.

 

2. In the pop-up window choose Java Project and click Next.

3. Enter the project name: Customer.

4. Choose Finish.


As a Result a new Java Project (for JDK 1.5) is created.


 

5. Create a new Web Service Client. Choose File --> New --> Other --> Web Service Client.


6. In the popup wizard enter the WSDL-URL and choose "Deploy Client" in the slider on the left (however you may choose whatever you like, it has no influence in this project type.


7. Choose "SAP NetWeaver" as Web Service Runtime instead of "Apache Axis". Otherwise you will not be able to "SAP Global datatypes", You will need them for the rather complex business data types.


8. Choose finish, a Java Proxy is generated.

Part 4: Creating a Web Service Client Application

 

Creating a new class

 

Use

 

To invoke the standalone proxy you need a new class with a main   method.

Procedure

 

1. Choose File --> New --> Class.

 

2. In the popup-window enter the class name: MyCustomer.

  3. Insert the   name of the package: +com.sap.tutorial . +You may also choose com.sap.xi.appl.se.global. This has the advantage, that you do not need to import the generated SAP Java Proxy by import statement.

  4. Select the checkbox public static void main(String[] args) to create a main method in the   class.

  5. Click Finish.



Creating source code

 

Use

 

To invoke the standalone proxy you have to create instances, insert   authentication and set the values for the request. The complete source code of   the class is also available at the end of this chapter.

Coding 

 

import java.util.List;


import javax.xml.ws.BindingProvider;


import com.sap.xi.appl.se.global.CustomerSimpleByNameAndAddressQueryMessage_SyncType;

import com.sap.xi.appl.se.global.CustomerSimpleByNameAndAddressQueryResponseIn;

import com.sap.xi.appl.se.global.CustomerSimpleByNameAndAddressQueryResponseInService;

import com.sap.xi.appl.se.global.CustomerSimpleByNameAndAddressResponseMessage_SyncType;

import com.sap.xi.appl.se.global.OrganisationNameType;

import com.sap.xi.appl.se.global.CustomerSimpleByNameAndAddressQueryMessage_SyncType.CustomerSimpleSelectionByNameAndAddressAnonymous;

import com.sap.xi.appl.se.global.CustomerSimpleByNameAndAddressResponseMessage_SyncType.CustomerAnonymous;


/**

   

  • @author<br />

   

  • <br />

  */

public class MyECCCustomer {

/**

   

  • Author: Oliver Stiefbold, NetWeaver Product Management<br />

  */

Optional: Proxy Settings in NWDS

 

image

 

 

 

 

It was only a few days ago that SAP NetWeaver was certified to be the first commercial application server to fully support the  Java EE 5 standard – but already we have the version of SAP NetWeaver that  achieved this remarkable status available for download here http://www.sdn.sap.com/irj/sdn/downloads?rid=/library/uuid/da699d27-0b01-0010-99b0-f11458f31ef2in SDN.</p>

<br

image



 

The introduction of Java EE 5   is arguably the most important landmark for the development of  enterprise-ready Java applications in years. Java EE 5 has totally rearranged  many areas of the Java Enterprise Edition, with a focus on enhancing ease of  development and developer productivity in general. SAP introduced a preview  version of SAP NetWeaver, which already exhibited a lot of Java EE 5  functionality, on this year’s JavaOne conference and also published it in SDN.  The replacement of this preview by a successor that now covers the entire set  of Java EE 5 standards comes earlier than expected – and obviously to the  surprise of many competitors. For more information on SAP’s position towards  Java EE, please check this SDN page



The SDN hitchhiker´s Guide through  Enterprise Portal Articles:

 

SAP Help Portal Portal Developer Guide

 

First of all have a look to our new Portal Developer Guide: see           new Portal Developer Guide

Downloads for Developers

 

Sneak Preview (180 day limitation) and Portal Development Kit

 

New to Enterprise Portal 6.0 SP9  (NW04 -SR 1)

 

  Transformation     Service - new to Sp9

 

  Transfomration       Service Samples - new to Sp9

 

Basics, Getting Started, always read:

 

Portal       Runtime Guide 648    (SAP Help)

 

User Interface and Client Scripting

 

Htmlb         Guidelines, Reference and Tutorial

 

EP   6.0 Client Framework  (link   to helpportal)

 

Enterprise       Portal Client Framework (EPCF 646) (pdf)

 

HTML-Business   for Java Using Beans 648   (pdf)

 

Connectivity EP to SAP ecosystem and 3rd party:

To Be Spoilt For Choice - Connecting EP to R/3 )

 

EP           6.0 Webservice Tutorial - for more the PDK

EP   6.0 Connector Framework

SAP   Java Connector Presentation

 

User Management API of the Web Application Server

 

SAP   WebAS Authentication Guideline - JAAS  (link to SAP help portal)

 

HowTo   Developing with UME 4.0 , JAAS (pdf)

 

Customizing the Logon User Interface of SAP Enterprise Portal

 

Using User Management API 4.0 with ASP.NET

 

Others

Using the New Page Builder Client Side API of EP6 SP2

Download - EP Application Integrator - example

 

Deprecated

JCO     Client Service 646 (pdf )

 

Setup and Implementation

 

Copying   an EP6.0 on WebAS 6.40 - MS SQL Installation

 

Installation       of the EP60 ZIP File with PDK (deprecated)

 

Installation - Guide PDK 5.0

 

 

-----------------------------

Have fun! Oliver

New HowTo Guide about JAAS on SDN:

User Management Engine

SAP WebAS Authentication Guideline - JAAS

The Java Authentication and Authorization Service (JAAS) is a set of APIs that enable services to authenticate and enforce access controls upon users. It implements a Java technology version of the standard Pluggable Authentication Module (PAM) framework, and supports user-based authorization.

read the full docu of the SAP implementation


BR, Oliver
Oliver Stiefbold

JAR Class Finder

Posted by Oliver Stiefbold Jul 20, 2004

As most of you know, EP6.0 EP-Plugin for Netweaver Developer Studio misses some support for finding the right jars for you Portal Component project. So there is some help from outside:

Jarfinder is a tool from IBM for Eclipse. It adds the JAR reference to your eclipse project.

Have fun with it, Oliver.

How to access HTML elements created with HTMLB using JavaScript: A short tutorial

 

 

Problem

 

 

The HTML elements created by HTML Business for Java (HTMLB) have ID-attributes, and the values of these attributes change with each iView invocation. These ID attributes are commonly used to uniquely identify and access certain HTML elements in an HTML page (or iView). This circumstance hampers attempts to access forms and input fields of an HTML form using JavaScript.

 

Solution

 

 

HTMLB provides access to the HTML IDs that are generated. After retrieving
the IDs, you can generate your JavaScript by setting the correct IDs at runtime.

 

 

Details

 

 

 

 

<<p> 

SAP NetWeaver Enterprise Portal on MS SQL - Developer Edition - Sneak Preview Package

Related Link - how to install PDK 5.0

Business Package for Portal Development Kit 60.3.0

Introduction

This package contains everything you need to get started working with the building blocks of SAP NetWeaver. The following components are included:

  • SAP Web Application Server Java 6.40 (J2EE Engine)
  • SAP NetWeaver Developer Studio
  • SAP Enterprise Portal 6.0 (incl. Knowledge Management and Collaboration)
Every component version relates to Support Package Stack 02 of SAP NetWeaver!

A brief note about this installation:
The complete Installation will take between 4 and 8 hours! (Depending on your hardware)
Please also keep in mind that the installation process is not trivial. Thus you should use the values provided in this quick installation guide.
The complete installation will be greatly simplified with the next SP release!

Quick Installation Guide

Hardware/Software Requirements
  • A Windows PC with at least 1Gb of memory and at least 6Gb of free disk-space
  • Microsoft Windows 2000 (at least SP3) or Windows Server 2003
  • Installed Microsoft SQL Server 2000 with all updates that are explained here
  • Installed Sun JDK 1.4.2_04 (Note that there are some known issues with this version. Please use 1.4.2_05 as soon as it is publicly available)
  • Installation target must be a NTFS drive (FAT won't work)

Please carefully check if you meet all these requirements before proceeding with the installation:

See the installation guide for the EP 6.0 SP4 sneak preview edition


How to develop Portal Content with EP 6.0 SP3 ++

Maybe you are one of the "lucky" folks who already received the EP 6.0 SP3++ in ramp-up. Well, if yes you probably noticed that the underlying Web AS Java Engine changed from 6.20 to 6.40. Web AS 6.40 Java experienced a major change in architecure and closes up to the proven ABAP VM architecture (however it will probably take another release to measure up to ABAP :-).


So, what are the most important changes for Protal Content Developers?

1. SAP Netweaver Developer Studio - no longer installing PDK plug-ins into Eclipse. NW DS offers all Java development tools out of the box.

2. Web Dynpro. SAP´s new UI technology - comparing to HTMLB it offers stunnig support for application developers with the new SAP Netweaver Developer Studio - following the MVC concept and strong visual support. However for projects with a strict timeline you should consider, that Web Dynpro is in ramp-up. Web Dynpro runs although in its on Java Server container, so you have no direct integration into the Portal Runtime PRT. However, if you dont plan to use PRT eventing, this should be no pain point.

3. The PRT-Java Server Bridge - from SP3 on, there is a seemless integration between PRT and the other Java Server services. Mutual access is easy. So feel free to use any technology the Web AS 6.40 Java offers and vice versa.

4. Portals unique features - putting it all together in a frontend. For developers: Roles, connectors, pages, navigation, taxonomies, repositories...

 

So, what are SAP recommendations for content development ?

Still - the answer is: It depends (see below)! WebAS 6.40 Java offers a bunch of new development tools and APIs. Enjoy it with your Portal!

Associated weblogs:

To Be Spoilt For Choice - Connecting EP to R/3

Content Developing with EP 6.0 and R/3



Special topic: Using Webdynpro in Portal Environment

EP Content Development on WebAS 6.40

Compliance with Java 2 Enterprise Edition
The SAP J2EE Engine supports the industry standard Java 2 Platform Enterprise Edition and therefore has a broad base of security and development standards. These J2EE services are - among SAP specific services like WebDynpro - now available for EP Content Development. The SAP J2EE Engine supports the following J2EE components and interfaces:

..

  • Enterprise JavaBeans
    All EJB types contained in the EJB 1.1 and EJB 2.0 specification:
  • Stateful and stateless session beans
  • Entity Beans
  • Message-driven Beans
  • Java Server Pages (JSP)
  • Java Servlets
  • Java Transaction API (JTA)
  • JDBC
  • Java Naming and Directory Interface (JNDI)
  • Java Mail
  • Java Message Service (JMS)
  • Java API for XML Processing (JAXP)
  • Compliance with Java Security Specifications
  • Java Cryptography Architecture (JCA)
  • Java Cryptography Extension (JCA)
  • Improved Container-Managed Persistence (EJB CMP)
  • Query Language (EJB QL)
  • Connector Architecture

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

                                                           
AvailabilitySAP Enterprise Portal 6.0 SP2
Browser RecommendationSee Product Availability Matrix for SAP Enterprise Portal         6.0 SP2 at service.sap.com/ep → Product       Information →  Enterprise Portal 6.0 → Product Availability Matrix.
LanguagesEN English
Data SourceSAP 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 IDDescription
pcd:portal_content/administrator/super_admin/super_admin_roleSuper Administration
pcd:portal_content/com.sap.pct/administrator/super_admin/com.sap.portal.super_admin_roleSuper 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_roleStandard User Role
pcd:portal_content/com.sap.pct/specialist/com.sap.km.ContentManager/com.sap.km.ContentManagerContent 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.

Hello Content Developers,

I got some questions in the past about why we took out some javadocs from the PDK 60.2. The reason is that we went with these APIs through RampUp and found out that   they were mis-designed, means they will never be able to do what they were intended to do. Well, the only solution then is to recommend not to use these APIs in content projects because you will never be happy with them, even if this means you have   to go on with the old EP 5.0 APIs - or in same cases wait until NetWeaver.

Best Regards,
Oliver

see Note: 725820

                 
                                                                                     
               

Symptom

               

Certain Enterprise Portal 6.0 APIs set to private after Rampup

               

Other terms

               

Javadoc, PDK, Rampup, EP, KM

               

Reason and Prerequisites

               

change in public API

               

Solution

               

For several Enterprise Portal 6.0 API packages support has been                   abandoned after the end of Ramp-Up. APIs released for public preview                   during Enterprise Portal Rampup are set to private due to design                   restrictions and will be replaced by new APIs in upcoming releases.                   Effective from end of Rampup and Start of unrestricted shipment                   of EP 6.0 from 1.1.2004 on.

               

The following packages are withdrawn and will be replaced.

               

Until EP 6.0 SP2 use the  EP 5.0 system landscape API. From EP                   6.0 SP3 (SAP NetWeaver '04 ramp-up start) on, use optional the                   System Landscape Directory of J2EE Engine:

               

com.sap.portal.ivs.iviewservice
                com.sap.portal.ivs.httpservice
                com.sap.portal.ivs.systemlandscapeservice

               

The following package will be released with EP 6.0 SP 3 (SAP NetWeaver                   '04 ramp-up start):

               

com.sap.portal.pagebuilder

               

The following package is supported but should not be used anymore                   for new projects. Will be replaced by a new SAP Configuration Framework:

               

com.sap.portal.runtime.config

               

The following package contains classes marked as "Experimental" in                   the respective JavaDoc (which denotes "private" or "internal"):

               

com.sapportals.wcm.repository

               

It is recommended not to use those classes.

               

 

             
     
                                               
PriorityRecommendations/additional info
Category 
Primary ComponentEP-PIN Portal Infrastructure
Secondary ComponentsEP-KM

Business Package for Portal Development Kit 60.2.2

The public version of the Portal Development Kit for Java (PDK) Business Package   is now available for SAP Enterprise Portal 6.0 on SDN for download. PDK 60.2.2   is based on EP 6.0 SP2, but It may be also imported and installed on previous   versions.

Remarks

Download Bug fixed at March, 25, 2004.

Prerequisites

  You have installed a standard SAP Enterprise Portal 6.0 SP0 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. We recommend using Eclipse because the Business Package
  for Portal Development Kit includes wizards that developers can download and import   into    Eclipse. These wizards automate tasks such as converting Java code into the correct   format  for uploading 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

                                                           
AvailabilitySAP Enterprise Portal 6.0 SP2
Browser RecommendationSee Product Availability Matrix for SAP Enterprise Portal         6.0 SP2 at service.sap.com/ep → Product       Information →  Enterprise Portal 6.0 → Product Availability Matrix.
LanguagesEN English
Data SourceSAP 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
  For details on installing business packages, see the Business Package Installation   Guide on iViewStudio.

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 IDDescription
pcd:portal_content/administrator/super_admin/super_admin_roleSuper Administration
pcd:portal_content/com.sap.pct/administrator/super_admin/com.sap.portal.super_admin_roleSuper Administration
pcd:portal_content/com.sap.pct/Developer/Portal_Development_Kit/ Roles/com.sap.portal.pdk.JavaDeveloper Java Developer
pcd:portal_content/com.sap.pct/every_user/general/com.sap.portal.eu_roleStandard User Role
pcd:portal_content/com.sap.pct/specialist/com.sap.km.ContentManager/com.sap.km.ContentManagerContent 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.

Fundamental Principles Behind Axiomatic Design

There are already a lot of publications about SAP s Enterprise Service Architecture. Briefly SAP ESA helps managing todays complexity, using SAP Netweaver Platform, including open technologies like Webservices.

But what is complexity? How can we handle it? And even more fundamental, how can we approach to complexity?
Let s have a look at what I learned from mechanical engineering!

 

Axiom 1
The Independence Axiom

Maintain the independence of Functional Requirements: In an acceptable design, the design and the functional requirements are related in such a way that a specific design can be adjusted to satisfy its corresponding FR without affecting other FRs.

 

image
image

Do you remember how difficult it was to adjust
temperature and volume?

Well - a better way.



Axiom 2
The Information Axiom

Minimize the information content: Among alternative designs which satisfy Axiom 1, the best has the minimum information content which means the maximum probability of success.

 


A brief Process Description of Axiomatic Design*

1.)The design is mapped in four domains; Customer-,Function-,Design- and Process-domain. The Product or Process being designed is described in the Design domain hierarchically broken down in a design-tree. For each design parameter DP the functional requirement FR answering the question "why this DP?" is to be found in the same position in a function tree in the function-domain. For each DP also the process variable PV, that is chosen to create that DP, answering the question "how to get this DP?" is to be found in the same position in the process-tree in the process-domain.

2.)The functional requirements are related to the customer domain answering the question "how to satisfy the customer?" The functional requirements on the highest level have to be the minimum set of necessary functional requirements FR in order to meet the overall intention with the product in order to satisfy the customers. Each FR has to be specified quantitatively with tolerance.

3.)On each level in the product tree there is a one -to-one correspondence between FR, DP and PV. The tree-structure is the same in the function-, design- and process-domains. The question "how?" leads from FR to DP to PV and the question "why?" leads from PV to DP to FR.

4.)Depending on the choice of DP s, the FR s can be independent or dependent. The design can be uncoupled, decoupled or coupled in its functional behavior, depending on the choice of DP s. An uncoupled design is the easiest to operate. A decoupled design can be operated by setting the DP s in correct sequence. A coupled design finally requires iteration when setting the design-parameters and should be avoided. The degree of coupling can be seen in the design-matrix, which expresses the connection between the vector of DP s and the vector of FR s. Axiom 1: "Maintain independence between functional requirements." is referring to this fundamental connection between FR s and DP s. The same relation exists between DP s and PV s.

5.)A design specified in terns of DP s has a certain probability to meet specified FR s within given tolerances. A design with high probability to meet FR s within tolerances has also a high probability to satisfy customers and is therefore preferable. Axiom 2 "Minimize information content." is referring to this fundamental connection. Information content is here defined as log2(1/p) where p is the probability to meet the requirements. In an uncoupled design smallest sum of information content is equivalent with highest probability to meet all functional requirements within tolerances.

6.)Each level in the FR-tree is constrained by the next higher level in the DP-tree. In the same way each level in the DP-tree is constrained from the next higher level in the PV-tree. None of the trees therefore can be created independently. Zig-zagging over the three domains is necessary in the detailing of the design and the processes to create it.

 

* This list of fundamental principles is set up by prof. Gunnar Sohlenius after many years of contact with prof. Nam P. Suh who originally proposed the axiomatic principles of design.

With EP 6.0 the SAP EP plugins 1.2.0 for developing Java iWiews with Eclipse changed and became a little bit more unconvinient. So it is no longer possible to reference automatically the project libraries from your Ep installation, as you know it from PDK 50.

This is for several reasons. With EP60 it is now possible to develop on a central instance of EP and also to develop against webservices. We currently evaluate concepts how to achieve automatic referencing in Eclipse for central instances of EP60 and Webservices again.

Therefore we created a workaround in your PDK role "Java Developer" under download, you may download the most important EP libs to your local desktop. (After clicking and saving "libraries.zip" you must rename it to *.zip) .

Sorry for the unconvinience, we will improve this in upcoming SPs.


image

Filter Blog

By date: