cancel
Showing results for 
Search instead for 
Did you mean: 

No endpoint for Service Interface

Former Member
0 Kudos

Hi everybody,

I have published my Service Interface to the Service Registry but unfortunately without an endpoint.

How can i configure an endpoint for a Service Interface within ESR? Should i use a Model in ESR?

regards,

Sid

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Sid,

What's your scenario? Point-to-point or mediated?

Regards, Trevor

Former Member
0 Kudos

Hi Trevor,

thanks for the reply!

My purpose is to consume a Service Interface (ESR) in Web Dynpro Java (Import Adaptive Web Service Model). But the created Model has no endpoint. I also don't understand where i have to implement my business logic perhaps also in ESR in a Model and Object definition, is this possible? Where would you implement the source code (logic)?

Sorry for my questions but i am new to ESR.

thanks,

Sid

Edited by: Sid on Nov 19, 2010 10:27 AM

Former Member
0 Kudos

Hi Sid,

Your business logic has to be implemented in the system that will be providing (provider system) the data / info etc.

e.g. You want to create a web service that allows you to update a customer's address details in SAP ECC & this functionlaity should be triggered from a Webdynpro Java User Interface.

- Webdynpro Java is the consuming application (also called consumer)

- SAP ECC is the backend system OR provider system OR provider

In this case your business logic will be in SAP ECC.

If you choose to go with a point-to-point scenario:

You could first setup a connection between SAP ECC (provider) & SAP PI. You could then model your inbound service interface in SAP PI. Now because you have visibility between SAP ECC & SAP PI, the service interface modeled in SAP PI become visible in SAP ECC (TCode SPROXY). You would then generate a provider proxy from this service interface & implement the business logic in there. Once the proxy is activated you can then configure an endpoint for it using TCode SOAMANAGER (see lots of guides on how here in SDN). In this case SAP PI is only used at design time just to model the service interface. At runtime Webdynpro Java would talk to SAP ECC directly via the endpoint that you would configure.

For a mediated approach:

Pretty much the same concept as above except this time you would also model an outbound service interface & map the inbound & outbound interface. The call would then be routed as follows - Webdynpro Java -> SAP PI -> SAP ECC but the business logic would still be implemented in SAP ECC.

There are lots of technicalities around this but there are lots of guides on SDN relating to this.

Regards, Trevor

Former Member
0 Kudos

HI Trevor,

thanks for the detailed description! I work with CE 7.1 EHP1 without PI.

For my understanding i have only one last question.

After do the following actions:

1. Define a Service Interface in ESR (Inside Out approach)

2. Use this Service Interface (ESR) in backend system to generate the proxy (SPROXY)

3. Create a RFC in the same system to call the proxy

If i want to execute my scenario, what had i import into my Web Dynpro?

a) import "Adaptive Web Service Model" (means i don't need step 3)

b) import the RFC from backend which call the proxy in the same system

regards,

Sid

Former Member
0 Kudos

Hi Sid,

I would use the following approach:

- Define Service Interface in ESR

- Generate proxy in the backend (no need for RFC in this case)

- Configure an endpoint binding for this Service in SOAMANAGER

- Optionally: You can publish your service in your Services Registry if you're using one in your landscape.

- When creating your Adaptive Web Service Model & selecting the WSDL source, you have some options, because the WSDL is only used at design-time:

a) Choose WSDL source as the ESR Service Interface

b) Choose Services Registry as your WSDL source OR

c) You can enter URL as you would see in SOAMANAGER - e.g. Open WSDL for selected binding' option

Regards, Trevor

Former Member
0 Kudos

Hi Trevor,

one last thing, if i choose:

a) Choose WSDL source as the ESR Service Interface

in my Web Dynpro, does it mean that the proxy will start automatically? Because there is my business logic.

Many thanks!

Sid

Former Member
0 Kudos

Hi Sid,

Nope. After you've done what you need to do in Web Dynpro you will still need to configure a logical port for this consumer. You will need to specify the service endpoint when configuring the logical port using SAP Netweaver Administrator.

So you only essentially use the WSDL to create you Adaptive Webservice model at design time. At runtime (which is when the endpoint get's called as specified in your logical port) is when the business logic actually get's executed.

Also see this useful guide:

[https://cw.sdn.sap.com/cw/docs/DOC-106281]

Regards, Trevor

Answers (0)