Show TOC

Creating iViews over Enterprise Applications and DatabasesLocate this document in the navigation structure

Use

The SAP NetWeaver Portal provides default iView templates, portal components, wizards and connectivity framework for generating iViews that access and retrieve data from back-end applications and enterprise platforms. The connectivity framework is based on the Java Connector Architecture (JCA) industry standard thus providing support for third-party connections to SAP and non-SAP back-end systems.

Currently, the portal provides a framework for creating iViews that connect to the following external applications:

  • SAP ERP: Enables you to create two types of iViews, which retrieve content from a SAP ERP system:

    • iViews displaying data that is rendered and tabulated into a matrix. The retrieval of data is based on a query which is generated by the wizard as a result of predefined import/export function modules you choose and conditions set by you. See Creating SAP Connector-Based iViews .

    • iViews displaying the GUI of a SAP application directly within the frame of an iView. See Creating SAP Application iViews .

    Examples of SAP ERP data and applications displayed in SAP iViews:

    • SAP ERP transactions

    • SAP ERP reports

    • BW (SAP NetWeaver Business Warehouse) reports

    • SAP Internet Application Components (IACs)

    • SAP MiniApps

  • Generic Databases: Enables you to create an iView that displays content accessed from a generic database, such as MS-SQL, via a JDBC provider. Data retrieval per iView is based on a predefined input/output functions or a custom-created query.

Note

SAP ERP applications are referred to as SAP R/3 for versions 4.7 and earlier.

Prerequisites

The following prerequisites are valid for all iView types mentioned above, except for those which natively display a:

  • Each back-end system to which you want to connect must have in the portal a representative connector ; the middleware through which iViews access the application. The SAP NetWeaver Portal automatically comes two connectors, a SAP ERP connector for accessing SAP ERP, BW, and CRM systems, and a Database (JDBC) connector for accessing generic databases.

  • In addition, the portal makes available, in the Portal Catalog, system templates that correspond to these connectors. System templates provide the property profiles required to access a system; essentially enabling the portal system landscape to link between portal content and the connectors it uses, and between portal content and the systems it uses.

    For detailed information, see Defining the System Landscape .

Process

Creating Content over a Connector

Note that this flow does not relate to iView that display a native SAP GUI within the frame of the iView (for more information, see Creating SAP Application iViews ).

  1. Deploy and configure a connector:

    1. After the portal is set up install the appropriate connectors.

    2. Install necessary application-specific components, if needed.

    3. Check if the corresponding system template has been set up. If not, one may need to be created from the System Landscape Editor.

    Note

    Currently, all supported connectors and respective system templates are installed automatically during portal installation.

  2. Create a new system:

    1. Create a new system in the System Landscape Editor using the above system template. The system provides the iView with the necessary credentials needed to access the enterprise application. See Creating Systems .

    2. Customize the system by providing the necessary properties specific to the back-end system being connected to. See Editing System Properties .

    3. Define an alias for the system. The alias will serve as a bridge between the iView and the system object. See Managing System Aliases .

  3. Create a new iView:

    1. Run the iView Wizard. See Creating SAP Connector-Based iViews and Creating iViews for Databases (JDBC) .

    2. Choose the system through its alias and define the data query.

    3. Save the iView.

    4. Add the iView to a page and run it.

    5. Customize iView properties in the Property Editor and test changes.

    6. Personalize the iView in a run time environment and test the changes.

    7. Change the iView system alias and test to see if data is being retrieved from a different system.

    8. Login with different credentials to test user mapping.

Figure 1: Flow of data for creating iViews based on the connector framework