cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with WSDL file generated by PI for sender SOAP

terri_walton2
Explorer
0 Kudos
626

I have a scenario SOAP to idoc that I am trying to test in PI7.1. I have created my objects in the ESR and completed the configuration in IB. When I test the configuration in IB, the data passes through PI to ECC correctly.

Now I want to export the WSDL file from the Sender Service Interface being used for this scenario and test it using SOAPUI. However, when I look at the WSDL file proposed by PI, there is no SOAP URL proposed in the WSDL. My understanding from looking at other threads in the the forum is that the URL should be proposed in the WSDL file, and I can then export this WSDL file to my PC, and upload it into SOAPUI for testing.

Why is the URL not being proposed in my WSDL file?

Thanks in advance for any help.

Terri

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Terri,

If yuo want to test with SOAP UI, then save the WSDL file from the Sender agreement in your local Machine.

simply load the WSDL in the SOAP UI by Creating the Project.

and there by you can trigger the interface by providing the login credentials of the PI system.

Regarda,

Praveen K

Answers (2)

Answers (2)

terri_walton2
Explorer
0 Kudos

My original question was answered, so I am marking this question as closed. I have another issue, and will open a new post for that issue.

baskar_gopalakrishnan2
Active Contributor
0 Kudos

>>However, when I look at the WSDL file proposed by PI, there is no SOAP URL proposed in the WSDL

>> Why is the URL not being proposed in my WSDL file?

Easy step to create WSDL.. Please follow this... few seconds work...

Click Sender agreement object

Go to menu Sender Agreement-->Display WSDL and save the file.

You will see the WSDL url in the WSDL content itself. Search for "<soap:address location" you will find both http and https URL.

So in PI 7.1, you dont need to worry about URL. Sender agreement takes care all the parameters from the communication channel.

Now load WSDL in SOAP UI , it will find endpoint URL automatically...

Hope this helps.

terri_walton2
Explorer
0 Kudos

Thanks Baskar that solved part of the problem.

When I use this newly generated WSDL file for testing in SOAPUI, I now get an error 401, which I believe has something to do with needing a user id and password. However, my scenario is not setup to require a userid or password. Any other help would be appreciated.

Below is the actual results from SOAPUI:

HTTP/1.1 401 Unauthorized

server: SAP NetWeaver Application Server 7.11 / AS Java 7.11

www-authenticate: Basic realm="XISOAPApps"

connection: close

pragma: no-cache

content-type: text/html;charset=ISO-8859-1

content-encoding: gzip

date: Thu, 03 Mar 2011 22:49:56 GMT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<html>

<head>

<title>Error Report</title>

<style>

td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}

A:link

A:visited

A:active

</style>

</head>

<body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0">

<table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75">

<tr bgcolor="#FFFFFF">

<td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b>&nbsp;&nbsp;401 &nbsp Unauthorized</b></font></td>

</tr>

<tr bgcolor="#3F73A3">

<td height="23" width="84"><img width=1 height=1 border=0 alt=""></td>

<td height="23"><img width=1 height=1 border=0 alt=""></td>

<td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP NetWeaver Application Server 7.11 / AS Java 7.11&nbsp;</b></font></td>

</tr>

<tr bgcolor="#9DCDFD">

<td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td>

</tr>

</table>

<br><br><br><br><br><br>

<p><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b>&nbsp;&nbsp;Error: Unauthorized<p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><b>&nbsp;&nbsp;Troubleshooting Guide <a href="https://sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/wiki?path=/display/jsts/home">https://sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/wiki?path=/display/jsts/home</a></p><p></b></font></p>

<p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><table><tr><td valign="top"><b>&nbsp;Details:</b></td><td valign="top"><PRE>No details available</PRE></font></td></tr></table></font></p>

</body>

</html>

baskar_gopalakrishnan2
Active Contributor
0 Kudos

HTTP 401 unauthorized error : You need to provide username and password to use your webservice.

Talk to BASIS team and get PI user account. Something like this user role will help

SAP_XI_APPL_SERV_USER

terri_walton2
Explorer
0 Kudos

Thanks Baskar for the timely information. I have forwarded this thread to my Basis person and hopefully we can resolve this issue.

baskar_gopalakrishnan2
Active Contributor
0 Kudos

Hi Terri,

You can test with your PI userId in SOAPUI too. It has similar user role. It might work too.

Baskar

rajasekhar_reddy14
Active Contributor
0 Kudos

Hi,

if you want to test SOAP scenarios, just use WS Navigator in Service Registry

in PI 7.1 , process very simple, publish your sender agrement in to Service Registry,then login to SR and test it in SR it self.

The authorization issue suppose to solve by your self, whene you upload WSDL,leftside window you have to enter PI system user name and password details then only your request will be send it to PI.

Regards,

Raj

terri_walton2
Explorer
0 Kudos

Hi Baskar

When I test with my userid and password in SOAPUI, I am now getting a new error 500 - Internal Error. I have passed this to my Basis person, along with references to OSS notes 840124 and 807000 as mentioned in thread /people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi, but he says everything is configured as per these notes.

My inbound messages to this partner are working correctly, but this outbound message is really causing me a headache. Any other help you can provide would be appreciated.

Terri

Edited by: Terri Walton on Mar 4, 2011 1:33 PM removed SOAPUI results due to formatting issue.

prateek
Active Contributor
0 Kudos

This error would mean that either the machine from which you are trying to post the data couldn't reach PI server Or the URL is incorrect. What is the URL you are using? Also, talk to your network (firewall) team to confirm if you can send data to PI URL from machine hosting SOAPUI.

Regards,

Prateek

terri_walton2
Explorer
0 Kudos

Hi Prateek,

The URL I was using was incorrect (case sensitive). I was using http://hostname:50000/xisoapadapter/messageservlet?channel=:BS_BUSINESS_SYSTEM:CC_soap_WorkOrderResp... instead of http://hostname:50000/XISOAPAdapter/Messageservlet?channel=:BS_BUSINESS_SYSTEM:CC_soap_WorkOrderResp....

After making this fix, I am now getting the error "no channelID specified or no channel found for the specified party, service, and channel name,' when testing in SOAPUI.

In SOAPUI, I am actually using the URL. I know the Business system name and sender Communication channel is correct, so I am thinking it has something to do with the sender service or Interface name being populated with x.

http://hostname:50000/XISOAPAdapter/MessageServlet?channel=:BS_BUSINESS_SYSTEM:CC_soap_WorkOrderResp...

I generated the WSDL in Integration Builder via Tools --> Display WSDL --> choosing the specific interface for this sender. I did not propose the URL, I entered the URL http://hostname:50000/XISOAPAdapter/Messageservlet?channel=:BS_BUSINESS_SYSTEM:CC_soap_WorkOrderResp....

For testing in SOAPUI, am I supposed to let the system propose the URL? Sorry for all the questions, but this is my first attempt at implementing an outbound SOAP message so I am learning on the fly.

Thanks, Terri

Edited by: Terri Walton on Mar 6, 2011 6:02 PM made error message in bold

terri_walton2
Explorer
0 Kudos

Hi Prakeen,

I forgot to mention in my last post, this is a prototype in our lab, and both systems are on the same network, so the firewall should not be the issue.

Terri