IBM InfoSphere Information Server vs. Microsoft BizTalk Server

Information Server is extremely useful to replace manual developments that require a lot of coding effort. It significantly increases the productivity of the initial development and the future maintenance of the processes since it has a visual development environment with self-documentation.

BizTalk is well suited as middleware. Where you wish to translate an input file into an output file and send it to some endpoint. In our case, we used it to convert and send files to SAP. In many ways, it very flexible, and you can do almost anything you want with it. In many ways, it's a better solution than your SAP XI or PI as middleware, since it's much less expensive, and allows you do interface with non-SAP systems.

Incentivized

• IIS best for ETL ,not ELT , and many and diffrent source systems.
• It also can process big data , unstuctured data
• It is not only DWH , you can use infosphere for analys and see the bigger architecture of your OLTP systems

Incentivized

• It is very user friendly. Users can change rules during run time and change workflow.
• Huge capacity for queueing messages. It supports all types of adapters like Oracle, Salesforce, SMTP, FTP, etc. Also users can built custom adaptors.
• If users want to dynamically deploy their solution without any downtime, this is a perfect solution. BizTalk will be a good fit, especially for public-facing websites.
• Well-proven in the market. I used it when developing a website for Virgin Trains, catering more than 800K user requests per day.
• Helps in load balancing.

Incentivized

• I would be nice to have a new web development environment for DataStage.
• Connectivity Packs such as Pack for SAP Application are a little pricey.
• It is confusing for new developers the possibility of developing jobs using different execution engines such as Parallel or Server.

Incentivized

• Microsoft BizTalk is over engineered for some situtations
• Microsoft BizTalk can be frustrating to use as it forces you to use the GUI as opposed to code
• Microsoft BizTalk is very resource intensive to create integrations

Incentivized

• Scale of implementation
• IBM techsupport

Incentivized

BizTalk will always be required at this hospital.

Incentivized

I gave a 7 because this product BizTalk does need time and training to get familiar with the usability and features, it is not that easy to use.

Incentivized

BizTalk Server has been supported for more than 15 years. It is well proven in the market. Microsoft has provided excellent support with technical issues.

Incentivized

Make sure you have everybody and all depts. On board during testing on test server.

Incentivized

DataStage is more robust and stable than ODI The ability to perform complex transformations or implement business rules is much more developed in DS

BizTalk was selected here mainly because it is easy to integrate to a .NET application (most of them are Web Service, WCF SOAP, WCF REST and Web API) and many backend databases are Microsoft SQL Server. Another benefit is that the monitoring job is easy to set up and centralize with other .NET application monitoring jobs.

Incentivized

• Productivity of the development of integration processes.
• Better documentation and governance.
• Reduce training costs of various technologies.

• A positive impact has been the quicker turnaround time of a part request and that part showing up in SAP using Biztalk as middleware.
• A somewhat negative impact has been the somewhat insufficient error logging/message capture settings that Biztalk provide. This has caused occasional delays when attempted to create parts for the business.
• A somewhat negative impact has been the need to have a specialized developer who understands Biztalk to troubleshoot issues with the Biztalk and SAP interaction when creating parts, and when adding new fields to the parts.

Incentivized