on 02-26-2013 8:06 AM
Hi Experts,
We have a scenario SOAP-PI-RFC Synchronous scenario. We are getting HTTP/1.1 401 Unauthorized when we try to send the request using SOAP UI. but when I try and execute the interface using RWB and directly send the message to integation engine the interface is working fine.
The User ID that I am using contains all roles and profiles and has all the access.
I have PI 7.1 SP 10.
Looking forward to your help and suggestions on the same.
Thanks,
Rupendra Sharma
Hi Rupendra,
Please check the following:
"sap.com/com.sap.aii.adapter.soap.app*XISOAPAdapter"
as well as "ClientCertLoginModule, SUFFICIENT"
Regarding the above you can refer to note #891877 - "Message-specific configuration of HTTP-Security".
In this context, XISOAPAdapter might be set to either
"ClientCertLoginModule" or "BasicPasswordLoginModule"; you might want to change this around in order to fix the HTTP 401 issue.
Regards,
Ridvan Polat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Try resetting the password & then restart Java Engine...Also check if the XI engine in activated in SICF in path sap->xi->engine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rupendra,
The sender SOAP based application is using the user name/password seems to be locked with incorrect attempts of the wrong password on PI JAVA stack.
You need to unlock & reset the password with the help of SAP security team & provide the new password to the sender SOAP based application to configure at their end.
When you are posting the data in RWB with your user credntials its working fine since your crendtials are not locked & working fine & this is why you are allowed to post the data.
Hope this would help you in solving your issue.
Regards,
Ashish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
We have a scenario SOAP-PI-RFC Synchronous scenario. We are getting HTTP/1.1 401 Unauthorized when we try to send the request using SOAP UI. but when I try and execute the interface using RWB and directly send the message to integation engine the interface is working fine.The User ID that I am using contains all roles and profiles and has all the access.
I have PI 7.1 SP 10.
If you are sending directly to Integration Engine via RWB when testing, then you should use the Propose URL option when generating your WSDL and not the http(s)://host:port/XISOAPAdapter/MessageServlet?channel=p:s:c . See this blog by Stefan http://scn.sap.com/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integra...
Hope this helps,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When I generate WSDL using propose URL.
http://<;hostname>:<port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=ECCCLNT200&Interface=urn:10509.com:PP:Test^SI_IB_LoginSync
When I generate from Display WSDL of sender agreement:
I have tested using all kinds of user System and Dialog. It gives same error.
Can you specify the URL format, you are using to create WSDL ?
It should be..
http://10.0.20.54:50000/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>
Regards,
Sunil
Making my problem a little more clear. Earlier this interface was working fine. Then we had SP10 upgrade and after that we started getting this error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You may need to re-create WSDL again as you mentioned that it was working before upgrade.
You can call to the sender SOAP adapter by two different UR Ls. SAP recommends to use
http://<host name>:<port name>/XISOAPAdapter/MessageServlet?senderParty=<name of the sender party>&senderService=<name of the sender service>&interface=<name of the interface>&receiverParty=<name of the receiver party>&receiverService=<name of the receiver service>&interfaceNamespace=<name of the interface namespace>
Refer below help doc once again and re-create WSDL once, it may help you, considering that there is no authorization issues.
Configuring the Sender SOAP Adapter
Regards,
Sunil
Hi Rupendra,
did you try with soap navigator also?
check below blog for more information.
Regards
Gagan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
1.Check the generated wsdl link for the port and other details. those details should be correct.
2.Check your WSDL link with soap ui external tool. there you can get more information.
Generate the WSDL from Tools, not from Sender aggrement.
check the below WSDL format. Give the exat WSDL to webserver team.
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Regards,
Kesava
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, I have entered basic credentials at the left side of SOAP UI. Also, I have cross checked credentials many times its fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
While pushing from soupui you have given credentials in authentication(aut)(credentials to connect PI server) tab right.
Can you check the credentials once again by re entering.It is not about roles it is about credentials typo mistake or password expired.
Regards
Venkat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rupendra,
There is an option to set userid and password in soap UI while sending message from Soap UI. Did you check with this?
Regards
Jeyakar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.