Portal Display 

PurposeThe portal workspace viewed by any portal user is comprised of various user interface units, which provide the interactive capabilities of the portal. The on-screen display of this workspace is governed by structural layout and design components that spatially arrange the navigational and content components in the workspace and provide their look and feel.

When users log on to the portal, the portal display that they receive is an integrated portal desktop—a combination of the user interface components described above.

The services and tools described in the topics that follow enable you to create and manage any number portal desktops to suit your business scenario. Through the use of customizable display rules, you can allocate portal desktops with varying designs, branding, or layouts to different scenarios, departments, and sub-companies in your work environment.

IntegrationThe following components are required for configuring the portal display:

Object Function Description

Framework page

Defines the layout and structure of a portal desktop.

A portal page comprising the entire set of user interface units required by a user to operate and navigate the portal

Portal theme Provides the look and feel of a portal desktop.

A portal object containing the definitions that describe the visual appearance of the control elements, font size, colors, and contrast of the user interface elements in a portal desktop.

Portal desktop Enables framework pages and portal themes to be assigned as a combined entity to portal users using scenario- and user-specific display rules.

A container-type portal object comprising selected framework pages and portal themes.

Rule collection (portal display rule)

Provides a means for assigning portal desktops to users at runtime.

A portal object containing the rules that describe the conditions for assigning portal desktops to users using either direct user-, group-, and role-specific parameters, or indirect platform-specific parameters, such as connection bandwidth, browser type, or browser version.

More InformationWorkflow for Portal Display Configuration

Framework Pages

Portal Themes

Portal Desktops

Portal Display Rules

 

Workflow for Portal Display Configuration 

PurposeThis topic summarizes the recommended steps that need to be performed to set up portal displays suitable for your business environment.

PrerequisitesYou have access to the following portal tools in the administration environment:

Tool Default Navigation Path Target Objects

Portal Content Studio Content Administration ® Portal Content

Framework pages (and other objects such as roles and iViews)

Theme Editor

(note that additional theme-related tools are available, which you may need access to)

System Administration ® Portal Display ® Theme Editor

Portal themes

Portal Desktop Editor System Administration ® Portal Display ® Desktops & Display Rules

Portal desktops

Portal Display Rules Editor System Administration ® Portal Display ® Desktops & Display Rules

Rule collections

You will also need the appropriate portal permissions to be able to access and maintain the relevant portal objects in their respective editors. For more information, see Portal Permissions.

Process FlowThe typical workflow for setting up the appropriate portal display for your environment is as follows:

       1.      Create a framework page to define the layout of navigational and content-based components in a portal desktop. See Creating and Editing a Framework Page.

       2.      Create portal themes to define the look and feel of a portal desktop. See Creating Themes in the Theme Editor.

       3.      Create a portal desktop by combining the framework pages and portal desktops. See Creating and Editing a Portal Desktop.

       4.      Create portal display rules to assign portal desktops to users. See Defining Portal Display Rules.

Portal desktop: design and assignment

 

Framework Pages 

DefinitionA portal page object containing user interface units, which together define the layout and structure of a portal desktop. A framework page contains the core iViews and pages that are required by a user to operate and navigate the portal.

StructureA typical framework page includes the following components that comprise a portal desktop (for details, see Portal Interface):

1. header area

2. navigation areas (for example, the top-level navigation and the navigation panel)

3. content area

An organization may generate more than one framework page for their portal users; each one customized to suit a different user environment, browsing scenario, or role (see Creating a Framework Page).

Framework pages are assigned to portal users through portal desktop objects (see Portal Desktops). A portal desktop object combines any number of framework pages and portal themes. The assignment of portal desktops to users, groups, or roles is enabled by means of a portal display rule (see Portal Display Rules). A portal display rule determines which default portal desktop is allocated to users when they log on to the portal, and hence provides the user with the portal themes and framework pages assigned to that portal desktop.

SAP NetWeaver Portal supplies a single framework page with the default portal installation (see Default Framework Page). Additional framework pages can be created by making copies of the default framework and then customizing them.

Although at design time more than one framework page may be assigned to a user, each user can use only one framework page instance at a time.

ExampleThe flexible design of framework pages and navigation layouts offers numerous adaptable options for various portal user experiences. For example, thin desktops can support slow dial-up connections. Varying framework pages in a company's portal may support different navigational needs for its employee intranet as opposed to its customer- or guest-based extranet.

Customized desktops offer flexible user experiences

 

Creating and Editing a Framework Page 

UseTo create a framework page, use the same tools as you use to create a regular portal page.

Procedure1. ...

To create or edit a framework page, use the Page Editor in the Portal Content Studio.

For more information, see Page Editing

To create your own framework page, we strongly recommend to use the default framework page (see Default Framework Page) shipped with the portal as a delta link template. This

ensures that the new framework page contains all necessary properties, and that future enhancements made to the default framework page by SAP are subsequently applied to your own framework page after upgrading.

For the portal runtime to recognize and fully support framework pages, such as underlying navigation-related mechanisms, eventing, and optimal performance, you need to set the Element in Framework Page property in the framework page and in the structural pages that compose it.

This property is necessary for page objects only. You do not need to set the property in iViews that compose or run in the framework page, such as iViews in the navigation panel and header area.You define the Element in Framework Page property described below in the Property Editor. For more information, see Property Editor.

'Element in Framework Page' PropertyThis property identifies the function of a particular page in relation to the entire framework page. Depending on the function of the page in the framework page, assign one of the following values:

1. Framework Page: Assign this value to the main page designated as the framework page. This is the page that holds the structural components constituting the framework page, and which you eventually combine with portal themes to create portal desktops (see Portal Desktops).

For example, this value is assigned to the Default Framework Page object (com.sap.portal.frameworkpage) that is shipped with the portal. See Default Framework Page.

1. Dynamic: Assign this value to the page within the framework page that changes with each navigation event at runtime.

For example, this value is assigned to the Desktop Innerpage object (com.sap.portal.innerpage) which is part of the default framework page shipped with the portal.

1. None: Assign this value to regular portal pages that display content in the portal runtime environment.

If instead of creating a framework page or inner page from a delta link template, you create them from scratch based on your own portal components, you must add the following code in the portal component descriptor file of the respective pages to provide the necessary property and values:

<property name="com.sap.portal.framework.phase" value="None">

<property name="plainDescription" value="Element in Framework Page"/>

<property name="validvalues" value="4/None9/Framework8/Navigate12/Personportal10/Personpage"/>

<property name="validValueTitle0" value="None"/>

<property name="validValueTitle1" value="Framework Page"/>

<property name="validValueTitle2" value="Dynamic"/>

<property name="validValueTitle3" value="Personalize Portal"/>

<property name="validValueTitle4" value="Personalize Page"/>

<property name="category" value="Navigation"/>

</property>

Default Framework Page 

UseThe default framework page supplied with SAP NetWeaver Portal provides the navigational and structural components required to navigate and operate the portal. You can modify the default framework page or create your own framework pages to meet the requirements of your organization.

Location in Portal Catalog: Portal Content ® Portal Users ® Standard Portal Users ® Default

Framework Page (pcd:portal_content/every_user/general/frameworkpage)

Do not modify the delta link source object of the abovementioned framework page, which is located in a subfolder under the Content Provided by SAP folder.

For more information about the intended runtime use of the user interface components in the default portal desktop, see Portal Interface. See also Navigation.

IntegrationThe default framework page supplied with SAP NetWeaver Portal is a single portal page containing default iViews and pages. These components are positioned in the framework page using default page layouts also supplied by SAP.

Pages and iViews in the Default Framework PageThe default framework page contains the following iViews and pages:

Page: Default Framework Page (com.sap.portal.frameworkpage)

This is a portal page that contains the following iViews and pages:

1. iView: Masthead iView

Administrators can show or hide the links in the Masthead iView at runtime by setting the Show Link in Masthead: <Link Name> properties in the iView using the Property Editor.

If you have configured your portal to accept anonymous users, you can add the language personalization dropdown list to the masthead, by changing the property Show Dropdown List in Masthead: Language Personalization for Anonymous Users in the Masthead iView to Yes. At runtime, anonymous users can change the portal language. If the anonymous user logs in as an authenticated user, the dropdown list disappears from the masthead, and the portal appears in the language defined for that user.

2. iView: Tool Area

This iView is assigned to the default framework page, but is by default in a hidden state. To display it, change the property of this iView by editing it in the default framework page (see Editing Content and Layout).

3. iView: Top-Level Navigation (see Top-Level Navigation) 4. iView: Page Title Bar (see Page Title Bar Navigation) 5. Page: Desktop Innerpage (com.sap.portal.innerpage)

This page contains the following iViews that comprise the navigation panel (see Navigation iViews) and the content area:

1. iView: Detailed Navigation (com.sap.portal.detailedNavigationTree) (see Detailed Navigation)

2. iView: Dynamic Navigation (see Dynamic Navigation) 3. iView: Drag&Relate Targets (see Drag&Relate Targets) 4. iView: Related Links (see Related Links) 5. iView: Portal Favorites (see Portal Favorites iView)

The Portal Favorites iView is available only after you have installed Knowledge Management.

6. iView: Content Area7. iView: Collaboration Detailed Navigation

(com.sap.netweaver.coll.CollaborationDetailedNavigation)

When Collaboration is installed, the Default Framework Page includes an additional Detailed Navigation iView that enables the integration of rooms in the portal.

The following figure illustrates the relative positioning of the components in the default framework page.

Layouts in the Default Framework PageThe pages and iViews in the default framework page are spatially positioned through the use of two default page layouts:

Page Layout Assigned to Page Description

Framework Page Layout

(pcd:portal_content/com.sap.pct/admin.templates/layouts/com.sap.portal.layoutPortal1_Framework)

