XI or MQ or both

[Former Member]

Hi All,

Allow me to explain my issue in detail. We are doing a SAP Implementation where we have around 4 SAP products other than R/3. XI is also used since it is mandatory for SCM. We need to finalise the design to connect the SAP systems to several other legacy systems (running on different platforms) which are inter-connected through MQ Series. So basically XI and MQ are mandatory for the above said reasons. We have 3 options to do the integration between SAP and the other legacy systems.

1) Connect SAP through XI (no MQ for this interface ) to each and every legacy system

2) Connect SAP through MQ alone (no XI for this interface) to and every legacy system

3) Connect SAP through XI to MQ and from there to whichever legacy system

We are currently inclined to Option 3. Here we just need to configure XI to one JMS adapter and let MQ take care of the other legacy systems. Also according to SAP, XI should integrate better with SAP on the other side. But we are concerned if there are going to be serious resource issues and whether troubleshooting at a later point of time is going to be difficult.

For Option 2 to work, MQ should have a SAP adapter. I believe that has to be separately purchased at a cost. Can you tell me what are the pros and cons of this option if at all the adapter is purchased.

I think Option 1 can be ruled out as MQ is a tested and proven Middleware product and should be preferred over XI unless there are other reasons. Also MQ is anyway used for inter-connecting the legacy systems.

Would like some insight into my lengthy problem I have elaborated this much so that there will be more understanding.

regards,

Madhavan

[Former Member · Accepted solution]

Option 3 is the preferred approach.

I do not see resource issues later. Your MQ should already be running on an established hardware configuration and it should be running without problems.

The XI landscape is totally separate from your MQ deployment, you would need an extra JMS server that may need running on a separate server, that is the only extra piece of hardware that i can see needs to be managed.

We are doing the same thing for a customer too. We feel that this is the best approach; We need to appropriately plan for the hardware sizing etc. for this approach. Overall, this is the most flexible and manageable approach going forward. Hope this helps.

[Former Member · Accepted solution]

Thanks for the response. I would appreciate some more input and sharing of experience from others also.

regards,

Madhavan

[Former Member]

HI,

I still haven't got any feedback on this topic. Can someone throw some light here.

regards,

Madhavan