Show TOC

Creating BSP Application iViewsLocate this document in the navigation structure

Use

You can integrate SAP Business Server Page Applications as an iView with no difficulty by selecting the SAP BSP template in the iView Wizard. The template is automatically installed with SAP Enterprise Portal.

Prerequisites
  • You selected the SAP BSP iView template in step 1 of the iView Wizard and followed the instructions given by the Wizard. For more information see Launching the iView Wizard and General Information .

  • A system configured with the Web Application Server (Web AS)

    The system must also have a valid alias, which is entered in the System property of the iVIew.

    More information: System Landscape

Process

You must maintain the following properties in order to display a BSP Application in the portal as an iView:

Mandatory fields:

  • System

  • Customer Namespace

  • Application Namespace

  • Business Server Page (BSP) Application

  • Start Page

Optional fields:

  • ApplicationParameter

  • Business Server Page (BSP) Alias

  • BSP Definition Type

  • Customer Exits for ParameterProvider'

  • Do not forward these parameters to BSP

  • HTTP Request Method

  • Logon Language

  • Parameters Forwarded to BSP

  • PortalSessionID

  • Stylesheet

  • Supply Portal Stylesheet

  • Use URL-Based Session Tracking

You can find general information about maintaining iView properties in Editing Object Properties and Editing iView Properties .

System

Enter the system alias for the desired SAP System.

The system alias refers to a SAP system that was defined in the portal.

More information: Creating Systems and Defining the System Alias

If you creating a new system, see SAP Note 761917 Information published on SAP site.

CustomerNamespace

Enter the parameter for the customer namespace here.

This parameter is taken from the back-end system.

Application Namespace

Enter the parameter for the namespace here (for example, SAP).

This parameter is taken from the back-end system.

Business Server Page (BSP) Application

Enter the application name here.

This parameter is taken from the back-end system.

Start Page

Enter the name of the page application here.

This parameter is taken from the back-end system.

Application Parameters

You can enter parameter values for certain screen fields for displaying BSP applications here.

This field is optional.

The parameter values are specified with the following syntax:

<Screen_field1>=<Parameter1>

&<Screen_field1>=<Parameter2>

&<...>=<...>,...

Business Server Page (BSP) Alias

This field is relevant only if the BSP Definition Type is set to Alias .

In this field you can enter the entire path of the application you want to launch. The format of the path should contain the application itself but not the start page. For an example, an alias could look like the following:

Sap/bc/bsp/sap/app_name , where Sap represents customer namespace.

Note

If you enter a value for this field, you do not need to enter a value for the Customer Namespace , Application Namespace , and Business server page (BSP) Application fields.

BSP Definition Type

In this field choose whether to launch the iView using an alias or the application.

If you choose Alias , you must enter a value for the Business Server Page (BSP) Alias property.

Customer Exits for 'ParameterProvider'

A customer exit is a way to extend the functionality of the ApplicationIntegration service by creating a custom code.

In this field you can enter the name of the field for the customer exit:

entry path="/com.sap.portal.appintegrator/customer_exits/parameter_provider/<field_name>

Parameters Forwarded to BSP

In this field you can enter the parameter names that you want to forward to the BSP.

The parameters are transferred to the ApplicationIntegration service in the request as part of the query string.

If you want to forward all the parameters, you can enter the value asterisk (*).

Do not forward these parameters to BSP

This field is only relevant if the value of the property "Parameters Forwarded to BSP" is asterisk (*).

In this field you can enter the parameters that you want to exclude from the BSP.

HTTP Request Method

This property defines which HTTP request method (GET or POST) will be used. The default value is GET.

If the property value is empty, the portal will use HTTP GET unless the URL exceeds 1024 characters or contains user credentials, in which case HTTP POST will be used.

Note

BSP supports request method HTTP POST only in newer Web AS versions and patches. Prior to SAP NetWeaver 7.0 SPS 07, the portal only supported HTTP GET to connect to BSP systems.

More information: SAP note 904249 Information published on SAP site

If you do not set either GET or POST, the portal computes the request method automatically.

Recommendation

The use of SSL and HTTP POST is recommended for communication between systems.

Logon Language

In this field you enter the language in which the transaction should be displayed.

The possible values are the language codes according to ISO 639. This field is optional. If you do not make an entry in this field, the portal language is used.

PortalSessionID

By defining values in this property, you determine if the session of the back-end application is administrated by the portal or by the back end. If the field is empty, the default behavior is that the back end administrates the session.

(for example, <IView.ID><User.UserID>) (for example, <IView.ID><User.UserID> )

Stylesheet

In this field you can enter a BSP-specific stylesheet (for example, 'controls' or 'ur'). If left empty, the BSP default stylesheet is used.

Supply Portal Stylesheet

In this field you can define whether or not to hand over the portal stylesheet to the BSP application.

Use URL-Based Session Tracking

This property can get two values, true or false .

If set to true , the BSP application is started with the parameter sap-syscmd=nocookie and the BSP session ID is stored in the URL.

If set to ' false ', the parameter sap-syscmd is omitted and the BSP session ID is stored in a cookie.

Recommendation

Do not change this property to ' false ' without being fully aware of the resulting effects.