Skip to Content

How to develop Portal Content with EP 6.0 SP3 ++

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
You must be Logged on to comment or reply to a post.
  • There are some ‘remarkable’ changes from EP6.0 SP2 to EP6.0 SP3 and higher; you changed the ‘middleware’ architecture from WAS6.20 to WAS6.40 – there will at first (my information)only a way to upgrade from EP5.0 directly to EP6.0 SP3++; EP6.0 SP2 will follow earliest at Q4/2004; so when developing components for EP6.0 SP2 (i.e. a repository) will there be a guarantee that it’s running in EP6.0 SP3 and higher as well?
    Please clearfy this issue for me, or let’s discuss about the migration topic!
    Thanks in advance!
    regards steffen
    • You are right. There is no Upgrader at the moment. Reagarding the Portal Components: The APIs of EP did not change. So there must be no problem. Otherwise it would be a bug.
  • Hi Oliver,

    I uploaded Java components on a EP6.0 SP3 Portal. it worked fine.
    When i updated a component the changes did not appear on the screen. This is something, which did not happen in the SP2 environment.
    Maybe a result of the additional State controller ?
    After a restart it worked. But this is something I don’t want to do on a productive machine…
    Do you have any hints how to overcome this obstacle?

    • we think about it. Tahts all. Because it s not so easy. JSF fits well to HTMLB, but not yet to Webdynpro controls. And Webdynpro is the future UI implementation.
      However, also from my point of view it would be great to offer JSF.

      Lets see, Oliver