Skip to Content

How to Memorize Between Different Apps Within the Portal?

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.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    May 12, 2004 at 06:22 AM

    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

    Add comment
    10|10000 characters needed characters exceeded

    • 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