GZIP— The use of compression during HTTP data transfer does make a big difference in the transfer volume on the network, and the additional cost of both server and client CPU overhead and latency. Specifically on slow/expensive networks, GZIP compression is a feature that can be activated. By default, BSP runtime does not compress any pages. The developer must himself decide on this option. This section describes all known pitfalls on the topic of GZIP.
BSP Documentation at Docupedia— Docupedia is a project that offers the official SAP NetWeaver documentation in a wiki format, which makes it really easy to search, edit and post your feedback.
PDF— PDF documents are one of the more popular type documents imbedded into BSP pages, especially for print output of business documents (ex: invoices, etc). There are a number of pitfalls when using PDF documents in BSP, see these references.
OTR— The Online Text Repository (OTR) is used extensively within BSP to handle language dependent texts.
Security— Security aspects is mostly dominated by the question how single-sign on works, activation of ICF nodes and how to prevent cross-side scripting attacks. This section collects all relevant links to the different topics.
Problem Handling— A lot of the problem handling within the SAP troubleticket system is influenced very much by the information that is supplied with the initial problem. This helps to ensure that all relevant information is available, and not be required to first quiry this through additional round-trips.
Customization— Look at aspects around customizing the behaviour of BSP applications
GEN_BRANCHOFFSET_LIMIT_REACHED— From time to time the error message GEN_BRANCHOFFSET_LIMIT_REACHED pops up. It is a very complex problem right from the heart of the ABAP VM. Let us look quickly at why it happens and some ideas to work around the problem. No, there is no patch for this problem.
Session Management in Portal— Once a BSP application is closed, it should not be listed in SM04, and no locks should be held in SM12. The rest of this page describes different reasons that cause this problems, and troubleshooting steps to follow to see if the sprecific reason is relevant.
Exceptions and Errors— This guide describes quickly how to get from a specific exception/error observed to relevant information that can help resolve the problem.
Debugging Problems— Sometimes, to the frustration of each developer, the debugger just refuses to start. This guide discusses typical problems that can cause this failure.
Cookie Problems— In the BSP environment a number of cookies can be used for different aspects. The two cookies sap-contextid and MYSAPSSO2 are often used and very important. This guide describes steps to troubleshoot cookie failure.
Handling Binary Data— This troubleshooting guide contains many different aspects around the handling of file up and downloads. Especially GZIP aspects, and also the different behaviours of the file upload mechanism of the browser.
Logon— There are many ways to authenticate a user against a WebAS system. This guide addresses common problems observed in this area.
Differences Between DESIGN2002 and DESIGN2003— Initially BSP shipped the HTMLB rendering library with the CLASSIC design (now deprecated). Later a DESIGN2002 was added (also deprecated), which was a hand-written HTML rendering engine. In the last years, this was replaced with DESIGN2003, that is based on SAP's new common HTML rendering engine that is used across all SAP products. Unfortunately, it is not always possible to get a 100% perfect match between the designs, due to the completely different architecture and implementations in use. Here the differences are documented.
Naming Requirements for Hostnames and Domains— From time to time we find that either authentication via Single Sign On or stateful application fail. This is due to the fact that the host and/or domain names are not standard conform. BSP attempts to set a session cookie in the browser to store the specific information, that is then silently discarded by the browser, as the location information in the cookie (based on host and domain names) are not valid. On the next HTTP roundtrip, this information will not be available, and the there will be either a request for new authentication or a new session will be opened (or both).
Fully Qualified Domain Name (FQDN)— Often, if a short form of an URL is used in the browser to address a specific host, for example http:// myHost/URL or an IP adddress, for example http:// 188.8.131.52/URL, this results in a short dump requesting that a Fully Qualified Domain Name (FQDN) be used. Here are described background information, problems and how to indentify these.
Using Proxies— This troubleshooting guide describes all the different problems observed with the use of proxies.