Multiple App servers and BSP debugging

My current client was having shocking performance on its SAP development system. This is not a good thing. There were many consultants getting quite frustrated and annoyed.

So after the time it takes to get these type of things organised they deployed a new app server for us. Hooray. Improved performance and happy consultants.

Here are some reminders for when you are trying to debug SAP Business Server Pages (BSP) applications you need to:

  1. Make sure you are connected to the right client. If your breakpoint is in client 200 it won’t stop at the breakpoint if you are logging onto client 300 with the browser. The best way to do this to absolutley make sure is to append sap-client=nnn to the url where nnn is your client number.
  2. Make sure are you pointing your browser at the right application server. You can either save a bookmark / favorite to the right app server or you can use the test from within transaction SE80 (the development workbench) or transaction BSP_WD_WORKBENCH (the web client workbench). Using ‘test’ does not guarrentee that the right client will be chosen as there may well be a default client set up in the Internet Connection Framework (transaction SICF).

So if you have a set a breakpoint in your BSP and you are not hitting it, check these two points. If you have set it all up correctly then your logic may well be at fault! That is probably why you are debugging.

Technorati Tags: , , , ,

Advertisements


%d bloggers like this: