Creating Service Endpoint in SOAMANAGER...

[Former Member]

Hi,

I published the service interface (inbound) from Enterprise Services Builder (from the WSDL tab & using Publish button).

I got a prompt, that said, "Release Status" --> Not Released..,

I don't see any End Points configured for this service in the service registry (the state column shows "Modeled" instead of Activated/Deployed).

One of the threads has same question, but it was never answered

Can anyone let me know how to use SOAMANAGER to create the Service Endpoint?

Edited by: srinivas M on Jun 22, 2010 10:26 PM

[Former Member · Accepted solution]

Please refer to below link and see if you have followed all the steps.

/people/bv.pillai/blog/2008/01/27/new-service-definitions-in-the-abap-development-environment-soamanager-150-sap-nw-70-sp14

Hope this is helpful and i understood where u r facing problem.

Thanks,

Hetal

[Former Member · Accepted solution]

Hi Hetal,

The blog you posted doesn't have any steps to create Service Endpoint. Also, my scenario is Java Application to PI to RFC(R3). Can you let me know how to create the End Point for the web service in the service registry?

When I test the web service using WS navigator, I get the similar error:

Invalid transport binding settingsHTTP Client, does not have endpoint url specified.

Thanks

Srinivas

[Former Member · Accepted solution]

Can you please go through the below link?

see if it is useful.

As well as go throught the below links also:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00985388-6748-2c10-0d83-f17c3e768...

/people/daniel.graversen/blog/2008/02/27/publish-services-from-pi-71-to-the-service-registry

Let me know if it doesnt help.

Thanks,

Hetal

[Former Member · Accepted solution]

>

> http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00985388-6748-2c10-0d83-f17c3e768...
> 

Thanks a lot for these helpful links!

What do you mean by this section:

1.6. Implement the generated methods, build and deploy on AS Java.

from the above document?

Do I have to provide the functionality for the generated methods myself?

I also don't see endpoint for the newly published service, and has no WSDL

WSDL:	N/A

Back to my original problem, how to create Endpoint for the service in Service Registry...

Thanks

Srinivas

Edited by: srinivas M on Jun 23, 2010 5:16 AM

[Former Member · Accepted solution]

Hi Srinivas,

I think you're going about this the wrong way...

From the scenario you've described the RFC module will be handling the actual provider logic so you are just brokering the webservice functionality.

In this case you won't publish the Service Interface from PI to the Service Registry because this would mean generating a proxy on PI & doing the proxy (provider) implementation in PI & configuring the endpoint using SOAMANAGER on PI, this would be a futile exercise.

