SOAP to RFC sync scenario

[Former Member]

Hello members:

we have a business scenario: SOAP to RFC sync

an external system (ABC) sends documentrequest thru XI SOAP adapter and makes an RFC call to a BAPI and gets back the resposne to the ABC system.we are handling 4 mappings. 1. request msg to a common msg 2. common msg to BAPI request3.bapi response to common msg 4. common msg to response msg(which is same as the req msg)

i have the request msg and common msg as external definitions. I did the following steps and wanted to

know if i am right.

1. there are no data type & msg type needed for this

2. 4 msg interfaces

i) document o/b sysnc

ii) document i/b sync

iii)common o/b sync

iiii) common i/b sync

3) 4 mappings

i) document to common

ii) common to bapi req

iii) bapi resp to common

iiii) common to req/response

4) 3 intf mappings

source intf********** target intf

i)document o/b common o/b uses mapping #1

ii)request :common i/b bapi i/b uses mapping #2

resposne:bapi i/b common i/b uses mapping #3

iii) common i/b document i/b uses mapping # 4

pls provide your inputs if my approach is rite? do i need to have 4 msg intefaces?has any made mappings where 4 mappings are involved ( without BPM)

Thanks in advance

[former_member206604]

Hi,

I think you will have only 2 interfaces.

1. Sync Outbound interface (SOAP Structure)

Two message types Req and Res

2. Sync Inbound interface (RFC Structure)

Two message types Req and Res

Then two message mapping

1. SOAP Request to RFC Request

2. RFC Response to SOAP Response

and finally one Interface mapping.

Thanks,

Prakash

[Former Member]

Hi ,

<i>1. request msg to a common msg 2. common msg to BAPI request3.bapi response to common msg 4. common msg to response msg(which is same as the req msg)</i>

Why you have taken common msg here...I think you can synchronously make a call to RFC and send the respose to SOAP.

sekhar

[Former Member]

Hi ,

I mean.....

1)Synchronous message interface for source.

2)No need to create target message interface.

3)Two message mappings

a)SOAP request and RFC request

b)RFC response and SOAP response

3)one Interface Mapping between SOAP synchronos message and BAPI.

sekhar

[Former Member]

hi,

Thanks for your replies. thats the straight forward way of doing it. but our business scenario requires the 4 mappings as i mentioned. the reason is they previously used an IBM middleware for this interface and now they are migrating to XI. so they used the common msg in their previous interfaces and want to retain it for future considerations like re-using the mappings with the common msg.Its like a Cannonical Msg.

[former_member206604]

Hi,

Are u using BPM for this..?

Then the Common Interface should be Abstract right.

Thanks,

Prakash

[Former Member]

prakash, we are not using any BPM. Thats where this gets confusing.

Can anyone suggest how do i do this scenario without using BPM

[former_member206604]

Hi,

To my knowledge you have to use BPM.

But still am not convinced in using the common type. What is that common type? Anyway the common type interface is not exposed anywhere out of XI it is used only inside XI. So my question is why should use that common interface? Use common interface as the outbound interface, I think thats the reason you are given the common interface.

Thanks,

Prakash

[Former Member]

They use that common msg b`se, as i mentioned earlier, they migrated from IBMs middleware to XI. they already had mappings done in that environment with that common object.So they want to include this common object in all their mappings.

Is kind of an unsatisfactory explanation...but thats the way it has to go.

[former_member206604]

Hi,

Then to my knowledge you have to go for BPM. I cannot think of any other workaround for this. Please let me know if you have any ideas..

Thanks

Prakash