cancel
Showing results for 
Search instead for 
Did you mean: 

How to Memorize Between Different Apps Within the Portal?

detlev_beutner
Active Contributor
0 Kudos

Hi there,

imagin an application which consists of different sub-applications, S1, S2, S3 (at the moment, these are defined as applications within one webdynpro project). Each of these apps starts with a wizard, asking for the name of user-A and user-B.

This application will run within EP; the sub-apps will be menu entries within the detailed navigation.

A user calls S1, typing in data for user-A and user-B, goes on within the wizard and then after finishing (or maybe also before) changes to S2 or S3. Now it is quite normal that he will again use the same user-A and user-B - so these now should be the default values (the same holds if he starts with S2 and then goes to S3 or S1, so in general the last values typed in by the user within one of these sub-apps should be used as default values).

Any idea? Is there any predefined way to achieve this?

Thanks in advance

Detlev

PS: For long term use of the application, it would be possible to store these values within a DB, which is used anyhow. So the user would have default values even days after he used the app the last time. Nevertheless, I ask myself if there is also a quick way to achieve this behaviour for session-lifecycle.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Detlev,

wouldn't it be possible to use portal eventing for this? Application A subscribes to an event fired by S1..S3, transporting the default values in a concatenated string parameter and promoting them to application S1..S3 on restart. This assumes, that A is responsible for launching S1..S3.

Best regards

Stefan

detlev_beutner
Active Contributor
0 Kudos

Hi Stefan,

the question is - who the f... is application A?!

I have got a webdynpro project, where the applications (I call them sub-apps, because all them together are the whole application, but they run as closed components) S1... are defined. An application is called via a specific URL; so I have different webdynpro iViews, for example within a workset, so that each (sub)application is represented as one menu item in the detailed navigation.

So I cannot realize where to put app A?!

Thanks in advance

Detlev

Former Member
0 Kudos

Hi Detlev,

it might be application A(lice) This was a classical misunderstanding.

Regards

Stefan

detlev_beutner
Active Contributor
0 Kudos

Hi Stefan,

nevertheless, any idea now that you got the situation?

Best regards,

Detlev

Former Member
0 Kudos

Hi Detlev,

not really, since i'm not a portal specialist (yet). I assume, that the WD apps are restarted from the beginning each time you select the specific menu item? So, if the portal framework doesn't provide such a non-persistent storage for, let's call it "form contents", the only solution might be using the DB.

Best regards,

Stefan

htammen
Active Contributor
0 Kudos

Hi Detlev,

have a look at the following class. You should get acces to the portal session via the IPortalComponentRequest to store and retrieve your data there.

public class WDWebContextAdapter

extends java.lang.Object

This class allows the access to the origin request. If Web Dynpro is used within the SAP Portal Runtime, the Web Dynpro application developer may use Portal services. For that, the origin request object is often needed to use a lot of the existing Portal services. In the Portal case, the origin request would be a IPortalComponentRequest object.

Regards

Helmut