XI - Can it handle non-SAP to non-SAP systems integration?

[Former Member]

Hi,

I would appreciate hearing from others on this forum on whether

> XI can handle non-SAP to non-SAP systems (it can do SAP to others quite well)

> Has anybody tried replacing existing solutions like MQ, Tibco etc?

> Problems faced, lessons learned etc..

We are actually going through the exercise of evaluating such an option but would be grateful for any info.

regards

m

[Former Member · Accepted solution]

Hi Maddux.,

In XI File to file and java based all these senarios are

Non SAP. That means XI can handle.

Regd's

Hari

[Former Member · Accepted solution]

Thanks Hari.. I am also looking at a higher architectural perspective for message size, volumes, ability to integrate with non-SAP systems like say Oracle DB, etc..whether there is a need for substantial SAP knowledge because the developers would be SAP unaware because there systems are legacy..

regards

m

[Former Member · Accepted solution]

Maddux:

Basically wherever Biztalk can be used, XI can

also be used. So Xi is capable to handle nonSAP

to nonSAP situations.

There is a recent thread about using Biztalk or

XI. So the answer to your second question is that

how much you can afford if you go XI.

Please give points.

[Former Member · Accepted solution]

Hi maddux,

xi is the integration plattform. It has some positive aspects if you got other SAP systems. But you do not need to have them.

SAP XI has a lot of adapters to connect to lot of different systems via FTP, JDBC, SOAP, HTTP etc.

You don't have to be an SAP-classic expert to use XI.

Hope this helps

Regards Mario

[Former Member · Accepted solution]

Hi Maddux,

There are few blogs our seniors has been done useing xi,

exchangeing messaage useing xi form sap to non sap like

oracle, mq, sql server,

Here i will send few blog look at them.

/people/laxman.molugu/blog/2006/08/13/integration-with-databases-made-easy-150-part-1

/people/sriram.vasudevan3/blog/2005/02/14/calling-stored-procs-in-maxdb-using-sap-xi

/people/alessandro.berta/blog/2005/10/04/save-time-with-generalized-jdbc-datatypes

http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm.

[Former Member · Accepted solution]

Hi Maddux,

http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

the above blogs will explaing the jdbc reaciver

Hope these clear your dought..

Regd's

Hari

[Former Member · Accepted solution]

Thanks guys.. Has anybody replaced an tried and tested middleware with XI i.e. were using Tib, WebMeth, MQ etc but moved to XI because the shop is now SAP centric. I have used SAP to non-SAP and looks fine. I am looking for any experience in b/w non-SAP to non-SAP.

Thanks for the enthusiastic responses.

m

[Former Member]

XI would be best fit for SAP – SAP or SAP – Non-SAP integrations. If U wanna go for pure Non-SAP to Non-SAP integration, better choice would be Non-XI technology. And its depends on the available adapters by XI. If your source or target system adapters are not available with in XI, U need to put extra afford for the adapters.

Finally the source or target is not SAP R/3, better to go for non-XI integration tools.

In some cases U can go for XI for Non-SAP to Non-SAP integrations, for ex: U wanna migrate data like CIDX or PIDX, which is XI supported adapter specific data to customer system. U can go for XI <b>CIDX/PIDX</b> adapters in XI.

From...

Yallabandi...

[Former Member]

Thanks all ! (Sorry for the delay)..

In summary, for non-SAP to non-SAP, XI seems to be the second choice unless it is a SAP centric shop. But from a maturity point of view, I think that SAP Xi may become better and challenge the existing market leaders purely because of it's excellent integration abilities with SAP and usage of open standards.

Thanks

m

[henrique_pinto]

XI can handle virtually any nonSAP2nonSAP scenario, given that you can afford to develop/pay for custom adapters. 🐵 By default, it accepts almost all of the most used industry/web standards (I'd point EDI as an exception, but seeburguer's EDI adapter handles that very well).

The problem is that XI is really expensive. So, if you just want to integrate simple scenarios, for example using Soap or http, it'd be better to buy or develop another solution. In the end, XI is affordable almost only for the big companies, which already use SAP most of the times (not by coincidence, I'd say). 🐵

Regards,

Henrique.

[Former Member]

Hi,

Currently, we are implementing an XI project to replace the old solutions which is based on Tuxedo for one of our customers.

The motivation to do this is that they are implementing a SAP system at the same time. I'd like to say if you are facing a non-SAP to non-SAP situation, XI maybe not the best choice.

Regard,

Ben