File->rfc->soap->rfc

[Former Member]

Hi

I have a scenario File to rfc it has to update the rfc table & the same file request has to call soap after updating the rfc table & the response from soap has to update rfc again....

I have designed bpm

1)Receive step asyc to receive the file

2)Send step aschyronus to update the rfc

3)Send step sychronous to call the soap

4)Transformation step to convert soap response to rfc input.

5)Send step aschyronous to update the rfc..

Do i need to use S/A bridge in my scenario...

Can any one you please breif me what steps are going to involve in bpm & Coresponding Message mappings & the interfcae mapping.

Any responses would be greatly appreciated...

I have seen all the related weblogs...

Thanks

ram

[Former Member]

Moorthy,

In third step bpm

Send step Sync - ( after getting the response from the RFC , send the file message to the SOAP)

I have taken Inbound interface synchronous

Input Message :File Request

OutPut message : Rfc Response

And the mappings for soap

File to soap request & soap response to an rfc response

When i try to activate the message interface

<b>Error</b>

***Activation of the change list canceled Check result for Message Interface Filesoaprfc_ib |

Message interface Message Interface Filesoaprfc_ib | urn:epcGlobal:xsd:1 references an RFC message and a non-RFC message****

This is where i am struggling from last 1 week,Can u please tell me the alternate how can i proceed..

Thanks

Ram

[moorthy]

Hi,

<i>Send step Sync - ( after getting the response from the RFC , send the file message to the SOAP)</i>

It is similar , what you did for the RFC right ?

There should be one inbound Synchronus interface of webservice/wsdl ie. for SOAP

Don't take what as below.

<i>Input Message :File Request

OutPut message : Rfc Response</i>

Your mapping should have FileRequest to SOAP Request

and SOAP Response to Some ResponseType called Response2.

This Repsonse2 is sent again to RFC and in this case your mapping should have

Response2 to RFC request

RFC Response to DummyResposne whatever you are using in first RFC call.

CHeck it in this way.. Hope it will work here.

Regards,

Moorthy

[Former Member]

Thanks for the responses

Moorthy i have worked using the steps which u have sent,i have few errors,i will double check again & i will post the errors.....

Thanks

ram

[Former Member]

Thanks Moorthy,

I have already done the scenario in weblog,I am going to take synchronous step to get the rfc response.Can u please brief me the steps in bpm.Because i want soap request to be triggered after updating the rfc table,the response has to update rfc again.I have related function modules,where it can send the request & response...

ram

[moorthy]

HI,

In BPM~

1) Receive Step to Receive the Fie Message

2) Send Step Sync ( ie, Recieved File message input to RFC)

• If you want you can check some Repsonse status for successful, before sending to SOAP

3) Send step Sync - ( after getting the response from the RFC , send the file message to the SOAP

4) After getting the Response update the RFC again, Send Sync

I think all mapping you can handle outside the BPM.

1) For BPM to RFC:

Req mapping between File Req an RFC Request

Respoonse Mapping between RFC response to File

Response( Some dummy message type to get the Response)

2) For BPM to SOAP:

Req Mapping between File Req to SOAP Req

Response Mapping between SOAP Response to SecondRFC Response

3) For BPM to RFC : last one

Response of Second Mapping to the Req of RFC

If you want Resp back to the BPM

Hope this helps,

Regards,

Moorthy

[moorthy]

HI,

If Async ., send to RFC means, how can you identify, is RFC table has been updated?

If it is Sync call to RFC, then you can go with the simple design of blog-

/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit

REgards,

Moorthy

[Former Member]

Hi,

The step are good if you don't need to see whether the uopdate has happened in RFC and based on that you want to go ahead.

<i>1)Receive step asyc to receive the file</i>

MI- Oubound async

MI- Abstract async1

2)Send step aschyronus to update the rfc

MI-Abstract async1 (send step will be async)

The above is if the data structure requred to be sent to RFC is same as in Abstract async1 else do a transformation from MI-Abstract asyn1 to abstract async2

3)Send step sychronous to call the soap

Here also if the metadata is not same as that of MI abstract1 then transformation step to move data to abstract sync3 (you need to have two message Interface here request response

4)Transformation step to convert soap response to rfc input.

response of the soap will be the input and output would be another MI for file metadata

5)Send step aschyronous to update the rfc..

MI for file metadata in previous step.

6. MI -Inbound async to pass from IP to the service you are using.

Hope this helps.

Regards

Vijaya