cancel
Showing results for 
Search instead for 
Did you mean: 

Synchronous Webservice & XML gateway application / Firewall config

Former Member
0 Kudos

Hello!! Gurus

We have been diligently working on building synchronous web services interface with the below pattern.

Internal Application(sync web services) ---> SAP PI ----> External Vendor (sync web services)

Thanks for the earlier responses on build & config. activity!!!

We are currently at a point where are looking to send message to the external vendor & get response back - however, we have a gateway appche application server & firewall which we have to take in to consideration.

In the past we had inbound asynchronous interface so we had written some rules where the sender comm. channel was specified as below in the gaeway Appache appl. server

Example: /ws/XISOAPAdapter/MessageServlet?channel=:BC_ExternalVendor:CC_ExternalVendor_SOAPSender

SO THAT any incoming Inbound Async can routed to the correct Sender Channel URL

HOWEVER, now that we have synchronous web-services - and there is no sender channel for inbound response coming back as it is triggered by the  BC_InternalApplocation:CC_InternalApplocation_SOAPSender


In case of the starlight forward Async outbound - we had ONLY specified the proxy serer host name in the channel.


We are currently getting this error (however, there is some firewall or gateway application config. setting that we need to request with infrastructure team).


<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.EOFException: Connection closed by remote host.</SAP:AdditionalText>


To Summarize:

  • For Synchronous outbound interfaces to external vendors - wat typically needs to be taken care off in the firewall seeting - any specific port of IP needs to be included ?!
  • If we have an gateway application server - apart from configuration this as the proxy server - wat URLs similar to the one above needs to configured so the response is coming (unlike wat we had configured earlier for async inbound)


Hope my message is clear - please email me if you need any addl. details or if I am unclear (apologies for the lengthy message)

Your help is greatly appreciated!!

Thank you,

Ritu

Accepted Solutions (0)

Answers (2)

Answers (2)

iaki_vila
Active Contributor
0 Kudos

Hi Ritu,

Just to add to Raghuraman suggestions is to use the TCPGateway SAP tool to help you to know where the message can be stuck. Check this blog

Regards.

former_member186851
Active Contributor
0 Kudos

Hello Ritu,

To send message to Web service.

1.Open the port at PI server level.

2.Check for firewall settings and whitelist the URL in the firewall.

3.Check for any proxy setting and configure the same if any in the channel.

4.And also check if the web service requires any username/password or Certificate based authentication.

5.In case of certificate based you need to import the same in PI. For username/password the same can be maintained in the channel.

And before going ahead just to ensure the web service is working fine you can use a SOAP UI and test it.

Below link gives the basic idea