Cons of SeeBeyond to BizTalk Migration

· Cannot be decoupled from the proprietary data storage layer – Microsoft SQL Server. This means a deployment must also acquire SQL Server licenses even though it may be using a different DB solution.

· Debugging the main business process logic - orchestrations – is non-standard, circuitous, and discouragingly complex (stepping through code debugging involves understanding the XLang library) – although nearly every error message has profuse help available from the online community.

· BizTalk development involves little coding but a lot of configuration. Configuration errors are cryptic, difficult to trap, trace or debug – resulting in once again defaulting to help from the community rather than the software itself

· UML compliance for modeling the business processes (Orchestrations) is missing

· Recovery of failed messages is manual and not automated

· Monitoring is dependent on additional software like Microsoft Operations Manager and is not available out of the box

· Runs only on Windows and not on other server operating systems like UNIX flavors. Although the Microsoft server platform is the fastest growing server system, this is still limiting to its adoption base for non-Windows deployments. The product is also reliant on core OS services like security, scale out and authentication.