Show TOC

Creating iViews Based on Remote ContentLocate this document in the navigation structure

Use

In SAP NetWeaver Portal, you can create local iViews that can consume content located on remote portals. The iView wizard provides templates that enable you to base your new iViews on portal component iViews/pages, Web Dynpro applications, and portal component iViews based on remote Web Dynpro applications, all of which reside on another portal.

Note

The portal containing the remote content on which the local iView is based, must be in the same domain as the local portal.

The integration options described in this section for the consumption of remote applications and iViews, and which use portal application integration technology, are similar to the integration methods used to create SAP Application iViews, such as those based on SAP applications. For more information, see Creating SAP Application iViews .

iView Types

The iView types that can be created to consume remote content are the following:

  • iView based on a remote portal component:

    The local portal component iView runs a remote portal component iView and displays it locally; the iView runs in the remote portal runtime.

  • iView based on an SAP transaction

  • IView based on a Web Dynpro ABAP application:

    This iView uses Web Dynpro ABAP technology to display an application running in a back-end system.

  • iView based on a remote Web Dynpro Java application:

    • Basic Web Dynpro iView

      This iView points, by means of a URL, to a remotely located application and displays it locally; while the application runs on the remote portal.

    • Advanced Web Dynpro iView

      This is a local iView that runs a remote Web Dynpro page

      Recommendation

      To locally integrate a remote Web Dynpro application that was developed in a previous SAP NetWeaver version (up to and including SAP NetWeaver '04), it is recommended to follow the wizard steps for creating a basic Web Dynpro iView.

      To locally integrate a remote Web Dynpro application, developed in a version from SAP NetWeaver 7.0 and higher, it is recommended to follow the wizard steps for creating an advanced Web Dynpro iView. This is because the application itself runs in a Web Dynpro page, it is tightly integrated with the portal, and the navigation target is resolved on the local portal.

Prerequisites

The following information describes behavior specific to the iView wizard and the use of iViews based on remote portal content, as well as the prerequisites for creating them.

  • The procedures, used to create local iViews that consume remote content, describe how to integrate the user-defined remote portal component iViews or Web Dynpro pages. These local iViews do not integrate any additional configuration of the remote iViews or pages on the remote portal. For example, the iView you are creating locally does not include the definition of OBN targets, Related Links, or Dynamic Navigation from the remote portal. Also, portal navigation links in the integrated remote iView, which work on the remote portal, cannot work locally unless the link targets are available and configured in the local portal.

    Note

    For additional navigation configurations, which may be integrated in the remote iView or page, to work locally, you can replicate the navigation conditions on the local portal to emulate the remote system, whether for related links, dynamic navigation, or OBN.

  • It is necessary to create a portal system object on the local portal that points to the application (remote) portal. No specific system type is recommended but the system must have Web Application Server (Web AS) properties, such as an SAP system with load balancing or an SAP system using a dedicated application server.

    The following system properties must be configured:

  • Web AS host and port

    • Web AS protocol

    • System alias

  • Web Dynpro Java pages on the remote portal must be set with end user permission assigned for the relevant users.

    Recommendation

    Setting end user permission to the folder level on the remote portal covers the permission requirement for both unit and nonunit objects.

  • Personalization of the locally created iView that integrates a remote Web Dynpro page performs the personalization on the remote page at the remote location and not on the local iView.

    Personalization of the remote Web Dynpro page is available in the role and is saved on the application (remote) portal.

  • If you refresh an iView within a Web Dynpro page (which is itself integrated by one of the creation options described for Web Dynpro Java iViews), or if you open it in a new window, the user configuration (for example, locale, theme, accessibility) is taken from the remote portal.

  • For iViews integrating remote portal component iViews, the local theme is used only if it exists on the remote portal. Otherwise, the default theme of the remote portal is used, as well as the remote locale of the user, and remote accessibility configuration.

    iViews integrating remote Web Dynpro Java applications use the local theme.

  • Changes to copied properties of the remote iView have no effect on the properties of the iView created locally.

    The following properties are copied to the local portal component iView:

    • Fixed Height

    • Height of External Window

    • Height Type

    • Launch in New Window

    • Window Features

    • Tray Type

    • Initial State of Navigation Panel

    The following properties are copied to the local Web Dynpro iView:

    • Fixed Height

    • Height of External Window

    • Height Type

    • Launch in New Window

    • Window Features

    • Tray Type

    • Customer Exits for 'ParameterProvider'

    • Initial State of Navigation Panel

    • Show 'Print' Option

  • There is no notification to the local portal if a Web Dynpro page on the remote portal is deleted. The local iView that consumes this page no longer functions.

  • It is not recommended to run the local Web Dynpro iView in a local portal page. Since the iView integrates a Web Dynpro page, this would run a page within a page and can cause undesired behavior, such as excessive scrolling. Rather, add the iView directly into a role or workset.

Authentication and Trust

The supported authentication method is SSO and the user ID must be identical on both the local and remote portals.

It is also necessary to create one-way trust from the remote system to the local system. This is necessary to enable the new iView wizard to display applications on the remote portal. To create trust, perform the following on the application (remote) system:

  1. Go to Start of the navigation path http://<application_portal_host>:<port>/sso2 Next navigation step Add Trusted System Next navigation step By Querying Trusted System End of the navigation path

  2. Select JAVA for the System Type and enter the details of the local portal in the fields that appear: Scheme , Host Name , Port Number , User Name , and Password .

More Information