Entering content frame

Object documentation SYSTEM_PUBLIC Locate the document in its SAP Library structure

Definition

BSP application SYSTEM_PUBLIC is a sample application for BSP application developers who want to adapt the individual fields of their logon screen, which is switched using the redirect to SYSTEM, user-specific to their BSP application.

Caution

Under no circumstances whatsoever should you make changes to BSP applications SYSTEMor SYSTEM_PUBLIC!

Use

you are using SYSTEM_PUBLIC to construct the URL that you enter as the redirect URL in Transaction SICFfor your node in the service tree.

Prerequisites

...

       1.      Close all browser windows so that the browser can save no authentication information whatsoever.

       2.      Before you start SYSTEM_PUBLIC, ensure that you are not logged on to PSE management (Single Sign On).

If you are already logged on, then log off PSE management, by clicking on the appropriate symbol on your desktop and choosing Log off.
This graphic is explained in the accompanying text

       3.      In the Object Navigator (Transaction SE80) enter SYSTEM_PUBLIC as the BSP application and choose Display.

       4.      Position the cursor on page default.htm of SYSTEM_PUBLIC and choose function key F8 (Test/Execute).

       5.      The browser logon screen is displayed, such as:
This graphic is explained in the accompanying text

Choose Cancel.

Caution

You must not log on here, so that the browser does not store your basic authentication.

       6.      You branch to a browser window with an address, such as:

This graphic is explained in the accompanying text

       7.      In the URL, replace bc with public.

This graphic is explained in the accompanying text

SYSTEM_PUBLIC is now displayed.

Note

BSP application SYSTEM_PUBLIC runs under the general display user SAPSYS.
This has the advantage that the browser has no authentication information and that each initial request for a private BSP application results in an authentication process. If BSP application SYSTEM is used, it is then started.

Structure

SYSTEM_PUBLIC looks as follows:

This graphic is explained in the accompanying text

 

From this interface you can try the different design options for a logon screen. You can hide and display individual fields, or assign them with default values. The aim is to construct a URL which you can then save in SICF with the redirect URL.

Parameters on the logon screen

Parameters

Example

Meaning

BspApplication

/sap/bc/bsp/sap/test01/default.htm

Name of your BSP application.
Enter the complete URL here (from the root node /).

BspHandlerClass

-

Internal class that is not usually used.
You can overwrite this class to make enhancements.

BspPrivacyStatement

../<public BSP-App>/<page name.htm>
See below

Page with copyright information.

BspTermsOfUse

../<public BSP-App>/<page name.htm>
See below

Page with general terms of use.

BspForgotPass

../<public BSP-App>/<page name.htm>
See below

Page with information on what should be done if users forget their password. Users can have a new password generated here.

BspPasswordHint

../<public BSP-App>/<page name.htm>
See below

Page with indirect information on passwords. If a user has forgotten his or her password, he or she can have a hint for the correct password sent.

BspPasswordViaEmail

../<public BSP-App>/<page name.htm>
See below

Page with information about the option of having a password sent by e-mail.

BspSignUpHere

../<public BSP-App>/<page name.htm>
See below

Page with the option of registering for a specific SAP Web AS System.

Registration always refers to a SAP Web AS System as a whole. As soon as authentication information is available, users can see all available BSP applications.

BspClient

BspClient=100

BspClientVisible=X

Client and client visibility.
The client must always be specified; it can also be hidden on the logon screen.

If you do not want to display the client, then write:
…BspClient=100
for example, so that client 100 is saved as an invisible field.

Note

To override the hard-coded client, use bspClient=<%=SYMANDT%> in Transaction SICF.
This is available if bspClient=100 is entered in Transaction SICF, although the production system should run in client 200.

BspLanguage

 

BspLanguage=EN

BspLanguageVisible=X

Language and language visibility setting.

If you do not want to display the language, then write:
…BspLanguage=DE
for example, so that the language German is saved as an invisible field.

BspSysIdVisible

 

BspSysIdVisible=X

System ID visibility. The system ID is the name of the SAP Web AS System.

BspAccessibility

BspAccessibilityCheckboxVisible

BspAccessibility=X

BspAccessibilityVisible=X

 

 

Specify the accessibility and visibility of a checkbox.

This option sets a flag in the BSP runtime, which can be used by BSP applications to output additional information in the HTML output stream, so that screen reader programs can better present the visual information on the screen.
BSP extension HTMLB uses this flag to change its rendering behavior.

BspChangePassword

BspChangePasswordVisible=X

 

Data for changing the password.

BspDontShowHttpsWarning

BspDontShowHttpsWarning=

Suppresses the warning created if there is no HTTP available.

Note

The warning is issued in the default setting, because then passwords cannot be transferred securely (encrypted) over the Internet.

BspDontForceHttps

BspDontForceHttps=

Prevents the use of HTTPS.

Note

This parameter is available as of SAP Web AS 6.20 SP 28.

We recommend you use this together with BspDontShowHttpsWarning.

BspUserLongNames

BspUserLongNames=

Specifies long user names.
This function is deactivated by default.
Logon can occur using either short or long user names and the logon can be attempted only once. You must therefore define which format should be used.

BspDumpFields

BspDumpFields=

Additional information which is listed under the SYSTEM logon screen and which is used for testing and debugging.

Note

Always switch these dump fields off before you generate your URL.

BspSAPGUILayout

BspSAPGUILayout=X

Place the logon dialog in the top left corner of the browser.

Caution

With parameters BspPrivacyStatement, BspTermsOfUse, BspForgotPass, BspPasswordHint, BspPasswordViaEmail and BspSignUpHere, always enter the relative or absolute path for the page that you want to jump to.
Ensure that it should be a page that is located in an active application (PUBLIC), which can also be reached using an anonymous display user. This page must not be located in the BSP application entered above, which uses SYSTEM.

Note that SAP does not provide the pages specified above with functionality for creating new users or resetting a password, for example. Whilst these pages are available in SYSTEM_PRIVATE, they are only empty shells for the type of services that are usually provided as Internet applications. Each application must decide which services it wants to provide behind these empty exit URLs, or if it wants to use them at all.

You can use pushbutton execute login to display how the logon screen will appear after you have made your modifications and to determine the correct URL for SICF.

Example

Sample URL (broken up to make it legible) and the logon screen

/sap/public/bsp/sap/system/login.htm?sap-url=<%=PATHTRANS%>
BspHandlerClass=&
BspPrivacyStatement=&
BspTermsOfUse=../system_public/termsofuse.htm&
BspForgotPass=../system_public/forgotpassword.htm&
BspPasswordHint=&
BspPasswordViaEmail=../system_public/passwordviaemail.htm&
BspSignUpHere=&
BspClient=000&
BspClientVisible=X&
BspLanguage=EN&
BspLanguageVisible=X&
BspSysIdVisible=X

This graphic is explained in the accompanying text



 

Leaving content frame