Default Framework Page

Layout is a single full-width column

Navigation Panel and Content Area Layout

(pcd:portal_content/com.sap.pct/admin.templates/layouts/com.sap.portal.layoutPortal1_WAandNavPanel).

Desktop Innerpage Layout is a two-column layout:

1. Navigation Panel: A narrow column on the left for the navigation panel and its iViews.

2. Work Area: A wide column on the right for

the content area.

Portal Themes 

PurposeA portal theme defines the visual appearance of the control elements, font size, colors, and contrast of the user interface elements of a portal desktop. A portal theme does not define the layout, structure, or contents of a portal desktop. This is defined by the default framework page.

Neither the framework page nor the portal theme are directly assigned to a user. Combinations of framework pages and portal themes result in portal desktops. Portal desktops are assigned to users. See also Portal Display Rules (Rule Collections).

You can develop your own portal themes by using one of the theme templates provided by SAP (such as SAP Chrome or SAP Streamline) for:

Changing the color scheme of the portal

Changing the font type and size

Including your own company logo

For an overview of the themes delivered with the portal, see Portal Themes in the Standard Content Delivery.

Implementation ConsiderationsYou create a portal theme in the Theme Editor. You access the Theme Editor in the delivered administrator role by choosing System Administration ® Portal Display ®Theme Editor.

You use the Theme Editor to edit a fixed number of theme properties (such as background color). The corresponding stylesheets are generated automatically and do not need to be edited directly.

The Theme Editor supports the CSS1 standard for cascading stylesheets.

Some of the functions of the Theme Editor are not available under Mozilla Firefox. See Using the Theme Editor under Mozilla FireFox.

The following tools and functions are available with the Theme Editor:

Theme Archive

Allows you to export and import your own themes.

1. ITS Theme Generator

Allows you to generate ITS stylesheets.

Theme Integrity Test

Supports error detection.

You can find all these tools and functions in the delivered administration role under System Administration ® Portal Display.

IntegrationThe following stylesheets can be changed with the Theme Editor:

The stylesheet for the entire portal

All ITS-based IACs and SAP MiniApps (with Release 4.6C and higher)

Stylesheets for the Business Information Warehouse releases 2.0 and 3.0

Portal Themes in the Standard Content Delivery  The following table lists the themes contained in the standard portal content:

Theme General Characteristic

SAP Streamline SAP Streamline uses light blue backgrounds that look good on monitors and newer presentation media, but tend to fade out when displayed through older beamers or LCD screens. It also uses a range of harmonic, similar color tones (mainly shades of blue with different dark-light values) in most elements.

SAP Tradeshow SAP Tradeshow is the primary choice for sales and presentation situations. It offers stronger light-dark contrast than the SAP Streamline theme by using darker border and background colors that stand out against the light body background. It uses stronger shades of blue that display well on all beamers and LCD screens.

SAP Chrome SAP Chrome offers users a further theme variation. This theme is neutral in color, consisting mostly of different tones of metallic gray, with the exception of the bright yellow buttons.

SAP High Contrast (supports accessibility)

SAP High Contrast supports the accessibility functions of SAP NetWeaver Portal. It was designed for users with poor sight to offer maximum contrast between text and background. The white background suits a number of high contrast users.

SAP High Contrast Black (supports accessibility)

This theme is an inversion of the High Contrast theme but also uses a number of bright colors for controls such as borders and text.

 

Working with Portal Themes  You perform actions such as creating, deleting, and assigning permissions to themes at different locations in the portal.

To work with themes, you must be assigned the system administrator or super administrator role. For example, as content administrator you cannot see any themes in the Portal Catalog.

The following table gives an overview of where you can perform theme-related actions in the portal:

Action Location

Create and change theme Choose System Administration ® Portal Display ® Theme Editor. The Theme Editor opens and you can create and change themes.

More information: Changing Style Parameters and Saving New Themes

Create folders for your own themes in the Portal Catalog

Call the Portal Catalog from the system administration role. For example, choose System Administration ® Portal Display ® Desktops & Display Rules. In the Portal Catalog, choose Portal Content ® Themes. You can create your own folders below the Themes folder and store your own themes there.

More information: Themes in the Portal Catalog

Delete themes Choose System Administration ® Portal Display ® Desktops & Display Rules.

More information: Deleting Themes

Assign themes to the portal desktop Choose System Administration ® Portal Display ® Desktops & Display Rules. The Portal Catalog and the Desktop Editor open. In the Portal Catalog under Portal Content ® Themes, select the themes that you want to assign to the desktop.

More information: Creating and Editing Portal Desktops

Assign permissions for themes Choose System Administration ® Permissions. Open the Portal Catalog and under Portal Content ® Themes assign the permissions.

More information: Themes and Permissions

For tips and tricks about working with the Theme Editor, see SAP note 679444.

 

Themes in the Portal Catalog 

UseThemes are stored in the Portal Content ® Themes folder in the Portal Catalog. Here you find:

        The themes delivered by SAP

        Your own themes

Make sure that you keep all your themes in the Themes folder (or a subfolder) and do not distribute themes to other locations in the Portal Catalog using Copy/Paste, as you can do with all other Portal Catalog objects. Themes should remain in their dedicated folder and not be moved to other locations.

When you save new themes in the Theme Editor, you can specify to save them in the Themes folder or in subordinate folders. For details, see Changing Style Parameters and Saving New Themes.

If you want to distribute theme administration across multiple administrators, you can create additional folders below the Portal Content ® Theme folder, store your themes there, and assign user permissions for these folders. In this way administrators can access different themes. See also Themes and Permissions.

 

Creating Themes in the Theme Editor 

PurposeIn the Theme Editor you can develop one or more themes for your portal users. Your own themes are always based on one of the templates provided by SAP. You can change the templates to meet your requirements, for example by changing the background color or swapping images and logos.

The Theme Editor offers the following functions:

        Preview Style Parameters

        Checking the Effect of Style Parameters

        Changing Style Parameters and Saving New Themes

        Undo/Redo and Reset Parameters

Note that in the Theme Editor you only see and edit the themes for which you have permission. See also Themes and Permissions.

The lock mechanism does not work for portal themes. This means that two administrators could edit the same theme at the same time. You can, however, prevent this with delegated administration and the assignment of permissions. See also Themes and Permissions.

 

Previewing Style Parameters 

UseBefore creating your own theme, select one of the templates provided by SAP and look at the predefined parameters to see what you want to change.

Procedure       1.      Choose System Administration ® Portal Display ® Theme Editor.

The Theme Editor opens.

       2.      Click the required template to edit the theme.

       3.      Click the individual elements on the left-hand side of the screen and view the parameters and their properties in the preview window.

If you experience problems seeing the preview, check the nonProxyHost settings. For more information, see Checking the nonProxyHost Settings for the Theme Editor.

Checking the Effect of Style Parameters 

UseYou can display the effect of a style’s parameters on the user interface.

Procedure       1.      On the left-hand side of the screen select a user interface theme element, for example Portal

Tool Area.

The various parameters appear in the lower part of the screen.

       2.      Place the mouse on a parameter name.

In the preview area, a red box marks the area influenced by this parameter.

Changing Style Parameters and Saving New Themes 

UseYou can create your own themes by changing the values of individual style parameters of an existing SAP template and saving the template under a new name in the Portal Catalog.

2. ...

You cannot edit the delivered SAP templates: They are only offered as read-only in edit mode. You have to store your changes to the template under a new name.

Procedure       1.      On the left-hand side of the screen, select an element of the user interface

In the preview area you see what the element looks like in the selected template. The different parameters for the selected element are displayed in the lower part of the screen under Styles.

       2.      Edit the relevant parameters.

Change the parameter values or add other logos and images (see Changing Logos and Images).

If you choose the Options link next to the input fields, a dialog box appears. This helps you to select the right value for the current parameter according to the CSS1 standard.

Note that you only see the effects of a change if you either press ENTER or click another input field.

       3.      Choose Save As to save the template.

       4.      Enter the following data for your theme:

        Name         Theme ID         In the dropdown list under Folder ID, search for the folder in the Portal Catalog where you

would like to store the theme. The folders Portal Content ® Themes and Portal Content ® Themes ® Customer appear as default values. The folders that you created yourself also appear in the list. For more information about themes in customer folders, see Themes in the Portal Catalog.

ResultYou created your own theme. Your themes are offered for editing on the selection screen of the Theme Editor under My Themes.

Changing Style Parameters and Saving New Themes 

UseYou can create your own themes by changing the values of individual style parameters of an existing SAP template and saving the template under a new name in the Portal Catalog.

3. ...

You cannot edit the delivered SAP templates: They are only offered as read-only in edit mode. You have to store your changes to the template under a new name.

Procedure       1.      On the left-hand side of the screen, select an element of the user interface

In the preview area you see what the element looks like in the selected template. The different parameters for the selected element are displayed in the lower part of the screen under Styles.

       2.      Edit the relevant parameters.

Change the parameter values or add other logos and images (see Changing Logos and Images).

If you choose the Options link next to the input fields, a dialog box appears. This helps you to select the right value for the current parameter according to the CSS1 standard.

Note that you only see the effects of a change if you either press ENTER or click another input field.

       3.      Choose Save As to save the template.

       4.      Enter the following data for your theme:

        Name         Theme ID         In the dropdown list under Folder ID, search for the folder in the Portal Catalog where you

would like to store the theme. The folders Portal Content ® Themes and Portal Content ® Themes ® Customer appear as default values. The folders that you created yourself also appear in the list. For more information about themes in customer folders, see Themes in the Portal Catalog.

ResultYou created your own theme. Your themes are offered for editing on the selection screen of the Theme Editor under My Themes.

Changing Style Parameters and Saving New Themes 

