cancel
Showing results for 
Search instead for 
Did you mean: 

RFC behind a standard Servive

Former Member
0 Kudos

Hi Experts,

I am able to run a WSDL file successfully, which is part of the standard delivered services.

Below is the url of the same.

http://<server>:<port>/sap/bc/srt/xip/sap/ECC_EMPTIMSHEETEMPQR?sap-client=.

As per my understandiing, the RFC associated with this service is ECC_EMPTIMSHEETEMPQR. but I am not able to view it in SE37. Also I am not able to access this service through the transaction - WSADMIN or WSCONFIG at the R/3 end.

Can some one explain to me why is it so?

Thanks and Regards,

- anto.

Accepted Solutions (1)

Accepted Solutions (1)

nilayghosh
Active Participant
0 Kudos

Hi Antony,

Please follow the steps below:

1. Go to WSCONFIG.

2. Enter <b>ECC_EMPTIMSHEETEMPQR</b> in the <i>Service Definition</i> and <i>Variant fields</i> and click on the <i>Create</i> button (F5) at the Application tool bar.

3. Click on the <i>Save</i> button from the tool bar. This will actually release the enterprise service.

4. Go to WSADMIN.

5. Expand the node <i>SOAP Application for XI Proxies</i>. You should find a node named <b>ECC_EMPTIMSHEETEMPQR</b>. Expand this node until you reach the Web Service ECC_EMPTIMSHEETEMPQR.

6. Select this Web Service and follow the menu path Goto -> Administration Settings. Enter the address of your J2EE Server like http://<hostname>:<P4 Port>. The P4 Port is generally 8011 but cross check with your NW Administrator. Save the value.

7. Click on the Web Service Homepage button from the application toolbar to launch the WS Navigator. Select the default option while doing so and you should now be ready to test the Enterprise Service.

Hope this helps. Please let me know if not.

Nilay

Former Member
0 Kudos

Hi Pushkar- I don't see the Endpoint type to be of Enterprise service from ESR. :(.

What patch/ stack shuhd i apply..

Also the standard services available in thje ES Workplace are not seen in my SAP discovery system. Some services are available in the Web Service repository. I am totally confused with some of my findings -

1. Some services that are running successfully are not present in WSADMIN transaction. (rather there are no sservices in the transaction)

2. But i see a lot of servces available in the Web Service repository URL and the corresponding RFCs in the backend.

3. Even the services seen in the WS Repository URL are not present even in WSCONFIG transaction.

Please help me out.. Anyspecific docs on linking these are really help full, i haver gone through most of the resources i have found....

Thank you very much.

- anto.

Answers (3)

Answers (3)

Former Member
0 Kudos

sorry, this post was accidentially.

Message was edited by:

Anton Wenzelhuemer

Former Member
0 Kudos

Hi Antony,

These are the webservices created from ESR interfaces.

you can go to SE80, select create Enterprise Service / Web Service -> Web Service.

when we create this, in Endpoint Type we specify "ESI Repository Interface Service" and select the check box on the next screen and so on.

Now you can see this service using WSADMIN under "SOAP Application for XI Proxies" .

Regards

Pushkar

Former Member
0 Kudos

In WSADMIN, we have

a) SOAP Application for RFC-Compliant FMs

b) SOAP Application for XI Proxies

Webservices created from RFCs can be located in first category.

n case we generate proxy from RFC,

link is something like this.

http://<host>:<port>/sap/bc/srt/rfc/sap/<func module>?sap-client=950&wsdl=1.1

Description:

Where as your service falls in the second category. You can locate this over there.

For second category the link is like this

http://<host>:<port>/sap/bc/srt/xip/sap/<application name>?sap-client=950&wsdl=1.1

Regards

Pushkar

Message was edited by:

Pushkar Anand

Former Member
0 Kudos

Hi Pushkar,

thanks for your update.. so where do i find this xi application? if it is not a Function module.

- anto.