cancel
Showing results for 
Search instead for 
Did you mean: 

ASYNC -> BPM -> SYNC

Former Member
0 Kudos

Hi,

I am trying to send a SELECT message to a JDBC adapter.

SEND

mode: SYNCHRONOUS

Synchronous Interface: mis_select

Request Message: select_req

ResponseMessage: select_res

mis_select is a Synchronous Abstract Inteface

select_req -> mi_select_req is a asynchronous abstract interface

select_res -> mi_select_res is a asynchronous abstract interface

When I try to activate my integration process I get the following error:

Message to be sent select_req and synchronous interface mis_select are not of the same type.

And the same for the response mesage.

I have looked at the message types in both interfaces and they are the same type as the synchronous interface.

Anyone knows what this error is about ?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Hans,

I have a similar JDBC receiver step in one of my ccBPMs.

I think there's a possibility that your Synchronous Abstract Interface is defined backwards. i.e. The request is the response and the response is the request.

From what I see, the "Output message" (in sync.Abs.Interface properties) should be the select (called <b>request message</b> in BPM step properties) and the "Input message" should be the response (called <b>response message</b> in BPM step properties).

Best Regards,

Ofer

Answers (3)

Answers (3)

Former Member
0 Kudos

Good Luck with your next questions!

Message was edited by:

Ofer Even-Tsur

Former Member
0 Kudos

Hi Hans!

The receiver determination only sees non-abstract (plain) interface mappings.

Cheers,

Ofer

Message was edited by:

Ofer Even-Tsur

Former Member
0 Kudos

Hi Ofer,

thanks for replying, indeed, thats the problem, with sync those must be switched ! mmm but now I cant use my synchronous interface in my reciever determination on the SENDER section, do you happen to know why ?

Message was edited by:

Hans Hahn