Solved: Error when the data triggered from SOAPUI to PI

Former Member · ‎08-10-2015

Hi all,

Am performing (SOAP to Proxy Scenario) / Inbound Scenario and triggering the data from SOAP UI tool,

As i said its soap to proxy scenario.When checked with the basis team they told that only https can be used and also the server name has to be changed.

I changed the details according w.r.t URL as well as in target url (Communication channel). I don't know what module needs to added in communication channel or what changes needs to be done w.r.t configuration.

I received the below error when the data is triggered from UI tool.

Error Code: 407 Proxy Authentication Required. Forefront TMG requires authorization to fulfill the request. Access to the Web Proxy filter is denied. (12209)

Full Error :

<HTML><HEAD><TITLE>Error Message</TITLE>

<BODY>

<TABLE><TR><TD id=L_dt_1><B>Network Access Message: The page cannot be displayed<B></TR></TABLE>

<TABLE>

<TR><TD id=L_dt_2>Technical Information (for Support personnel)

<UL>

<LI id=L_dt_3>Error Code: 407 Proxy Authentication Required. Forefront TMG requires authorization to fulfill the request. Access to the Web Proxy filter is denied. (12209)

<LI id=L_dt_4>IP Address: 10.31.0.31

<LI id=L_dt_5>Date: 8/10/2015 8:38:29 AM [GMT]

<LI id=L_dt_6>Server: NLWL31.stahl.com

<LI id=L_dt_7>Source: proxy

</UL></TD></TR></TABLE></BODY></HTML>

Please let me know what actions needs to be taken for the above error.

Regards,

Vikram.

iaki_vila · ‎08-10-2015

Hi Vikram,

You have a firewall that blocks the communication. Check this thread https://social.technet.microsoft.com/Forums/forefront/en-US/77c9c7a2-86a1-45d0-bb82-ed3f40cb3920/122...

web-proxy-filter-is?forum=Forefrontedgegeneral

Regards.

apu_das2 · ‎08-10-2015

Hi Vikram,

There is no need to change the URL if you are testing it it from project VPN.

Just create a WS from Display Web Service option of ID , import it in SOAPUI . It should work properly if your interface is created properly.

Now when you will provide the WS to third party they will use it from internet not from intranet . In this case your basis/network team need to provide you a public IP which will point your internal PI server IP and it should work properly.

Suppose below URL is after generating WS from ID -

http://vhbryndxci.xxx.yyy.corp:50000/XISOAPAdapter/MessageServlet?abcd/abcde/pqr

where http://vhbryndxci.xxx.yyy.corp:50000 is the internal PI IP

Now third party should call -

https://test.public.com/XISOAPAdapter/MessageServlet?abcd/abcde/pqr

where https://test.public.com is the public IP pointing internal IP http://vhbryndxci.xxx.yyy.corp:50000

Thanks,

Apu