Service Publication from PI Repository vs Directory vs SOAMANAGER

[Former Member]

Hi

I have question on the service publication states when it is published from ECC and PI

Let say we have a scenario where we need to call a Server Proxy via PI.

When I publish the service from PI Repository(inbound service interface), it is registered in SR as

Service State - Modeled

System - <PI SID>_ESROn<Host>

No Endpoint in this case, since it is not configured.

I implement the server proxy in ECC and configure endpoint publish it through SOAMANAGER , It is registered separately

in SR as

Service State - Configured

System - <ECC SID>On<Host>

But this is not via PI mediated and also publication system is different.

Now I am confused, the same service, when I published from PI-ESR, it is "Modeled" with PI system name.

When I Publish it from ECC, It creates separate entry with state configured(if I define endpoint for it)

Why there is an option/need to publish Service from PI Repository at all, when it remains in the model state?

Another question:

There is an option to publish the service from PI Directory too. It is available from Sender Agreement(for the Outbound

Service Interface for the same Proxy). When I do it from here.. It makes another entry in service registry

Now state is configured But the Service name is not what I published from PI-ESR.

I published the inbound Service i/f from ESR. The service I publish from PI Directory is Outbound SI

So If I need to use PI mediated publication it will always be Sender Agreement (Outbound interface) with SOAP adapter,

right???????

Again I don't see any point publishing Inbound Interface from ESR. coz I can not configure it.

Can you explain me how PI publications(from ESR or Directory) affects the SR entry?

Thanks,

[Former Member · Accepted solution]

Hi,

First you need to understand role of SR, it is just yellowpage to locate service it is nothing to do with actual implementation or runtime of service.

If you notice provider system is part of key in SR so same service with same name you can publish from 'n' systems.

SR is also manage or support lifecycle stage of service so you can see different state like "Modeled" etc.

>Why there is an option/need to publish Service from PI Repository at all, when it remains in the model state?

It is not often used but it is required when you want to share your metadata with different implenting tools like java or .net they can locate service from SR and do the implementation in their respective technologies. You can even publish service in SR by providing url of wsdl in SR.

>Now state is configured But the Service name is not what I published from PI-ESR

making service out of sender agreement is old feature of PI (since 3.0), sender agreement behave like webservice and any external application call it via SOAP and then it trigger message execution in PI, so it look like following:

consumer appl -> Sender agreement (trigger->PI messaging [receiver determination+transformation etc])

>Again I don't see any point publishing Inbound Interface from ESR. coz I can not configure it.

You are missing point here, it is NOT mandatory to publish service at all but it is option given so that modeling of serivce is always segrated from implementation and publish is required not for consumption of service but to extract meadata as well i.e. if have team of java developer who want to develop webservice which is configured in ESR then they have 2 option, either locate service in SR or connect/download wsdl from ESR directly (connection with ESR is easy as both toolinmg developed by SAP) but same is not true for any other webservice development tool and they will prefer to extract metadata from SR.

I hope this clarify your doubts.

Regards,

Gourav

[Former Member · Accepted solution]

Hi Gaurav,

Thanks for the clarification. Things are getting clear now in eSOA.

Regards,