Reuse existing interfaces

[Former Member]

Hello experts,

Could someone please help me understand what the best approach would be to reuse existing interfaces.

For eg: I have a FIle to iDoc scenario. Now I would need to create another scenario say for eg; File to web service.

How best can I make use of the File side development which I am already done with.

I am a newbie trying to learn PI. I am on PI 7.1 EHP1.

Thank you.

[Former Member · Accepted solution]

If your incoming payload is the same, in the Integration repositiory reuse the Data Type, Message Type and Message Interface.

In Configuration, if the sender of the file is the same, reuse the business system and sender communication channel.

Thanks

Prati

[Former Member]

Thank you Rodrigo for your quick response.

These interfaces mentioned are just made up and not real customer scenarios.

I understood your approach. I could make out that, you are suggesting to club end to end interfaces into one model only if they have common sender or receiver interface. Please correct me if I am wrong.

I was actually planning to have a single model

SI(1) -> BO ->SI(2)

Is it advisable to do it this way? Experts, please enlighten us.

Thank you.

[rodrigoalejandro_pertierr]

I understood your approach. I could make out that, you are suggesting to club end to end interfaces into one model only if they have common sender or receiver interface. Please correct me if I am wrong.
I was actually planning to have a single model
SI(1) -> BO ->SI(2)

you will club interfaces in the model only if the data to transfer is common

for example you have to send data (create a customer) from X system, and from sistem Y you will update customer data. so you will define one SI with two operation.

at receiver side you will define 1 SI with two operation (also unless the target structure is an IDOC,in this case no SI is needed)

when modelling you will define one BO which will refers to both process component (take a look to page 15 point 4.3.5 in the PI BEST PRACTICES MODELING document)

once you define, for example, the sender SI, you will publich it in the SR, then any sistem apart of X and Y wich could need to create or update data in the target system will use the same ws, to do that, they will seach in the SI for customer services and if any of the services published apply for they need will use it.

another example could be any system need to create/update a new customer in the target system, to do that they could search the wsdl in the SR, get the wsdl and from they own app complete the data.

Edited by: Rodrigo Alejandro Pertierra on Sep 24, 2010 12:39 PM

[Former Member]

Thank you all for sharing your comments. This discussion would help many of us to set the basics straight.

As mentioned previously, I am trying to reuse already developed SI's.

Also I would like to do this via modelling of SI in ESR.

I have gone through the link provided by Hareenkumar above as well.

Here is the my understanding. COuld someone please confirm if this is the best way to architect it.

Scenario: We have three different interfaces.

a) File to File

b) File to web service ( Sender interface is similar to Sender of (a) )

c) web service to File ( Receiver interface is similar to that of (a) )

I will be creating 2 SI's. Each for Inbound and Outbound.

There will be one BO ( I am assuming this to be PI )

SI - Inbound will have two operation's, one for file and the other for web service.

SI - Outbound will have two operation's, one for file and the other for web service.

Please confirm if the above architecture is correct.

I could be totally wrong here. Looking for guidance from experts.

Thanks again.

[rodrigoalejandro_pertierr]

Scenario: We have three different interfaces.
a) File to File
b) File to web service ( Sender interface is similar to Sender of (a) )
c) web service to File ( Receiver interface is similar to that of (a) )
I will be creating 2 SI's. Each for Inbound and Outbound.
There will be one BO ( I am assuming this to be PI )
SI - Inbound will have two operation's, one for file and the other for web service.
SI - Outbound will have two operation's, one for file and the other for web service.

The number of SI wil depend of the kind of data to exchange. if those interfaces dont have nothing in common (data) yuo will have to define

2 outbound SI for file and another for web services.

now, the first two file exhange common data ( data concerning customer) you can define 1 SI_customer with two operation and another SI for the web services and another for the inbound file structure (scenario c)

when modeling will depend as i mentioned before of the kind of data.you wil define 2 models (one for interface a and b) and a second model for your interface WS-File(c)

take a look to this presentation:

PI Best Practices: Modeling

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/303856cd-c81a-2c10-66bf-a4af539b8...

if it is no clear let me know

Edited by: Rodrigo Alejandro Pertierra on Sep 24, 2010 12:18 PM

[Former Member]

Hi Radhika,

Publishing WS and reusing it is the ESOA architecture which is been incorporated in PI with its 7.1 version.

You will find many blogs and threads on SDN regarding this ESOA architecture.

Advantage over here is, once you will publish your web service in the Service Registry, you can use it N number of times, no matter what kind of scenario it is.

-Supriya.

[former_member200962]

I was wondering if we could publish the entire Service Interface ( via modelling of SI in ESR ) and reuse them accordingly.

Yes, you can publish the entire Service Interface.....but now are your interfaces involving SOAP (web-service communication)?

help.sap.com says that The Services Registry is a registry for Web services.

I am not sure how experts have suggested that publishing a Service Interface in Service registry for FILE to IDOC scenario will work?

Can anybody please confirm?

Regards,

Abhishek.

[rodrigoalejandro_pertierr]

hi,

I am not sure how experts have suggested that publishing a Service Interface in Service registry for FILE to IDOC scenario will work?

you publich in the SR all your service that belong to your integration landscape, you cand define the taxonomies,roles to access to ws,ect. so you access one place to see all service. (governance). each of this services encapsulate the funtionality that make it weakly coupled to the legacy or sap application. by this way you can call any of the ws in the SR from any system at any moment with out the need to be a PI scenario. thats why BAPIs, and server and client proxy also can be published as web services.

is a bit clear now? i have some SOA docuements i can share, i found then in the SDN i any want to look for some.

Enterprise SOA in a Nutshell

SOA Best Practices

Service Provisioning & Governance

SOA Governance Framework

SAP NetWeaver Process Integration and SOA Best Practices

Rgds

Rodrigo P-.

[Former Member]

If there are many design objects used across ur multiple interface which are common in this case u can create one common SWCV and create all ur common design objects in the same, and create the dependency between this Common SWCV and other SWCV which is going to reuse the Design object.

It is depends on u -how u r going to design ur SWCV and Design objects.,

chirag

[Former Member]

Thank you Pratichi for the quick reply.

Actually I was going through documentation on PI 7.1 EHP1 and I saw that we could publish services to SR and reuse them.

Though I have fully not understood these, I was wondering if we could publish the entire Service Interface ( via modelling of SI in ESR ) and reuse them accordingly.

Maybe I am not making any sense here. But was looking for guidance from experts.

Any help/directions would be appreciable.

Thank you.

[Former Member]

Hi Radhika,

Check the below blog, this may help you to know about the reuage of service interfaces:

/people/abhishek.salvi/blog/2009/07/31/using-service-interfaces-now-reuse-one

Thanks,

[Former Member]

Actually I was going through documentation on PI 7.1 EHP1 and I saw that we could publish services to SR and reuse them. 

You can't use this functionality in the scenario that you have quoted above.

No easy way other than reading and hands-on. There are many documents which has described this topic in details and in simple language.

[rodrigoalejandro_pertierr]

the idea of reusing WS publiched in the SR is that any app internal or external can point to the WS coz the functionality itseft is encapsualted in the WS. thats onecore point of SOA make the functinality loosely coupled from the app.

now in PI you can reuse it coz you can call any of this WS and avoid to develop a new app with the same functionality. by this way you avoid duplicate functionality, and the mantain is also more quickly so the TCO is minimum and anticipate further changes if you have the propers models in the ESR.

hope you have a better aproach. if not let me know.