UseYou can create your own themes by changing the values of individual style parameters of an existing SAP template and saving the template under a new name in the Portal Catalog.

4. ...

You cannot edit the delivered SAP templates: They are only offered as read-only in edit mode. You have to store your changes to the template under a new name.

Procedure       1.      On the left-hand side of the screen, select an element of the user interface

In the preview area you see what the element looks like in the selected template. The different parameters for the selected element are displayed in the lower part of the screen under Styles.

       2.      Edit the relevant parameters.

Change the parameter values or add other logos and images (see Changing Logos and Images).

If you choose the Options link next to the input fields, a dialog box appears. This helps you to select the right value for the current parameter according to the CSS1 standard.

Note that you only see the effects of a change if you either press ENTER or click another input field.

       3.      Choose Save As to save the template.

       4.      Enter the following data for your theme:

        Name         Theme ID         In the dropdown list under Folder ID, search for the folder in the Portal Catalog where you

would like to store the theme. The folders Portal Content ® Themes and Portal Content ® Themes ® Customer appear as default values. The folders that you created yourself also appear in the list. For more information about themes in customer folders, see Themes in the Portal Catalog.

ResultYou created your own theme. Your themes are offered for editing on the selection screen of the Theme Editor under My Themes.

Portal Themes and Right-to-Left (RTL) Languages 

UseRight-to-left languages, such as Hebrew and Arabic, require different stylesheets and images than the left-to-right languages (LTR).

Due to the fact that generating stylesheets for RTL languages takes some time, when you create a new theme, only the stylesheets for the LTR languages are generated in the standard setting. You configure the generation of stylesheets in the service configuration interface.

FeaturesThe following functions are provided:

        Configuring Right-to-Left Languages

        Uploading Images for Right-to-Left Languages

Stylesheets for RTL languages can only be generated for the Unified Rendering stylesheets of a theme part.

iViews on a page can be displayed with either RTL or LTR stylesheets only. A mixed display only works if an iView is isolated on a page.

In addition, the iView property Forced Request Languages overwrites the personalized portal language that was set. This property has an effect on the stylesheets that are generated for the overall page.

 

Configuring Right-to-Left Languages 

UseIn the standard settings for the portal, when you create themes, stylesheets are not automatically generated for right-to-left (RTL) languages. This is because creating stylesheets for both left-to-right (LTR) and RTL languages is a time-consuming process. You should only set RTL stylesheet generation if it is absolutely necessary.

Procedure       1.      In the portal, choose System Administration ® System Configuration ® Service Configuration.

       2.      In the Portal Catalog, navigate to Applications ® com.sap.portal.themes.designservice ® Services ® design.

       3.      Right-click design and from the context menu choose Configure.

The service is loaded in the Property Editor and can be modified.

       4.      The com.sapportals.portal.design.textDirection property contains the value LTR by default. Change the value to the following:

LTR,RTL

       5.      Save the modified service.

ResultWhen you create a theme, both the LTR and RTL stylesheets are now generated.

Uploading Images for Right-to-Left Languages 

UseYou can upload images for right-to-left languages for your themes using the Right-to-Left Image Uploader available in the Support Desk.

Procedure1. ...

       1.      Choose System Administration ® Support ® Support Desk.

       2.      Select Themes.

       3.      Under Test and Configuration Tools, select Edit “Right to Left” Theme Images.

       4.      Select the theme for which you want to upload special images.

The image parameters available within the themes are listed. You can also search for the parameters for which you want to upload images.

       5.      Click Browse next to the input field of a parameter and select the required file.

       6.      Click Upload to upload the file.

Exporting and Importing Themes 

UseYou use the Theme Archive tool to import and export themes as zip files.

Procedure       1.      Choose System Administration ® Portal Display ® Theme Archive.

Your themes are listed under Export Themes.

       2.      To export a theme, click the theme to be exported and specify a target folder for the zip file.

       3.      To import a theme:

6.                             a.      Specify the path to the theme that you want to import, or choose Browse to select the zip file of a theme.

7.                             b.      If you want the imported theme to overwrite existing themes, select Overwrite Existing Theme.

8.                             c.      Choose Import.

Deleting Themes 

UseYou delete themes from the Portal Catalog in Desktop & Display Rules.

Procedure       1.      Choose System Administration ®Portal Display ® Desktops & Display Rules.

       2.      In the Portal Catalog choose Portal Content ® Themes, right-click a theme and choose Delete.

You cannot delete the theme templates provided by SAP. You also cannot delete themes that are still being used in the desktop.

 

Theme Generator for the Internet Transaction Server 

UseYou use the ITS Theme Generator to generate an ITS stylesheet for an existing theme.

For information about style integration between Internet Application Components (MiniApps in ABAP-based systems, IACs) and SAP NetWeaver Portal, see SAP note 607843.

You need to regenerate or modify the stylesheet definitions for the ITS under the following conditions:

        If you are using the ITS and want to adjust services from ABAP-based systems (for example IACs) to the SAP NetWeaver Portal look and feel.

        If a higher ITS patch release is installed to update the ITS components. Stylesheets are release-dependent and therefore have to be adjusted if the ITS is upgraded. This is true for the theme templates delivered by SAP as well as for your own themes.

The functions for adjusting the stylesheets are offered with ITS Release 4.6D-C4 Patch Level 233 (see also SAP Note 454827).

IntegrationIf an ITS service is started from a portal, a URL extension is used to guide the ITS to the correct style information in the portal.

PrerequisitesAll ITS instances must have identical release versions.

If you are using ITS ≤ 6.20, you must install the file designer-x.sar on an ITS instance. This file provides the sap_preview and sap_generate services for generating the ITS stylesheets.

FeaturesYou generate the ITS parts for your themes.

You can also adjust the design changes you made for Workplace Release 2.10 and 2.11 to the look and feel of the SAP NetWeaver Portal.

ActivitiesIf you are using ITS, it is not sufficient to adjust your theme using the Theme Editor. You must also use the functions of the ITS Theme Generator.

All the user interface elements that are relevant for the ITS (other than images) can also be adapted with the Theme Editor. However, the Theme Editor only records the changes that affect the ITS. When the stylesheets are generated, the ITS stylesheets are not taken into consideration.

Subsequent generation by the ITS Theme Generator is necessary. In addition, ITS images can only be edited using this tool.

Proceed as follows:

       1.      Create a theme in the Theme Editor and save it.

See also Changing Style Parameters and Saving New Themes.

       2.      Choose System Administration ® Portal Display ® ITS Theme Generator.

       3.      Enter data as follows:

9.                             a.      If you are using ITS ≤ 6.20, enter the following data:

        ITS Server: Enter the full domain URL on which the designer-x.sar file was installed. Use the following syntax:

http://<server>:<port>/scripts/wgate/

        ITS Preview Service: Enter the service whose ITS styles are to be adjusted. The sap_preview service is specified by default. This service contains all the elements for previewing ITS images.

        Portal Theme: Specify the theme for which the ITS parts should be generated and images should be adjusted.

You do not need either a user or a password.

10.                             b.      If you are using ITS 6.40, enter the following data:

        ITS Server: Enter the URL of the ITS server. Use the following syntax:

http://<server>:<port>/sap/bc/gui/sap/its/

        User         Password         ITS Preview Service: Enter any IAC that is running on the server.

The ITS Theme Generator opens in edit mode. The upper part of the screen shows a preview of the ITS images. In the lower part of the screen, you can change images. You can see the effect of your changes in the preview area.

       4.      In the Edit Area, move the mouse over the images. In the preview area the location of the image is marked with a red box. You can now change and replace images. See also Changing Logos and Images.

       5.      Choose Generate.

All ITS stylesheets are generated.

The settings made in the Theme Editor only show their effect now.

2. ...

Performing Theme Integrity Tests 

UseThe theme integrity test helps you find errors in your portal themes. Choose System Administration ® Portal Display ® Theme Integrity Test.

ActivitiesThe following tests are provided:

Test Name Input Description

Server Side URL Connection Test

Any URL Use this test to check that portal resources are available on the server using an HTTP link. For example, whether the static Theme Editor preview is loaded on the server side. This test is also used to test the URL on the portal itself.

Personalization Test

User ID Tests the personalization status of the user.

The test result displays the folder name (technical name) of the theme that the user selected during personalization.

If the user did not personalize the theme, a message is displayed.

PCD Test   Tests the connection to the PCD or database.

This connection is needed when themes are created or changed in the Theme Editor.

Use these tests before entering a customer message. You can copy the results of the tests into your message.

Note that you can perform additional tests in the Themes area of the Support Desk, which is located at System Administration ® Support ® Support Desk. Cluster theme integrity tests are provided under Test and Configuration Tools. For example:

LafService Integrity Test: Tests the file structure for the Theme Editor. For example, are all the stylesheets for all supported browsers available? Is there a separate folder in the file structure for the ITS?

ITS Connection Test:

1. Is the connection to the ITS available?2. Was the designer-x.car file installed on the ITS?3. Is the correct version of the ITS available?

Where are Your Themes Stored in the Portal?   The theme templates provided by SAP and your own themes are stored in the portal database in the Portal Content Directory (PCD). Further server scenarios are possible.

When you generate a theme, the stylesheets are automatically adjusted accordingly in these folders.

Each template and each theme consists of different theme parts. The individual parts consist of CSS stylesheets and images.

 

Themes and Permissions 

UseYou assign permissions for entire folders containing themes, but not for individual themes.

IntegrationIn contrast to other portal objects, themes have a fixed repository in the Portal Catalog. That is, they are in a specific folder from which they cannot be moved to another location. For more information, see Themes in the Portal Catalog.

You cannot create or edit themes in the Content Administration environment. For more information, see Working with Portal Themes.

Activities1. ...2. Create themes and store them in the relevant folder in the Portal Catalog under Portal

