Show TOC

9.2 How to Integrate NWBC into an IBM WebSphere PortalLocate this document in the navigation structure


IBM WebSphere offers standard functionality for embedding static URLs. Dynamic URL functionality would require portal-specific development, such as building a new Web part based on the standard “Page Viewer” Web part. This has the following consequences:

  • Technical information about server or port has to be typed in and stored for each integrated Web Dynpro application. Changes to this information cannot be done centrally but have to be updated everywhere.

  • Runtime information like logon language or accessibility information cannot be passed dynamically to the integrated Web Dynpro application.

A solution would be to implement a non-SAP portal-specific Web Dynpro ABAP application portlet.

Web Dynpro ABAP applications are integrated into this portal by using the Web Clipping portlet. The Web Clipping portlet displays the linked content within an iFrame.

Navigation Between SAP Applications

There are two different ways of navigation: direct and indirect navigation. Indirect navigation should always be the preferred way because it decouples calling from called application. It also makes the calling application more independent of changes - for example, changing client environment.

Indirect navigation always requires a mediator. A typical mediator is the SAP Portal or the NBWC. Applications using OBN as navigation technology cannot be integrated into non-SAP portals as is. Embedding them - either directly or indirectly via the Report Launchpad - into the non-SAP portals would disable their navigation capabilities.

Therefore, applications have to navigate either directly (for example, calling hard-coded URLs) or indirectly via SAP Portal independent navigation services.

Single Sign-On

Client Certificates

This approach can be realized using available technology. But it is expensive for customers. They need to set up a Public Key Infrastructure (compare PSE Management at SAP). The customers have to map the client logon user (compare SAP_ALL user at SAP) to the user ID that is used in the ABAP system and the client certificate. The mapping is stored in table USREXTID. The mapping is done manually or automatically (by reports running on regular basis or by user management system).


IBM is using the proprietary token format LTAP. SAP ABAP servers do not support proprietary token formats. Token mapping capability is required and has to be developed. The SAP Java stack (portal) offers such LTAP/SAPLogon-Ticket mapping functionality.

Single Sign-Off and Session Management

Currently no single sign-off is provided. The user has to close all browser windows manually to terminate all back-end sessions. Clicking on Logout in the non-SAP portals does not end sessions created by SAP applications, which were launched in new browser windows.

Compare the behavior of the SAP Portal: there the application integrator knows all sessions of opened browser windows and terminates them.

User Management

A user management system is capable of creating, for example, SAP back-end users in parallel to the creation of non-SAP portal users. The user management system is also relevant regarding user mapping in case of different user IDs and regarding mapping of client certificates to back-end users.

SAP offers Java-based SAP NetWeaver Identity Management. IBM offers Tivoli Identity Manager.

Look and Feel

Style sheet mapping is not possible. The customer has to adapt the SAP style sheets by using the Theme Editor, which is currently only available in combination with the SAP Portal.

The alternative would be that the SAP style sheet files are directly changed by using an editor.

Steps to Integrate Web Dynpro ABAP into IBM WebSphere Via NWBC

  1. Create a user group and assign a new user to that group. For more information, see 9.2.1 Create a User Group and Assign a New User to That Group .

  2. Create a portlet pointing to the Web Dynpro ABAP application via NWBC. For more information, see 9.2.2 Create a Portlet Pointing to a WDA Application va NWBC .

  3. Create a portal page including the Web Dynpro ABAP portlet. For more information, see 9.2.3 Create a Portal Page Including the WDA Portlet .

  4. Allow a user group to access the portal page and the portlet. For more information, see 9.2.4 Allow the User Group to Access the Portal Page and the Portlet .

  5. Start the application. For more information, see 9.2.5 Start the Application .





More Information
  • Web Dynpro ABAP