Query reg the ( Stateful/Stateless ) BSP pages

[Former Member]

Hi Group,

I have a few queries in BSPs as under:

1)

while defining the BSPs, in the Properties, we will define the BSP page as may be "Until the Page change or Request or Session ".... I want to know the relevance of each of these settings.....

2)

I have ( say 2 BSP applications - BSP1 and BSP2 ). can there be a situation wherein the BSP1 will be accessing some componenets of the other application BSP2 ? if so, how can it be achieved and in what circumstances this situtation arises?

Thanks for your help in advance.

Regards,

Vishnu.

[RenaldWittwer · Accepted solution]

Hi,

the difference between statefull and stateless is described very good in the documentation

http://help.sap.com/saphelp_nw04/helpdata/en/cc/d6eefc28f711d5991f00508b6b8b11/frameset.htm

If you want to access data from different BSP, have a look at server side cookies

http://help.sap.com/saphelp_nw04/helpdata/en/2a/31b97b35a111d5992100508b6b8b11/frameset.htm

Best regards

Renald

[former_member184111]

Hi Vishnu,

Few lines from SAP help.

The lifetime parameter specifies the length of time during which the instance of the page or controller is retained.

The lifetime is relevant only if the BSP application is being processed statefully.

With stateful BSPs, there can be three different variants of lifetime:

Up to the page change (lifetime_page)
The page is destroyed if a different page is used.

For the duration of the request (lifetime_request)
The page is destroyed after each individual request, that is, is only available for the duration of each request.

For the duration of the session (lifetime_session)
The page is destroyed at the end of the session.

One practical example is .

We have a BSP application that is called from another ITS application using a link.There are few radiobuttons and DDLBs in the BSP page.We used to get old values for UI elements(the RB selected by user in previous session or value selected by user in DDLB in previous session),everytime the link was clicked.

We set the page lifetime to session and added sap-sessioncmd=open(this URl parameter is used to open a new session everytime the link is clicked), so that a fresh session is started everytime the link is clicked .This solved the problem.

Regarding your second query , as suggested by Renald you can use server cookies or Application class to share data objects between different applications.

Hope it helps,

Anubhav