Keep same JCo Session when navigating away an re-entering WebDynpro Java ap

[Former Member]

We implemented the SAP CRM 7.0 ICWebClient - a BSP-based call center web application - and went live with one of our sites last month.

In our CRM 7.0 ICWebClient application, we integrated a WebDynpro Java application that does RFC calls to an SAP ERP system. The way we chose to integrate the WebDynpro Java application into the ICWebClient application was via the so-called transaction launcher (very common in ICWebClient - it can launch any Web Application via configurable but only static urls).

Our call center agents perform a sequence of steps every couple of minutes which is technically launching different web applications in the so-called workarea (comparable to an HTML-iframe) of the ICWebClient.

One of the web applications that is launched is this WebDynpro Java application. Functionally everything is working fine, but the performance of the RFC calls from the WebDynpro Java application to the ERP is slow. We believe the reason for this is, that whenever we navigate away from the

WebDynpro Java application and then re-entering at some point of time, we have a new RFC connection to ERP and all caching that is done on the ERP side (mainly by standard function modules) is lost.

So we look for a way to keep a WebDynpro Java session and especially the JCo session alive as long as our internet explorers are not closed or an explicit logout is done, although we sometimes navigate away from the WebDynpro Java application. We have few users (40) and it is a pure intranet scenario.

[siarhei_pisarenka3]

Hi

It's hard to advise anything here without clear performance analysis. Maybe try to check the following:

1. Check that WebDynpro JCo destinations of the App is pooled. And check also the pool capacity of the destinations. You can do this in WebDynpro Console. Maybe the pool is too low and need to be extended.

2. WebDynpro application can have special 'sleeping' state. It was designed especially for your case I think. When you navigate away of the WD App it can get Suspended state. And when you back to the App it'll Resume again.

Maybe the mode will help you. Read Suspend and Resume Plug topic. Here is some info from it:

"...used to suspend a running Web Dynpro application (when the suspend plug is fired) in order to jump to an external Web application and to resume the Web Dynpro application (using the resume plug) at the same position as soon as it is called by the external application..."

"The external application received the URL, which it must use later to call the Web Dynpro application again, in the form of a parameter. This parameter is called sap-wd-resumeurl and consists of the URL of the Web Dynpro application and of a parameter containing the session ID. This parameter enables the external application to call the Web Dynpro application via the resume plug. Additional parameters that have been included can now be read and processed. When you intend to navigate from the external application back to the Web Dynpro application, you can again include parameters into the resume URL of the Web Dynpro application."

BR, Siarhei