Netweaver Portal not needed anymore?

I recently sat in on a number of Ramp Up Knowledge Transfer (RKT) sessions for SAP ERP HCM Employee Self Service (ESS) and Manager Self Service (MSS). Over the last couple of years SAP have talked to many customers about their requirements in this area, in particular smaller customers, who want to reduce the current cost of ownership, in short the portal environment is too expensive for them.

The majority of SAP Netweaver Portal deployments have typically been vertically focused only, providing access to SAP applications in particular ESS and MSS. Only large enterprises and wall-to-wall SAP shops seem to use SAP Portal for content management, application integration and collaboration. The feedback from many customers who have reluctantly implemented the Netweaver Portal to take advantage of SAP functionality is that it is a bloated collection of un-pluggable applications, too rigid and constrained for them to consider as a complete horizontal portal solution.

Starting with Enhancement Pack 5 (Ehp5), the SAP Enterprise Portal infrastructure is not mandatory for ESS and MSS functionality. All role content will be ABAP based and applications will be deployed using Webdynpro for ABAP (WD4A) Floor Plan Manager (FPM).

The move from Java to ABAP potentially means for a lot of custmers no more dependence on the Portal, no need for a Java stack or Java development and technical resources.

Could the porting of ESS from Java to ABAP be the beginning of the end of SAP Netweaver Portal or is this part of a strategy for meeting the different customer technology requirements?

Gartner adds insight in its Magic Quadrant for Horizontal Portals report 2009

Some customers are looking to expose SAP transactions in other portals.

SAP has shifted from its original strategy of Netweaver Portal being the only portal necessary across large enterprises to one accepting the existence of other portal technologies.

The report also says

Netweaver Portal has some gaps when compared with other leading horizontal portal products in content management, collaboration, social networking and enterprise mashup capability.

This would explain some of the other more predictable ways SAP are improving the cost of owning Netweaver Portal for their customers, including:

  • an enhanced configurable Ajax framework with widgets and drop and drag functionality
  • an improved WYSIWYG Web Page Composer with mashup capabilities
  • personal and shared Workspaces
  • Wiki and Forum applications
  • automated and integrated transports
  • greater interoperability and openness through industry standards
  • Not to mention some of complimentary ECM, BPM and EIM applications available from SAP and partners

    For many who were looking for an out these changes will represent the beginning of end of thier Netweaver Portal journey. For those companies identified as already having a multi portal landscape these changes will be seen as options and opportunities, likewise for those who haven’t yet thought about it.  For the companies who have chosen Netweaver as a platform for compostition and collaboration they will see the changes as a sign of a platform maturing.


    5 Responses to Netweaver Portal not needed anymore?

    1. Mittal says:

      Plz keep me updated.

    2. shankar says:

      good blog
      I think it is nice that SAP has decided to support third party portals.Also their are various new exciting features being shipped along with upcoming version which will take SAP closer to Web 2.0.I guess it is high time SAP starts standardizing portal development and start following standard frameworks atleast for j2ee development.

      Though as a portal consultant,i would not appreciate the blog title ;)….but yes change long due in this space..

    3. rsol1 says:

      Hi Shankar,
      The intention of the blog was to highlight that a good strategy is one which creates options. SAP’s Portal strategy has moved from a single proprietary option, to a strategy with lots of options, including the one stop shop, multi portal landscape and the not needed anymore options (which could be seen as either the best of breed or the no portal portal option).

      I take you point about the title, I thought by posing a question it would provoke thought. Any suggestions on a better one?

      • shankar says:

        No intention to criticize the title,thats why the smiley.
        The day i heard of WDA ,i was sure that this was inevitable.The WDJ interface was too restrictive.Hope WDA one is expandable.SAP never took FPM for WDJ seriously,and development of custom app is pain,where as we have dedicated forum for same in WDA.

        But with ABAP in picture the issue of UI will again be an issue because customer need better and slightly exotic interface when it comes to ESS/MSS.


    4. Miloslav says:

      Yes, it’s interesting SAP is coming back to ABAP stack – from backend and ESS/MSS scenarios point of view logical related to SAP Netweaver Business Client.

      Anyway I think NW Portal will include features that won’t make sense to implement in ABAP stack like in the case of ESS/MSS. Portal may be rather seen as other basic service provider and discuss what services are effective to provide just by the portal.

    Leave a Reply

    Fill in your details below or click an icon to log in: Logo

    You are commenting using your account. Log Out /  Change )

    Google+ photo

    You are commenting using your Google+ account. Log Out /  Change )

    Twitter picture

    You are commenting using your Twitter account. Log Out /  Change )

    Facebook photo

    You are commenting using your Facebook account. Log Out /  Change )


    Connecting to %s

    %d bloggers like this: