multiple app servers and web dynpro in the portal

[former_member186444]

We have a Web Dynpro ABAP application in a portal in which when the user closes the browser window using the normal 'X' at the top right of the browser. This triggers an event that leads to a custom piece of code that unlocks a particular record. This works great in our development environment, where we have one application server. However, in our QA system, where we have multiple application servers, this does not work every time. The event is not always triggered. To prove that it is the multiple application servers that is causing the problem, we turned off all but one in QA and the event was triggered every time.

I'm a developer, not a Basis specialist. However, our Basis staff are very busy right now (and avoiding the issue as it's difficult!), so I thought I'd try my own investigation. But honestly, I have no idea where to look for an answer. This seems to be like looking for needle in a haystack.

Does anyone have any ideas what could be causing this or can point me to an area in which I should be looking? Presumably there is a setting on one server that is not on another. Question is - which setting?

thanks,

Malcolm.

[wouter_peeters]

Hello Malcolm,

We are having a simular situation but with not with Web Dynpro ABAP applications but regular reports and enhancements. Our problem was that executing the exact scenario on each application server gave different results and gave issues. When we put all the users of certain reports on the same server, the problem was gone.

We even experienced a situation when we transported an enhancement to PRO ( 3 AS ) where the enhancement was not activated on all AS giving different results on each AS.

At the moment business is reverting back to 1 AS to avoid these issues. Could you give an update how your situation has evolved?

Greets

Wouter

[former_member186444]

Hi Wouter,

I'm afraid we are no further forward with this and time pressures have forced use into using an alternative solution - locking and unlocking upon save instead of upon entering the record and closing the browser. Not ideal at all.

cheers,

Malcolm.

[Former Member]

Hi,

Think this could be problem with SSO config.

I think this can solve your problem

http://scn.sap.com/thread/63826

Thanks,

Sreeni.

[Former Member]

Hi,

From the description it looks like the trigger after browser close is going to a different application server. In one app server scenario, it works fine as the trigger also is going back to the same application server.

Could you check if the custom code trigger has ability to access the specific app server node ID? Then, the app server node ID from where the browser was closed could be references while triggering the custom code. Check out the blog below to find which J2EE dispatched and server ID is called during a session and after session close, the same server ID should be called by the trigger.

http://scn.sap.com/people/piyush.kumar7/blog/2006/05/10/troubleshooting-portal-server-nodes-using-fi...

There is a javascript too which gives the server ID information for the active session: type javascript:document.cookie in the browser.

Hope it remotely helps

Regards,

Srikishan

[former_member186444]

Hi Srikishan,

thanks for your reply. Unfortunately it is not custom code that triggers the event. It is standard behaviour when the browser is closed that the event is raised. My bit of custom code just reacts to that event.