Show TOC

 Integration Using the Portal Content StudioLocate this document in the navigation structure


Portal Content Studio is the central environment in the portal for creating and managing portal content. You can use it to edit the following types of portal content.

  • iViews
  • Portal pages
  • Layouts of portal pages
  • Portal roles
  • Worksets

For more information about calling Portal Content Studio, see Using Portal Content Studio .


Portal Catalog

You manage portal content with the portal catalog. The portal catalog enables you to search, display and manage portal content that is saved in the Portal Content Directory (PCD).

More information: Using the Portal Catalog .

You use wizards and object editors to create and maintain portal content. More information: Using Object Editors and Creating Portal Objects .


The wizards are launched in the portal catalog (see Launching the iView Wizard and General Information ):

  1. Select a folder in the portal catalog.
  2. To start the wizard, choose New → iView in the folder's context menu. You can select from a variety of iViews. The most important iViews are:
    • BEx Web Application iView
    • KM Document iView
    • KM Navigation iView
    • SAP Transaction iView
    • SAP BSP (Business Server Page) iView for Web Interface (from BW-BPS)

For more information about these iViews, see Display of BEx and BW Objects in the Portal . The wizards prompt users for the required iView properties.

Object Editors

The object editors make it possible to make changes to iView properties directly. Using object editors, you can maintain the views for Related Links and Dynamic Navigation as well as authorizations.

More information: Editing Portal Objects .

In addition to the properties described in Display of BEx and BW Objects in the Portal , you can edit all of the other properties of the iView. The iView ID can be changed retroactively.

Important properties for BEx Web applications as iViews are:

  • iView name: Title of the iView. This is displayed in the Open/Save dialog in BEx Web Application Designer.
  • Description
  • Type of height
  • Fixed height (in pixels)

More information: iView Properties .

Using the Portal Cache

The Cache Level, Cache Validity Period and Isolation Method properties are necessary for using the portal cache. Using the portal cache has the following benefits:

  • Significant improvement of interface reaction time
  • Avoidance of redundant page re-rendering when the portal page is called again
  • Caching (similar to Web browser caching) for server-based, dynamic pages on the Web (such as BEx Web applications)

You can make the following settings for the cache level:

  • No Caching (None): With the None option, the BEx Web application is called again in the BW system with each call.
  • Session Related (Session): With the Session option the cache is filled specific to the user. After finishing the current session by closing all Web browser windows, the cache is invalidated.
  • Common for All Users (Shared): With the Shared option, the cache is not filled specific to the user; instead it is filled the same for all users. Personalization is ignored.
  • Own User (User): With the User option the cache is filled specific to the user. The cache is updated or invalidated automatically by the cache validity period process. BEx personalization and iView personalization are taken into account.

The cache validity period is specified in milliseconds. The isolation method has to be set to URL. The settings for using the portal cache are to be made manually by the administrator for every iView with a BEx Web application.

Using the portal cache enables a full proxy mode of the portal. Full proxy mode means that only the portal server communicates directly with the BW server. All requests (HTTP requests) from the user's (client) Web browser are answered by the portal server. The user's Web browser (client) does not have direct access to the BW server. The BW server can thus be protected against external access and is located in the internal network zone. For external access, the portal server can be located in the DMZ network zone (demilitarized zone). The protocol for communication between the Web browser from the user (client) and the portal server, as well as between the portal server and the BW server, is either HTTP or HTTPS. In both cases, the port number can be configured.