NWBC: Calling Transaction with OBN and tranfering additional data

[Former Member]

When navigating in NWBC 3.0 from a Web Dynpro ABAP application to an ABAP transaction using OBN, I would like to transfer additional data that was not yet saved on database. The data is not a simple parameter, but about 10KB large.

What is the best way to achieve that?

My ideas so far:

A. Save data to database (not possible due to running LUW; can't COMMIT)

B. Use Shared Memory (will not work if customer uses several application servers)
C. Transfer data as OBN parameter (works only for strings up to a size of 2000 characters)

Maybe for B, the shared memory option: is there a way of making sure that the application server the Web Dynpro ABAP application runs on, is provided via OBN to the called ABAP application? Then SHM would be an option.

Thx for your advice in advance!

[thomas_jung · Accepted solution]

There is a way around the multiple application servers issue with Shared Memory.  You can update the Shared Memory object instance on all application servers (or from the receiving application check all application servers remotely to find the correct one).  Either way the technical approach is similiar. You can call function module TH_SERVER_LIST to get a list of all active Application Servers. You can then loop through this list and call an RFC which can communicate with each application server.  This way you can either propigate your data into all application servers or from the destination application in the OBN call back to the originated application server to get the information you need.

[Former Member · Accepted solution]

Great!

Thomas, thanks a lot sharing your knowledge about this workaround.