Content ® Themes.

To access the permissions for the Themes folder, in the Portal Catalog, right-click the Themes folder and select Open ® Permissions.

If you want to distribute theme administration across multiple administrators, you can create additional folders below folder Portal Content ® Themes, store your themes there, and assign permissions for the theme administrators for these folders. In this way administrators can access different themes.

3. Launch the Permission Editor with System Administration ® Permissions and assign permissions.

For more information, see Portal Permissions.

Checking the nonProxyHost Settings for the Theme Editor 

UseIf the theme editor’s preview function does not work correctly, you need to check that the portal is configured with the correct nonProxyHost settings.

Procedure       1.      Go to System Administration ® System Configuration ® Service Configuration.

       2.      In the Portal Catalog, open Applications ® com.sap.portal.ivs.httpservice ® Services.

       3.      Right-click proxy, and select Configure.

       4.      In the HTTP – Bypass Proxy Servers property, enter the relevant server information. For example, *.yourCompany.

Separate entries with a pipe character ( | ).

       5.      Restart the proxy service:

1. Go to ...

11.                             a.      Go to System Administration ® Support ® Portal Runtime.12.                             b.      In the “Portal Anywhere” Admin Tools section, select Application Console.13.                             c.      Select the com.sap.portal.ivs.httpservice service and click show.14.                             d.      In the com.sapportals.portal.ivs.proxy.ProxyServerService row, click restart.

To check that your settings are correct, run the Server Side URL Connection Test. If the nonProxyHost settings are incorrect, the test displays an HTTP error. For more information, see Performing Theme Integrity Tests.

Portal Desktops 

DefinitionFor portal users, a portal desktop defines the structural layout and design of the portal workspace displayed on the screen. It is a structured collection of iViews, pages, themes, and layouts, which can be personalized at runtime.

In the design time environment, a portal desktop is a collection of framework pages and portal themes, which is defined and customized by content administrators, and ultimately assigned to portal users through portal display rules.

UsePortal desktops combine personalization and scenario-based options for portal users at runtime:

        The openness and flexibility of framework pages enable administrators to design custom-made navigation layouts that suit numerous portal user experiences. For example, thin desktops can support dial-up connections, while customized framework pages support different navigational needs for a company’s employee intranet and customer-based extranet.

Portal users automatically receive the appropriate framework page based on transparent display rules, which are predefined by the portal administrator. See Portal Display Rules.

        Portal users have the freedom to choose a portal theme to personalize the look and feel of their portal desktop.

StructureA portal desktop is a portal object that comprises any number of framework pages and portal themes:

        Framework page: Defines the layout of navigational and structural elements in the portal desktop. For more information, see Framework Pages.

A portal desktop may contain more than one framework page. The administrator responsible for configuring the portal desktop object sets the active framework page.

        Portal Theme: Defines the overall look-and-feel of user interface elements in a portal desktop, such as color, contrast, and font usage. For more information, see Portal Themes.

A portal desktop may contain more than portal theme. The administrator responsible for configuring the portal desktop object sets the default portal theme. At runtime, users can personalize their portal desktop by choosing a portal theme to suit their needs and taste.

For information about creating your own portal desktops, see Creating and Editing a Portal Desktop.

SAP NetWeaver Portal supplies a default portal desktop, which includes a default framework page and default portal themes. For a more information, see Default Portal Desktops.

Creating and Editing a Portal Desktop 

UseYou use the Portal Desktop Editor to create portal desktop objects. A portal desktop combines framework pages and portal themes into a single entity, which are later assigned to portal users through display rules.

Prerequisites1. Access to the Portal Desktop Editor in the default system administrator role.

2. At least read/write permission for the Portal Catalog folder in which you want to create or edit a portal desktop object.

3. At least read permission for the relevant framework pages and portal themes in the PCD (Portal Content Directory).

Procedure

Creating a Portal DesktopNavigate to System Administration ® Portal Display ® Desktops & Display Rules.

In the Portal Catalog, right-click the folder in which you want to create a portal desktop object, and from the context menu choose New ® Portal Desktop.

The Portal Desktop Editor opens.

In the Portal Desktop Name field, enter a friendly name for the portal desktop object.

In the Portal Desktop ID field, enter a unique ID for the portal desktop object.

Assign framework pages and portal themes to the portal desktop:

1. To add a framework page or portal theme to the portal desktop, right-click the desired object in the Portal Catalog and choose either Add Framework Page to Portal Desktop or Add Theme to Portal Desktop.

1. To remove a framework page or portal theme from the portal desktop, choose the radio button of the desired object, and click Remove.

Specify both an active framework page and a default portal theme for the portal desktop. To do so, choose the radio button of the desired object listed in the editor, and click Set Default.

Click Save.

The portal desktop object is created in the selected folder. You may access it later from the Portal Catalog for further editing.

Editing a Portal Desktop4. ...

Navigate to System Administration ® Portal Display ® Desktops & Display Rules.

In the Portal Catalog, right-click the portal desktop object that you want to edit and from the context menu, choose Open ® Object.

The Portal Desktop Editor opens and displays the framework pages and portal themes currently assigned to the selected portal desktop object. Click Locate in Portal Catalog to find the assigned objects in the Portal Catalog tree.

Add or remove framework pages and portal themes to or from the portal desktop as you would when creating a portal desktop (see procedure above). You may also specify a different active framework page and default portal theme.

Click Save.

Specifying a Browser CaptionBy default, the text SAP NetWeaver Portal appears in the caption of the browser in which the portal is displayed. You can edit this text so that different portal desktops use different browser captions.

5. ...

Navigate to Content Administration ® Portal Content.

In the Portal Catalog, right-click the active framework page of the portal desktop whose caption you want to change and from the context menu, choose Open ® Object.

In the Property Editor, from the Property Category dropdown list, choose Navigation.

In the Desktop Title property, specify the text that you want to appear in the browser caption.

Click Save.

Default Portal Desktop 

UseSAP NetWeaver Portal supplies a single default desktop, which includes a framework page and default portal themes.

Location in Portal Catalog: Portal Content ® Portal Users ® Standard Portal Users ® Default

Portal Desktop (pcd:portal_content/every_user/general/defaultDesktop)

Do NOT delete or move this default portal desktop. If at runtime the portal is unable to resolve a portal desktop for a given user based on the defined display rules, the default desktop is automatically provided.

In addition to the default portal desktop, you can create your own portal desktop to meet the specific requirements of your organization.

IntegrationThe default portal desktop object contains the following objects:

Object type Included objects

Framework page         Default Framework Page

This framework page comprises three main areas: header area, navigation panel, and the content area. See Default Framework Page.

Portal theme         SAP Streamline (sap_standard)

        SAP Chrome (sap_chrome)

        SAP High Contrast Black (sap_hcb)

        SAP High Contrast (sap_highcont)

        SAP Tradeshow (sap_tradeshow)

Portal Display Rules (Rule Collections)  

DefinitionA set of conditions defined by a portal administrator determining which portal desktops (a portal object combining selected framework pages with portal themes; see Portal Desktops) are assigned to portal users at runtime in SAP NetWeaver Portal. This allows organizations to allocate portal desktops with varying designs, branding, or layouts to different departments, subcompanies, or platform-specific scenarios.

Display rule definitions are transparent to portal users. At logon, users are seamlessly presented with the appropriate portal desktop assigned to their role, group, user, or scenario.

UseThe following examples describe some scenarios that may require the need for alternative portal desktops:

Internal employees versus external customers and partners

Users accessing the portal through a dial-up connection (requiring a thin client desktop) versus broadband connections

Subcompanies belonging to the same organization (requiring different company branding in the portal header)

Display rules can be a combination of platform configuration and user-specific rules, by specifying the following:

Type Description

Names of users, groups, and roles This method of portal desktop assignment to users is direct. You are stating exactly which users will receive each desktop.

Connection bandwidth, browser type, browser version, and portal URL aliases

This type of portal desktop assignment to users is indirect. You are not specifying a particular user directly, but stating a configuration that may correspond to any user.

StructurePortal display rules are defined as portal objects known as rule collections. A rule collection comprises a set of conditions, constructed by IF and THEN expressions, which together provide a means for assigning portal desktops to users at runtime.

A rule collection comprises the following components:

1. An IF statement on its own is referred to as an expression. Likewise, a THEN statement on its own is referred to as an expression.

2. The segments that make up an IF or THEN expression are referred to as parameter, operator, and value.

3. A combination of one or more nested IF expressions with a single THEN expression is collectively referred to as an IF-THEN condition or just condition.

4. A combination of one or more conditions is collectively referred to as a rule collection.

Rule collection: the components comprising an IF-THEN condition.

The possible parameters that you can assign to each IF and THEN expression, per expression, are as follows:

IF parameters THEN parameters

1. users

2. groups

3. roles

4. connection bandwidth

5. portal URL aliases

6. browser type

7. browser version

8. portal desktops

9. rule collections

IntegrationThe portal runtime determines the appropriate desktop assignment for each user logging on to the portal. The assignment is based on conditions defined in the default rule collection object, named Master Rule Collection (main_rules). See Master Rule Collection.

You can create additional rule collection objects and delegate them to different administrators in your organization. Each administrator is responsible for defining the display rules for their specified rule collection object by assigning portal desktops to users and use cases in their suborganization.

The portal runtime starts with the Master Rule Collection object. Additional rule collection objects must be added as nested conditions in the Master Rule Collection object for them to take effect.

If at runtime, the portal is unable to resolve a portal desktop for a given user based on the defined display rules, the Default Portal Desktop is automatically provided. See Default Portal Desktop.

Rule collection objects are stored in the Portal Content Directory (PCD). You use the Portal Display Rule Editor to create and edit rule collection objects. See Defining Portal Display Rules.

Display rules do not determine which portal content (iViews and pages) is assigned to portal roles, nor does it determine the roles and groups to which users are assigned. For more information, see Role Editor and Workset Editor and Assigning Roles to Users and Groups.

You can include predefined portal URL aliases as part of your display rules. For more information, see Portal URL Aliases.

PrerequisitesBefore you define specific portal display rules, we recommend that you first generate the necessary framework pages, portal themes, and portal desktops.

ExampleThe following diagram illustrates how portal display rules are resolved at runtime:

Portal Display Rules: Runtime activity upon user logon

 

Defining Portal Display Rules 

UseRule collections allow you to define the way in which portal desktops are assigned to portal users at runtime.

You use the Portal Display Rules Editor to create rule collection objects.

Note the following:

Conditions are prioritized according to their top-to-bottom order of appearance in the rule collection. If a user fits more than one condition, then the first condition that is true for that user, determines which portal desktop is displayed. See the example below for details.

An IF-THEN condition may contain unlimited nested IF expressions.

An IF-THEN condition may contain only a single THEN expression.

A rule collection object may contain conditions that reference other rule collection objects. For example:

IF Browser Type = Microsoft Internet Explorer

THEN Rule collection = pcd:Display_Rules/MSIE_Rules

Prerequisites1. You have access to the Portal Display Rules Editor (by default, it is assigned to the system

administration role).

2. You have at least read/write permissions for the Portal Catalog folder in which you are creating or editing a rule collection object.

3. You have at least read administrator permissions on the relevant portal desktop and rule collection objects in the Portal Catalog.

4. If you intend to use portal URL aliases in your display rules, you need to configure your portal gateway accordingly. See Portal URL Aliases.

Procedure

Creating a Rule CollectionNavigate to System Administration ® Portal Display ® Desktops & Display Rules.

In the Portal Catalog, right-click a folder in which you want to create a rule collection object and choose New ® Rule Collection. The Portal Display Rules Editor opens.

In the Rule Collection Name field, enter a friendly name for the rule collection object.

In the Rule Collection ID field, enter a unique ID for the rule collection object.

Define the conditions of the display rules using a combination of IF and THEN expressions:

Action Description

Adding a new IF-THEN condition

6. ...

In the rule collection list, choose any existing IF or THEN expression and click Add IF Expression. A new IF-THEN condition is added to the end of the rule collection list (use the Move Up and Move Down buttons to correctly position the new condition).

By default, the new expression is defined as: IF User = * THEN Portal Desktop =

pcd:portal_content/every_user/general/defaultDesktop. Change the default values for each expression, as needed.

Repeat the following steps to define each of the IF and THEN expressions separately:

15. In the rule collection list, choose the relevant IF or THEN expression. The expression’s currently assigned parameters are displayed in the editing area above the rule collection list.

16. In the editing area, define the parameter, operator, and value of the expression in the appropriate dropdown menus and text boxes.

Note the following:

When choosing an operator, select = for equals and NE for not equals.

Roles, groups, users, portal desktops, and rule collections require that you enter a full path and object ID. Precede the path with pcd: (without the slash) and follow with the full PCD path name and object ID. For example:

pcd:portal_content/every_user/general/eu_role

Instead of typing in the name of a role, portal desktops, or rule collection manually, you can choose the target object by right-clicking it in the Portal Catalog and then choosing Add <object_type> to Expression in the context menu.

You may use a wildcard value in the form of an asterisk (*) where necessary.

When entering a portal URL alias, enter only the alias segment of the URL. For example: portal/light or portal/guest.

17. When you have completed the expression, click Apply. The updated expression is added to the rule collection list.

Assign the new condition to the appropriate position in the rule collection list using the Move Up and Move Down buttons.

Action Description

Adding a nested IF expression

7. ...

Choose a THEN expression in an existing condition. Note that the nested IF expression is added directly above the selected THEN expression and below the last IF expression in the current IF-THEN condition.

The parameters of the THEN expression are displayed in the editing area above the rule collection list.

In the editing area, choose IF as the expression type in the first dropdown menu. A new IF expression is added to the rule collection list.

In the editing area, define the parameter, operator, and value of the IF expression in the appropriate menus and text boxes, as described above.

When you have completed the expression, click Apply. The updated IF expression is added to the selected IF-THEN condition.

Changing the priority of IF-THEN conditions

In the rule collection list, choose the root IF expression in the IF-THEN condition that you want to move, and then click either Move Up or Move Down.

This action moves the entire IF-THEN condition of the selected IF expression, including any nested IF expressions.

Deleting an IF-THEN condition

In the rule collection list, choose the root IF expression in the IF-THEN condition you want to delete, and then choose Delete.

This action deletes the entire IF-THEN condition.

1.Click Save. The rule collection object is created in the selected folder. You may access it later from the Portal Catalog for further editing.

Editing a Rule Collection8. ...

Navigate to System Administration ® Portal Display ® Desktops & Display Rules.

In the Portal Catalog, right-click a rule collection object that you want to edit and choose Open ® Object.

The Portal Display Rules Editor opens and displays the conditions of the selected rule collection object.

Add, remove, or modify conditions as described in the table above.

Click Save.

ExampleThe diagram below illustrates how conflicting conditions are resolved; for example when a user matches more than one condition. At logon, the system begins with the first condition at the top of the list and works its way down until it reaches a match. Once a match is made, the user is given the portal desktop assigned to that condition, regardless of any matching conditions that may follow.

User ConfigurationA particular company has the following setup:

1. Two roles: External and Internal

2. The role Internal contains users who also belong to two user groups: N.America and Asia

3. User A belongs to both the role Internal and the user group N.America

4. User B belongs to both the role Internal and the user group Asia

5. User C belongs to the role External

Conditions Defined in Portal Display Rules1. If Group = N.America

Then Portal Desktop = Orange Flavor

2. If Role = InternalThen Portal Desktop = Green Flavor

3. If Group = AsiaThen Portal Desktop = Blue Flavor

4. If Role = ExternalThen Portal Desktop = Red Flavor

Note that (i) user A matches conditions 1 and 2; (ii) user B matches conditions 2 and 3; and (iii) user C matches condition 4.

ResultsAccording to the list of priorities, these are the results:

1. User A receives portal desktop "Orange Flavor" (according to condition 1 which has priority over rule 2)

2. User B receives portal desktop "Green Flavor" (according to condition 2 which has priority over rule 3)

3. User C receives portal desktop "Red Flavor" (according to condition 4)

Master Rule Collection 

UseSAP NetWeaver Portal supplies a default rule collection object named Master Rule Collection (main_rules). The portal runtime analyzes the display rules defined in this object to determine which portal desktop to provide to users when they log on to the portal.

Location in Portal Catalog: Portal Content > Portal Administrators > Super Administrators > Master

Rule Collection (main_rules) (pcd:portal_content/administrator/super_admin/main_rules).

Do not delete or move this rule collection object. Without this object, the portal runtime cannot assign a desktop to users logging on to the portal.

IntegrationIf you are using additional rule collection objects in the Portal Catalog, you must add them to the Master Rule Collection object as nested conditions for them to take effect.

FeaturesBy default, the Master Rule Collection object contains the following condition:

IF User = *THEN Portal Desktop = pcd:portal_content/every_user/general/defaultDesktop

This is a generalized condition (where the parameter type User is defined as a wildcard value) that assigns the default portal desktop supplied with the portal (see Default Portal Desktop) to any user logging on to the portal.

Typically, this condition should be maintained as the last condition in the Master Rule Collection object, thus providing a fallback option if the rule collection does not specify a desktop assignment for every possible user or scenario. Nevertheless, if the portal is unable to resolve a portal desktop for a given user based on the defined display rules, even without the aforementioned condition, the Default Portal

Desktop desktop object is automatically given to the user.

Portal URL Aliases  You can include predefined portal URL aliases as part of your display rules. Portal URL aliases utilize a gateway mechanism in the portal that enables you to define and configure an alias for a path in the portal URL.

Clients can use the preconfigured portal URL aliases to access the portal according to different use cases or scenarios. Each preconfigured portal URL path is characterized by a unique segment, referred to as the alias. For example, having defined more than one entry URL, you can configure the gateway to direct a URL to a high or low bandwidth connection, guest or employee, and so on.

A portal URL path is formulated as follows: http://<hostname>:<port>/<path>/irj/portal/<alias>

where <alias> represents the unique segment of the path.

For example: http://myhost:50000/irj/portal/light or http://myhost:50000/irj/portal/guest.

Before you can define a display rule using a portal URL alias, you need to configure your gateway mechanism accordingly. For instructions on doing so, see How to Configure the J2EE Engine Deployment Descriptor on SAP Developer Network at sdn.sap.com/irj/sdn/howtoguides ® SAP NetWeaver 2004 ® Portal.

For information about incorporating portal URL aliases in a rule collection, see Defining Portal Display Rules.

 

Portal Content Directory (PCD)  The Portal Content Directory (PCD) is a software layer for accessing the information about portal objects. The information is stored in the portal database.

The PCD stores portal objects as a set of trees of nodes. The main top-level node is called portal_content, whose tree contains nodes for iView, page, workset, role and other semantic objects. The tree can also contain folder nodes.

For more information, see the PCD central note 715309 (NetWeaver 2004) or 588904 (EP 6.0).

PCD Inspector  

Purpose

With the PCD Inspector tool, you can perform a thorough analysis of objects stored in the PCD in case you need support. You can also centrally modify PCD objects.

The change function should only be used with great care and by persons who have expert PCD knowledge. Accidental changes (such as deleting a PCD object) normally cannot be undone and could gravely endanger or permanently damage the portal.

IntegrationYou go to the PCD Inspector from the Support page.

Choose Support ® Support Desk ® Portal Content Directory. In the Test and Configuration Tools area, click on PCD Inspector.

