|
|
 |
|
|
bTalk vs. EAI
The most common misunderstanding of bTalk is comparing it to an Enterprise Application Integration product. Although bTalk offers connectivity to SAP R/3 (which most EAI products do as well) - it is a completely different architecture and used for a different purpose.
In short, bTalk is used to develop e-Business applications that access SAP R/3 via the web browser real-time. Meanwhile, EAI solutions directly impact a company's system architecture and are geared towards non-real-time processing via middleware.
|
|
More Links
FAQs
|
| bTalk |
Enterprise Application Integration |
| Real-Time connectivity (required for the web) |
| Leverages the Web Application Server |
| Uses Web Technology (JSP, ASP, CFML, XML) |
| Component Architecture |
| Built for the Web Developer |
| Easy to Implement and Use |
| Generates all the code required. No configuration or implementation. |
| Realization of ROI immediately |
|
| NOT Real-Time connectivity. EAI tools use messaging. |
| EAI software is middleware. EAI does not leverage a web environment. |
| Does not use Web Technology (except XML). |
| Middleware. |
| Requires training and understanding of proprietary tools and technology. |
| Complex due to the requirement to support multiple applications. |
| Known for long Implementations and high risk of failure. |
|
|
|
|
The above comparison is not to discredit EAI Tools. EAI has a place and a purpose - to integrate multiple backend applications. EAI technology was NOT built for the web, and can not be used to create a REAL-TIME connection between the web application and SAP R/3. If you need to integrate PeopleSoft and SAP R/3 to ensure payroll is consolidated, then purchase an EAI package. If you want to allow customers to check sales order status on the Internet, or Employees enter time and expense, then use bTalk.
For more details on the comparison between bTalk and EAI solutions, click here.
|
|
