OpenText acquired BPM solution Metastorm in 2011, and has rebranded the product as OpenText MBPM. It is an alternative BPM solution to OpenText's primary BPM offering called OpenText Cordys Business Process Management.
We used BizTalk Server as we had all other integrating applications developed on .Net and using Microsoft development environment. Kafka is best if integration is between non-Microsoft applications. We had few adapters developed using Microsoft .Net framework. BizTalk is well …
Microsoft BizTalk was chosen as the integration hub many years ago. It is still in use in a number of places in the organization however we are no longer developing specifically for this product in mind. We now develop in a number of places and if Microsoft BizTalk is the …
We did look at Jitterbit dataloader from Salesforce.com. Jitterbit seems like a pretty decent solution if you are doing a lot of uploads into Salesforce.com. However, its not nearly as flexible as Microsoft Biztalk is. Biztalk allows you to create any type of custom solution …
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 …
We found that OpenText MBPM held its own quite well against IBM BPM. We ended up choosing OpenText MBPM due to the analytics, complex routing, and the ease of SOA service integration. Furthermore, the ability to quickly develop simple User interfaces make this tool a daily …
Before first using Metastorm at a previous company, I reviewed 30 systems, shortlisted 4 and chose Metastorm as being intuitively the easiest to develop with. We have recently looked at a number of alternatives but decide to stick with OpenText BPM.
I have evaluated [business process management] products such as Nintex, K2, and Intapp. Each of these products are excellent options, and each have strengths and weaknesses. Metastorm and K2 in my opinion offer more flexibility, but require a higher level of technical ability …
Features
Microsoft BizTalk Server
OpenText MBPM
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
Microsoft BizTalk Server
-
Ratings
OpenText MBPM
7.0
Ratings
10% below category average
Dashboards
00 Ratings
7.90 Ratings
Standard reports
00 Ratings
9.00 Ratings
Custom reports
00 Ratings
4.00 Ratings
Process Engine
Comparison of Process Engine features of Product A and Product B
Microsoft BizTalk Server
-
Ratings
OpenText MBPM
7.3
Ratings
13% below category average
Process designer
00 Ratings
8.10 Ratings
Process simulation
00 Ratings
7.10 Ratings
Business rules engine
00 Ratings
9.00 Ratings
SOA support
00 Ratings
6.00 Ratings
Process player
00 Ratings
7.00 Ratings
Support for modeling languages
00 Ratings
8.00 Ratings
Form builder
00 Ratings
6.90 Ratings
Model execution
00 Ratings
6.10 Ratings
Collaboration
Comparison of Collaboration features of Product A and Product B
Microsoft BizTalk Server
-
Ratings
OpenText MBPM
7.6
Ratings
9% below category average
Social collaboration tools
00 Ratings
7.60 Ratings
Content Management Capabilties
Comparison of Content Management Capabilties features of Product A and Product B
It is perfectly suited if some heavy operation needs to be automated where jobs can be queued up. Scalable app which is required to develop in a lesser time frame. Good for when users should be able to change rules more frequently without any downtime, like promotions. The server is well proven in the market. BizTalk server is the best fit if all other integration adapters are developed using Microsoft applications and if all applications are meant to be processed on a Windows environment.
OpenText MBPM is well suited for rapid application development where process workflows are well designed in a detailed environment. A servicing organization could benefit from being able to manage and design complex case management processes and applications. It is not suited for the automotive industry where complex custom engineering processes exist within product engineering (vehicle) and manufacturing plants.
BizTalk uses Microsoft Visual Studio as the IDE (integrated development environment) tool, and it's very easy to use.
The orchestration engine of BizTalk addresses resource issue very well for long-running business processes by dehydrating and rehydrating orchestration instances.
BizTalk is very easy to integrate if the development is mainly on the Microsoft software family.
BizTalk needs to be better at tracking down errors after the fact. Input files by default get deleted after processing successfully, unless you specifically specify that they don't. This can be an issue where you need to see what the input file contained, since you may have errors showing up in your target platform, in our case this was SAP.
BizTalk logging needs improved. It needs to be able to log the content of the messages it sends and receives. It would be good if the log had a link to the input and output files.
BizTalk needs to allow a simple way to preserve the input and output files for debugging purposes. A master setting on the orchestration would be helpful for this.
The Metastorm process engine is based on an older version of .NET. Updating to a newer version would resolve several known issues with .NET email functionality.
Metastorm builds web pages at run time. While the UI presented to the end user is fine, the Document Object Model is convoluted and subject to change with new releases. Providing a more simplified DOM or at very least a custom function to replace document.getElementById() would make client-side scripting a much more powerful tool.
One function that I've seen Metastorm competitors do well, is email wizards. Having a WYSIWYG email editor would be really nice.
Microsoft BizTalk is not an intuitive product. It requires many hours of looking through the settings to achieve what you need. Using 3rd party DLLs is a nightmare as you are forced to register them in the GAC of the server and this process is quite cumbersome just to use a DLL.
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.
We did look at Jitterbit dataloader from Salesforce.com. Jitterbit seems like a pretty decent solution if you are doing a lot of uploads into Salesforce.com. However, its not nearly as flexible as Microsoft Biztalk is. Biztalk allows you to create any type of custom solution you wish, whereas Jitterbit is much more limited.
We found that OpenText MBPM held its own quite well against IBM BPM. We ended up choosing OpenText MBPM due to the analytics, complex routing, and the ease of SOA service integration. Furthermore, the ability to quickly develop simple User interfaces make this tool a daily component of our most-used toolbox components.