FeaturesCentral functions of the PCD Inspector are for example:

        Search the hierarchy structure of the PCD

        Search for PCD objects

        Display object properties

        Visualize object dependencies and delta links

        Compare object properties

        Copy, change or delete object properties

        Display the where-used list for linked objects

        Adjust data for portal content migration

For detailed documentation on using the tool, see the guide „PCD Inspector - Support Tool for

Experts“. For information about the availability of the guide, see SAP Note 854937.

ConstraintsThe PCD Inspector can be used for a broad range of applications. Because of the large number and complexity of the functions, the risk of corrupting or losing data, and the danger of causing irreversible damage to the portal, you are explicitly reminded that the PCD Inspector should only be used in change mode (read-write mode) with the greatest possible care.

In case of doubt, use the standard administration tools for content management and content maintenance. For more information see Portal Catalog and Object Editors & Wizards in the Portal Content Studio.

ExampleApplication example fort he PCD Inspector:

Display of all iViews assigned to role super_admin_role 1. ...

       1.      Navigate to the repository in which the role is stored:pcd ® portal_content ® com.sap.pct ® administrator ® super_admin .

       2.      Click on icon Search .

       3.      Define the search parameters and choose object type iViews. The object URL for starting the search in this example is pcd:portal_content/com.sap.pct/administrator/super_admin/com.sap.portal.super_admin_role

       4.      Choose Search and then Display Search Results.

PCD Inspector  

Purpose

With the PCD Inspector tool, you can perform a thorough analysis of objects stored in the PCD in case you need support. You can also centrally modify PCD objects.

The change function should only be used with great care and by persons who have expert PCD knowledge. Accidental changes (such as deleting a PCD object) normally cannot be undone and could gravely endanger or permanently damage the portal.

IntegrationYou go to the PCD Inspector from the Support page.

Choose Support ® Support Desk ® Portal Content Directory. In the Test and Configuration Tools area, click on PCD Inspector.

FeaturesCentral functions of the PCD Inspector are for example:

        Search the hierarchy structure of the PCD

        Search for PCD objects

        Display object properties

        Visualize object dependencies and delta links

        Compare object properties

        Copy, change or delete object properties

        Display the where-used list for linked objects

        Adjust data for portal content migration

For detailed documentation on using the tool, see the guide „PCD Inspector - Support Tool for

Experts“. For information about the availability of the guide, see SAP Note 854937.

ConstraintsThe PCD Inspector can be used for a broad range of applications. Because of the large number and complexity of the functions, the risk of corrupting or losing data, and the danger of causing irreversible damage to the portal, you are explicitly reminded that the PCD Inspector should only be used in change mode (read-write mode) with the greatest possible care.

In case of doubt, use the standard administration tools for content management and content maintenance. For more information see Portal Catalog and Object Editors & Wizards in the Portal Content Studio.

ExampleApplication example fort he PCD Inspector:

Display of all iViews assigned to role super_admin_role 1. ...

       1.      Navigate to the repository in which the role is stored:pcd ® portal_content ® com.sap.pct ® administrator ® super_admin .

       2.      Click on icon Search .

       3.      Define the search parameters and choose object type iViews. The object URL for starting the search in this example is pcd:portal_content/com.sap.pct/administrator/super_admin/com.sap.portal.super_admin_role

       4.      Choose Search and then Display Search Results.

Configuration for the Portal Content Directory  Nearly all of the central settings for the Portal Content Directory (PCD) can be found and configured in the PCDStartup.Properties configuration file. To modify these settings, you need to activate write-protect mode in the Visual Administrator.

The location of the PCD and the configuration file is defined by the PCD.Home configuration property.

 

Property PCD.Home  This variable value defines the location of the PCD configuration file. In a clustered environment, this should be a central location (that is, shared between all server nodes of a cluster) in order to provide a common configuration for the whole cluster.

The value of PCD.Home is defined by default by the J2EE Engine. A shared global directory, that is used by all the applications of the J2EE Engine, is used. The global directory for the PCD resides at /usr/sap/<Instance>/sys/global/pcd.

This directory also contains the PCDStartup.Properties configuration file.

The value of PCD.Home can be overridden by a system property.

 

Properties PCD.Share and PCD.Temp  The values of the properties PCD.Share and PCD.Temp are defined in the PCDStartup.Properties configuration file.

Variable Use

PCD.Share The value of this property is the path to a folder in the file system where central (that is, shared between several portal servers belonging to the same cluster) files are stored. In contrast to EP 5.0, in EP 6.0 a database is used as storage for the PCD. However, there are still files stored in this central folder for import and export, for example. In a clustered portal environment, you should define a central share location and specify its path as the value for PCD.Share.

The default setting for PCD.Share is the value of PCD.Home.

PCD.Temp Some PCD applications need a folder where temporary data can be stored. It must be possible to create and delete folders and files at this location. However, the folder should not be shared between nodes in a clustered environment.

It is essential that the folder not be too deep in the file structure. Otherwise the maximum path length on Windows systems may be exceeded when temporary files are created.

The default value for PCD.Temp is a relative path.

 

Configuration File PCDStartup.Properties  The pcdStartUp.properties file contains all the configuration parameters for the PCD. These configuration parameters refer, for example, to the following areas: PCD trace, lock service, generic layer, ACL service, transport service, and migration.

You activate write-protect mode for this configuration file in Visual Administrator. For more information, see Setting Write-Protect Mode for the PCD.

The pcdStartUp.properties file is created automatically the first time the portal is started after installation. Most of the configuration parameters of the file already contain default values.

You make changes to the pcdStartUp.properties file on the J2EE Engine. In the portal administration environment you check the configuration parameters and reload the default configuration.

The pcdStartUp.template.properties file exists in parallel with the pcdStartUp.properties file. This file is shipped as part of the IRJ Web Application. The pcdStartUp.template.properties file contains a list of the available configuration parameters that you can define for the PCD. The list of parameters includes a description of each parameter.

Settings in pcd.Startup.template.properties have no affect on the PCD configuration.

The first time you start up the portal, the PCD configuration service checks whether the pcdStartUp.properties file is stored in the <pcd.home>/pcd.Startup.properties directory. If it does not exist, it is created by generating a copy of pcdStartup.template.properties.

PCD configuration parameters can also be defined as system properties. Settings that are defined as system properties always overwrite the settings in pcdStartUp.properties.

 

Setting Write-Protect Mode for the PCD 

UseYou can prevent data from being written to the Portal Content Directory (PCD) by activating write-protect mode. For example, you can activate write-protect mode when migrating data from an old portal system to a new one in order to prevent data from being written to the old system during this time.

The following components are affected by write-protect mode:

Component Effect

Portal Object editors are either not available at all or have limited functionality. For example, portal administrators cannot import or export packages using the Package Transport Editor. They also cannot create new objects, delete objects, or edit objects using the object editors. Personalization of the portal themes is not available. When the portal is in write-protect mode, error messages appear when you attempt to call functions that are not available.

Collaboration You cannot create new rooms, or edit or delete existing rooms.

User Management Engine

You cannot create portal roles, but you can create and change UME roles since they are not stored in the PCD. You cannot assign portal roles to actions, neither in the user management administration console nor in the Role Editor.

You do not set write-protect mode from the PCD configuration file PCDStartup.Properties; rather, you set it from within the service configuration of the Visual Administrator.

Procedure2. ...

       1.      Start the Visual Administrator.

       2.      Choose Global Configuration ® Server ® Services ® com.sap.portal.pcd.gl.

The properties of the service are displayed:

18.                             a.      Pcd.Pl.WriteProtectActivated defines whether or not write-protect mode is activated. By default it is set to false.

19.                             b.      Pcd.Pl.WriteProtectCause describes the reason that write-protect mode is activated. This information appears in the log files.

       3.      Activate write-protect mode by entering true as the value for Pcd.Pl.WriteProtectActivated.

       4.      Click Update and then click Save.

A confirmation dialog box opens.

       5.      To apply the changes to all cluster elements, click yes.

The Reset dialog box opens.

       6.      To restart the service, click yes.

       7.      To reset the default values, click the Reset Default Global Properties icon.

Write-protect mode can only be configured for the entire cluster. You should therefore perform the configuration in the Global Configuration tab of the Visual Administrator. Local server configurations are ignored.

It is not necessary to switch on write-protect mode to create an online backup. For more information about online backup, see SAP note 779708.

Checking Configuration Parameters and Reloading Configuration 

UseThe portal provides you with a user interface in the administration environment that contains the following functions:

        You can display the current values of PCD configuration file pcdStartUp.properties.

        You can load the configuration again. You do this when you change the configuration file.

Procedure1. ...

       1.      In the system administration role, choose System Administration ® Support. The Support Desk appears.

       2.      Select the area Portal Content Directory.

       3.      Click on PCD Configuration in the test and configuration tools. The next screen shows all the parameter values currently maintained for the PCD.

       4.      To reload the configuration, choose Reload.

Note that reloading using the administration UI only affects the current cluster node, but does not affect all the clusters.

 

Troubleshooting and Support Desk 

PurposeAs portal administrator, you can access various support tools that help you to with troubleshooting in the portal.

You can find these tools in the administrator role for system administration under System Administration ® Support. You can find the Support Desk in the detailed navigation.

 

Start troubleshooting in the portal at this location. If you cannot solve your problem with the provided tools, create a customer message.

FeaturesThe Support Desk is a collection of support pages for the main components of the portal. The first page contains a list of the main areas of the portal and links to the relevant support pages. There is a list of known problems and their solutions for each area. You can also perform automatic configuration checks to look for errors and inconsistencies in the portal.

 

 

Creating a Service Message 

