Hi Shyam.
In addition to the above information this link provides u the information about the features of XI and the way the other EAI (Integration Tools) differ from XI.
Differences bet biztalk and xi:
- SAP XI is largely based on J2EE (+ proprietary ABAP)
while BizTalk 2004 is completely built on .Net
(as opposed to its predecessors that were COM based)
- XI comes with more (technical) adapters in the box:
POP: Biztalk only supports SMTP
JMS: Biztalk only supports MSMQ and MQSeries
JDBC: BizTalk can only talk to SQL Server
- BizTalk has support for EDI, which is completely lacking in SAP XI
- SAP XI allows the use of XSLT but prefers its own event-driven (but
somewhat limited) message mapping solution
(the use of a 3rd party XSLT graphical mapper like Sonic StylusStudio is
an alternative)
BizTalk uses XSLT as its mapping technology and comes with a full blown
XSLT graphical mapper
- SAP XI is more resource hungry than BizTalk
- SAP XI is more complex and has a steeper learning curve
BizTalk is Microsoft-based therefore limited to one environment. It is
however cheaper and simpler to use for less complicated scenarios.
Comparison of XI with TIBCO
1) Tibco does publish/subscribe very well. There is no such concept in XI. You can however "fake" pub/sub
2) Has many adapters that are Tibco built..SAP relies on other vendors except for a few
3) Tibco does not have asynch SOAP/HTTP. XI does
4) Tibco UI is much more matured than XI. Simple and productive techniques (for example a JDBC adapter has ways of verifying connection etc..) Lot less features in XI
5) Concept of integration in terms of semantics and steps is a little more complex in XI
6) XI's monitoring, message level trace, message resubmission, pipelining, components monitoring are way ahead of Tibco.
7) XI lacks took like BW Tester to test the process before deployment ("activation")
😎 XI - no need to message with stupid ledger files like Tibco . It is much more clean
9) The process of deployment is easy in XI.. No need to worry about multiple moving components
Bottomline:
XI is evolving but it is a question of time when they clean up the weaknesses and catch/beat TIBCO
SAP BC:
The SAP Business Connector is a middleware product based on webMethods’ B2B Integration Server. It allows you to integrate with R/3 using open and non proprietary technology. SAP BC uses the Internet as communication platform and XML/HTML as data format. Thus it seamlessly integrates different IT architectures with R/3.
SAP BC allows for full bi-directional communication to and from R/3. On the one hand all SAP functionality accessible using BAPIs and IDocs can be made available to business partners over the Internet as secure XML-based services. On the other hand applications and information running on a remote web site can be instantly invoked by a simple SAP function call thus making the information of the Web available to an R/3 System.
SAP BC provides an XML layer on top of R/3 functionality so that other applications do not need any understanding of R/3 internal data structures or protocols. You can deploy SAP BC to simply but effectively achieve business-to-business integration between trading partners, thereby extending the reach of your SAP infrastructure to customers, partners and suppliers. Examples for applications may include real-time integration between supplier inventories and your SAP System or multi-vendor product, price and availability information and your purchasing application.
For more information refer this link;;;
Thanks,
Ramakrishna.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.