Using Oracle SAP Adapter and IBSE for inbound IDOCs

Question

I have been able to successfully use the Oracle SAP Adapter (e.g., IWAY) using the IWAY Business Services Engine (IBSE) to call a BAPI and have information returned. This use case is well documented and seems to be reliable.
However, I have had difficulty finding any examples where IBSE is used with IDOCS. In my case, I would like to have SAP send an IDOC and receive this IDOC in a Fusion 11g environment. I see conflicting statements in the document. On one hand, Section 3 of this document
http://download.oracle.com/docs/cd/E15523_01/doc.1111/e17057/config.htm#BABBGAAH
States "Events are not applicable when using a BSE configuration."
On the other hand, I see lots of documentation that says that you need to configure an Event in order for the IDOC to be sent to the proper destination. IBSE gives the ability to define events for IDOCs but the events are limited to either RMI or JMS. I have looked at the format of the JMS message and it looks extremely difficult to setup.
Has anyone done this before?

Answer 1

Let me try what ever I can to answer.
Loss of IDOCS should not happen. Are you starting the channels in iWay test tools while the JCA adapter is also running?. That should not be the case. iWay Test tools is only for design time purpose. It is not required for runtime. ie. Create channels and test the IDOCS being received. After that stop the channel and start running the server.
I suspect that starting channel in iWay test tools and JCA adapter/BPEL simultaneously will definitely result in IDOCS loss. Some of the IDOCS will come to iWay test tool while others will go to JCA/BPEL.
Regarding 2, lets us discuss this after this loss of messages is solved.
"Another issue that we have with the JCA approach is the requirement to have have a separate channel and a separate program ID for every IDOC. In our SAP system, we have thousands of IDOCS so having to setup a different channel and program ID for each one is going to be a difficult task".Yes. Initial versions of adapter used to support receiving all idocs on same channel. In your case MATMAS05/IORDER01 are received on same programID and customers used has logic to identify what idoc was coming. It was observed that complexity of the application increases exponentially with increased idocs and the debugging effort.And also the interface is not clean. That is the JCA end point cannot be assocaited with a specific WSDL so you will not what you will receive and of what type. To ease this, later version of adapter supported this feature that each idoc type is assocaited with a specific program ID. MATAS05--PID1, IORDER01--PID2. Adapter will ignore if MATMAS05 is sent on PID2.
In OSB we have concept of AnyXML service but I doubt if BPEL has such concept. If I remember OSB smart connect supported your exact use-case, but in later version it was decided to discontinue AnyXML inbounds.
Are you really planning to use hundreds of IDOCS on same PID?. Did you think of debugging complexity in such application? If you really think this need to be supported, please raise an enhancement request with Support. Product management will review your request for further action.
Thanks
Manoj