SOAP Receiver

[vuyyurujyothi]

Hi All,

I have scenario: RFC to SOAP.

Sender Side 1 BAPI and Receiver side 3 WebServices belongs to one system. i.e., target side 3 message structures and business service.

As sender side RFC is used, no need to Outbound Interface.

I have one external definition which contains message types for all 3 web services.

I have created 3 Inbound Interfaces.

Created one message mapping as 1:3 mapping and also same as interface mapping.

Could you pls suggest me how to do configuration for this?

Regards,

Jyothi.

[Former Member · Accepted solution]

Hi Jyoti,

As you have explained you have a RFC to Webservice scenario.

Lets assume your Webservices do different operation and those are different Service interfaces from PI's point of view.

They are ever from different business system.

So Config would be like this:

Receiver determination:

RFC sender(ECC)----to----All 3 Business systems.

Interface DEtermination:

Extended: As you are using 1:3 mapping the interfaces should be determined dynamically as well depending on the mapping program(different message target type).

Sender Agreement:

1 with one RFC sender cpomm channel.

Receiver Agreement:

3 receiver agreements for 3 business systems with 3 comm channels.

Cheers,

Abhishek Paul.

[vuyyurujyothi · Accepted solution]

Hi Abhishek,

But target side there is only one Business Service.

Is there any possibility to config only with one Business service?

Thanks,

Jyothi.

[baskar_gopalakrishnan2 · Accepted solution]

I think it is possible with one business service for 3 soap adapters.

[Former Member · Accepted solution]

Hi Jyoti,

In receiver side if you have only one business system them its pretty straight instead of determining three you provide just one receiver.

Main concern here of your is interface determination.

Cheers,

Abhishek Paul

[vuyyurujyothi · Accepted solution]

Yes Abhishek,

Interface Determination is my concern.

Regards,

Jyothi.

[Former Member · Accepted solution]

Hi Jyoti,

If some one has mentioned Extended Interface Determination, it is not wrong coz you might be using PI 7.1 that does not specify it to be extended but till PI 7.0 we needed to exclusively specify extended interface determination.

Now you have 3 interfaces and that holds 3 different message types that you are achieving through 1:3 mapping but at runtime when you dynamically determine the interface depending on the message type through single mapping program its an extended interface determination PIu2019s point of view.

So go ahead, if itu2019s PI7.1 or above your purpose will be accomplished.

Cheers,

Abhishek Paul.

[baskar_gopalakrishnan2]

This is multimapping. Are u doing BPM or without BPM.

ID objects

1 sender cc, 1 sender agreement, 3 receiver agreement, 3 Interface determination, 3 receiver soap cc, 3 receiver agreement.

[vuyyurujyothi]

Hi Bhaskar,

Without BPM I am doing.

SENDER BS

Sender CC

Receiver BS

Receiver CC1

Receiver CC2

Receiver CC3

Sender Agrmt

Receiver Agrmt1

Receiver Agrmt2

Receiver Agrmt3

Interface Determination1

Interface Determination2

Interface Determination3

What about Receiver Determination?

Is the above configuration is ok?

[baskar_gopalakrishnan2]

Without BPM means 1 Receiver Determination and 1 Interface Determination.

Mapping decides respective webservices. ID is extended here.

[vuyyurujyothi]

Hi Bhaskar,

There is no need of Extended Interface determination as message needs to go to all 3 web services always.

Regards,

Jyothi.

[baskar_gopalakrishnan2]

Thanks for the elaborate requirement.