on 2013 Dec 05 7:08 PM
Hello,
I've developed this scenario with all things that I considered necesary. But I have a problem that I cannot solve yet. Using the SXMB_MONI I saw this error:
and also I have this message obtained from WS Navigator:
I really tried everything in order to solve this issues (SM59, SICF, SXI_CACHE, SXMB_ADM, Notes 75186, 517484 and 796726, etc.). So now I'm asking for your help.
Thanks.
Pablo
The problems seems to be solved. It was a simple thing. The data i've received to put in my CCs was wrong. The user had no permissions to invoque the RFC in the sender CC and the proxy.
Thanks to all of you for your answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Pablo,
As you said that there is proxy server in between PI System and WS server, is there any authentication required to pass through that proxy server? are you maintaining any proxy server credentials in the communication channel?
Also I would suggest you to try a Telnet connection and perform a trace-route from your PI system to the WS server. It might help you in locating the point where authorization is getting failed.
Thanks
VJ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Someone told me that I should try with a Java Proxy in the middle. Does anyone know something about this posibility?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
please refer the below links
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Can you please elaborate more about the error and the WSDL URL you are using.
Is the server where this webservice is hosted is in same network as of your PI System ?
Is there any firewall/proxy server between PI system and this server ? If yes, it might be rejecting your WS request.
Regards
VJ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In your above responses you have mentioned that, you were able to complete the request using SOAPUI, can you take the payload from that successful request and trigger a test message from RWB, this will clarify if there is some issue with the RFC.
If the request still gets in error then I would suggest you to again check the firewall rule and test if you are able to make connection to the WS server from PI System.
Also you can use XPI Inspector tool to get the trace logs for WS request and response to see where your request is getting blocked.
Regards
VJ
Did you check that also?
your RFC is unicode enabled?
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,
Check your login credential.
Regards,
Mani
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Thank you for your answer.
I tried with SOAP UI and the result was "System.Web.Services.Protocols.SoapException: Server was unable to read request. ---> System.InvalidOperationException: There is an error in XML document (10, 29). ---> System.FormatException: Input string was not in a correct format."
When I edited that parameter with a correct value SOAP UI worked. But, when I do the same thing in the execution of the RFC the error persists.
Hi Pablo,
where exactly do you send the request? Have you made sure that you send the payload data to the WSDL endpoint and not to the WSDL location? The address with "?WSDL" in the end should be the wrong one. soapUI recognizes this automatically, in PI you have to put that manually.
You could also try WSNavigator to see whether it works. The advantage of WSNavigator over soapUI is that it is executed on PI system, not on your client.
Regards,
Jörg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Can you please check if the url you are using is correct. Make sure it is in the proper format. Also try opening it up in a browser and see if it is working.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
403 means the request received by server but refuses to take any further action..
Can you check if the configured URL is valid along with the valid credentials?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
66 | |
10 | |
10 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.