Web service Scenario

[Former Member]

Dear Experts,

I have 2 scenarios for Process integration wherein I have to consume 2 web services.

One is on a system which is in our landscape and the other one is outside the landscape.

I wanted to know how different would the configurations be for these two scenarios? Would there be a party involved in scenario 1 or 2? Would there be a difference the way the SOAP receiver adapter is configured?

How many SLD entries would I need?

Any help would be appreciated..

Thanks, Rolmen

[Former Member · Accepted solution]

I wanted to know how different would the configurations be for these two scenarios?

>> Not much difference.

Would there be a party involved in scenario 1 or 2?

>> You do not need any party for either interfaces. Also remember, you need to use a party when you want to change some header fields of your XI message (in B2B scenarios for example) with party you can also use IDOC partner profiles other then LS. But in most A2A scenarios you never use the party object in ID.

Would there be a difference the way the SOAP receiver adapter is configured?

>> No changes. Only thing you will have to do is open a port for acessing the web service which is not in your landscape. This is done either by Basis or Engineering (IS) team.

How many SLD entries would I need?

>> Can you please explain? SLD entries would be normal (Prd, SWCV, BS, TS) as usual for interfaces. No additional/special entries required. In external system you have to create a third party TS, or otherwise if you have not much idea abt the same, use Business Service/Business Component.

Cheers!

Souvik

Edited by: Souvik Chatterjee on Apr 26, 2011 2:51 PM

[Former Member · Accepted solution]

> >> In external system you have to create a third party TS, or otherwise if you have not much idea abt the same, use Business Service/Business Component.

First of all, thanks for the quick responses..

Well, I was referring to the A2A scenario. Basically, the XI system is in the process being set up. Hence I was unsure about the SLD entities.. So it would only be the SAP systems in our landscape, right? What if the scenario involved a 3rd party adapter (for OSI PI system).... In this case, would there have to be an additional entry in the SLD for the OSI PI system in question??

It would more helpful if you could elaborate more on 'use Business Service/Business Component'.. This would be for the external system?

[rajasekhar_reddy14 · Accepted solution]

Hi,

In your case you dont required SLD entry, you can create Bussiness component in ID.

It would more helpful if you could elaborate more on 'use Business Service/Business Component'.. This would be for the external system?

search in sdn.

Regards,

Raj

[Former Member · Accepted solution]

Hi Rolmen,

For SAP to SAP scenarios, you need to register the systems as Technical Systems (using rz70 tcode from Backend systems).

Subsequently u need to create Business systems for these also, which will be used in PI (Int Directory) for data processing.

Now, if you have a non-SAP system outside your landscape, you have 2 options:

1. You have all technical details about the system, then create a TS and BS

2. You do not have much idea about the system, use Business Service/Business Component in the Directory to represent the third party system. For this u do not need any TS or BS in SLD. - - You need this in ur scenario

Let me know if you have any queries.

Cheers,

Souvik

[Former Member · Accepted solution]

Thanks Souvik.. That was really helpful.

So this leaves out just one scenario..

A Non-SAP system in our landscape.. So If I have understood you correctly, since I have all technical details about this system, I would create Business System for this.. Right?

[Former Member · Accepted solution]

Hi Rolmen,

Yes correct. Since you have all the details about the third party system, first create a Technical System (say TS1) and then create a Business system (say BS1) and assign it to TS1.

In Integration Directory, import the Business System BS1 and create a Receiver/Sender Comm Channel of type SOAP and enter the parameters to access the Web Service.

Hope this clarifies.

Regards,

Souvik

[Former Member · Accepted solution]

Hi Souvik.. Thanks for the clarification..

Now, if I attempt to consume this web sevice directly through a report, what would be the risks in a production scenario?

Do I really have to go via XI because I have consumed free services in ABAP reports and it works pretty well.. But this was just testing..

Is it recommended to consume services directly(A2A case)? If not, why so?

Thanks in Advance..

[baskar_gopalakrishnan2 · Accepted solution]

>>Now, if I attempt to consume this web sevice directly through a report, what would be the risks in a production scenario?

Do I really have to go via XI because I have consumed free services in ABAP reports and it works pretty well.. But this was just testing.. Is it recommended to consume services directly(A2A case)? If not, why so?

PI is a SOA middleware and if you consume webservice via PI ,you have standard features such as monitoring, message reprocessing in case of failure and more. Plus, PI SOAP adapter supports standard security features like ssl , signing and encryption, client authentication and more. These you might not need to handle via abap coding. Hope that helps.

[Former Member · Accepted solution]

Hi Rolen,

I absolutely agree with Baskar above.

You need to decide whether you want to have PI as middleware or use ABAP report or se80 to consume the web service.

I can give you an example of complex scenario frm my exp where we dint use PI. we had a proxy to web service scenaro via PI. Now we had 2 levels of validation, each frm different location, then we had to call the target web service if validations were sucessful.

In this case the scenario via PI looked like - Proxy-PI-1stValidation-PI-2ndValidation-PI-WebService.

This looked very complex and we were thinking of using BPM also. But, then we came up with the solution of using se80 instead of PI to access the validations and web service.

Hope this helps.

Souvik

[Former Member · Accepted solution]

Thank You Baskar and Souvik..

My case is rather straight forward. There is a sytem in our landsacape(at plant site) which has a service running. I have to consume this service , validate the data and call a bapi to update data in a few tables. this report would run as a batch at regular intervals..

After reading te responses, I personally don't see any need of PI in this case as it is a batch program. Moreover, the server hosting the service runs in HA mode (primary-secondary).. so the chances of service being unavilable are minimal.. The only concern would be the authentication details sent to that server through sent from my program.. But, i assume, this can be done by the calling SE80 program itself.

Please do correct me if I have missed out on something..

Thanks again..

[Former Member · Accepted solution]

Yups.. in this scenario PI not required.

But, in case you believe monitoring, a dedicated middleware for all interfaces, etc. are a guiding force for you to deciding the middleware then you should go for PI.

The only concern would be the authentication details sent to that server through sent from my program..

>> Not a proper reason for using PI. can be easily done using se80

Regards,

Souvik

[former_member463616]

Hi,

>>>It would more helpful if you could elaborate more on 'use Business Service/Business Component'.. This would be for the external system?

We use Business service then system is not your landscape in these we don't these others system details we use Business

services. Business Service which can't define in SLD, because we don't know the technical landscapes of where data transferring from.

Business system we use we have the Business System in our landscape. Business System Which is defined in SLD, Where we know the data transferring from specific landscape.

Regards,

P.Rajesh

Edited by: Rajesh_1113 on Apr 26, 2011 3:33 PM

[Former Member]

there wont be any difference in the soap receiver adapter configurations.

If u want then u can go for party configuration in ur 2nd scenario where web service is outside ur landscape.

/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1

[former_member200962]

Would there be a party involved in scenario 1 or 2?

you can create 1 party for the WS not in your landscape....it is not mandatory to create a Party...

Would there be a difference the way the SOAP receiver adapter is configured? 

no difference.

How many SLD entries would I need?

why are you looking for SLD entry?