on 04-07-2014 5:44 PM
Hi ,
We are using nwbc4 PL12 desktop software and it's configured to back end Ehp6 through http & https.
Even though we close the session in nwbc desktop it remains exist in Backend system,Please see the below attachment.
If i use the same url used in NWBC desktop in IE browser directly it closes the session in the backend when i click on logoff.
Please let me know is there any settings do i need to do at NWBC/system level for this to work same as browser.
Regards
Janakiram
Hello Janakiram,
Please check, if Your Runtime is on the most current version - #1963267 - SAP NWBC ABAP Runtime Patch 36.
Best regards
Melinda
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Melinda,
thanks for the quick response.
I see the note explains about NWBC Patch 36,we are using NWBC4 PL4 and PL12 desktop client on different systems.
We are using corbu theme in NWBC_CFG table and it works well.
when you launch https/https url directly from browser and logout session wil lbe killed in backend.
But when you launch the http/http surl from NWBC desktop client sessions are not killed in the back end even though you log out from NWBC.
We are planning to use only corbu theme instead of tradeshow.
we are running on 731 patch6
SAP_BASIS 731 0006 SAPKB73106
SAP_ABA 731 0006 SAPKA73106
Regards
Janakiram
Hello Janakiram,
Also Desktop Client uses Runtime Environment, and that should be always as current as possible.
Please check it by type 4 in
https://service.sap.com/sap/support/notes/1864151
Best regards
Melinda
Hi Melinda,
Thanks for the link to understand the Runtime environment.
I have applied the note to bring the Runtime to current version.
Still i am facing the same issue.NWBC thin client working perfect.
NWBC Desktop client session is still present in backend even after logout.
Is there any additional settings do i need to perform related to NWBC thick client.
Regards
Janakiram
Thanks everyone for providing your inputs on the issue.
I got response from sap and below two settings resolved my issues.
For accessing from IE Browser:Accessing from NWBC Desktop client:
Activate the below services in the back end system.
SICF-->default_host/sap/public/icf/logoff -->Activate this service
NOTE: Make sure to communicate with users to log out from the system after their work.If they are not log out sessions will be sitting in the back end.
Regards
Janakiram
Jana
NWBC could call various types of application that could spawn additional processes that runs on the background (E.g. POWL, Web DynPro or Even background ABAP etc). Even if you close NWBC those processes will still run (because it's a background process; not a user session controlled by NWBC).
So my 2 cents ... do a trace and find out what process\application that it's running at the background (Use: SM04, User > Activate (Detail). And then combine those info with what you see in the Process Overview (SM50). This way you will be narrow down what's the offending process and figure out what to do with them.
As personal example, I notice that some of my POWL report launched via NWBC still keeps on running; even after I closed my NWBC sessions. My trace lead me to process ... which as a matter, I could NOT even shut down via SM50 (I have to shut it down at the OS level). As a work around, nowadays I created my query in such a way so that selections will be limited and will NOT overwhelm the system.
Cheers
Damean
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.