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!
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)
- 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