What you need to be doing is publishing the Sender Agreement (with it's associated SOAP Sender channel) in the Service Registry so PI behaves like a broker for the Abap backend webservice provider.

See link below & refer to the 'Brokered Service implemented in own system' section:

[http://graversen.org/2008/02/27/publishing-services-in-pi-71/]

You'll notice towards the end of that section how the endpoint is actually configured for this scenario. It sounds like you're essentially trying to webservice enable the RFC through PI...Unless I've missed something.

Regards, Trevor

[Former Member · Accepted solution]

Hi Trevor,

I followed your approach earlier and the RFC got published as a web service. We cannot use this web service directly. All the XML mappings are done in the Enterprise Services Builder. We have to use a service interface (Inbound) and then generate the proxy based on this interface. Prior to PI 7.1, we were using XI 2.0 using this approach (all my effort is to migrate the java proxies to PI 7.1).

@Raj,

I followed the blog link you posted, but I couldn't search the web service in the SOAMANAGER. I am able to search the service in Service Registry.

@Hetal

I don't see endpoint for the service in the service registry.

Thanks

Srinivas

Edited by: srinivas M on Jun 23, 2010 3:39 PM

[Former Member · Accepted solution]

Hi Srinivas,

This is the point I'm trying to make...

Using TCode SOAMANAGER from the PI box won't yield the results you're looking for. If you launch SOAMANAGER from the Abap backend you should then see the service you're looking for.

I'm saying, because you can't use the webservice directly, it has to be brokered through PI. You would have Service Interface with underlying operation XML mapped to backend RFC. Configure your sender agreement with a SOAP comm channel. In the Sender agreement drop down menu you have 2 options, Display WSDL & Publish WSDL. You could use the displayed WSDL to generate your Java Proxy & optionally publish the WSDL to the Services Registry but you'll notice a defaulted endpoint when you Display the WSDL already. That's the endpoint that the Java proxy will hit.

Regards, Trevor

[Former Member · Accepted solution]

>

> Using TCode SOAMANAGER from the PI box won't yield the results you're looking for. If you launch SOAMANAGER from the Abap backend you should then see the service you're looking for.

Hi Trevor,

Why do I have to use SOAMANAGER on the backend system (R3)..., there is no service in the R3 system...

Earlier I imported RFCs(from the backend R3) into Enterprise Services Builder to create the service interfaces. I tried your suggestion, but after activating the SOAMANAGER, I get a blank screen when I run (showing hour glass). It just won't open...

Thanks

Srinivas

Edited by: srinivas M on Jun 23, 2010 5:01 PM

[Former Member · Accepted solution]

>

> It sounds like you're essentially trying to webservice enable the RFC through PI...Unless I've missed something.
>

I am working on Java proxy migration as we upgraded from XI 2.0 to PI 7.1

In my context, I followed http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00985388-6748-2c10-0d83-f17c3e768...

But I don't see endpoint for the service in the service registry.

How to create endpoint in SOAMANAGER on PI.

Thanks

Srinivas

[Former Member · Accepted solution]

I think this should work for you.

It shows full Web Service scenario how you can configure.

specially refer to page - 12 to know how to create end points.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/109aa318-5aa6-2a10-799d-a495383c1...

Thanks,

Hetal

Edited by: hetal shah on Jun 23, 2010 7:56 PM

[Former Member · Accepted solution]

Hi Hetal,

Why do I need to create a web service out of the RFC in the backend system?

My scenario is a simple java client is calling Java proxy to send a XML file to the R3. The mappings are created in PI (Enterprise Services Builder).

In my case the receiver is R3 RFC. The WS Provider would need to exist on PI itself?

Thanks

Srinivas

[Former Member · Accepted solution]

Hi Srini,

In your case, the guide you're referencing is only good for designing your Service Interface. How did you generate your Java proxy previously in XI 2.0?

What I'm saying is that you should forget about TCode SOAMANAGER, it's not the right tool for what you are trying to achieve.

I'm saying your steps should be as follows:

- Import RFC/s into ESR

- Model your Service Interface with underlying operation/s, message types, data types.

- Do you XML mapping between Service Interface & imported RFC

- Do you config in Integration Directory (sender agreement etc.) and use a SOAP comm channel as the sender channel.

- Get the WSDL from the Sender Agreement drop down menu in Integration Diretcory.

- That WSDL will have a default endpoint.

- Use that WSDL to generate your Java proxy

- Test your implemented Java proxy.

Don't use SOAMANAGER for endpoint config. Don't create webservice out of RFC. SOAMANAGER would have only been relevant if you webservice enabled your RFC in the backend. Then you would use SOAMANAGER in the backend system & configure relevant endpoint for that webservice. In that case the Java proxy could bypass PI altogether with the request call & hit the backend endpoint directly. Now all you have is an RFC in the backend & you want to be able to send an XML request over HTTP from the Java Proxy to PI then on to the RFC.

Regards, Trevor

[Former Member · Accepted solution]

>

>  - Get the WSDL from the Sender Agreement drop down menu in Integration Diretcory.
>  - That WSDL will have a default endpoint.
>  - Use that WSDL to generate your Java proxy
>  - Test your implemented Java proxy.

I imported the WSDL by connecting to Service Registry from NWDS 7.1

After I generate do I have to write a test client in the same project, to call the proxy before I deploy the whole EAR?

What are the next steps ...

Thanks a lot for your reply

Srinivas

[Former Member · Accepted solution]

This message was moderated.

[Former Member · Accepted solution]

Thanks

Srinivas

[Former Member]

Steps to be followed to create end Point for the service definition you have created from RFC.

http://help.sap.com/saphelp_nwpi71/helpdata/EN/c8/f0a0c9f03541edafe783c4a0ddb1aa/frameset.htm

[rajasekhar_reddy14]

check out this blog

/people/shibaji.chandra3/blog/2010/02/17/soa-web-service-expose-and-consume-configuration-with-soamanager

Regards,

Raj