PurposeThe Support Desk allows portal users to contact their internal support organization directly from their regular work areas and provides help desk employees with a fully integrated message handling system. An automatic data collector captures important system data, such as the portal release, support package level, and database version.

A direct connection to SAP enables help desk employees to forward an error message to the SAP Support Desk back office. When an SAP support engineer makes changes to the message status, for example solving a message, the changes are transferred automatically to the original message at your Support Desk.

PrerequisitesThere are several prerequisites for allowing users to create service messages from the portal. For example, you have to install and prepare an SAP Solution Manager backend system and connect it to SAP NetWeaver Portal. You also have to maintain the properties of the Request Support iView corresponding to your individual scenario.

For more information, see Setting up Support Desk Scenario.

Process FlowPortal users can contact the internal Support Desk from the portal by creating a service message using the Request Support iView.

This iView is not assigned to a role at shipment. You as an administrator can decide which users should use this scenario and how to navigate to this iView.

Initially the iView can be found by choosing System Administration ® Support ® Support Desk ® SAP Request Support ® RequestSupport.

Portal users create an error message by supplying a subject and description, selecting a component from the dropdown list, setting a priority, optionally adding file attachments and choosing Submit. When the message is created, the system automatically collects the relevant system data, such as the release, support package level, message number, and so on.

Setting up a Support Desk Scenario 

PrerequisitesAn SAP Solution Manager backend system is installed and customized.

See SAP Service Marketplace on service.sap.com/instguides ® SAP Solution Manager ® Installation Guides.

The SAP Solution Manager system is defined in the System Landscape.

See Running the System Landscape Wizard.

The plug-in is installed on the SAP Solution Manager system.

See SAP Notes 215609 and 177895.

Portal users have a valid user ID in the target SAP Solution Manager system. This ID can be defined by user mapping. The corresponding Solution Manager user must have authorization to open support notifications.

You do not need to implement one-to-one user mapping. It is also possible to map one user to a special user group.

ProcedureYou create and maintain the properties of the Request Support iView to suit your scenario:

Choose Content Administration ® Portal Content.

Right-click a folder and choose New from PAR ® iView to launch the iView Wizard.

In the Portal Archive Selection step, select com.sap.portal.epsolman and choose Next.

Select the EPSolman portal component, and choose Next.

Fill out the general iView properties and choose Next.

Choose Finish.

Select Open the object for editing.

In the Property Editor, choose the Show All property category.

Maintain the following properties:

1. R/3 Installation Number of the Solution Manager

This can also be the SAP NetWeaver Portal installation number. This number is provided by SAP.

1. Portal DBMS short name

2. Portal DBMS release

3. Valid R/3 connection in jcoDestinations.xml in the Portal System Landscape This is usually the system alias that you defined for the Solution Manager system in the system landscape.

4. Target R/3 Solution Manager version

Release of the Solution Manager system

5. System ID of the Portal (optional)Assign the Request Support iView to a role corresponding to your Support Desk scenario.

Optional: You can add an option to the page title bar in your runtime portal that enables portal users to access the Request Support iView:

20. Open the default framework page in the Page Editor.21. Select the Page Title Bar and click Properties.22. In the Property Editor, choose the Appearance – Tray property Category.23. In the Show ‘Report a Problem’ Option property, select Yes.

Optional: You can also replace the supplied iView with your own iView by setting the path in the ‘Report a Problem’ iView Path property.

 

Read SAP note 641707, containing the most recent information about the Request Support iView.

Administration of the Distributed Query Engine (DQE)  The Distributed Query Engine (DQE) is a NetWeaver ‘04 portal service that is capable of simultaneously processing queries to multiple systems. Content developers can write complex queries across different back-end systems, which the DQE can parse and pass to each single system. DQE then puts the results together into one result set.

The portal makes three administration tools available by which the administrator can effect control over certain aspects of DQEoperations.

Purpose

DQE Property Editor Configure properties affecting DQE performance

Session Manager View and control DQE sessions

Metadata Loader Preload system metadata to improve run time performance

See the following:

DQE Property Editor

DQE Session Manager

Metadata Loader

 

DQE Property Editor 

DefinitionA portal utility for configuring property values related to the performance of the Distributed Query Engine (DQE).

UseThe DQE service exposes methods to access and update essential properties through the administration tools. Eleven properties are exposed and configurable by means of the DQE Property Editor. These properties are shown in the table below.

The value type of all the properties is integer, except for Storage Directory and Log Level. For each property, the default value appears as initially configured within the DQE. In addition, in the property description table below, the minimum and maximum values, and the increment to use when changing the property values, are specified. There are no firm rules for the maximum and increment values for some properties; these have been specified with a “?” to denote that you can choose alternative values. The following is a list of the properties.

Property DescriptionDefault

[Min, Max, Increment]

Process Pool Maximum Threads

Maximum number of threads allowed to be pooled for processing at any given time

15

[1, 100?, 1]

Process Pool Thread Time To Live

Time-to-live for process pool thread, in milliseconds

120000[1000, 3600000?, 1000?]

Process Timeslice The period of time allowed for which a process for a single query is allowed to run uninterrupted, in milliseconds

2000

[100, 10000?, 100?]

Buffer Memory Available The amount of memory that buffer management should use, in megabytes

128

[1, 2048?, doubling]

Buffer Active Memory Threshold

The percentage of buffer management that serves as a threshold for active memory management

90

[1, 100, 1]

Buffer Management Interval

The maximum size of a batch sent between connector and query service. Should be even multiple of processor batch size

1000

[500, 3600000?, 500]

Connector Batch Size The maximum size of a batch sent between connector and query service. Should be even multiple of processor batch size

1000

[500, 10000, 500]

Processor Batch Size The maximum size of a batch sent internally within the query processor. Should be <= the connector batch size

500

[500, 10000, 500]

Storage Directory The location to store temporary buffers too large to fit in memory

../<path_to_storage_location>

Maximum Open Files The maximum number of open file descriptors that should be cached in the storage directory. Normally depends on OS settings for # open files per process

10

[1, 256, 1]

Log Level DQE logging level. See Logging section See “Choosing a Log Level” below

To access the DQEProperty Editor:

In the portal top-level navigation, choose System Administration ® Distributed Query Engine ® Configuration.

After changing property values, you can save them or restore them to the default values.

Modified properties become effective by restarting the J2EE Engine.

Choosing a Log LevelThe logging levels which can be set for the DQE server are described in the table below. In the DQE Property Editor, choose a log level name from the drop-down list.

Log Level

Log Level Name

Description

0 NONE No logging

1 CRITICAL Generally used to record an event or error that must be recorded (if any logging is used). If it is used to record an error, it usually means that the system encountered a critical error that affects the integrity, accuracy, reliability and/or capability of the system.

2 ERROR Error messages are generally used to record unexpected problems, or errors that are not critical in nature and from which the system can automatically recover.

3 WARNING Warning messages generally describe expected errors from which the system should recover. However, this level is used to record the fact that such an error or event did occur.

4 INFO This level of logging is the usually the normal level. All interesting periodic events should be logged at this level so someone looking through the log can see the amount and kind of processing happening in the system.

5 DETAIL Such messages are moderately detailed, and help to debug typical problems in the system. Generally, these messages are not so detailed that the big picture gets lost.

6 TRACE The most detailed logging level, used to trace system execution for difficult problems. At this level, logging may be so verbose that system performance may be affected.

 

 

DQE Session Manager 

Definition

A portal utility that displays sessions running on the Distributed Query Engine, as well as the specific queries running in these sessions, and permits the portal administrator to view the details of any specific session and, if needed, to terminate a session, or its constituent queries.

Use

The Session Manager can display all processes, whether current or inactive, which have been launched for processing to the DQE. The Session Manager allows the portal administrator to manage these sessions, insofar it enables to monitor all sessions, current and inactive, or active sessions only.

The administrator can see which users have launched DQE sessions.

The administrator can see how long a session has been running, when the session queries were launched, and when query processing began.

The administrator can terminate sessions if needed, for example, sessions running for a long time with no results returned.

To access the Session Manager:

In the portal top-level navigation, choose System Administration ® Distributed Query Engine ®

Session Manager.

Structure

The Session Manager iView is made up of two parts:

Sessions

The upper section, Sessions, displays the DQE sessions in tabular form, showing the user who launched the session and length of time for which the session has been running.

There is a checkbox above the table for showing active sessions only. Below the table are two buttons:

        Details opens an additional table, Query Details in the lower part of the iView.

        Terminate ends the processing of the selected session.

Query Details

The Query Details table, in the lower part of the Session Manager iView, shows the query of the selected session, including the following details

        Query string         Query submit time         Query processing start time

Below the table is a Terminate button for ending the processing of the selected query.

Metadata Loader 

DefinitionA utility that allows the portal administrator to preload object model or table metadata into a Distributed Query Engine cache. As well as the pre-caching of metadata, the DQE permits the canceling of the cache, or unloading of existing metadata of tables that are no longer needed, or the metadata of which has changed.

UsePreloading table metadata enhances performance during runtime in the productive environment. The ability to preload table metadata improves performance for accessing important tables, the metadata of which would be loaded on the fly by the DQE during runtime if it were not preloaded. Note that the on-the-fly upload of metadata occurs only the first time that a specific table is addressed.

The ability to remove (unload) from the DQE cache the metadata of tables that are not needed decreases load and eliminates storing in the DQE cache of unnecessary data.

To access the Metadata Loader:

In the portal top-level navigation, choose System Administration ® Distributed Query Engine ® Metadata Loader.

StructureThe tool is displays a two pane tree view: the left pane, labeled Available, showing the available portal systems, which expand to show the objects in each system; the right pane, labeled Loaded, showing the objects already loaded into the DQEcache.

