Is it possible to deactivate JDBC response?

[Former Member]

Hi gurus,

My environment: PI 7.31 Java-Only.

Already i have a sync scenario 1 as below:

Sync Proxy SI_Delivery_os <--> JDBC Table 1

It works well.

Now I want to add an async scenario 2:

SI_Delivery_os --> JDBC Table 2.

In this scenaio Response are not required.

As I know RequestResponseBean or Async/Sync Bridge Module could be helpful, but they are used in Sender Channel.

How deativated the response of Scenario 2?

Thanks a lot in advance!

Regards

Rene

[iaki_vila · Accepted solution]

Hi Rene,

You can use RequestOneWayBean to sync/async conmmunication: http://help.sap.com/saphelp_tm80/helpdata/en/45/20ccefc2180733e10000000a155369/content.htm

Regards,

[Former Member · Accepted solution]

Hi Vila,

I'm trying now.

If it works, let you know.

Regards

Rene

[ambrish_mishra · Accepted solution]

Hi Rene,

Also look at the link http://scn.sap.com/community/pi-and-soa-middleware/blog/2011/03/07/unleash-synchronous-scenarios

Ambrish

[Former Member · Accepted solution]

Hi Ambrish,

I have read this thread. This is about Async --> Sync Scenario, but not Sync -> Async.

Except this, during test, i noticed, that sync Sender to multiple Receiver is impossible, isn't it?

So I have to ask ABAP developer to create an async outbound inteface for table 2?!

Regards

Rene

[ambrish_mishra · Accepted solution]

Hi Rene,

Yes it is not possible so it is better to create a separate interface.

Ambrish

[ambrish_mishra · Accepted solution]

Hi Rene,

Yes it is not possible so it is better to create a separate interface.

Ambrish

[Former Member · Accepted solution]

anyway, after long-term working with PI, i'm sorry to say, that PI is not an optimal tool to make everything run.

Just pushing, is the best solution.

Any complicated business logic makes PI headache.

[iaki_vila · Accepted solution]

Hi Rene,

You  can always ask for further innovations in the idea place https://ideas.sap.com/ct/s.bix?c=97F64433-5773-403E-A7C6-D7EB3BD6428D, if we share our experiences and demmands this tool could be better and better.

From XI 2.0 this tool has evolutioned considerably, i admit that it has some gaps but for the 90% of interfaces it runs perfect, at least with my experience, and the other cases is always an intereseting experience to avoid the routine

Regards.

[ambrish_mishra · Accepted solution]

Hi Rene,

I am one of the staunch admirers of this tool and am yet to see a strong middleware for SAP integration.

In retrospect, Sync message to multiple inbound interface not possible is logical since getting response back for one message from 2 recipient systems is not possible.

As Inaki rightly said, there might be some gaps.... but this one is not a gap

Hope you agree.

Ambrish

[ambrish_mishra]

Hi Rene,

I can confirm that Michal's suggestion of having the inbound interface as async will work.

Ambrish

[MichalKrawczyk]

hi,

create the input service interface as async and not sync - this approach works with some web services so maybe it will also work on jdbc

BTW

proxy SI_Delivery_os also needs to be async

Regards,

Michal Krawczyk

[Former Member]

Hi Michal,

thanks for prompt reply!

Perhaps you have not understood me correctly.

The sync proxy SI_Delivery_os cannot be changed to async!

This proxy must serve 2 inbound service interfaces in parallel: 

sync JDBC receiver to table 1 and

asyc JDBC receiver to table 2 in the same time.

I have tried to create an async service inteface for table 2 and create Operation Mapping. But it is not allowed to map sync SI to asyc SI.

More idea?

Thanks and Regards

Rene

[MichalKrawczyk]

hi,

>>>The sync proxy SI_Delivery_os cannot be changed to async!

then you need to create a new proxy - SI_Delivery_async and use it in the code,

there's no normal way of handling that in another way (bpm usage for this would be crazy...)

just add this new async SI

Regards,

Michal Krawczyk