Skip to Content

We’re back, as usual, with each release of SAP NetWeaver to discuss the latest and greatest portal features, this time for SAP NetWeaver 7.0 SP Stack 13. Some are small and cosmetic, others are more substantial, but hopefully all will be useful to you.

So here goes, in no particular order:

  • Navigation Zoom: You can now designate a navigation node to zoom when clicked, meaning that the current navigation hierarchy disappears and the children of the clicked node become the top-level nodes.

    For example, I created a role (MyRole) with a workset (MyWS) and two worksets inside this workset: MyWS-2 (a navigation zoom point) and PlainWS. When displayed in the portal, the navigation zoom node is displayed with an arrow inside the folder.

    When you click on the node, the navigation is reset and starts from the children of the clicked node:

    A link (Back to main portal) is provided to return to the regular navigation.

    For more information, see Configuring Navigation Zoom.

  • Indexing Portal Content: This feature, known internally as the Portal Spider, enables indexing of portal content via the standard KM/TREX search bar at the top of the portal.

    The secret to all this is a new portal component that can take a navigation node and, instead of displaying the regular markup, returns indexable text that a search crawler can understand. If the node is a role, workset or page, it returns text related to meta-attributes of the object, as well as links to worksets, pages and iViews inside, so these can be indexed as well.

    This component also enables you to have your external facing portal indexed by external crawlers by supplying a special URL to the crawler. You can also choose to only index a subset of roles.

    Up until now, you could either do a KM search (which did not include portal content) or you could search the PCD (which did not include the content within pages, and also did not let you to search for iViews within pages). The point is that there was no search of the content in the portal.

    If you do not have KM installed, an iView template is provided to create a search iView for portal content.

    For more information, see Indexing Portal Content.

  • URL iView: The URL iView now enables you to send dynamic parameters based on the current user, or parameters based on system information, such as the server name or port number.

    For example, you may have a web site to which you want to create a URL iView, and which accepts a language parameter to set the language. You could get the language for the current user and pass it as a URL parameter.

    Originally, the URL iView was meant for simple static pages, and could only send static parameters. Later, the current user and the user’s password could also be sent. Now, other attributes of the current user can be sent, or details about the current portal installation.

    For more information, see Configuring URL Parameters.

  • Desktop Title: The browser title of the portal is the current page, followed by a string that is set by a PRT property. You can now set the title with a property in the framework page and, naturally, set different titles for different framework pages.

    The following shows the Desktop Title property in the property editor for the default framework page:

    The value then appears in the browser title:

    For more information, see Creating and Editing a Portal Desktop.

  • Highlight DTN Row: A small cosmetic feature enables you to highlight the row of the selected navigation node in the detailed navigation.

    Up until now, only the word was highlighted. Highlighting the entire row makes it easier to pick out the highlighted node, and makes the look more uniform.

    You can specify the background color of the highlight, by setting the Background Color of the Selected Node property in Navigation Panel –> Detailed Navigation list.

    For more information, see Features Enabled Through DTN Properties.

  • Service Map Pictograms: You can now specify that the icons (pictograms) also be displayed as clickable links to the listed iView. Up until now, only the name of the iView was clickable.

    Pictogram is Clickable is a new property on the Service Map iView.

    For more information, see Creating a Service Map iView.

  • Mode Delegation in Portal Runtime: For a portal component, you can now specify more then one mode to delegate to another component. Up until now, the syntax for the delegation enabled you to specify just one mode and, then, a component for that mode.

    Portal components are always run under a mode, which determines which method is called during the content phase (generally it is the default mode, which calls the doContent() method).

    You may want to delegate to another component whenever in a particular mode.

    For more information, see Delegation.

  • Transport Portal EPAs Using CTS: You can now automate the transport of portal content via CTS by creating, with the help of new tools, a DC from an EPA file. The creation of the EPA file is still a manual process using the portal transport UIs.

    For more information, see Karin Sudrow’s blog Using the Enhanced Change and Transport System in a Portal Environment

  • Navigation Web Service: You can obtain the navigation hierarchy via a Web service. This enables you to create access to portal content even when not running in a Java environment in within the same virtual machine.

    Currently, this is not documented, but will be fully documented by SP Stack 14.

To report this post you need to login first.


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

  1. Former Member
    We have 15K users deployed internally on Portal.

    Navigation Zoom, I like it, but it could be an issue if the navigation structure is pretty deep, so I’d use it with caution. 

    Desktop title is cool…. we need that.

    Like the Highlight DTN row – makes a difference…

    Love the Workset map clickable icons.

    I like the Indexing options for Portal Content, but can’t figure out the specifics to enable it…definitely needed though.

    I do wish more layout set enhancements were available, e.g., Tab Explorer: sub-folders under the Rendered folders.  It’s there, but more than 2 levels down, and u start losing track of root that you started with.

    Having said that, this is a step in the right direction.

    1. Daniel Wroblewski Post author
      Hi Jason,

      Here is a list of features and their status:

      * Navigation Zoom: Not in 2004
      * Indexing Portal Content: Not in 2004
      * URL iView: In SP 21
      * Desktop Title: In SP 21
      * Highlight DTN Row: In SP 21
      * Workset/Service Map Pictograms: Workset Map in SP 21, not sure about Service Map
      * Mode Delegation in Portal Runtime: Not in 2004
      * Navigation Web Service: Not in 2004
      * Transport Portal EPAs Using CTS: Not in 2004


  2. Former Member
    Portal is generally evolving with new capabilities ( though I fear in terms quality and testing ). What about User Interface, we are still not end user centric as far as portal ( forget about other SAP applications ).
    1. Daniel Wroblewski Post author
      Hi Priya,

      There is a lot of work being done on UI — in fact, portal is now included in an area called User Enablement, and all PM activities emphasize what we have to offer (or will offer) as far as UI.

      Among the initiatives is providing business packages for R/3 systems within the portal, the new Business Client, Duet for integration with Microsoft Office, Ajax framework page and page builder, among others.

      You can check out the SAP UI strategy in SDN.

      Did you have something specific in mind?


  3. Former Member
    Hi Daniel,

    Thanks alot for a nice blog.

    We have a question actually reg. SP13 upgrade on our Production Portal environment.

    Background of the application:
    We are on 2004s EP7.0 SP10 on AIX with Oracle and implemented FPN also. These days we are facing lot of issues with SP10 so SAP has suggested to go for SP13.

    For upgradation to the portal with FPN implementation what components we need to download?
    As I know to download theese components
    1.Enterprise Portal
    2.Application Server Java &
    3. EP Core

    But do we need to download Business Intelligence components for the upgradtion or not?

    Previously we haven’t installed any BI related components on Portal envirnonment.
    Can you please clarify this?

    Advance thanks

    Sreedhar G

      1. Former Member
        Thanks for your valuable reply.

        I have one more question on SP13.
        Is there functionality for to recover the deleted document from KM in portal. Please clarify?

        Sreedhar G


Leave a Reply