Add and Remove buttons enable the administrator to load and unload specific tables into and out of the DQE cache. The Metadata Loader enables the transfer of an entire system by selecting it and transferring it to the other pane. In the expanded system trees multi-select is enabled, using the Ctrl and Shift keys to load or unload several objects at once.

After transferring tables between the two panes, choose Save to apply the changes. Use the Refresh button to see possible changes in the available systems list.

SearchWhere systems have a large number of objects, the search mechanism above the preload panes enables finding by system alias object, the names of which are known to you.

Additional InformationImportant information about refreshing visible data and troubleshooting, is provided in the UI of the Metadata Loader.

 

 

Workload Distribution 

UseWith workload distribution you can optimize the stability, availability and load of your portal. It is a mechanism for assigning specific content-driven workload to sub-topologies of the J2EE Engine cluster setups – the zones. It is based on the handling of external requests. A zone consists of one or more J2EE instances. An instance consists of a J2EE Engine Dispatcher and one or more application servers.

You isolate certain parts of the portal that can cause problems. By assigning a topic to a zone, the corresponding code can be entirely isolated from other code parts with respect to session management, server-side eventing, etc. You define zones (one or more server nodes) in your J2EE cluster environment. You then assign these zones portal content (J2EE applications, portal applications, roles, worksets, pages or iViews) from the portal system administration.

No zones are set up by default – the portal content executes on all cluster nodes. You should set up workload distribution if certain parts of the portal endanger the stability or load of the portal. We recommend this especially for custom developments.

The content administrator will normally assign portal content to zones.

FeaturesYou can assign portal content to zones according to certain criteria. The following groups (classes) are available:

Portal Content Assignment

Portal Component A certain portal component is assigned.

Portal Application All elements of a certain portal application, including the portal components it contains, are assigned.

Context The object ID of a folder structure in the Portal Catalog (PCD path) is assigned. All the elements of a folder structure are thus mapped to a zone.

Topic All iViews whose property Work Distribution Topic has a certain value are assigned. The property is maintained in the Property Editor.

At portal runtime, the distribution mechanism identifies the zone specification from the incoming request. The SAP Web Dispatcher handles the incoming requests. When it accepts a connection, it sends the request to the assigned server node and distributes the load across the servers and zones in order to insure equal distribution. The following rule is valid when determining the zone:

1. ...

       1.      Portal Component

       2.      Portal Application

       3.      Context

       4.      Topic

The portal component criterium is first checked. If there is no valid assignment, the remaining criteria are checked in the listed order.

If no assignment is found, the portal content is executed on a random cluster.

If the content is not allowed for a zone, an error message is displayed in the portal. This message also appears if portal content is not correctly assigned to zones (e.g. in case of inconsistencies).

There is an inconsistency if Zone za is assigned to a page, but this page contains an iView that is assigned to Zone zb with the property Work Distribution Topic.

By default the error message iView DedicationAlerter of portal component sap.com.portal.supportability.isolde is called. You can display a different iView (e.g. with your own error message text).

For detailed information about the configuration read Defining Workload Distribution.

Workload distribution is only possible for URL isolated iViews. Embedded iViews are not supported at the moment. For more information see Isolation Method of iViews.

Defining Workload Distribution 

PurposeUsing workload distribution, you can optimize the stability, availability, and load of the portal. It is a mechanism for assigning specific content-driven workload to sub-topologies of the J2EE Engine cluster setups – the zones.

Process FlowWorkload Distribution scenarios are defined in the following steps:

1. ...

       1.      Configuring the SAP Web Dispatcher

       2.      Activating Workload Distribution

       3.      Defining the Path to the Error Message iView

       4.      Assigning Portal Content to Zones

Configuring the SAP Web Dispatcher 

UseThe following figure shows how to include the SAP Web Dispatcher as load balancer in the Workload Distribution scenario:

For more information about the SAP Web Dispatcher concept, see the SAP Web Dispatcher documentation.

Procedure1. ...

       1.      Configure the Web Dispatcher profile and adjust files icrgroups.txt and urlinfo.txt for the zone definition (see the example files at the end of this section).

icrgroups.txt

File icrgroups.txt consists of two sections, separated by an empty line.

icrgroups.txt (for n zones)version 1.0 8 J2EE<ClusterID_J2EEDispatcher_1>8J2EE<ClusterID_J2EEDispatcher_2>8…J2EE<ClusterID_J2EEDispatcher_n>88 (empty row)<zonealias_1>:J2EE<J2EEDispatcherClusterID_1>8<zonealias_2>:J2EE<J2EEDispatcherClusterID_2>8…(empty row)

Enter J2EE plus the J2EE dispatcher cluster ID row by row as instance name in the first section of this file. The J2EE dispatcher registers itself on the message server with the cluster ID when the J2EE Engine is installed. You can, for example, look for the corresponding cluster ID using the configuration tools.

Make sure that you use the correct notation.

In the second section of the file, you define a zone alias and assign one or more instances to this zone. You can assign multiple instances to a zone by inserting a comma as separator between the instances, for example:

<zonealias_2>:J2EE<J2EEDispatcherClusterID_2>,J2EE<J2EEDispatcherClusterID_3>,...

You must close file icrgroups.txt with Return, as specified in the syntax. Do not add any additional empty lines or characters.

urlinfo.txtFile urlinfo.txt consists of 1 section without empty lines.

urlinfo.txt (for n zones)version 1.0 8 PREFIX=/irj~<zonealias_1>/&GROUP=<zonealias_1>&CASE=&VHOST=*.*;&STACK=J2EE8PREFIX=/irj~<zonealias_2>/&GROUP=<zonealias_2>&CASE=&VHOST=*.*;&STACK=J2EE8…PREFIX=/irj~<zonealias_n>/&GROUP=<zonealias_n>&CASE=&VHOST=*.*;&STACK=J2EE8(empty row)

You must close file urlinfo.txt with Return, as specified in the syntax. Do not add any additional empty lines or characters.

URLhttp://host:port/<prefix>/…/…

       2.      (Optional) If files icrgroups.txt and urlinfo.txt are contained in a directory other than the SAP Web Dispatcher, specify the complete path in the Web Dispatcher profile.

See also examples for UNIX™ and Windows™.

       3.      Check if the zone separator is entered for each server node in the J2EE cluster.

The zone separator is a special symbol that is used in the URL to separate the context nodes of the application from the zone (logon group).

irj~zawhere ~ is the zone separator

For more information, see Configuring the Zone Separator.

Example

icrgroups.txtversion 1.0 8 J2EE84688008J2EE846990088 za:J2EE84688008za:J2EE84688008(empty row)

urlinfo.txtversion 1.0 8 PREFIX=/irj~za/&GROUP=za&CASE=&VHOST=*.*;&STACK=J2EE8PREFIX=/irj~zb/&GROUP=zb&CASE=&VHOST=*.*;&STACK=J2EE8

Web dispatcher profile# SAPSYSTEM must be unique number on physical host

SAPSYSTEM = 66

# use static description files for logon groups: group info

wdisp/group_info_location = file://icrgroups.txt

# use static description files for # logon groups: url prefixes

wdisp/url_map_location = file://urlinfo.txt

# trace level

rdisp/TRACE = 1

# SAP WebDisp listen ports

icm/server_port_0 = PROT=HTTP,PORT=8855,TIMEOUT=120

# Resources

icm/min_threads = 10icm/max_threads = 50

icm/max_conn = 500icm/req_queue_len = 500

# number of backend connections

wdisp/HTTP/max_pooled_con = 500wdisp/HTTPS/max_pooled_con = 500

UNIX pathfile:///usr/sap/<SID>/sapwebdisp/icrgroups.txt

Windows pathwdisp/server_info_location = file://C:\Program Files\SAP\SAPWebDisp\icrgroups.txt

Activating Workload Distribution 

ProcedureIn service Redirector set property distribution.enabled to true.

1. ...

       1.      Choose System Administration ® System Configuration ® Service Configuration.

       2.      Choose Portal Catalog ® Browse.

       3.      Navigate to the Redirector portal service and change to edit mode.

The Redirector service can be found in subfolder Services of application com.sap.portal.supportability.isolde.

       4.      Set property distribution.enabled to true and choose Save.

       5.      Perform a Restart of the Portal Service.

Defining the Path to the Error Message iView 

UseBy default the iView DedicationAlerter of portal component sap.com.portal.supportability.isolde is called. You can display a different iView (e.g. with your own error message text).

Procedure1. ...

       1.      Choose System Administration ® Support ® Support-Desk ® Portal Runtime ® Workload Distribution Configuration.

       2.      Click on folder Workload Distribution Configuration.

       3.      Go to edit mode for service DistributionConfiguration.

       4.      In the field Default Alert iView Name enter the desired iView path and click on Apply.

Do not change the properties HTTP Methods and Use Absolute Path.

Assigning Portal Content to Zones 

UseYou can assign portal content to zones using the classes portal component, portal application, context or topic.

Procedure2. ...

       1.      Choose System Administration ® Support ® Support-Desk ® Portal Runtime ® Workload Distribution Configuration.

       2.      Click on folder Content to Zone Mapping.

       3.      Select the required class.

24.                             a.      Create a unique ID for the assignment.25.                             b.      Define content for this assignment using the name field.

ContextObject ID of a folder structure in the Portal Catalog.Portal ComponentName of the portal component. A path need not be defined.Portal ApplicationName of the portal application (*.PAR). A path need not be defined.TopicValue of iView property or page property Work Distribution Topic.

26.                             c.      With the zone alias, define the zone to which the topics are assigned. Use the zone alias that you defined in icrgroups.txt. For more information see Configuring the SAP Web Dispatcher.

       4.      Repeat Step 4c until you have assigned your portal content.

ExampleOne example of assigning pages and iViews to zones is to assign property Work Distribution Topic the value isolate_za in the Property Editor.