Show TOC

Creating BSP ApplicationsLocate this document in the navigation structure

Use

You can create BSP applications only with the Web Application Builder but not with external Web development environments.

Prerequisites

If you wish to create the BSP application in another namespace that differs from the standard namespace, you may only use the values provided by the system as namespace identifiers.

Procedure
Note

Like all Repository objects, a BSP application can be created by copying it. Note that the corresponding MIMEs are not copied to the target object when you copy BSP applications. For each new BSP application, the system creates an identically named directory in the MIME Repository, but it is empty.

To create a new BSP application:

  1. Open the Object Navigator (SE80).

  2. Choose the BSP Application category from the object list selection and enter the name of the application you want to create.

    If you wish to assign the new BSP application to a valid namespace XYZ that differs from the standard namespace, you must place the namespace as a prefix in front of the actual name of the BSP application. The complete name must then be written in this form: /XYZ/BSPApplication.

  3. Click Display or choose ENTER to confirm your entry.

    The system checks to see whether or not a BSP application with that name already exists in the SAP System. If it does not exist already, the Create Object dialog box appears.

  4. Choose Yes to create the BSP application.

    The dialog box Web Application Builder: Create BSP Application is displayed.

  5. Enter a meaningful short description.

  6. Choose Create.

    The system then displays the Create Object Catalog Entry dialog box.

  7. Assign a package to the service.

    The system displays the BSP application you have created in the object list tree structure.

Result

The BSP application has been created in the Repository as a development object.

Caution

With the new BSP application, a service node with the same name is automatically generated in the HTTP service maintenance (transaction SICF). As a rule, no such entry exists for BSP applications that were created in earlier releases. In such cases, you must create this node manually in the service maintenance transaction. You call up the corresponding display through the menu function Start of the navigation path Goto Next navigation step HTTP Service Maintenance End of the navigation path. Execute the steps as they are described in the section Creating an ICF Service.

Afterwards, you can assign further attributes for the BSP applications at this point:

Property

Description

Initial BSP

Here you enter the name of a page that is to be used to start the BSP application. This entry is important whenever you test the BSP application from within the workbench.

Application class

If you enter the name of an ABAP class as the application class in this field, then this class can be directly referenced in the BSP application using the predefined object application. You do not need to create an instance of the application class and you can directly access its components (methods, attributes, and events) from any BSP page.

An application class is used to transfer the business logic to a global class that, in turn, is used to access business data using BAPI calls, for example.

In general an application class can be assigned to multiple BSP applications. (All of thses applications use the same business logic).

Note that the application class must exist in the same system and cannot be addressed through RFC.

Stateful

Activate this checkbox whenever the BSP application should be implemented as stateful. For an explanation of this, refer to the section Stateful BSP Applications.

XSRF Protection

You have the following option to protect a BSP application from XSRF attacks. Note the following points:

  • The first page of a BSP application that is called must be flagged as the Start BSP (tab page Properties of this BSP page).

  • If a BSP application consists of multiple BSP application objects, then it is necessary to activate the XSRF protection for each individual application object separately