Consuming Webservice from a different network

[Former Member]

Hi All,

Scenario:

We have a SAP system and .Net application which are running on different networks. As of now, the data generated in SAP system is manually entered in the .Net application and viceversa (updation of data to SAP from the .Net application also happens manually).

Now we want to automate this process using webservices. For that, we have created a Webservice from SAP ES workplace using ABAP and created a WSDL file of the service.

Now our doubt is, how the .Net application which in different network, will be able access this webservice.

What are the required steps to consume this webservice from the SAP system. Is asynchronous data transimission possible between the two systems.Is our approach of using webservice correct here ?

Kindly suggest with your inputs on the possible solution for our scenario.

Thanks,

Aman.

[Former Member · Accepted solution]

Hi,

Having webservice on different network is not a issue here, problem would be if communication between those 2 network possible or not, for example none of the network accessible from outside, i.e. internet then it is not possible to do this until you configure some kind of virtual network to allow communication between two network, normally webservices are accessible over internet.

For Async scenario webservices are not recommended approach. Why you don't use middleware like XI/PI or Biztalk for communication between SAP and .Net application. I am sure XI will be able to connet your two different networks.

Regards,

Gourav

[Former Member · Accepted solution]

Hi Gourav,

Thanks for your inputs.

I would like to add one point here, the manual process which i meant was, like theres a shared folder that is present in one network and a custom program which reads that info.

In this scenario, using webservices will still be a good option or not?

If going for implementing PI, what are the pros and cons to be considered here.

Do suggest....

Thanks,

Aman.

[Former Member · Accepted solution]

Hi,

XI is preffered choice of middlewafre for SAP dominated landscape, but it add to cost in term of hardware/effort etc so implementing XI is strategic decision needs to be taken on higher level after evaluating all enterprise requirement.

>I would like to add one point here, the manual process which i meant was, like theres a shared folder that is present in one network and a custom program which reads that info

If you can access shared folder then I am sure you can access webservice as well but I suggest you should try to access RFC directly to get data from SAP landscape (more about .Net connector is available here: http://help.sap.com/saphelp_nw04/Helpdata/EN/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm )

PI implementation key decision area:

- Size of SAP infrasatructure.

- Number of interconnected applications (A2A communication) hosted on different system/networks and sharing common data for one need or another.

- Communication with supplier/Vendor/Customer landscape (B2B communication).

If answer of above if very few then PI is not right choice else I suggest to go for XI/PI and gadually migrate all connections to central place i.e. SAP XI/PI.

Regards,

Gourav Khare