cancel
Showing results for 
Search instead for 
Did you mean: 

Access to Backend

Former Member
0 Kudos
114

Hi,

We are planning to work with Webdynpro for Java. What is the best approach to retrieve data from Oracle as back end system. We have JavaBean model and Adaptive Webservice model. I have gone through some tutorials where in an EJB can be exposed as Webservice and can be used in Webdynpro as Adaptive Webservice model.

Can any one please suggest what are the advantages and disadvantages of using Java bean model or Webservice model.

Thanks,

Portal

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Use the JavaBean model when a Java API resides on the J2EE Engine your Web

Dynpro application will run on.

For example

EJBs*

BI Java SDK

MDM Java API

KM Java API

3rd-party Java API

(delivered as EJBs or otherwise)

Your other option of connecting to your Java API is by creating a web service

wrapper for it. This is potentially development intensive and adds a layer of network communication.

Refer, SDN page for Backend Access - Webdynpro Model:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/403e6bf5-426e-2910-b0a8-a9554...

Regards,

Anagha

Edited by: Anagha Jawalekar on Nov 19, 2008 9:26 AM

Former Member
0 Kudos

Hi,

what are the advantages disadvantages of using Java bean model.

Thanks,

Portal

Answers (2)

Answers (2)

former_member1
Active Participant
0 Kudos

If the Bean is residing on the same server, its better to use bean directly instead of xposing as a WS. coz its quicker.

p_2_5_6_9_6_0
Active Participant
0 Kudos

Hi,

Like Web Services the Bean Model allows to work with bean methods via a model execution in web dynpro.

For information on how to use it please refer to: https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/4072c0d0-c21e-2b10-ab84-e2c183d3...

or

https://www.sdn.sap.com/irj/sdn/event/webinars?rid=/library/uuid/f09604ae-860a-2b10-9cb8-a29d27ca1cc...

Advantage are pretty much the same as web services: you get a wizard to implement the beans, you can abstract your model and ui (view) etc.

Disadvantages: Though possible, it is difficult to switch models after implementation and there is the step for configuring destinations etc. Performace can be slow on the first access - but usually speeds up on repeated use of the bean at runtime.

Hope that this helps you.

Thanks.

p256960.