In the BSP programming model, the session_id can be transferred either as a cookie or as a URI parameter, where by default it is transferred as a cookie. The URI parameter in the URL is the statement in brackets after the namespace specification, such as (bD1kZSZjPTAwMA==).

When BSP applications are integrated in the Portal, the session_id is not created as a cookie, as is the usual case, it must be generated in the URL instead, because otherwise it would not be possible to differentiate between the BSP sessions. This is why the existing BSP Session Handling was enhanced with a variant without cookies.

• The initial call is made using the additional parameter:
  sap-syscmd=nocookie

• With a stateful application, the session_id in the URL is coded within the parenthetical expression.

• Method runtime->get_url( ) is ready for the application to specify a target URL, for example, such as in the case of a form.

• The <htmlb:form> element executes this coding independently if no cookies are used.

Interface IF_BSP_RUNTIME was enhanced with the following additional methods:

• if_bsp_runtime->get_url ( relative_url type string optional )
  determines a target URL and enclodes the session_id if necessary

• if_bsp_runtime->has_sid_in_url( )
  returns 'X' if the session_id in the URL is encoded (this means that parameter sap-syscmd=nocookie was set)

The interface IF_BSP_NAVIGATION was also enhanced:
Methods if_bsp_navigation->goto_page( )or if_bsp_navigation->goto_page_cs( ) of the navigation object were enhanced so that the target page was adjusted.