Different Listener functionality in MII 12.0.12 and MII 12.1.9?

[Former Member]

Dear All,

we have just upgraded our test system from version 12.0.12 to 12.1.9 and found some basic changes in the way listeners are supported. I would like to confirm what I have learned from my SAP Message.

In 12.0.12, we used the Listeners like follows:

- in SAP, we defined separate RFC destinations with unique ProgramIDs

- in MII, we defined a message listener for each of the RFC destinations

- IDocs and RFCs (like CONTROL_RECIPE_DOWNLOAD) from SAP to MII could be sent using the same RFC destination

- Messages to MII were handled by different Processing Rules. The same IDoc type could be configured in separate Rules, using separate Listeners, and therefore different transactions could be configured to process the messages.

In 12.1.9, it seems to be a different world:

- in NetWeaver, we have to create one two listeners for one SAP system, one XMIIIDOC and one XMIIRFC, using different ProgramIDs

- in SAP we need two RFC destinations, one for IDocs and one for RFCs

- for a specific IDoc type, only one Processing Rule can be used, because only one Listener exists for one SAP. A dispatcher transaction is needed to interpret the received messages and send it to the correct transaction that processes it.

The effect of the change is that we have to redesign all SAP to MII interfaces.

In SAP

- create new RFC destinations for the RFCs

- change all configurations that send RFC to MII, using the new RFC destination

- change all configurations that send IDocs to MII, using the new IDoc destination

In MII

- create new dispatcher transactions for the different message types to distribute the messages to the correct handling transactions

I hope I could explain it correctly. Is this the way MII 12.1 receives IDocs / RFCs from SAP ECC?

Regards

Michael

[agentry_src]

Hi Michael,

I guess I never would have anticipated using multiple RFC or IDoc Listeners as the parsing agent. Not saying it is wrong, just not an anticipated use. I thought that establishing a single connection was the "right" way to go and that the sorting and parsing would take place within the Processing Rule Editor.

But there is little or nothing in the documentation that would indicate multiple connections are invalid or not Best Practices. As you discovered, the connections in 12.1 are set up differently from those in 12.0.

I know you have a ticket open, but your solution is probably the fastest to implement.

Regards,

Mike

Edited by: Michael Appleby on Nov 21, 2011 2:35 PM

[Former Member]

Hi Mike,

I appreciate your quick answer (here and in the ticket).

I have also talked to Pedro Iglesias and we agreed that the way we have been using the 12.0 interface configuration is not really the "usual" way. I will think about an easy way to adapt to the 12.1 concept and using our "old" transactions.

One of the misleading facts may also be that we are using one central MII system with several connected sites and one central SAP system, instead of several MII systems in the sites that connect to one central SAP. So for us the different RFC destinations make good sense.

Well anyway... welcome to the new world ...

Regards

Michael