NWBC for desktop will take some time to start in the beginning. Apart from that once it started , then the performance and overhead footprints of all applications running in NWBC are still the same as if they would run standalone.
Thanks...that is what we had hoped however we continue to see the delays. We are in SBX and still making changes. I hope as we move through the landscape the performance improves. Some folks on our Basis team are looking at run time logs to see if they can pin point hang ups.
we have created some custom web-den pro pages and running transactions like QE01 and a few custom Zcodes in the background. We are starting to do some traces to see if we can see where the hang up is at.
Here is more information regarding your question...During transaction processing within RAI-example Goods receipts, MB01, MB31 and MB0A as well as LT06. Response time is 'ok' using transactions outside of the RAI development. Log on is not an issue.
Are you aware of the Performance Aspects chapter (and sub chapters) of the application help? The first thing that comes to my mind is that NWBC is not using SAP GUI for Windows to render classic dynpro transactions but SAP GUI for HTML aka webgui. Share also the version and patch level of your NWBC for Desktop, SAP_BASIS version and SP level and NWBC ABAP runtime version and patch level.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.